Re: [PR] HBASE-28240 Phase II: Suspend TRSP and SCP when they can not get regi… [hbase]

2023-12-22 Thread via GitHub


Apache-HBase commented on PR #5559:
URL: https://github.com/apache/hbase/pull/5559#issuecomment-1868232860

   :confetti_ball: **+1 overall**
   
   
   
   
   
   
   | Vote | Subsystem | Runtime | Comment |
   |::|--:|:|:|
   | +0 :ok: |  reexec  |   0m 27s |  Docker mode activated.  |
   ||| _ Prechecks _ |
   | +1 :green_heart: |  dupname  |   0m  1s |  No case conflicting files 
found.  |
   | +1 :green_heart: |  hbaseanti  |   0m  0s |  Patch does not have any 
anti-patterns.  |
   | +1 :green_heart: |  @author  |   0m  0s |  The patch does not contain any 
@author tags.  |
   ||| _ master Compile Tests _ |
   | +1 :green_heart: |  mvninstall  |   3m 19s |  master passed  |
   | +1 :green_heart: |  compile  |   2m 37s |  master passed  |
   | +1 :green_heart: |  checkstyle  |   0m 34s |  master passed  |
   | +1 :green_heart: |  spotless  |   0m 44s |  branch has no errors when 
running spotless:check.  |
   | +1 :green_heart: |  spotbugs  |   1m 34s |  master passed  |
   ||| _ Patch Compile Tests _ |
   | +1 :green_heart: |  mvninstall  |   2m 38s |  the patch passed  |
   | +1 :green_heart: |  compile  |   2m 36s |  the patch passed  |
   | +1 :green_heart: |  javac  |   2m 36s |  the patch passed  |
   | +1 :green_heart: |  checkstyle  |   0m 34s |  the patch passed  |
   | +1 :green_heart: |  whitespace  |   0m  0s |  The patch has no whitespace 
issues.  |
   | +1 :green_heart: |  hadoopcheck  |  10m  9s |  Patch does not cause any 
errors with Hadoop 3.2.4 3.3.6.  |
   | +1 :green_heart: |  spotless  |   0m 42s |  patch has no errors when 
running spotless:check.  |
   | +1 :green_heart: |  spotbugs  |   1m 36s |  the patch passed  |
   ||| _ Other Tests _ |
   | +1 :green_heart: |  asflicense  |   0m  8s |  The patch does not generate 
ASF License warnings.  |
   |  |   |  34m  3s |   |
   
   
   | Subsystem | Report/Notes |
   |--:|:-|
   | Docker | ClientAPI=1.43 ServerAPI=1.43 base: 
https://ci-hbase.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-5559/8/artifact/yetus-general-check/output/Dockerfile
 |
   | GITHUB PR | https://github.com/apache/hbase/pull/5559 |
   | Optional Tests | dupname asflicense javac spotbugs hadoopcheck hbaseanti 
spotless checkstyle compile |
   | uname | Linux a1ea33f9823d 5.4.0-1103-aws #111~18.04.1-Ubuntu SMP Tue May 
23 20:04:10 UTC 2023 x86_64 x86_64 x86_64 GNU/Linux |
   | Build tool | maven |
   | Personality | dev-support/hbase-personality.sh |
   | git revision | master / 5201ae2de2 |
   | Default Java | Eclipse Adoptium-11.0.17+8 |
   | Max. process+thread count | 79 (vs. ulimit of 3) |
   | modules | C: hbase-server U: hbase-server |
   | Console output | 
https://ci-hbase.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-5559/8/console 
|
   | versions | git=2.34.1 maven=3.8.6 spotbugs=4.7.3 |
   | Powered by | Apache Yetus 0.12.0 https://yetus.apache.org |
   
   
   This message was automatically generated.
   
   


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: issues-unsubscr...@hbase.apache.org

For queries about this service, please contact Infrastructure at:
us...@infra.apache.org



[jira] [Commented] (HBASE-28269) Fix broken ruby scripts and clean up logging

2023-12-22 Thread Hudson (Jira)


[ 
https://issues.apache.org/jira/browse/HBASE-28269?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=1779#comment-1779
 ] 

Hudson commented on HBASE-28269:


Results for branch branch-2
[build #951 on 
builds.a.o|https://ci-hbase.apache.org/job/HBase%20Nightly/job/branch-2/951/]: 
(x) *{color:red}-1 overall{color}*

details (if available):

(/) {color:green}+1 general checks{color}
-- For more information [see general 
report|https://ci-hbase.apache.org/job/HBase%20Nightly/job/branch-2/951/General_20Nightly_20Build_20Report/]


(/) {color:green}+1 jdk8 hadoop2 checks{color}
-- For more information [see jdk8 (hadoop2) 
report|https://ci-hbase.apache.org/job/HBase%20Nightly/job/branch-2/951/JDK8_20Nightly_20Build_20Report_20_28Hadoop2_29/]


(x) {color:red}-1 jdk8 hadoop3 checks{color}
-- For more information [see jdk8 (hadoop3) 
report|https://ci-hbase.apache.org/job/HBase%20Nightly/job/branch-2/951/JDK8_20Nightly_20Build_20Report_20_28Hadoop3_29/]


(x) {color:red}-1 jdk11 hadoop3 checks{color}
-- For more information [see jdk11 
report|https://ci-hbase.apache.org/job/HBase%20Nightly/job/branch-2/951/JDK11_20Nightly_20Build_20Report_20_28Hadoop3_29/]


(/) {color:green}+1 source release artifact{color}
-- See build output for details.


(/) {color:green}+1 client integration test{color}


> Fix broken ruby scripts and clean up logging
> 
>
> Key: HBASE-28269
> URL: https://issues.apache.org/jira/browse/HBASE-28269
> Project: HBase
>  Issue Type: Bug
>  Components: jruby
>Affects Versions: 3.0.0-alpha-4
>Reporter: Nihal Jain
>Assignee: Nihal Jain
>Priority: Major
>  Labels: ruby
> Fix For: 2.6.0, 3.0.0-beta-1, 2.5.8
>
>
> Some of the ruby scripts are broken in 3.x as they are referencing 
> non-existent classes, these were deprecated earlier and removed in 3.x:
>  * {{org.apache.hadoop.hbase.client.HBaseAdmin}}
>  * {{org.apache.hadoop.hbase.HTableDescriptor}}
> Following 4 scripts are failing:
> {code:java}
> NameError: missing class name org.apache.hadoop.hbase.client.HBaseAdmin
>   method_missing at org/jruby/javasupport/JavaPackage.java:253
>at region_status.rb:50
> {code}
> {code:java}
> {NameError: missing class name org.apache.hadoop.hbase.HTableDescriptor
>   method_missing at org/jruby/javasupport/JavaPackage.java:253
>at replication/copy_tables_desc.rb:30
> {code}
> {code:java}
> NameError: missing class name org.apache.hadoop.hbase.client.HBaseAdmin
>   method_missing at org/jruby/javasupport/JavaPackage.java:253
>at draining_servers.rb:28
> {code}
> {code:java}
> NameError: missing class name org.apache.hadoop.hbase.client.HBaseAdmin
>   method_missing at org/jruby/javasupport/JavaPackage.java:253
>at shutdown_regionserver.rb:27
> {code}



--
This message was sent by Atlassian Jira
(v8.20.10#820010)


[jira] [Commented] (HBASE-28274) Flaky test: TestFanOutOneBlockAsyncDFSOutput (Part 2)

2023-12-22 Thread Hudson (Jira)


[ 
https://issues.apache.org/jira/browse/HBASE-28274?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=1780#comment-1780
 ] 

Hudson commented on HBASE-28274:


Results for branch branch-2
[build #951 on 
builds.a.o|https://ci-hbase.apache.org/job/HBase%20Nightly/job/branch-2/951/]: 
(x) *{color:red}-1 overall{color}*

details (if available):

(/) {color:green}+1 general checks{color}
-- For more information [see general 
report|https://ci-hbase.apache.org/job/HBase%20Nightly/job/branch-2/951/General_20Nightly_20Build_20Report/]


(/) {color:green}+1 jdk8 hadoop2 checks{color}
-- For more information [see jdk8 (hadoop2) 
report|https://ci-hbase.apache.org/job/HBase%20Nightly/job/branch-2/951/JDK8_20Nightly_20Build_20Report_20_28Hadoop2_29/]


(x) {color:red}-1 jdk8 hadoop3 checks{color}
-- For more information [see jdk8 (hadoop3) 
report|https://ci-hbase.apache.org/job/HBase%20Nightly/job/branch-2/951/JDK8_20Nightly_20Build_20Report_20_28Hadoop3_29/]


(x) {color:red}-1 jdk11 hadoop3 checks{color}
-- For more information [see jdk11 
report|https://ci-hbase.apache.org/job/HBase%20Nightly/job/branch-2/951/JDK11_20Nightly_20Build_20Report_20_28Hadoop3_29/]


(/) {color:green}+1 source release artifact{color}
-- See build output for details.


(/) {color:green}+1 client integration test{color}


> Flaky test: TestFanOutOneBlockAsyncDFSOutput (Part 2)
> -
>
> Key: HBASE-28274
> URL: https://issues.apache.org/jira/browse/HBASE-28274
> Project: HBase
>  Issue Type: Test
>  Components: flakies, integration tests, test
>Reporter: Andor Molnar
>Assignee: Andor Molnar
>Priority: Major
> Fix For: 2.6.0, 2.4.18, 3.0.0-beta-1, 2.5.8
>
>
> The following test sometimes fails for me when running locally with Maven:
> TestFanOutOneBlockAsyncDFSOutput.testRecover()
> I can't really figure out the reason, but it's probably a side effect of the 
> preceding test: testConnectToDatanodeFailed(). This test also restarts one of 
> the datanodes in the MiniDFS cluster just like testRecover() and it somehow 
> causes the failure.
> {noformat}
> java.lang.AssertionError: flush should fail
>   at org.junit.Assert.fail(Assert.java:89)
>   at 
> org.apache.hadoop.hbase.io.asyncfs.TestFanOutOneBlockAsyncDFSOutput.testRecover(TestFanOutOneBlockAsyncDFSOutput.java:154)
>   at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method){noformat}
> The flush() call is testRecover() should fail, because we restart one of the 
> DN in the DFS cluster which is expected to brake connection. It succeeds 
> though if the preceding test already restarted a DN. No matter which DN we 
> restart, even if they're different, the error occurs.
> I also tried to add CLUSTER.waitDatanodeFullyStarted() at the end of 
> testConnectToDatanodeFailed(), looks like it made the tests slightly more 
> stable, but didn't help fully.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)


[jira] [Commented] (HBASE-28224) ClientSideRegionScanner appears not to shutdown MobFileCache

2023-12-22 Thread Hudson (Jira)


[ 
https://issues.apache.org/jira/browse/HBASE-28224?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=1781#comment-1781
 ] 

Hudson commented on HBASE-28224:


Results for branch branch-2
[build #951 on 
builds.a.o|https://ci-hbase.apache.org/job/HBase%20Nightly/job/branch-2/951/]: 
(x) *{color:red}-1 overall{color}*

details (if available):

(/) {color:green}+1 general checks{color}
-- For more information [see general 
report|https://ci-hbase.apache.org/job/HBase%20Nightly/job/branch-2/951/General_20Nightly_20Build_20Report/]


(/) {color:green}+1 jdk8 hadoop2 checks{color}
-- For more information [see jdk8 (hadoop2) 
report|https://ci-hbase.apache.org/job/HBase%20Nightly/job/branch-2/951/JDK8_20Nightly_20Build_20Report_20_28Hadoop2_29/]


(x) {color:red}-1 jdk8 hadoop3 checks{color}
-- For more information [see jdk8 (hadoop3) 
report|https://ci-hbase.apache.org/job/HBase%20Nightly/job/branch-2/951/JDK8_20Nightly_20Build_20Report_20_28Hadoop3_29/]


(x) {color:red}-1 jdk11 hadoop3 checks{color}
-- For more information [see jdk11 
report|https://ci-hbase.apache.org/job/HBase%20Nightly/job/branch-2/951/JDK11_20Nightly_20Build_20Report_20_28Hadoop3_29/]


(/) {color:green}+1 source release artifact{color}
-- See build output for details.


(/) {color:green}+1 client integration test{color}


> ClientSideRegionScanner appears not to shutdown MobFileCache
> 
>
> Key: HBASE-28224
> URL: https://issues.apache.org/jira/browse/HBASE-28224
> Project: HBase
>  Issue Type: Bug
>  Components: Scanners
>Affects Versions: 2.5.5
>Reporter: Mark Hale
>Assignee: Becker Ewing
>Priority: Minor
> Fix For: 2.6.0, 2.4.18, 3.0.0-beta-1, 2.5.8
>
>
> As far as I can tell from the code, and also what I see in jstack, 
> ClientSideRegionScanner doesn't appear to shutdown it's MobFileCache. After 
> doing a lot of scanning of a snapshot, application threads are polluted with 
> a lot of MobFileCache ScheduledThreadPoolExecutors that never seem to get 
> cleaned up.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)


[jira] [Commented] (HBASE-28224) ClientSideRegionScanner appears not to shutdown MobFileCache

2023-12-22 Thread Hudson (Jira)


[ 
https://issues.apache.org/jira/browse/HBASE-28224?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=1772#comment-1772
 ] 

Hudson commented on HBASE-28224:


Results for branch branch-2.4
[build #672 on 
builds.a.o|https://ci-hbase.apache.org/job/HBase%20Nightly/job/branch-2.4/672/]:
 (/) *{color:green}+1 overall{color}*

details (if available):

(/) {color:green}+1 general checks{color}
-- For more information [see general 
report|https://ci-hbase.apache.org/job/HBase%20Nightly/job/branch-2.4/672/General_20Nightly_20Build_20Report/]


(/) {color:green}+1 jdk8 hadoop2 checks{color}
-- For more information [see jdk8 (hadoop2) 
report|https://ci-hbase.apache.org/job/HBase%20Nightly/job/branch-2.4/672/JDK8_20Nightly_20Build_20Report_20_28Hadoop2_29/]


(/) {color:green}+1 jdk8 hadoop3 checks{color}
-- For more information [see jdk8 (hadoop3) 
report|https://ci-hbase.apache.org/job/HBase%20Nightly/job/branch-2.4/672/JDK8_20Nightly_20Build_20Report_20_28Hadoop3_29/]


(/) {color:green}+1 jdk11 hadoop3 checks{color}
-- For more information [see jdk11 
report|https://ci-hbase.apache.org/job/HBase%20Nightly/job/branch-2.4/672/JDK11_20Nightly_20Build_20Report_20_28Hadoop3_29/]


(/) {color:green}+1 source release artifact{color}
-- See build output for details.


(/) {color:green}+1 client integration test{color}


> ClientSideRegionScanner appears not to shutdown MobFileCache
> 
>
> Key: HBASE-28224
> URL: https://issues.apache.org/jira/browse/HBASE-28224
> Project: HBase
>  Issue Type: Bug
>  Components: Scanners
>Affects Versions: 2.5.5
>Reporter: Mark Hale
>Assignee: Becker Ewing
>Priority: Minor
> Fix For: 2.6.0, 2.4.18, 3.0.0-beta-1, 2.5.8
>
>
> As far as I can tell from the code, and also what I see in jstack, 
> ClientSideRegionScanner doesn't appear to shutdown it's MobFileCache. After 
> doing a lot of scanning of a snapshot, application threads are polluted with 
> a lot of MobFileCache ScheduledThreadPoolExecutors that never seem to get 
> cleaned up.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)


[jira] [Commented] (HBASE-28274) Flaky test: TestFanOutOneBlockAsyncDFSOutput (Part 2)

2023-12-22 Thread Hudson (Jira)


[ 
https://issues.apache.org/jira/browse/HBASE-28274?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=1771#comment-1771
 ] 

Hudson commented on HBASE-28274:


Results for branch branch-2.4
[build #672 on 
builds.a.o|https://ci-hbase.apache.org/job/HBase%20Nightly/job/branch-2.4/672/]:
 (/) *{color:green}+1 overall{color}*

details (if available):

(/) {color:green}+1 general checks{color}
-- For more information [see general 
report|https://ci-hbase.apache.org/job/HBase%20Nightly/job/branch-2.4/672/General_20Nightly_20Build_20Report/]


(/) {color:green}+1 jdk8 hadoop2 checks{color}
-- For more information [see jdk8 (hadoop2) 
report|https://ci-hbase.apache.org/job/HBase%20Nightly/job/branch-2.4/672/JDK8_20Nightly_20Build_20Report_20_28Hadoop2_29/]


(/) {color:green}+1 jdk8 hadoop3 checks{color}
-- For more information [see jdk8 (hadoop3) 
report|https://ci-hbase.apache.org/job/HBase%20Nightly/job/branch-2.4/672/JDK8_20Nightly_20Build_20Report_20_28Hadoop3_29/]


(/) {color:green}+1 jdk11 hadoop3 checks{color}
-- For more information [see jdk11 
report|https://ci-hbase.apache.org/job/HBase%20Nightly/job/branch-2.4/672/JDK11_20Nightly_20Build_20Report_20_28Hadoop3_29/]


(/) {color:green}+1 source release artifact{color}
-- See build output for details.


(/) {color:green}+1 client integration test{color}


> Flaky test: TestFanOutOneBlockAsyncDFSOutput (Part 2)
> -
>
> Key: HBASE-28274
> URL: https://issues.apache.org/jira/browse/HBASE-28274
> Project: HBase
>  Issue Type: Test
>  Components: flakies, integration tests, test
>Reporter: Andor Molnar
>Assignee: Andor Molnar
>Priority: Major
> Fix For: 2.6.0, 2.4.18, 3.0.0-beta-1, 2.5.8
>
>
> The following test sometimes fails for me when running locally with Maven:
> TestFanOutOneBlockAsyncDFSOutput.testRecover()
> I can't really figure out the reason, but it's probably a side effect of the 
> preceding test: testConnectToDatanodeFailed(). This test also restarts one of 
> the datanodes in the MiniDFS cluster just like testRecover() and it somehow 
> causes the failure.
> {noformat}
> java.lang.AssertionError: flush should fail
>   at org.junit.Assert.fail(Assert.java:89)
>   at 
> org.apache.hadoop.hbase.io.asyncfs.TestFanOutOneBlockAsyncDFSOutput.testRecover(TestFanOutOneBlockAsyncDFSOutput.java:154)
>   at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method){noformat}
> The flush() call is testRecover() should fail, because we restart one of the 
> DN in the DFS cluster which is expected to brake connection. It succeeds 
> though if the preceding test already restarted a DN. No matter which DN we 
> restart, even if they're different, the error occurs.
> I also tried to add CLUSTER.waitDatanodeFullyStarted() at the end of 
> testConnectToDatanodeFailed(), looks like it made the tests slightly more 
> stable, but didn't help fully.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)


[jira] [Commented] (HBASE-28274) Flaky test: TestFanOutOneBlockAsyncDFSOutput (Part 2)

2023-12-22 Thread Hudson (Jira)


[ 
https://issues.apache.org/jira/browse/HBASE-28274?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17799989#comment-17799989
 ] 

Hudson commented on HBASE-28274:


Results for branch branch-2.6
[build #18 on 
builds.a.o|https://ci-hbase.apache.org/job/HBase%20Nightly/job/branch-2.6/18/]: 
(x) *{color:red}-1 overall{color}*

details (if available):

(/) {color:green}+1 general checks{color}
-- For more information [see general 
report|https://ci-hbase.apache.org/job/HBase%20Nightly/job/branch-2.6/18/General_20Nightly_20Build_20Report/]


(/) {color:green}+1 jdk8 hadoop2 checks{color}
-- For more information [see jdk8 (hadoop2) 
report|https://ci-hbase.apache.org/job/HBase%20Nightly/job/branch-2.6/18/JDK8_20Nightly_20Build_20Report_20_28Hadoop2_29/]


(x) {color:red}-1 jdk8 hadoop3 checks{color}
-- For more information [see jdk8 (hadoop3) 
report|https://ci-hbase.apache.org/job/HBase%20Nightly/job/branch-2.6/18/JDK8_20Nightly_20Build_20Report_20_28Hadoop3_29/]


(x) {color:red}-1 jdk11 hadoop3 checks{color}
-- For more information [see jdk11 
report|https://ci-hbase.apache.org/job/HBase%20Nightly/job/branch-2.6/18/JDK11_20Nightly_20Build_20Report_20_28Hadoop3_29/]


(/) {color:green}+1 source release artifact{color}
-- See build output for details.


(/) {color:green}+1 client integration test{color}


> Flaky test: TestFanOutOneBlockAsyncDFSOutput (Part 2)
> -
>
> Key: HBASE-28274
> URL: https://issues.apache.org/jira/browse/HBASE-28274
> Project: HBase
>  Issue Type: Test
>  Components: flakies, integration tests, test
>Reporter: Andor Molnar
>Assignee: Andor Molnar
>Priority: Major
> Fix For: 2.6.0, 2.4.18, 3.0.0-beta-1, 2.5.8
>
>
> The following test sometimes fails for me when running locally with Maven:
> TestFanOutOneBlockAsyncDFSOutput.testRecover()
> I can't really figure out the reason, but it's probably a side effect of the 
> preceding test: testConnectToDatanodeFailed(). This test also restarts one of 
> the datanodes in the MiniDFS cluster just like testRecover() and it somehow 
> causes the failure.
> {noformat}
> java.lang.AssertionError: flush should fail
>   at org.junit.Assert.fail(Assert.java:89)
>   at 
> org.apache.hadoop.hbase.io.asyncfs.TestFanOutOneBlockAsyncDFSOutput.testRecover(TestFanOutOneBlockAsyncDFSOutput.java:154)
>   at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method){noformat}
> The flush() call is testRecover() should fail, because we restart one of the 
> DN in the DFS cluster which is expected to brake connection. It succeeds 
> though if the preceding test already restarted a DN. No matter which DN we 
> restart, even if they're different, the error occurs.
> I also tried to add CLUSTER.waitDatanodeFullyStarted() at the end of 
> testConnectToDatanodeFailed(), looks like it made the tests slightly more 
> stable, but didn't help fully.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)


[jira] [Commented] (HBASE-28224) ClientSideRegionScanner appears not to shutdown MobFileCache

2023-12-22 Thread Hudson (Jira)


[ 
https://issues.apache.org/jira/browse/HBASE-28224?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=1770#comment-1770
 ] 

Hudson commented on HBASE-28224:


Results for branch branch-2.6
[build #18 on 
builds.a.o|https://ci-hbase.apache.org/job/HBase%20Nightly/job/branch-2.6/18/]: 
(x) *{color:red}-1 overall{color}*

details (if available):

(/) {color:green}+1 general checks{color}
-- For more information [see general 
report|https://ci-hbase.apache.org/job/HBase%20Nightly/job/branch-2.6/18/General_20Nightly_20Build_20Report/]


(/) {color:green}+1 jdk8 hadoop2 checks{color}
-- For more information [see jdk8 (hadoop2) 
report|https://ci-hbase.apache.org/job/HBase%20Nightly/job/branch-2.6/18/JDK8_20Nightly_20Build_20Report_20_28Hadoop2_29/]


(x) {color:red}-1 jdk8 hadoop3 checks{color}
-- For more information [see jdk8 (hadoop3) 
report|https://ci-hbase.apache.org/job/HBase%20Nightly/job/branch-2.6/18/JDK8_20Nightly_20Build_20Report_20_28Hadoop3_29/]


(x) {color:red}-1 jdk11 hadoop3 checks{color}
-- For more information [see jdk11 
report|https://ci-hbase.apache.org/job/HBase%20Nightly/job/branch-2.6/18/JDK11_20Nightly_20Build_20Report_20_28Hadoop3_29/]


(/) {color:green}+1 source release artifact{color}
-- See build output for details.


(/) {color:green}+1 client integration test{color}


> ClientSideRegionScanner appears not to shutdown MobFileCache
> 
>
> Key: HBASE-28224
> URL: https://issues.apache.org/jira/browse/HBASE-28224
> Project: HBase
>  Issue Type: Bug
>  Components: Scanners
>Affects Versions: 2.5.5
>Reporter: Mark Hale
>Assignee: Becker Ewing
>Priority: Minor
> Fix For: 2.6.0, 2.4.18, 3.0.0-beta-1, 2.5.8
>
>
> As far as I can tell from the code, and also what I see in jstack, 
> ClientSideRegionScanner doesn't appear to shutdown it's MobFileCache. After 
> doing a lot of scanning of a snapshot, application threads are polluted with 
> a lot of MobFileCache ScheduledThreadPoolExecutors that never seem to get 
> cleaned up.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)


[jira] [Commented] (HBASE-28269) Fix broken ruby scripts and clean up logging

2023-12-22 Thread Hudson (Jira)


[ 
https://issues.apache.org/jira/browse/HBASE-28269?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17799988#comment-17799988
 ] 

Hudson commented on HBASE-28269:


Results for branch branch-2.6
[build #18 on 
builds.a.o|https://ci-hbase.apache.org/job/HBase%20Nightly/job/branch-2.6/18/]: 
(x) *{color:red}-1 overall{color}*

details (if available):

(/) {color:green}+1 general checks{color}
-- For more information [see general 
report|https://ci-hbase.apache.org/job/HBase%20Nightly/job/branch-2.6/18/General_20Nightly_20Build_20Report/]


(/) {color:green}+1 jdk8 hadoop2 checks{color}
-- For more information [see jdk8 (hadoop2) 
report|https://ci-hbase.apache.org/job/HBase%20Nightly/job/branch-2.6/18/JDK8_20Nightly_20Build_20Report_20_28Hadoop2_29/]


(x) {color:red}-1 jdk8 hadoop3 checks{color}
-- For more information [see jdk8 (hadoop3) 
report|https://ci-hbase.apache.org/job/HBase%20Nightly/job/branch-2.6/18/JDK8_20Nightly_20Build_20Report_20_28Hadoop3_29/]


(x) {color:red}-1 jdk11 hadoop3 checks{color}
-- For more information [see jdk11 
report|https://ci-hbase.apache.org/job/HBase%20Nightly/job/branch-2.6/18/JDK11_20Nightly_20Build_20Report_20_28Hadoop3_29/]


(/) {color:green}+1 source release artifact{color}
-- See build output for details.


(/) {color:green}+1 client integration test{color}


> Fix broken ruby scripts and clean up logging
> 
>
> Key: HBASE-28269
> URL: https://issues.apache.org/jira/browse/HBASE-28269
> Project: HBase
>  Issue Type: Bug
>  Components: jruby
>Affects Versions: 3.0.0-alpha-4
>Reporter: Nihal Jain
>Assignee: Nihal Jain
>Priority: Major
>  Labels: ruby
> Fix For: 2.6.0, 3.0.0-beta-1, 2.5.8
>
>
> Some of the ruby scripts are broken in 3.x as they are referencing 
> non-existent classes, these were deprecated earlier and removed in 3.x:
>  * {{org.apache.hadoop.hbase.client.HBaseAdmin}}
>  * {{org.apache.hadoop.hbase.HTableDescriptor}}
> Following 4 scripts are failing:
> {code:java}
> NameError: missing class name org.apache.hadoop.hbase.client.HBaseAdmin
>   method_missing at org/jruby/javasupport/JavaPackage.java:253
>at region_status.rb:50
> {code}
> {code:java}
> {NameError: missing class name org.apache.hadoop.hbase.HTableDescriptor
>   method_missing at org/jruby/javasupport/JavaPackage.java:253
>at replication/copy_tables_desc.rb:30
> {code}
> {code:java}
> NameError: missing class name org.apache.hadoop.hbase.client.HBaseAdmin
>   method_missing at org/jruby/javasupport/JavaPackage.java:253
>at draining_servers.rb:28
> {code}
> {code:java}
> NameError: missing class name org.apache.hadoop.hbase.client.HBaseAdmin
>   method_missing at org/jruby/javasupport/JavaPackage.java:253
>at shutdown_regionserver.rb:27
> {code}



--
This message was sent by Atlassian Jira
(v8.20.10#820010)


[jira] [Commented] (HBASE-28275) [Flaky test] Fix 'test_list_decommissioned_regionservers' in TestAdminShell2.java

2023-12-22 Thread Hudson (Jira)


[ 
https://issues.apache.org/jira/browse/HBASE-28275?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17799936#comment-17799936
 ] 

Hudson commented on HBASE-28275:


Results for branch branch-2.5
[build #455 on 
builds.a.o|https://ci-hbase.apache.org/job/HBase%20Nightly/job/branch-2.5/455/]:
 (/) *{color:green}+1 overall{color}*

details (if available):

(/) {color:green}+1 general checks{color}
-- For more information [see general 
report|https://ci-hbase.apache.org/job/HBase%20Nightly/job/branch-2.5/455/General_20Nightly_20Build_20Report/]


(/) {color:green}+1 jdk8 hadoop2 checks{color}
-- For more information [see jdk8 (hadoop2) 
report|https://ci-hbase.apache.org/job/HBase%20Nightly/job/branch-2.5/455/JDK8_20Nightly_20Build_20Report_20_28Hadoop2_29/]


(/) {color:green}+1 jdk8 hadoop3 checks{color}
-- For more information [see jdk8 (hadoop3) 
report|https://ci-hbase.apache.org/job/HBase%20Nightly/job/branch-2.5/455/JDK8_20Nightly_20Build_20Report_20_28Hadoop3_29/]


(/) {color:green}+1 jdk11 hadoop3 checks{color}
-- For more information [see jdk11 
report|https://ci-hbase.apache.org/job/HBase%20Nightly/job/branch-2.5/455/JDK11_20Nightly_20Build_20Report_20_28Hadoop3_29/]


(/) {color:green}+1 source release artifact{color}
-- See build output for details.


(/) {color:green}+1 client integration test{color}


> [Flaky test] Fix 'test_list_decommissioned_regionservers' in 
> TestAdminShell2.java
> -
>
> Key: HBASE-28275
> URL: https://issues.apache.org/jira/browse/HBASE-28275
> Project: HBase
>  Issue Type: Test
>  Components: flakies, test
>Reporter: Nihal Jain
>Assignee: Nihal Jain
>Priority: Minor
> Fix For: 2.6.0, 2.4.18, 3.0.0-beta-1, 2.5.8
>
>
> See flaky board: 
> [https://nightlies.apache.org/hbase/HBase-Find-Flaky-Tests/master/1345/output/dashboard.html]
> Failed : 
> [14675|https://ci-hbase.apache.org//job/HBase-Flaky-Tests/job/master/14675]  
> [14676|https://ci-hbase.apache.org//job/HBase-Flaky-Tests/job/master/14676]  
> [14677|https://ci-hbase.apache.org//job/HBase-Flaky-Tests/job/master/14677]  
> [14678|https://ci-hbase.apache.org//job/HBase-Flaky-Tests/job/master/14678]  
> [14679|https://ci-hbase.apache.org//job/HBase-Flaky-Tests/job/master/14679]  
> [14680|https://ci-hbase.apache.org//job/HBase-Flaky-Tests/job/master/14680]  
> [14681|https://ci-hbase.apache.org//job/HBase-Flaky-Tests/job/master/14681]  
> [14682|https://ci-hbase.apache.org//job/HBase-Flaky-Tests/job/master/14682]  
> [14683|https://ci-hbase.apache.org//job/HBase-Flaky-Tests/job/master/14683]  
> [14684|https://ci-hbase.apache.org//job/HBase-Flaky-Tests/job/master/14684]  
> [14685|https://ci-hbase.apache.org//job/HBase-Flaky-Tests/job/master/14685]  
> [14686|https://ci-hbase.apache.org//job/HBase-Flaky-Tests/job/master/14686]  
> [14687|https://ci-hbase.apache.org//job/HBase-Flaky-Tests/job/master/14687] 



--
This message was sent by Atlassian Jira
(v8.20.10#820010)


[jira] [Commented] (HBASE-28274) Flaky test: TestFanOutOneBlockAsyncDFSOutput (Part 2)

2023-12-22 Thread Hudson (Jira)


[ 
https://issues.apache.org/jira/browse/HBASE-28274?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17799938#comment-17799938
 ] 

Hudson commented on HBASE-28274:


Results for branch branch-2.5
[build #455 on 
builds.a.o|https://ci-hbase.apache.org/job/HBase%20Nightly/job/branch-2.5/455/]:
 (/) *{color:green}+1 overall{color}*

details (if available):

(/) {color:green}+1 general checks{color}
-- For more information [see general 
report|https://ci-hbase.apache.org/job/HBase%20Nightly/job/branch-2.5/455/General_20Nightly_20Build_20Report/]


(/) {color:green}+1 jdk8 hadoop2 checks{color}
-- For more information [see jdk8 (hadoop2) 
report|https://ci-hbase.apache.org/job/HBase%20Nightly/job/branch-2.5/455/JDK8_20Nightly_20Build_20Report_20_28Hadoop2_29/]


(/) {color:green}+1 jdk8 hadoop3 checks{color}
-- For more information [see jdk8 (hadoop3) 
report|https://ci-hbase.apache.org/job/HBase%20Nightly/job/branch-2.5/455/JDK8_20Nightly_20Build_20Report_20_28Hadoop3_29/]


(/) {color:green}+1 jdk11 hadoop3 checks{color}
-- For more information [see jdk11 
report|https://ci-hbase.apache.org/job/HBase%20Nightly/job/branch-2.5/455/JDK11_20Nightly_20Build_20Report_20_28Hadoop3_29/]


(/) {color:green}+1 source release artifact{color}
-- See build output for details.


(/) {color:green}+1 client integration test{color}


> Flaky test: TestFanOutOneBlockAsyncDFSOutput (Part 2)
> -
>
> Key: HBASE-28274
> URL: https://issues.apache.org/jira/browse/HBASE-28274
> Project: HBase
>  Issue Type: Test
>  Components: flakies, integration tests, test
>Reporter: Andor Molnar
>Assignee: Andor Molnar
>Priority: Major
> Fix For: 2.6.0, 2.4.18, 3.0.0-beta-1, 2.5.8
>
>
> The following test sometimes fails for me when running locally with Maven:
> TestFanOutOneBlockAsyncDFSOutput.testRecover()
> I can't really figure out the reason, but it's probably a side effect of the 
> preceding test: testConnectToDatanodeFailed(). This test also restarts one of 
> the datanodes in the MiniDFS cluster just like testRecover() and it somehow 
> causes the failure.
> {noformat}
> java.lang.AssertionError: flush should fail
>   at org.junit.Assert.fail(Assert.java:89)
>   at 
> org.apache.hadoop.hbase.io.asyncfs.TestFanOutOneBlockAsyncDFSOutput.testRecover(TestFanOutOneBlockAsyncDFSOutput.java:154)
>   at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method){noformat}
> The flush() call is testRecover() should fail, because we restart one of the 
> DN in the DFS cluster which is expected to brake connection. It succeeds 
> though if the preceding test already restarted a DN. No matter which DN we 
> restart, even if they're different, the error occurs.
> I also tried to add CLUSTER.waitDatanodeFullyStarted() at the end of 
> testConnectToDatanodeFailed(), looks like it made the tests slightly more 
> stable, but didn't help fully.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)


[jira] [Commented] (HBASE-28269) Fix broken ruby scripts and clean up logging

2023-12-22 Thread Hudson (Jira)


[ 
https://issues.apache.org/jira/browse/HBASE-28269?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17799937#comment-17799937
 ] 

Hudson commented on HBASE-28269:


Results for branch branch-2.5
[build #455 on 
builds.a.o|https://ci-hbase.apache.org/job/HBase%20Nightly/job/branch-2.5/455/]:
 (/) *{color:green}+1 overall{color}*

details (if available):

(/) {color:green}+1 general checks{color}
-- For more information [see general 
report|https://ci-hbase.apache.org/job/HBase%20Nightly/job/branch-2.5/455/General_20Nightly_20Build_20Report/]


(/) {color:green}+1 jdk8 hadoop2 checks{color}
-- For more information [see jdk8 (hadoop2) 
report|https://ci-hbase.apache.org/job/HBase%20Nightly/job/branch-2.5/455/JDK8_20Nightly_20Build_20Report_20_28Hadoop2_29/]


(/) {color:green}+1 jdk8 hadoop3 checks{color}
-- For more information [see jdk8 (hadoop3) 
report|https://ci-hbase.apache.org/job/HBase%20Nightly/job/branch-2.5/455/JDK8_20Nightly_20Build_20Report_20_28Hadoop3_29/]


(/) {color:green}+1 jdk11 hadoop3 checks{color}
-- For more information [see jdk11 
report|https://ci-hbase.apache.org/job/HBase%20Nightly/job/branch-2.5/455/JDK11_20Nightly_20Build_20Report_20_28Hadoop3_29/]


(/) {color:green}+1 source release artifact{color}
-- See build output for details.


(/) {color:green}+1 client integration test{color}


> Fix broken ruby scripts and clean up logging
> 
>
> Key: HBASE-28269
> URL: https://issues.apache.org/jira/browse/HBASE-28269
> Project: HBase
>  Issue Type: Bug
>  Components: jruby
>Affects Versions: 3.0.0-alpha-4
>Reporter: Nihal Jain
>Assignee: Nihal Jain
>Priority: Major
>  Labels: ruby
> Fix For: 2.6.0, 3.0.0-beta-1, 2.5.8
>
>
> Some of the ruby scripts are broken in 3.x as they are referencing 
> non-existent classes, these were deprecated earlier and removed in 3.x:
>  * {{org.apache.hadoop.hbase.client.HBaseAdmin}}
>  * {{org.apache.hadoop.hbase.HTableDescriptor}}
> Following 4 scripts are failing:
> {code:java}
> NameError: missing class name org.apache.hadoop.hbase.client.HBaseAdmin
>   method_missing at org/jruby/javasupport/JavaPackage.java:253
>at region_status.rb:50
> {code}
> {code:java}
> {NameError: missing class name org.apache.hadoop.hbase.HTableDescriptor
>   method_missing at org/jruby/javasupport/JavaPackage.java:253
>at replication/copy_tables_desc.rb:30
> {code}
> {code:java}
> NameError: missing class name org.apache.hadoop.hbase.client.HBaseAdmin
>   method_missing at org/jruby/javasupport/JavaPackage.java:253
>at draining_servers.rb:28
> {code}
> {code:java}
> NameError: missing class name org.apache.hadoop.hbase.client.HBaseAdmin
>   method_missing at org/jruby/javasupport/JavaPackage.java:253
>at shutdown_regionserver.rb:27
> {code}



--
This message was sent by Atlassian Jira
(v8.20.10#820010)


[jira] [Commented] (HBASE-28269) Fix broken ruby scripts and clean up logging

2023-12-22 Thread Hudson (Jira)


[ 
https://issues.apache.org/jira/browse/HBASE-28269?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17799935#comment-17799935
 ] 

Hudson commented on HBASE-28269:


Results for branch branch-3
[build #109 on 
builds.a.o|https://ci-hbase.apache.org/job/HBase%20Nightly/job/branch-3/109/]: 
(/) *{color:green}+1 overall{color}*

details (if available):

(/) {color:green}+1 general checks{color}
-- For more information [see general 
report|https://ci-hbase.apache.org/job/HBase%20Nightly/job/branch-3/109/General_20Nightly_20Build_20Report/]




(/) {color:green}+1 jdk8 hadoop3 checks{color}
-- For more information [see jdk8 (hadoop3) 
report|https://ci-hbase.apache.org/job/HBase%20Nightly/job/branch-3/109/JDK8_20Nightly_20Build_20Report_20_28Hadoop3_29/]


(/) {color:green}+1 jdk11 hadoop3 checks{color}
-- For more information [see jdk11 
report|https://ci-hbase.apache.org/job/HBase%20Nightly/job/branch-3/109/JDK11_20Nightly_20Build_20Report_20_28Hadoop3_29/]


(/) {color:green}+1 source release artifact{color}
-- See build output for details.


(/) {color:green}+1 client integration test{color}


> Fix broken ruby scripts and clean up logging
> 
>
> Key: HBASE-28269
> URL: https://issues.apache.org/jira/browse/HBASE-28269
> Project: HBase
>  Issue Type: Bug
>  Components: jruby
>Affects Versions: 3.0.0-alpha-4
>Reporter: Nihal Jain
>Assignee: Nihal Jain
>Priority: Major
>  Labels: ruby
> Fix For: 2.6.0, 3.0.0-beta-1, 2.5.8
>
>
> Some of the ruby scripts are broken in 3.x as they are referencing 
> non-existent classes, these were deprecated earlier and removed in 3.x:
>  * {{org.apache.hadoop.hbase.client.HBaseAdmin}}
>  * {{org.apache.hadoop.hbase.HTableDescriptor}}
> Following 4 scripts are failing:
> {code:java}
> NameError: missing class name org.apache.hadoop.hbase.client.HBaseAdmin
>   method_missing at org/jruby/javasupport/JavaPackage.java:253
>at region_status.rb:50
> {code}
> {code:java}
> {NameError: missing class name org.apache.hadoop.hbase.HTableDescriptor
>   method_missing at org/jruby/javasupport/JavaPackage.java:253
>at replication/copy_tables_desc.rb:30
> {code}
> {code:java}
> NameError: missing class name org.apache.hadoop.hbase.client.HBaseAdmin
>   method_missing at org/jruby/javasupport/JavaPackage.java:253
>at draining_servers.rb:28
> {code}
> {code:java}
> NameError: missing class name org.apache.hadoop.hbase.client.HBaseAdmin
>   method_missing at org/jruby/javasupport/JavaPackage.java:253
>at shutdown_regionserver.rb:27
> {code}



--
This message was sent by Atlassian Jira
(v8.20.10#820010)


[jira] [Commented] (HBASE-28275) [Flaky test] Fix 'test_list_decommissioned_regionservers' in TestAdminShell2.java

2023-12-22 Thread Hudson (Jira)


[ 
https://issues.apache.org/jira/browse/HBASE-28275?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17799934#comment-17799934
 ] 

Hudson commented on HBASE-28275:


Results for branch branch-3
[build #109 on 
builds.a.o|https://ci-hbase.apache.org/job/HBase%20Nightly/job/branch-3/109/]: 
(/) *{color:green}+1 overall{color}*

details (if available):

(/) {color:green}+1 general checks{color}
-- For more information [see general 
report|https://ci-hbase.apache.org/job/HBase%20Nightly/job/branch-3/109/General_20Nightly_20Build_20Report/]




(/) {color:green}+1 jdk8 hadoop3 checks{color}
-- For more information [see jdk8 (hadoop3) 
report|https://ci-hbase.apache.org/job/HBase%20Nightly/job/branch-3/109/JDK8_20Nightly_20Build_20Report_20_28Hadoop3_29/]


(/) {color:green}+1 jdk11 hadoop3 checks{color}
-- For more information [see jdk11 
report|https://ci-hbase.apache.org/job/HBase%20Nightly/job/branch-3/109/JDK11_20Nightly_20Build_20Report_20_28Hadoop3_29/]


(/) {color:green}+1 source release artifact{color}
-- See build output for details.


(/) {color:green}+1 client integration test{color}


> [Flaky test] Fix 'test_list_decommissioned_regionservers' in 
> TestAdminShell2.java
> -
>
> Key: HBASE-28275
> URL: https://issues.apache.org/jira/browse/HBASE-28275
> Project: HBase
>  Issue Type: Test
>  Components: flakies, test
>Reporter: Nihal Jain
>Assignee: Nihal Jain
>Priority: Minor
> Fix For: 2.6.0, 2.4.18, 3.0.0-beta-1, 2.5.8
>
>
> See flaky board: 
> [https://nightlies.apache.org/hbase/HBase-Find-Flaky-Tests/master/1345/output/dashboard.html]
> Failed : 
> [14675|https://ci-hbase.apache.org//job/HBase-Flaky-Tests/job/master/14675]  
> [14676|https://ci-hbase.apache.org//job/HBase-Flaky-Tests/job/master/14676]  
> [14677|https://ci-hbase.apache.org//job/HBase-Flaky-Tests/job/master/14677]  
> [14678|https://ci-hbase.apache.org//job/HBase-Flaky-Tests/job/master/14678]  
> [14679|https://ci-hbase.apache.org//job/HBase-Flaky-Tests/job/master/14679]  
> [14680|https://ci-hbase.apache.org//job/HBase-Flaky-Tests/job/master/14680]  
> [14681|https://ci-hbase.apache.org//job/HBase-Flaky-Tests/job/master/14681]  
> [14682|https://ci-hbase.apache.org//job/HBase-Flaky-Tests/job/master/14682]  
> [14683|https://ci-hbase.apache.org//job/HBase-Flaky-Tests/job/master/14683]  
> [14684|https://ci-hbase.apache.org//job/HBase-Flaky-Tests/job/master/14684]  
> [14685|https://ci-hbase.apache.org//job/HBase-Flaky-Tests/job/master/14685]  
> [14686|https://ci-hbase.apache.org//job/HBase-Flaky-Tests/job/master/14686]  
> [14687|https://ci-hbase.apache.org//job/HBase-Flaky-Tests/job/master/14687] 



--
This message was sent by Atlassian Jira
(v8.20.10#820010)


[jira] [Commented] (HBASE-28275) [Flaky test] Fix 'test_list_decommissioned_regionservers' in TestAdminShell2.java

2023-12-22 Thread Hudson (Jira)


[ 
https://issues.apache.org/jira/browse/HBASE-28275?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17799925#comment-17799925
 ] 

Hudson commented on HBASE-28275:


Results for branch master
[build #970 on 
builds.a.o|https://ci-hbase.apache.org/job/HBase%20Nightly/job/master/970/]: 
(/) *{color:green}+1 overall{color}*

details (if available):

(/) {color:green}+1 general checks{color}
-- For more information [see general 
report|https://ci-hbase.apache.org/job/HBase%20Nightly/job/master/970/General_20Nightly_20Build_20Report/]




(/) {color:green}+1 jdk8 hadoop3 checks{color}
-- For more information [see jdk8 (hadoop3) 
report|https://ci-hbase.apache.org/job/HBase%20Nightly/job/master/970/JDK8_20Nightly_20Build_20Report_20_28Hadoop3_29/]


(/) {color:green}+1 jdk11 hadoop3 checks{color}
-- For more information [see jdk11 
report|https://ci-hbase.apache.org/job/HBase%20Nightly/job/master/970/JDK11_20Nightly_20Build_20Report_20_28Hadoop3_29/]


(/) {color:green}+1 source release artifact{color}
-- See build output for details.


(/) {color:green}+1 client integration test{color}


> [Flaky test] Fix 'test_list_decommissioned_regionservers' in 
> TestAdminShell2.java
> -
>
> Key: HBASE-28275
> URL: https://issues.apache.org/jira/browse/HBASE-28275
> Project: HBase
>  Issue Type: Test
>  Components: flakies, test
>Reporter: Nihal Jain
>Assignee: Nihal Jain
>Priority: Minor
> Fix For: 2.6.0, 2.4.18, 3.0.0-beta-1, 2.5.8
>
>
> See flaky board: 
> [https://nightlies.apache.org/hbase/HBase-Find-Flaky-Tests/master/1345/output/dashboard.html]
> Failed : 
> [14675|https://ci-hbase.apache.org//job/HBase-Flaky-Tests/job/master/14675]  
> [14676|https://ci-hbase.apache.org//job/HBase-Flaky-Tests/job/master/14676]  
> [14677|https://ci-hbase.apache.org//job/HBase-Flaky-Tests/job/master/14677]  
> [14678|https://ci-hbase.apache.org//job/HBase-Flaky-Tests/job/master/14678]  
> [14679|https://ci-hbase.apache.org//job/HBase-Flaky-Tests/job/master/14679]  
> [14680|https://ci-hbase.apache.org//job/HBase-Flaky-Tests/job/master/14680]  
> [14681|https://ci-hbase.apache.org//job/HBase-Flaky-Tests/job/master/14681]  
> [14682|https://ci-hbase.apache.org//job/HBase-Flaky-Tests/job/master/14682]  
> [14683|https://ci-hbase.apache.org//job/HBase-Flaky-Tests/job/master/14683]  
> [14684|https://ci-hbase.apache.org//job/HBase-Flaky-Tests/job/master/14684]  
> [14685|https://ci-hbase.apache.org//job/HBase-Flaky-Tests/job/master/14685]  
> [14686|https://ci-hbase.apache.org//job/HBase-Flaky-Tests/job/master/14686]  
> [14687|https://ci-hbase.apache.org//job/HBase-Flaky-Tests/job/master/14687] 



--
This message was sent by Atlassian Jira
(v8.20.10#820010)


[jira] [Commented] (HBASE-28269) Fix broken ruby scripts and clean up logging

2023-12-22 Thread Hudson (Jira)


[ 
https://issues.apache.org/jira/browse/HBASE-28269?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17799926#comment-17799926
 ] 

Hudson commented on HBASE-28269:


Results for branch master
[build #970 on 
builds.a.o|https://ci-hbase.apache.org/job/HBase%20Nightly/job/master/970/]: 
(/) *{color:green}+1 overall{color}*

details (if available):

(/) {color:green}+1 general checks{color}
-- For more information [see general 
report|https://ci-hbase.apache.org/job/HBase%20Nightly/job/master/970/General_20Nightly_20Build_20Report/]




(/) {color:green}+1 jdk8 hadoop3 checks{color}
-- For more information [see jdk8 (hadoop3) 
report|https://ci-hbase.apache.org/job/HBase%20Nightly/job/master/970/JDK8_20Nightly_20Build_20Report_20_28Hadoop3_29/]


(/) {color:green}+1 jdk11 hadoop3 checks{color}
-- For more information [see jdk11 
report|https://ci-hbase.apache.org/job/HBase%20Nightly/job/master/970/JDK11_20Nightly_20Build_20Report_20_28Hadoop3_29/]


(/) {color:green}+1 source release artifact{color}
-- See build output for details.


(/) {color:green}+1 client integration test{color}


> Fix broken ruby scripts and clean up logging
> 
>
> Key: HBASE-28269
> URL: https://issues.apache.org/jira/browse/HBASE-28269
> Project: HBase
>  Issue Type: Bug
>  Components: jruby
>Affects Versions: 3.0.0-alpha-4
>Reporter: Nihal Jain
>Assignee: Nihal Jain
>Priority: Major
>  Labels: ruby
> Fix For: 2.6.0, 3.0.0-beta-1, 2.5.8
>
>
> Some of the ruby scripts are broken in 3.x as they are referencing 
> non-existent classes, these were deprecated earlier and removed in 3.x:
>  * {{org.apache.hadoop.hbase.client.HBaseAdmin}}
>  * {{org.apache.hadoop.hbase.HTableDescriptor}}
> Following 4 scripts are failing:
> {code:java}
> NameError: missing class name org.apache.hadoop.hbase.client.HBaseAdmin
>   method_missing at org/jruby/javasupport/JavaPackage.java:253
>at region_status.rb:50
> {code}
> {code:java}
> {NameError: missing class name org.apache.hadoop.hbase.HTableDescriptor
>   method_missing at org/jruby/javasupport/JavaPackage.java:253
>at replication/copy_tables_desc.rb:30
> {code}
> {code:java}
> NameError: missing class name org.apache.hadoop.hbase.client.HBaseAdmin
>   method_missing at org/jruby/javasupport/JavaPackage.java:253
>at draining_servers.rb:28
> {code}
> {code:java}
> NameError: missing class name org.apache.hadoop.hbase.client.HBaseAdmin
>   method_missing at org/jruby/javasupport/JavaPackage.java:253
>at shutdown_regionserver.rb:27
> {code}



--
This message was sent by Atlassian Jira
(v8.20.10#820010)


[jira] [Updated] (HBASE-28279) Bump up jetty-server, jetty-http to 9.4.53.v20231009

2023-12-22 Thread Rajeshbabu Chintaguntla (Jira)


 [ 
https://issues.apache.org/jira/browse/HBASE-28279?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Rajeshbabu Chintaguntla updated HBASE-28279:

Summary: Bump up jetty-server, jetty-http to 9.4.53.v20231009  (was: Bump 
up jetty-server to 9.4.53.v20231009)

> Bump up jetty-server, jetty-http to 9.4.53.v20231009
> 
>
> Key: HBASE-28279
> URL: https://issues.apache.org/jira/browse/HBASE-28279
> Project: HBase
>  Issue Type: Bug
>  Components: thirdparty
>Reporter: Rajeshbabu Chintaguntla
>Assignee: Rajeshbabu Chintaguntla
>Priority: Major
>
> Bump up jetty-server to 9.4.53.v20231009 to avoid CVE CVE-2023-36478



--
This message was sent by Atlassian Jira
(v8.20.10#820010)


[jira] [Created] (HBASE-28279) Bump up jetty-server to 9.4.53.v20231009

2023-12-22 Thread Rajeshbabu Chintaguntla (Jira)
Rajeshbabu Chintaguntla created HBASE-28279:
---

 Summary: Bump up jetty-server to 9.4.53.v20231009
 Key: HBASE-28279
 URL: https://issues.apache.org/jira/browse/HBASE-28279
 Project: HBase
  Issue Type: Bug
  Components: thirdparty
Reporter: Rajeshbabu Chintaguntla
Assignee: Rajeshbabu Chintaguntla


Bump up jetty-server to 9.4.53.v20231009 to avoid CVE CVE-2023-36478



--
This message was sent by Atlassian Jira
(v8.20.10#820010)


[jira] [Created] (HBASE-28278) FileSystem.getFileStatus can not get the correct file length for files which are being written

2023-12-22 Thread Duo Zhang (Jira)
Duo Zhang created HBASE-28278:
-

 Summary: FileSystem.getFileStatus can not get the correct file 
length for files which are being written
 Key: HBASE-28278
 URL: https://issues.apache.org/jira/browse/HBASE-28278
 Project: HBase
  Issue Type: Bug
  Components: Replication
Reporter: Duo Zhang


When reading from a opening WAL file in replication, we will use 
FileSystem.getFileStatus to get the file length and then use it to calculate 
the trailer's position. But if a file is being written, you can not get the 
correct length from namenode, you could even get a 0 if the file has only one 
block(for most WAL files).

This will not lead to real data loss as we do not rely on the file length to 
determine whether we should read the file, but since it will mess up the 
trailer's position, it may lead to incorrect metrics, like un cleanly closed 
wal files, and fail some UTs, and also output some confusing logs.

We should find a way to make it better.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)


[jira] [Resolved] (HBASE-28224) ClientSideRegionScanner appears not to shutdown MobFileCache

2023-12-22 Thread Duo Zhang (Jira)


 [ 
https://issues.apache.org/jira/browse/HBASE-28224?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Duo Zhang resolved HBASE-28224.
---
Fix Version/s: 2.6.0
   2.4.18
   3.0.0-beta-1
   2.5.8
 Hadoop Flags: Reviewed
   Resolution: Fixed

Pushed to all active branches.

Thanks [~bewing] for contributing!

> ClientSideRegionScanner appears not to shutdown MobFileCache
> 
>
> Key: HBASE-28224
> URL: https://issues.apache.org/jira/browse/HBASE-28224
> Project: HBase
>  Issue Type: Bug
>  Components: Scanners
>Affects Versions: 2.5.5
>Reporter: Mark Hale
>Assignee: Becker Ewing
>Priority: Minor
> Fix For: 2.6.0, 2.4.18, 3.0.0-beta-1, 2.5.8
>
>
> As far as I can tell from the code, and also what I see in jstack, 
> ClientSideRegionScanner doesn't appear to shutdown it's MobFileCache. After 
> doing a lot of scanning of a snapshot, application threads are polluted with 
> a lot of MobFileCache ScheduledThreadPoolExecutors that never seem to get 
> cleaned up.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)


Re: [PR] HBASE-28224 ClientSideRegionScanner appears not to shutdown MobFileCache [hbase]

2023-12-22 Thread via GitHub


Apache9 merged PR #5578:
URL: https://github.com/apache/hbase/pull/5578


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: issues-unsubscr...@hbase.apache.org

For queries about this service, please contact Infrastructure at:
us...@infra.apache.org



Re: [PR] HBASE-28224 ClientSideRegionScanner appears not to shutdown MobFileCache [hbase]

2023-12-22 Thread via GitHub


Apache9 commented on PR #5578:
URL: https://github.com/apache/hbase/pull/5578#issuecomment-1867661043

   > @Apache9 any chance you have an idea on when this PR will be merged? Not 
urgent, I just don't want this PR to get lost
   
   Sorry, forgot this one.
   
   Let me merge and cherry-pick to other branches.


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: issues-unsubscr...@hbase.apache.org

For queries about this service, please contact Infrastructure at:
us...@infra.apache.org



[jira] [Commented] (HBASE-28276) Change zookeeper.zone.parent and restart hbase cluster, hmaster will be stuck waiting for hbase:meta online

2023-12-22 Thread terrytlu (Jira)


[ 
https://issues.apache.org/jira/browse/HBASE-28276?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17799767#comment-17799767
 ] 

terrytlu commented on HBASE-28276:
--

hi  [~zhangduo], could you please help and see if there are some suggestions 
for this issue or the attached patch ?  seems you are familiar with the logic 
here

> Change zookeeper.zone.parent and restart hbase cluster, hmaster will be stuck 
> waiting for hbase:meta online 
> 
>
> Key: HBASE-28276
> URL: https://issues.apache.org/jira/browse/HBASE-28276
> Project: HBase
>  Issue Type: Bug
>Affects Versions: 2.2.7
>Reporter: terrytlu
>Priority: Major
>     Attachments: HBASE-28276-20231222-2.2.7.patch, 
> image-2023-12-21-18-34-33-586.png, image-2023-12-21-18-36-36-282.png, 
> image-2023-12-21-18-41-55-819.png, image-2023-12-21-18-42-47-764.png
>
>
> In our scenario, we usually change zookeeper.zone.parent=/hbase-unsecure to 
> /hbase-secure when enabling kerberos authentication. after restart the hbase 
> cluster, we will almost certainly be stuck on master initalization. 
> we can see hmaster stuck in waiting for the InitMetaProcedure finish
> !image-2023-12-21-18-34-33-586.png|width=1221,height=220!
> In the regionserver log, we find the regionserver receive duplicate open meta 
> region request, and it does not respond to hmaster the second time. so the 
> hmaster wait the procedure in a long time.
> !image-2023-12-21-18-36-36-282.png|width=1527,height=163!
> We suspect that both the servercrash procedure and hmaster startup trigger 
> the procedure for the online meta table.
> !image-2023-12-21-18-41-55-819.png|width=714,height=331!
>  
> hmaster log this, so it will send a assign meta request to regionserver
> !image-2023-12-21-18-42-47-764.png|width=720,height=30!
>  
> So any suggestions to avoid this?
>  



--
This message was sent by Atlassian Jira
(v8.20.10#820010)


[jira] [Commented] (HBASE-28276) Change zookeeper.zone.parent and restart hbase cluster, hmaster will be stuck waiting for hbase:meta online

2023-12-22 Thread terrytlu (Jira)


[ 
https://issues.apache.org/jira/browse/HBASE-28276?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17799761#comment-17799761
 ] 

terrytlu commented on HBASE-28276:
--

I found the bootstrap logic has changed in 
https://issues.apache.org/jira/browse/HBASE-24471 , and fixed in hbase 2.4.0

upload a patch that has a protection logic to avoid the issue for version 
before 2.4.0

> Change zookeeper.zone.parent and restart hbase cluster, hmaster will be stuck 
> waiting for hbase:meta online 
> 
>
> Key: HBASE-28276
> URL: https://issues.apache.org/jira/browse/HBASE-28276
> Project: HBase
>  Issue Type: Bug
>Affects Versions: 2.2.7
>Reporter: terrytlu
>Priority: Major
>     Attachments: HBASE-28276-20231222-2.2.7.patch, 
> image-2023-12-21-18-34-33-586.png, image-2023-12-21-18-36-36-282.png, 
> image-2023-12-21-18-41-55-819.png, image-2023-12-21-18-42-47-764.png
>
>
> In our scenario, we usually change zookeeper.zone.parent=/hbase-unsecure to 
> /hbase-secure when enabling kerberos authentication. after restart the hbase 
> cluster, we will almost certainly be stuck on master initalization. 
> we can see hmaster stuck in waiting for the InitMetaProcedure finish
> !image-2023-12-21-18-34-33-586.png|width=1221,height=220!
> In the regionserver log, we find the regionserver receive duplicate open meta 
> region request, and it does not respond to hmaster the second time. so the 
> hmaster wait the procedure in a long time.
> !image-2023-12-21-18-36-36-282.png|width=1527,height=163!
> We suspect that both the servercrash procedure and hmaster startup trigger 
> the procedure for the online meta table.
> !image-2023-12-21-18-41-55-819.png|width=714,height=331!
>  
> hmaster log this, so it will send a assign meta request to regionserver
> !image-2023-12-21-18-42-47-764.png|width=720,height=30!
>  
> So any suggestions to avoid this?
>  



--
This message was sent by Atlassian Jira
(v8.20.10#820010)


[jira] [Updated] (HBASE-28276) Change zookeeper.zone.parent and restart hbase cluster, hmaster will be stuck waiting for hbase:meta online

2023-12-22 Thread terrytlu (Jira)


 [ 
https://issues.apache.org/jira/browse/HBASE-28276?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

terrytlu updated HBASE-28276:
-
Attachment: HBASE-28276-20231222-2.2.7.patch

> Change zookeeper.zone.parent and restart hbase cluster, hmaster will be stuck 
> waiting for hbase:meta online 
> 
>
> Key: HBASE-28276
> URL: https://issues.apache.org/jira/browse/HBASE-28276
> Project: HBase
>  Issue Type: Bug
>Affects Versions: 2.2.7
>Reporter: terrytlu
>Priority: Major
>     Attachments: HBASE-28276-20231222-2.2.7.patch, 
> image-2023-12-21-18-34-33-586.png, image-2023-12-21-18-36-36-282.png, 
> image-2023-12-21-18-41-55-819.png, image-2023-12-21-18-42-47-764.png
>
>
> In our scenario, we usually change zookeeper.zone.parent=/hbase-unsecure to 
> /hbase-secure when enabling kerberos authentication. after restart the hbase 
> cluster, we will almost certainly be stuck on master initalization. 
> we can see hmaster stuck in waiting for the InitMetaProcedure finish
> !image-2023-12-21-18-34-33-586.png|width=1221,height=220!
> In the regionserver log, we find the regionserver receive duplicate open meta 
> region request, and it does not respond to hmaster the second time. so the 
> hmaster wait the procedure in a long time.
> !image-2023-12-21-18-36-36-282.png|width=1527,height=163!
> We suspect that both the servercrash procedure and hmaster startup trigger 
> the procedure for the online meta table.
> !image-2023-12-21-18-41-55-819.png|width=714,height=331!
>  
> hmaster log this, so it will send a assign meta request to regionserver
> !image-2023-12-21-18-42-47-764.png|width=720,height=30!
>  
> So any suggestions to avoid this?
>  



--
This message was sent by Atlassian Jira
(v8.20.10#820010)


Re: [PR] HBASE-28249 Bump jruby to 9.3.13.0 and related joni and jcodings to 2… [hbase]

2023-12-22 Thread via GitHub


NihalJain commented on PR #5568:
URL: https://github.com/apache/hbase/pull/5568#issuecomment-1867456502

   Will merge this to master, branch-3, branch-2 and branch-2.6 tonight, please 
let me know if any concerns.


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: issues-unsubscr...@hbase.apache.org

For queries about this service, please contact Infrastructure at:
us...@infra.apache.org



[jira] [Commented] (HBASE-28275) [Flaky test] Fix 'test_list_decommissioned_regionservers' in TestAdminShell2.java

2023-12-22 Thread Nihal Jain (Jira)


[ 
https://issues.apache.org/jira/browse/HBASE-28275?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17799737#comment-17799737
 ] 

Nihal Jain commented on HBASE-28275:


Tests are not failing any more: 
[https://nightlies.apache.org/hbase/HBase-Find-Flaky-Tests/master/1348/output/dashboard.html]
Succeeded : 
[14716|https://ci-hbase.apache.org//job/HBase-Flaky-Tests/job/master/14716]  
[14717|https://ci-hbase.apache.org//job/HBase-Flaky-Tests/job/master/14717]  
[14718|https://ci-hbase.apache.org//job/HBase-Flaky-Tests/job/master/14718]  
[14719|https://ci-hbase.apache.org//job/HBase-Flaky-Tests/job/master/14719]  
[14720|https://ci-hbase.apache.org//job/HBase-Flaky-Tests/job/master/14720]  
[14721|https://ci-hbase.apache.org//job/HBase-Flaky-Tests/job/master/14721]  
[14722|https://ci-hbase.apache.org//job/HBase-Flaky-Tests/job/master/14722]  
[14723|https://ci-hbase.apache.org//job/HBase-Flaky-Tests/job/master/14723]  
[14724|https://ci-hbase.apache.org//job/HBase-Flaky-Tests/job/master/14724]  
[14725|https://ci-hbase.apache.org//job/HBase-Flaky-Tests/job/master/14725]  
[14726|https://ci-hbase.apache.org//job/HBase-Flaky-Tests/job/master/14726]  
[14727|https://ci-hbase.apache.org//job/HBase-Flaky-Tests/job/master/14727]  
[14728|https://ci-hbase.apache.org//job/HBase-Flaky-Tests/job/master/14728]  
[14729|https://ci-hbase.apache.org//job/HBase-Flaky-Tests/job/master/14729]  
[14730|https://ci-hbase.apache.org//job/HBase-Flaky-Tests/job/master/14730]  
[14731|https://ci-hbase.apache.org//job/HBase-Flaky-Tests/job/master/14731]  
[14732|https://ci-hbase.apache.org//job/HBase-Flaky-Tests/job/master/14732]  
[14733|https://ci-hbase.apache.org//job/HBase-Flaky-Tests/job/master/14733]  
[14734|https://ci-hbase.apache.org//job/HBase-Flaky-Tests/job/master/14734]  
[14735|https://ci-hbase.apache.org//job/HBase-Flaky-Tests/job/master/14735] 

> [Flaky test] Fix 'test_list_decommissioned_regionservers' in 
> TestAdminShell2.java
> -
>
> Key: HBASE-28275
> URL: https://issues.apache.org/jira/browse/HBASE-28275
> Project: HBase
>  Issue Type: Test
>  Components: flakies, test
>Reporter: Nihal Jain
>Assignee: Nihal Jain
>Priority: Minor
> Fix For: 2.6.0, 2.4.18, 3.0.0-beta-1, 2.5.8
>
>
> See flaky board: 
> [https://nightlies.apache.org/hbase/HBase-Find-Flaky-Tests/master/1345/output/dashboard.html]
> Failed : 
> [14675|https://ci-hbase.apache.org//job/HBase-Flaky-Tests/job/master/14675]  
> [14676|https://ci-hbase.apache.org//job/HBase-Flaky-Tests/job/master/14676]  
> [14677|https://ci-hbase.apache.org//job/HBase-Flaky-Tests/job/master/14677]  
> [14678|https://ci-hbase.apache.org//job/HBase-Flaky-Tests/job/master/14678]  
> [14679|https://ci-hbase.apache.org//job/HBase-Flaky-Tests/job/master/14679]  
> [14680|https://ci-hbase.apache.org//job/HBase-Flaky-Tests/job/master/14680]  
> [14681|https://ci-hbase.apache.org//job/HBase-Flaky-Tests/job/master/14681]  
> [14682|https://ci-hbase.apache.org//job/HBase-Flaky-Tests/job/master/14682]  
> [14683|https://ci-hbase.apache.org//job/HBase-Flaky-Tests/job/master/14683]  
> [14684|https://ci-hbase.apache.org//job/HBase-Flaky-Tests/job/master/14684]  
> [14685|https://ci-hbase.apache.org//job/HBase-Flaky-Tests/job/master/14685]  
> [14686|https://ci-hbase.apache.org//job/HBase-Flaky-Tests/job/master/14686]  
> [14687|https://ci-hbase.apache.org//job/HBase-Flaky-Tests/job/master/14687] 



--
This message was sent by Atlassian Jira
(v8.20.10#820010)


[jira] [Comment Edited] (HBASE-28269) Fix broken ruby scripts and clean up logging

2023-12-22 Thread Nihal Jain (Jira)


[ 
https://issues.apache.org/jira/browse/HBASE-28269?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17799734#comment-17799734
 ] 

Nihal Jain edited comment on HBASE-28269 at 12/22/23 9:12 AM:
--

Tested sanity on branch-2.5+ and pushed change to branch-2.5+. For branch-2.x, 
even though the scripts are not broken but good to patch to keep code in sync 
and remove deprecated calls. 
Unfortunately, code does not apply directly on 2.4. As the scripts works fine 
there w/o the patch too, skipping. Let me know, if we still want this there

Thanks for the review [~zhangduo] !


was (Author: nihaljain.cs):
Tested sanity on branch-2.5+ and pushed change to branch-2.5+. For branch-2.x, 
even though the scripts are not broken but good to patch to keep code in sync 
and remove deprecated calls. 
Unfortunately, code does not apply directly on 2.4. As the scripts works fine 
there w/o the patch too, skipping. Let me know, if we still want this there

Thanks for the review [@Apache9|https://github.com/Apache9] !

> Fix broken ruby scripts and clean up logging
> 
>
> Key: HBASE-28269
> URL: https://issues.apache.org/jira/browse/HBASE-28269
> Project: HBase
>  Issue Type: Bug
>  Components: jruby
>Affects Versions: 3.0.0-alpha-4
>Reporter: Nihal Jain
>Assignee: Nihal Jain
>Priority: Major
>  Labels: ruby
> Fix For: 2.6.0, 3.0.0-beta-1, 2.5.8
>
>
> Some of the ruby scripts are broken in 3.x as they are referencing 
> non-existent classes, these were deprecated earlier and removed in 3.x:
>  * {{org.apache.hadoop.hbase.client.HBaseAdmin}}
>  * {{org.apache.hadoop.hbase.HTableDescriptor}}
> Following 4 scripts are failing:
> {code:java}
> NameError: missing class name org.apache.hadoop.hbase.client.HBaseAdmin
>   method_missing at org/jruby/javasupport/JavaPackage.java:253
>at region_status.rb:50
> {code}
> {code:java}
> {NameError: missing class name org.apache.hadoop.hbase.HTableDescriptor
>   method_missing at org/jruby/javasupport/JavaPackage.java:253
>at replication/copy_tables_desc.rb:30
> {code}
> {code:java}
> NameError: missing class name org.apache.hadoop.hbase.client.HBaseAdmin
>   method_missing at org/jruby/javasupport/JavaPackage.java:253
>at draining_servers.rb:28
> {code}
> {code:java}
> NameError: missing class name org.apache.hadoop.hbase.client.HBaseAdmin
>   method_missing at org/jruby/javasupport/JavaPackage.java:253
>at shutdown_regionserver.rb:27
> {code}



--
This message was sent by Atlassian Jira
(v8.20.10#820010)


[jira] [Resolved] (HBASE-28274) Flaky test: TestFanOutOneBlockAsyncDFSOutput (Part 2)

2023-12-22 Thread Balazs Meszaros (Jira)


 [ 
https://issues.apache.org/jira/browse/HBASE-28274?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Balazs Meszaros resolved HBASE-28274.
-
Fix Version/s: 2.6.0
   2.4.18
   3.0.0-beta-1
   2.5.8
   Resolution: Fixed

> Flaky test: TestFanOutOneBlockAsyncDFSOutput (Part 2)
> -
>
> Key: HBASE-28274
> URL: https://issues.apache.org/jira/browse/HBASE-28274
> Project: HBase
>  Issue Type: Test
>  Components: flakies, integration tests, test
>Reporter: Andor Molnar
>Assignee: Andor Molnar
>Priority: Major
> Fix For: 2.6.0, 2.4.18, 3.0.0-beta-1, 2.5.8
>
>
> The following test sometimes fails for me when running locally with Maven:
> TestFanOutOneBlockAsyncDFSOutput.testRecover()
> I can't really figure out the reason, but it's probably a side effect of the 
> preceding test: testConnectToDatanodeFailed(). This test also restarts one of 
> the datanodes in the MiniDFS cluster just like testRecover() and it somehow 
> causes the failure.
> {noformat}
> java.lang.AssertionError: flush should fail
>   at org.junit.Assert.fail(Assert.java:89)
>   at 
> org.apache.hadoop.hbase.io.asyncfs.TestFanOutOneBlockAsyncDFSOutput.testRecover(TestFanOutOneBlockAsyncDFSOutput.java:154)
>   at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method){noformat}
> The flush() call is testRecover() should fail, because we restart one of the 
> DN in the DFS cluster which is expected to brake connection. It succeeds 
> though if the preceding test already restarted a DN. No matter which DN we 
> restart, even if they're different, the error occurs.
> I also tried to add CLUSTER.waitDatanodeFullyStarted() at the end of 
> testConnectToDatanodeFailed(), looks like it made the tests slightly more 
> stable, but didn't help fully.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)


[jira] [Updated] (HBASE-28269) Fix broken ruby scripts and clean up logging

2023-12-22 Thread Nihal Jain (Jira)


 [ 
https://issues.apache.org/jira/browse/HBASE-28269?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Nihal Jain updated HBASE-28269:
---
Fix Version/s: 2.6.0
   3.0.0-beta-1
   2.5.8

> Fix broken ruby scripts and clean up logging
> 
>
> Key: HBASE-28269
> URL: https://issues.apache.org/jira/browse/HBASE-28269
> Project: HBase
>  Issue Type: Bug
>  Components: jruby
>Affects Versions: 3.0.0-alpha-4
>Reporter: Nihal Jain
>Assignee: Nihal Jain
>Priority: Major
>  Labels: ruby
> Fix For: 2.6.0, 3.0.0-beta-1, 2.5.8
>
>
> Some of the ruby scripts are broken in 3.x as they are referencing 
> non-existent classes, these were deprecated earlier and removed in 3.x:
>  * {{org.apache.hadoop.hbase.client.HBaseAdmin}}
>  * {{org.apache.hadoop.hbase.HTableDescriptor}}
> Following 4 scripts are failing:
> {code:java}
> NameError: missing class name org.apache.hadoop.hbase.client.HBaseAdmin
>   method_missing at org/jruby/javasupport/JavaPackage.java:253
>at region_status.rb:50
> {code}
> {code:java}
> {NameError: missing class name org.apache.hadoop.hbase.HTableDescriptor
>   method_missing at org/jruby/javasupport/JavaPackage.java:253
>at replication/copy_tables_desc.rb:30
> {code}
> {code:java}
> NameError: missing class name org.apache.hadoop.hbase.client.HBaseAdmin
>   method_missing at org/jruby/javasupport/JavaPackage.java:253
>at draining_servers.rb:28
> {code}
> {code:java}
> NameError: missing class name org.apache.hadoop.hbase.client.HBaseAdmin
>   method_missing at org/jruby/javasupport/JavaPackage.java:253
>at shutdown_regionserver.rb:27
> {code}



--
This message was sent by Atlassian Jira
(v8.20.10#820010)


[jira] [Commented] (HBASE-28269) Fix broken ruby scripts and clean up logging

2023-12-22 Thread Nihal Jain (Jira)


[ 
https://issues.apache.org/jira/browse/HBASE-28269?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17799734#comment-17799734
 ] 

Nihal Jain commented on HBASE-28269:


Tested sanity on branch-2.5+ and pushed change to branch-2.5+. For branch-2.x, 
even though the scripts are not broken but good to patch to keep code in sync 
and remove deprecated calls. 
Unfortunately, code does not apply directly on 2.4. As the scripts works fine 
there w/o the patch too, skipping. Let me know, if we still want this there

Thanks for the review [@Apache9|https://github.com/Apache9] !

> Fix broken ruby scripts and clean up logging
> 
>
> Key: HBASE-28269
> URL: https://issues.apache.org/jira/browse/HBASE-28269
> Project: HBase
>  Issue Type: Bug
>  Components: jruby
>Affects Versions: 3.0.0-alpha-4
>Reporter: Nihal Jain
>Assignee: Nihal Jain
>Priority: Major
>  Labels: ruby
>
> Some of the ruby scripts are broken in 3.x as they are referencing 
> non-existent classes, these were deprecated earlier and removed in 3.x:
>  * {{org.apache.hadoop.hbase.client.HBaseAdmin}}
>  * {{org.apache.hadoop.hbase.HTableDescriptor}}
> Following 4 scripts are failing:
> {code:java}
> NameError: missing class name org.apache.hadoop.hbase.client.HBaseAdmin
>   method_missing at org/jruby/javasupport/JavaPackage.java:253
>at region_status.rb:50
> {code}
> {code:java}
> {NameError: missing class name org.apache.hadoop.hbase.HTableDescriptor
>   method_missing at org/jruby/javasupport/JavaPackage.java:253
>at replication/copy_tables_desc.rb:30
> {code}
> {code:java}
> NameError: missing class name org.apache.hadoop.hbase.client.HBaseAdmin
>   method_missing at org/jruby/javasupport/JavaPackage.java:253
>at draining_servers.rb:28
> {code}
> {code:java}
> NameError: missing class name org.apache.hadoop.hbase.client.HBaseAdmin
>   method_missing at org/jruby/javasupport/JavaPackage.java:253
>at shutdown_regionserver.rb:27
> {code}



--
This message was sent by Atlassian Jira
(v8.20.10#820010)


[jira] [Updated] (HBASE-28269) Fix broken ruby scripts and clean up logging

2023-12-22 Thread Nihal Jain (Jira)


 [ 
https://issues.apache.org/jira/browse/HBASE-28269?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Nihal Jain updated HBASE-28269:
---
Hadoop Flags: Reviewed
  Resolution: Fixed
  Status: Resolved  (was: Patch Available)

> Fix broken ruby scripts and clean up logging
> 
>
> Key: HBASE-28269
> URL: https://issues.apache.org/jira/browse/HBASE-28269
> Project: HBase
>  Issue Type: Bug
>  Components: jruby
>Affects Versions: 3.0.0-alpha-4
>Reporter: Nihal Jain
>Assignee: Nihal Jain
>Priority: Major
>  Labels: ruby
> Fix For: 2.6.0, 3.0.0-beta-1, 2.5.8
>
>
> Some of the ruby scripts are broken in 3.x as they are referencing 
> non-existent classes, these were deprecated earlier and removed in 3.x:
>  * {{org.apache.hadoop.hbase.client.HBaseAdmin}}
>  * {{org.apache.hadoop.hbase.HTableDescriptor}}
> Following 4 scripts are failing:
> {code:java}
> NameError: missing class name org.apache.hadoop.hbase.client.HBaseAdmin
>   method_missing at org/jruby/javasupport/JavaPackage.java:253
>at region_status.rb:50
> {code}
> {code:java}
> {NameError: missing class name org.apache.hadoop.hbase.HTableDescriptor
>   method_missing at org/jruby/javasupport/JavaPackage.java:253
>at replication/copy_tables_desc.rb:30
> {code}
> {code:java}
> NameError: missing class name org.apache.hadoop.hbase.client.HBaseAdmin
>   method_missing at org/jruby/javasupport/JavaPackage.java:253
>at draining_servers.rb:28
> {code}
> {code:java}
> NameError: missing class name org.apache.hadoop.hbase.client.HBaseAdmin
>   method_missing at org/jruby/javasupport/JavaPackage.java:253
>at shutdown_regionserver.rb:27
> {code}



--
This message was sent by Atlassian Jira
(v8.20.10#820010)


Re: [PR] HBASE-28269 Fix broken ruby scripts and clean up logging [hbase]

2023-12-22 Thread via GitHub


NihalJain commented on PR #5588:
URL: https://github.com/apache/hbase/pull/5588#issuecomment-1867429569

   
   > * Build code with `assembly:single`
   > * Untar the tarball
   > * Start hbase in local mode
   >   
   >   * Start `hbase shell` and ensure logs are as expected
   >   * Create a table 't1' via shell: `create 't1', 'cf'`
   >   * Start `hbase shell --debug` and ensure debug logs are coming
   > * Run following to test and ensure output/behaviour is as expected. Also 
now nosisy logging is not there:
   >   
   >   * `./hbase org.jruby.Main get-active-master.rb`
   >   * `./hbase org.jruby.Main replication/copy_tables_desc.rb 
127.0.0.1:2181:/hbase  127.0.0.1:2181:/hbase t1`
   >   * `./hbase org.jruby.Main draining_servers.rb add hostname:16020`
   >   * `./hbase org.jruby.Main draining_servers.rb list`
   >   * `./hbase org.jruby.Main draining_servers.rb remove hostname:16020`
   >   * `./hbase org.jruby.Main shutdown_regionserver.rb IP:16020`
   >   * Also modified one of the scripts and ensured `setRootLevel` works as 
expected
   > * Also ran `hbase-shell` tests locally and ensured tests pass
   
   Tested above on branch-2.5+ and pushed change. 
   Code does not apply directly on 2.4, hence skipping. As the scripts works 
fine there w/o the patch too, skipping. 
   
   Thanks for the review @Apache9 !


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: issues-unsubscr...@hbase.apache.org

For queries about this service, please contact Infrastructure at:
us...@infra.apache.org



Re: [PR] HBASE-28274 Flaky test: TestFanOutOneBlockAsyncDFSOutput (Part 2) [hbase]

2023-12-22 Thread via GitHub


meszibalu merged PR #5592:
URL: https://github.com/apache/hbase/pull/5592


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: issues-unsubscr...@hbase.apache.org

For queries about this service, please contact Infrastructure at:
us...@infra.apache.org