[jira] [Commented] (HBASE-21493) Release 1.2.9
[ https://issues.apache.org/jira/browse/HBASE-21493?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16690804#comment-16690804 ] Sean Busbey commented on HBASE-21493: - RC0 VOTE posted: https://lists.apache.org/thread.html/832ac5299d6da39f208b93b4b29d113d32a8a3a6e770973692372cc6@%3Cdev.hbase.apache.org%3E > Release 1.2.9 > - > > Key: HBASE-21493 > URL: https://issues.apache.org/jira/browse/HBASE-21493 > Project: HBase > Issue Type: Task > Components: community >Affects Versions: 1.2.9 >Reporter: Sean Busbey >Assignee: Sean Busbey >Priority: Major > Fix For: 1.2.9 > > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (HBASE-21445) CopyTable by bulkload will write hfile into yarn's HDFS
[ https://issues.apache.org/jira/browse/HBASE-21445?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sean Busbey updated HBASE-21445: Priority: Major (was: Critical) > CopyTable by bulkload will write hfile into yarn's HDFS > > > Key: HBASE-21445 > URL: https://issues.apache.org/jira/browse/HBASE-21445 > Project: HBase > Issue Type: Bug > Components: mapreduce >Reporter: Zheng Hu >Assignee: Zheng Hu >Priority: Major > Fix For: 1.5.0, 1.3.3, 2.2.0, 2.0.3, 1.4.9, 2.1.2, 1.2.9 > > Attachments: HBASE-21445.v1.patch > > > When using CopyTable with bulkload, I found that all hfile's are written in > our Yarn's HDFS cluster. and failed to load hfiles into HBase cluster, > because we use different HDFS between yarn cluster and hbase cluster. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (HBASE-21445) CopyTable by bulkload will write hfile into yarn's HDFS
[ https://issues.apache.org/jira/browse/HBASE-21445?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sean Busbey updated HBASE-21445: Priority: Critical (was: Major) > CopyTable by bulkload will write hfile into yarn's HDFS > > > Key: HBASE-21445 > URL: https://issues.apache.org/jira/browse/HBASE-21445 > Project: HBase > Issue Type: Bug > Components: mapreduce >Reporter: Zheng Hu >Assignee: Zheng Hu >Priority: Critical > Fix For: 1.5.0, 1.3.3, 2.2.0, 2.0.3, 1.4.9, 2.1.2, 1.2.9 > > Attachments: HBASE-21445.v1.patch > > > When using CopyTable with bulkload, I found that all hfile's are written in > our Yarn's HDFS cluster. and failed to load hfiles into HBase cluster, > because we use different HDFS between yarn cluster and hbase cluster. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (HBASE-21489) TestShell is broken
[
https://issues.apache.org/jira/browse/HBASE-21489?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Reid Chan updated HBASE-21489:
--
Resolution: Fixed
Status: Resolved (was: Patch Available)
> TestShell is broken
> ---
>
> Key: HBASE-21489
> URL: https://issues.apache.org/jira/browse/HBASE-21489
> Project: HBase
> Issue Type: Umbrella
> Components: shell
>Affects Versions: 3.0.0, 2.2.0
>Reporter: Duo Zhang
>Assignee: Reid Chan
>Priority: Major
> Fix For: 3.0.0, 2.2.0
>
> Attachments: HBASE-21489.master.001.patch
>
>
> ===
> Error:
> test_Grant_should_set_access_rights_appropriately(Hbase::SecureAdminMethodsTest):
> TypeError: wrong argument type String (expected byte[])
> org/jruby/javasupport/JavaArrayUtilities.java:76:in `bytes_to_ruby_string'
> org/jruby/javasupport/JavaArrayUtilities.java:57:in `bytes_to_ruby_string'
> org/jruby/java/addons/StringJavaAddons.java:16:in `from_java_bytes'
> /home/jenkins/jenkins-slave/workspace/HBase-Flaky-Tests_master-M6IJIUBEFGBLJA2QZFJ5NFMN4UCZCOJZHSKUZTUZSLWEH6TJXWBQ/hbase-shell/src/main/ruby/hbase/security.rb:145:in
> `block in user_permission'
> /home/jenkins/jenkins-slave/workspace/HBase-Flaky-Tests_master-M6IJIUBEFGBLJA2QZFJ5NFMN4UCZCOJZHSKUZTUZSLWEH6TJXWBQ/hbase-shell/src/main/ruby/hbase/security.rb:144:in
> `user_permission'
> src/test/ruby/hbase/security_admin_test.rb:63:in `block in
> test_Grant_should_set_access_rights_appropriately'
> 60: test_grant_revoke_user =
> org.apache.hadoop.hbase.security.User.createUserForTesting(
> 61: $TEST_CLUSTER.getConfiguration, "test_grant_revoke",
> []).getName()
> 62: security_admin.grant(test_grant_revoke_user,"W", @test_name)
> => 63: security_admin.user_permission(@test_name) do |user,
> permission|
> 64: assert_match(eval("/WRITE/"), permission.to_s)
> 65: end
> 66:
> ===
> ===
> Error:
> test_Revoke_should_rid_access_rights_appropriately(Hbase::SecureAdminMethodsTest):
> TypeError: wrong argument type String (expected byte[])
> org/jruby/javasupport/JavaArrayUtilities.java:76:in `bytes_to_ruby_string'
> org/jruby/javasupport/JavaArrayUtilities.java:57:in `bytes_to_ruby_string'
> org/jruby/java/addons/StringJavaAddons.java:16:in `from_java_bytes'
> /home/jenkins/jenkins-slave/workspace/HBase-Flaky-Tests_master-M6IJIUBEFGBLJA2QZFJ5NFMN4UCZCOJZHSKUZTUZSLWEH6TJXWBQ/hbase-shell/src/main/ruby/hbase/security.rb:145:in
> `block in user_permission'
> /home/jenkins/jenkins-slave/workspace/HBase-Flaky-Tests_master-M6IJIUBEFGBLJA2QZFJ5NFMN4UCZCOJZHSKUZTUZSLWEH6TJXWBQ/hbase-shell/src/main/ruby/hbase/security.rb:144:in
> `user_permission'
> src/test/ruby/hbase/security_admin_test.rb:51:in `block in
> test_Revoke_should_rid_access_rights_appropriately'
> 48: create_test_table(@test_name)
> 49: table = table(@test_name)
> 50: user =
> org.apache.hadoop.hbase.security.User.getCurrent().getName();
> => 51: assert_equal(1,
> security_admin.user_permission(@test_name).length)
> 52: security_admin.revoke(user, @test_name)
> 53: assert_equal(0,
> security_admin.user_permission(@test_name).length)
> 54: end
> ===
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (HBASE-21489) TestShell is broken
[
https://issues.apache.org/jira/browse/HBASE-21489?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16690792#comment-16690792
]
Reid Chan commented on HBASE-21489:
---
Thanks for the review.
Let me push it to branch-2 and master branch if you don't mind.
> TestShell is broken
> ---
>
> Key: HBASE-21489
> URL: https://issues.apache.org/jira/browse/HBASE-21489
> Project: HBase
> Issue Type: Umbrella
> Components: shell
>Affects Versions: 3.0.0, 2.2.0
>Reporter: Duo Zhang
>Assignee: Reid Chan
>Priority: Major
> Fix For: 3.0.0, 2.2.0
>
> Attachments: HBASE-21489.master.001.patch
>
>
> ===
> Error:
> test_Grant_should_set_access_rights_appropriately(Hbase::SecureAdminMethodsTest):
> TypeError: wrong argument type String (expected byte[])
> org/jruby/javasupport/JavaArrayUtilities.java:76:in `bytes_to_ruby_string'
> org/jruby/javasupport/JavaArrayUtilities.java:57:in `bytes_to_ruby_string'
> org/jruby/java/addons/StringJavaAddons.java:16:in `from_java_bytes'
> /home/jenkins/jenkins-slave/workspace/HBase-Flaky-Tests_master-M6IJIUBEFGBLJA2QZFJ5NFMN4UCZCOJZHSKUZTUZSLWEH6TJXWBQ/hbase-shell/src/main/ruby/hbase/security.rb:145:in
> `block in user_permission'
> /home/jenkins/jenkins-slave/workspace/HBase-Flaky-Tests_master-M6IJIUBEFGBLJA2QZFJ5NFMN4UCZCOJZHSKUZTUZSLWEH6TJXWBQ/hbase-shell/src/main/ruby/hbase/security.rb:144:in
> `user_permission'
> src/test/ruby/hbase/security_admin_test.rb:63:in `block in
> test_Grant_should_set_access_rights_appropriately'
> 60: test_grant_revoke_user =
> org.apache.hadoop.hbase.security.User.createUserForTesting(
> 61: $TEST_CLUSTER.getConfiguration, "test_grant_revoke",
> []).getName()
> 62: security_admin.grant(test_grant_revoke_user,"W", @test_name)
> => 63: security_admin.user_permission(@test_name) do |user,
> permission|
> 64: assert_match(eval("/WRITE/"), permission.to_s)
> 65: end
> 66:
> ===
> ===
> Error:
> test_Revoke_should_rid_access_rights_appropriately(Hbase::SecureAdminMethodsTest):
> TypeError: wrong argument type String (expected byte[])
> org/jruby/javasupport/JavaArrayUtilities.java:76:in `bytes_to_ruby_string'
> org/jruby/javasupport/JavaArrayUtilities.java:57:in `bytes_to_ruby_string'
> org/jruby/java/addons/StringJavaAddons.java:16:in `from_java_bytes'
> /home/jenkins/jenkins-slave/workspace/HBase-Flaky-Tests_master-M6IJIUBEFGBLJA2QZFJ5NFMN4UCZCOJZHSKUZTUZSLWEH6TJXWBQ/hbase-shell/src/main/ruby/hbase/security.rb:145:in
> `block in user_permission'
> /home/jenkins/jenkins-slave/workspace/HBase-Flaky-Tests_master-M6IJIUBEFGBLJA2QZFJ5NFMN4UCZCOJZHSKUZTUZSLWEH6TJXWBQ/hbase-shell/src/main/ruby/hbase/security.rb:144:in
> `user_permission'
> src/test/ruby/hbase/security_admin_test.rb:51:in `block in
> test_Revoke_should_rid_access_rights_appropriately'
> 48: create_test_table(@test_name)
> 49: table = table(@test_name)
> 50: user =
> org.apache.hadoop.hbase.security.User.getCurrent().getName();
> => 51: assert_equal(1,
> security_admin.user_permission(@test_name).length)
> 52: security_admin.revoke(user, @test_name)
> 53: assert_equal(0,
> security_admin.user_permission(@test_name).length)
> 54: end
> ===
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (HBASE-21496) Set version to 2.0.3 on branch-2.0 in prep for first RC
[
https://issues.apache.org/jira/browse/HBASE-21496?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16690756#comment-16690756
]
stack commented on HBASE-21496:
---
{code}
$ mvn clean org.codehaus.mojo:versions-maven-plugin:2.5:set -DnewVersion=2.0.3
$ find . -name pom.xml -exec git add {} \;
$ git commit ...
{code}
> Set version to 2.0.3 on branch-2.0 in prep for first RC
> ---
>
> Key: HBASE-21496
> URL: https://issues.apache.org/jira/browse/HBASE-21496
> Project: HBase
> Issue Type: Sub-task
>Reporter: stack
>Assignee: stack
>Priority: Major
> Fix For: 2.0.3
>
>
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Resolved] (HBASE-21496) Set version to 2.0.3 on branch-2.0 in prep for first RC
[ https://issues.apache.org/jira/browse/HBASE-21496?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] stack resolved HBASE-21496. --- Resolution: Fixed Release Note: Changed version on branch-2.0 from 2.0.2 to 2.0.3. Pushed. Resovling. > Set version to 2.0.3 on branch-2.0 in prep for first RC > --- > > Key: HBASE-21496 > URL: https://issues.apache.org/jira/browse/HBASE-21496 > Project: HBase > Issue Type: Sub-task >Reporter: stack >Assignee: stack >Priority: Major > Fix For: 2.0.3 > > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (HBASE-21495) Create 2.0.3 Release
stack created HBASE-21495: - Summary: Create 2.0.3 Release Key: HBASE-21495 URL: https://issues.apache.org/jira/browse/HBASE-21495 Project: HBase Issue Type: Task Reporter: stack Assignee: stack Fix For: 2.0.3 Push a 2.0.3 release. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (HBASE-21496) Set version to 2.0.3 on branch-2.0 in prep for first RC
stack created HBASE-21496: - Summary: Set version to 2.0.3 on branch-2.0 in prep for first RC Key: HBASE-21496 URL: https://issues.apache.org/jira/browse/HBASE-21496 Project: HBase Issue Type: Sub-task Reporter: stack Assignee: stack Fix For: 2.0.3 -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (HBASE-21495) Create 2.0.3 Release
[ https://issues.apache.org/jira/browse/HBASE-21495?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] stack updated HBASE-21495: -- Description: Push a 2.0.3 release. Nightlies look pretty good: https://builds.apache.org/view/H-L/view/HBase/job/HBase%20Nightly/job/branch-2.0/ (was: Push a 2.0.3 release.) > Create 2.0.3 Release > > > Key: HBASE-21495 > URL: https://issues.apache.org/jira/browse/HBASE-21495 > Project: HBase > Issue Type: Task >Reporter: stack >Assignee: stack >Priority: Major > Fix For: 2.0.3 > > > Push a 2.0.3 release. Nightlies look pretty good: > https://builds.apache.org/view/H-L/view/HBase/job/HBase%20Nightly/job/branch-2.0/ -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (HBASE-21494) NPE when loading RecoverStandByProcedure
[
https://issues.apache.org/jira/browse/HBASE-21494?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Duo Zhang updated HBASE-21494:
--
Fix Version/s: 3.0.0
> NPE when loading RecoverStandByProcedure
>
>
> Key: HBASE-21494
> URL: https://issues.apache.org/jira/browse/HBASE-21494
> Project: HBase
> Issue Type: Sub-task
> Components: Replication
>Reporter: Duo Zhang
>Priority: Major
> Fix For: 3.0.0
>
>
> {noformat}
> 2018-11-16,21:06:04,676 ERROR
> [master/c4-hadoop-tst-ct05:19100:becomeActiveMaster]
> org.apache.hadoop.hbase.master.HMaster: Failed to become active master
> java.lang.NullPointerException
> at
> org.apache.hadoop.hbase.master.replication.RecoverStandbyProcedure.afterReplay(RecoverStandbyProcedure.java:151)
> at
> org.apache.hadoop.hbase.master.replication.RecoverStandbyProcedure.afterReplay(RecoverStandbyProcedure.java:39)
> at
> org.apache.hadoop.hbase.procedure2.ProcedureExecutor.lambda$loadProcedures$1(ProcedureExecutor.java:524)
> at java.util.ArrayList.forEach(ArrayList.java:1249)
> at
> org.apache.hadoop.hbase.procedure2.ProcedureExecutor.loadProcedures(ProcedureExecutor.java:509)
> at
> org.apache.hadoop.hbase.procedure2.ProcedureExecutor.access$400(ProcedureExecutor.java:78)
> at
> org.apache.hadoop.hbase.procedure2.ProcedureExecutor$2.load(ProcedureExecutor.java:330)
> at
> org.apache.hadoop.hbase.procedure2.store.wal.WALProcedureStore$2.load(WALProcedureStore.java:474)
> at
> org.apache.hadoop.hbase.procedure2.store.wal.ProcedureWALFormatReader.finish(ProcedureWALFormatReader.java:148)
> at
> org.apache.hadoop.hbase.procedure2.store.wal.ProcedureWALFormat.load(ProcedureWALFormat.java:103)
> at
> org.apache.hadoop.hbase.procedure2.store.wal.WALProcedureStore.load(WALProcedureStore.java:465)
> at
> org.apache.hadoop.hbase.procedure2.ProcedureExecutor.load(ProcedureExecutor.java:321)
> at
> org.apache.hadoop.hbase.procedure2.ProcedureExecutor.init(ProcedureExecutor.java:596)
> at
> org.apache.hadoop.hbase.master.HMaster.createProcedureExecutor(HMaster.java:1517)
> at
> org.apache.hadoop.hbase.master.HMaster.finishActiveMasterInitialization(HMaster.java:947)
> at
> org.apache.hadoop.hbase.master.HMaster.startActiveMasterManager(HMaster.java:2311)
> at
> org.apache.hadoop.hbase.master.HMaster.lambda$run$0(HMaster.java:587)
> at java.lang.Thread.run(Thread.java:745)
> {noformat}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (HBASE-21490) WALProcedure may remove proc wal files still with active procedures
[
https://issues.apache.org/jira/browse/HBASE-21490?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16690535#comment-16690535
]
Duo Zhang commented on HBASE-21490:
---
OK I found this
{noformat}
2018-11-16,21:06:04,667 INFO
[master/c4-hadoop-tst-ct05:19100:becomeActiveMaster]
org.apache.hadoop.hbase.procedure2.store.wal.WALProcedureStore: Remove the
oldest log
hdfs://c4tst-xiaomi/hbase/c4tst-sync1/MasterProcWALs/pv2-0185.log
2018-11-16,21:06:04,667 INFO
[master/c4-hadoop-tst-ct05:19100:becomeActiveMaster]
org.apache.hadoop.hbase.procedure2.store.wal.ProcedureWALFile: Archiving
hdfs://c4tst-xiaomi/hbase/c4tst-sync1/MasterProcWALs/pv2-0185.log
to hdfs://c4tst-xiaomi/hbase/c4tst-sync1/oldWALs/pv2-0185.log
2018-11-16,21:06:04,672 DEBUG
[master/c4-hadoop-tst-ct05:19100:becomeActiveMaster]
org.apache.hadoop.hbase.procedure2.store.wal.WALProcedureStore: Removed
log=hdfs://c4tst-xiaomi/hbase/c4tst-sync1/MasterProcWALs/pv2-0185.log,
activeLogs=[hdfs://c4tst-xiaomi/hbase/c4tst-sync1/MasterProcWALs/pv2-0186.log,
hdfs://c4tst-xiaomi/hbase/c4tst-sync1/MasterProcWALs/pv2-0187.log]
{noformat}
I think there maybe something wrong when building the holdingCleanupTracker
under some special case. Let me dig.
> WALProcedure may remove proc wal files still with active procedures
> ---
>
> Key: HBASE-21490
> URL: https://issues.apache.org/jira/browse/HBASE-21490
> Project: HBase
> Issue Type: Sub-task
> Components: proc-v2
>Reporter: Duo Zhang
>Priority: Major
>
> It happens for me several times. After master restart, all the procedures are
> gone.
> And the proc wal files were deleted before restarting, I see this in the
> master's log
> {noformat}
> 2018-11-16,20:57:40,177 INFO [WALProcedureStoreSyncThread]
> org.apache.hadoop.hbase.procedure2.store.wal.WALProcedureStore: Remove all
> state logs with ID less than 184, since all the active procedures are in the
> latest log
> 2018-11-16,20:57:40,177 INFO [WALProcedureStoreSyncThread]
> org.apache.hadoop.hbase.procedure2.store.wal.ProcedureWALFile: Archiving
> hdfs://c4tst-xiaomi/hbase/c4tst-sync1/MasterProcWALs/pv2-0184.log
> to hdfs://c4tst-xiaomi/hbase/c4tst-sync1/oldWALs/pv2-0184.log
> {noformat}
> Let me dig...
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (HBASE-21494) NPE when loading RecoverStandByProcedure
[
https://issues.apache.org/jira/browse/HBASE-21494?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16690537#comment-16690537
]
Duo Zhang commented on HBASE-21494:
---
OK the problem is that we initialize the SyncReplicationReplayWALManager in the
initializeZKBasedSystemTrackers, which is after we load procedures. We should
move it before we load procedures. Will prepare a patch soon. The fix is easy,
but we need to UT.
> NPE when loading RecoverStandByProcedure
>
>
> Key: HBASE-21494
> URL: https://issues.apache.org/jira/browse/HBASE-21494
> Project: HBase
> Issue Type: Sub-task
> Components: Replication
>Reporter: Duo Zhang
>Priority: Major
> Fix For: 3.0.0
>
>
> {noformat}
> 2018-11-16,21:06:04,676 ERROR
> [master/c4-hadoop-tst-ct05:19100:becomeActiveMaster]
> org.apache.hadoop.hbase.master.HMaster: Failed to become active master
> java.lang.NullPointerException
> at
> org.apache.hadoop.hbase.master.replication.RecoverStandbyProcedure.afterReplay(RecoverStandbyProcedure.java:151)
> at
> org.apache.hadoop.hbase.master.replication.RecoverStandbyProcedure.afterReplay(RecoverStandbyProcedure.java:39)
> at
> org.apache.hadoop.hbase.procedure2.ProcedureExecutor.lambda$loadProcedures$1(ProcedureExecutor.java:524)
> at java.util.ArrayList.forEach(ArrayList.java:1249)
> at
> org.apache.hadoop.hbase.procedure2.ProcedureExecutor.loadProcedures(ProcedureExecutor.java:509)
> at
> org.apache.hadoop.hbase.procedure2.ProcedureExecutor.access$400(ProcedureExecutor.java:78)
> at
> org.apache.hadoop.hbase.procedure2.ProcedureExecutor$2.load(ProcedureExecutor.java:330)
> at
> org.apache.hadoop.hbase.procedure2.store.wal.WALProcedureStore$2.load(WALProcedureStore.java:474)
> at
> org.apache.hadoop.hbase.procedure2.store.wal.ProcedureWALFormatReader.finish(ProcedureWALFormatReader.java:148)
> at
> org.apache.hadoop.hbase.procedure2.store.wal.ProcedureWALFormat.load(ProcedureWALFormat.java:103)
> at
> org.apache.hadoop.hbase.procedure2.store.wal.WALProcedureStore.load(WALProcedureStore.java:465)
> at
> org.apache.hadoop.hbase.procedure2.ProcedureExecutor.load(ProcedureExecutor.java:321)
> at
> org.apache.hadoop.hbase.procedure2.ProcedureExecutor.init(ProcedureExecutor.java:596)
> at
> org.apache.hadoop.hbase.master.HMaster.createProcedureExecutor(HMaster.java:1517)
> at
> org.apache.hadoop.hbase.master.HMaster.finishActiveMasterInitialization(HMaster.java:947)
> at
> org.apache.hadoop.hbase.master.HMaster.startActiveMasterManager(HMaster.java:2311)
> at
> org.apache.hadoop.hbase.master.HMaster.lambda$run$0(HMaster.java:587)
> at java.lang.Thread.run(Thread.java:745)
> {noformat}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Created] (HBASE-21494) NPE when loading RecoverStandByProcedure
Duo Zhang created HBASE-21494:
-
Summary: NPE when loading RecoverStandByProcedure
Key: HBASE-21494
URL: https://issues.apache.org/jira/browse/HBASE-21494
Project: HBase
Issue Type: Sub-task
Reporter: Duo Zhang
{noformat}
2018-11-16,21:06:04,676 ERROR
[master/c4-hadoop-tst-ct05:19100:becomeActiveMaster]
org.apache.hadoop.hbase.master.HMaster: Failed to become active master
java.lang.NullPointerException
at
org.apache.hadoop.hbase.master.replication.RecoverStandbyProcedure.afterReplay(RecoverStandbyProcedure.java:151)
at
org.apache.hadoop.hbase.master.replication.RecoverStandbyProcedure.afterReplay(RecoverStandbyProcedure.java:39)
at
org.apache.hadoop.hbase.procedure2.ProcedureExecutor.lambda$loadProcedures$1(ProcedureExecutor.java:524)
at java.util.ArrayList.forEach(ArrayList.java:1249)
at
org.apache.hadoop.hbase.procedure2.ProcedureExecutor.loadProcedures(ProcedureExecutor.java:509)
at
org.apache.hadoop.hbase.procedure2.ProcedureExecutor.access$400(ProcedureExecutor.java:78)
at
org.apache.hadoop.hbase.procedure2.ProcedureExecutor$2.load(ProcedureExecutor.java:330)
at
org.apache.hadoop.hbase.procedure2.store.wal.WALProcedureStore$2.load(WALProcedureStore.java:474)
at
org.apache.hadoop.hbase.procedure2.store.wal.ProcedureWALFormatReader.finish(ProcedureWALFormatReader.java:148)
at
org.apache.hadoop.hbase.procedure2.store.wal.ProcedureWALFormat.load(ProcedureWALFormat.java:103)
at
org.apache.hadoop.hbase.procedure2.store.wal.WALProcedureStore.load(WALProcedureStore.java:465)
at
org.apache.hadoop.hbase.procedure2.ProcedureExecutor.load(ProcedureExecutor.java:321)
at
org.apache.hadoop.hbase.procedure2.ProcedureExecutor.init(ProcedureExecutor.java:596)
at
org.apache.hadoop.hbase.master.HMaster.createProcedureExecutor(HMaster.java:1517)
at
org.apache.hadoop.hbase.master.HMaster.finishActiveMasterInitialization(HMaster.java:947)
at
org.apache.hadoop.hbase.master.HMaster.startActiveMasterManager(HMaster.java:2311)
at org.apache.hadoop.hbase.master.HMaster.lambda$run$0(HMaster.java:587)
at java.lang.Thread.run(Thread.java:745)
{noformat}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (HBASE-21494) NPE when loading RecoverStandByProcedure
[
https://issues.apache.org/jira/browse/HBASE-21494?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Duo Zhang updated HBASE-21494:
--
Component/s: Replication
> NPE when loading RecoverStandByProcedure
>
>
> Key: HBASE-21494
> URL: https://issues.apache.org/jira/browse/HBASE-21494
> Project: HBase
> Issue Type: Sub-task
> Components: Replication
>Reporter: Duo Zhang
>Priority: Major
> Fix For: 3.0.0
>
>
> {noformat}
> 2018-11-16,21:06:04,676 ERROR
> [master/c4-hadoop-tst-ct05:19100:becomeActiveMaster]
> org.apache.hadoop.hbase.master.HMaster: Failed to become active master
> java.lang.NullPointerException
> at
> org.apache.hadoop.hbase.master.replication.RecoverStandbyProcedure.afterReplay(RecoverStandbyProcedure.java:151)
> at
> org.apache.hadoop.hbase.master.replication.RecoverStandbyProcedure.afterReplay(RecoverStandbyProcedure.java:39)
> at
> org.apache.hadoop.hbase.procedure2.ProcedureExecutor.lambda$loadProcedures$1(ProcedureExecutor.java:524)
> at java.util.ArrayList.forEach(ArrayList.java:1249)
> at
> org.apache.hadoop.hbase.procedure2.ProcedureExecutor.loadProcedures(ProcedureExecutor.java:509)
> at
> org.apache.hadoop.hbase.procedure2.ProcedureExecutor.access$400(ProcedureExecutor.java:78)
> at
> org.apache.hadoop.hbase.procedure2.ProcedureExecutor$2.load(ProcedureExecutor.java:330)
> at
> org.apache.hadoop.hbase.procedure2.store.wal.WALProcedureStore$2.load(WALProcedureStore.java:474)
> at
> org.apache.hadoop.hbase.procedure2.store.wal.ProcedureWALFormatReader.finish(ProcedureWALFormatReader.java:148)
> at
> org.apache.hadoop.hbase.procedure2.store.wal.ProcedureWALFormat.load(ProcedureWALFormat.java:103)
> at
> org.apache.hadoop.hbase.procedure2.store.wal.WALProcedureStore.load(WALProcedureStore.java:465)
> at
> org.apache.hadoop.hbase.procedure2.ProcedureExecutor.load(ProcedureExecutor.java:321)
> at
> org.apache.hadoop.hbase.procedure2.ProcedureExecutor.init(ProcedureExecutor.java:596)
> at
> org.apache.hadoop.hbase.master.HMaster.createProcedureExecutor(HMaster.java:1517)
> at
> org.apache.hadoop.hbase.master.HMaster.finishActiveMasterInitialization(HMaster.java:947)
> at
> org.apache.hadoop.hbase.master.HMaster.startActiveMasterManager(HMaster.java:2311)
> at
> org.apache.hadoop.hbase.master.HMaster.lambda$run$0(HMaster.java:587)
> at java.lang.Thread.run(Thread.java:745)
> {noformat}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (HBASE-21490) WALProcedure may remove proc wal files still with active procedures
[
https://issues.apache.org/jira/browse/HBASE-21490?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16690533#comment-16690533
]
Duo Zhang commented on HBASE-21490:
---
OK, the root cause is a bug in RecoverStandByProcedure, there is a NPE when
loading it and then causes the master down. But after two times of restarts,
the file contains the procedures is deleted.
{noformat}
2018-11-16,20:43:37,454 INFO
org.apache.hadoop.hdfs.server.namenode.FSNamesystem.audit: allowed=true
ugi=hbase_tst/hadoop@XIAOMI.HADOOP (auth:KERBEROS) ip=/10.132.16.33
cmd=create
src=/hbase/c4tst-sync1/MasterProcWALs/pv2-0185.log
perm=hbase_tst:supergroup:rw-r-proto=rpc
2018-11-16,21:05:58,652 INFO
org.apache.hadoop.hdfs.server.namenode.FSNamesystem.audit: allowed=true
ugi=hbase_tst/hadoop@XIAOMI.HADOOP (auth:KERBEROS) ip=/10.132.16.34
cmd=open
src=/hbase/c4tst-sync1/MasterProcWALs/pv2-0185.log proto=rpc
2018-11-16,21:05:58,747 INFO
org.apache.hadoop.hdfs.server.namenode.FSNamesystem.audit: allowed=true
ugi=hbase_tst/hadoop@XIAOMI.HADOOP (auth:KERBEROS) ip=/10.132.16.34
cmd=open
src=/hbase/c4tst-sync1/MasterProcWALs/pv2-0185.log proto=rpc
2018-11-16,21:06:04,196 INFO
org.apache.hadoop.hdfs.server.namenode.FSNamesystem.audit: allowed=true
ugi=hbase_tst/hadoop@XIAOMI.HADOOP (auth:KERBEROS) ip=/10.132.16.34
cmd=open
src=/hbase/c4tst-sync1/MasterProcWALs/pv2-0185.log proto=rpc
2018-11-16,21:06:04,305 INFO
org.apache.hadoop.hdfs.server.namenode.FSNamesystem.audit: allowed=true
ugi=hbase_tst/hadoop@XIAOMI.HADOOP (auth:KERBEROS) ip=/10.132.16.34
cmd=open
src=/hbase/c4tst-sync1/MasterProcWALs/pv2-0185.log proto=rpc
2018-11-16,21:06:04,669 INFO
org.apache.hadoop.hdfs.server.namenode.FSNamesystem.audit: allowed=true
ugi=hbase_tst/hadoop@XIAOMI.HADOOP (auth:KERBEROS) ip=/10.132.16.34
cmd=rename
src=/hbase/c4tst-sync1/MasterProcWALs/pv2-0185.log
dst=/hbase/c4tst-sync1/oldWALs/pv2-0185.log
perm=hbase_tst:supergroup:rw-r- proto=rpc
2018-11-16,21:07:12,776 INFO
org.apache.hadoop.hdfs.server.namenode.FSNamesystem.audit: allowed=true
ugi=hbase_tst/hadoop@XIAOMI.HADOOP (auth:KERBEROS) ip=/10.132.16.34
cmd=delete src=/hbase/c4tst-sync1/oldWALs/pv2-0185.log
{noformat}
Let me check what is going on here...
> WALProcedure may remove proc wal files still with active procedures
> ---
>
> Key: HBASE-21490
> URL: https://issues.apache.org/jira/browse/HBASE-21490
> Project: HBase
> Issue Type: Sub-task
> Components: proc-v2
>Reporter: Duo Zhang
>Priority: Major
>
> It happens for me several times. After master restart, all the procedures are
> gone.
> And the proc wal files were deleted before restarting, I see this in the
> master's log
> {noformat}
> 2018-11-16,20:57:40,177 INFO [WALProcedureStoreSyncThread]
> org.apache.hadoop.hbase.procedure2.store.wal.WALProcedureStore: Remove all
> state logs with ID less than 184, since all the active procedures are in the
> latest log
> 2018-11-16,20:57:40,177 INFO [WALProcedureStoreSyncThread]
> org.apache.hadoop.hbase.procedure2.store.wal.ProcedureWALFile: Archiving
> hdfs://c4tst-xiaomi/hbase/c4tst-sync1/MasterProcWALs/pv2-0184.log
> to hdfs://c4tst-xiaomi/hbase/c4tst-sync1/oldWALs/pv2-0184.log
> {noformat}
> Let me dig...
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (HBASE-20952) Re-visit the WAL API
[
https://issues.apache.org/jira/browse/HBASE-20952?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16690523#comment-16690523
]
Hudson commented on HBASE-20952:
Results for branch HBASE-20952
[build #53 on
builds.a.o|https://builds.apache.org/job/HBase%20Nightly/job/HBASE-20952/53/]:
(x) *{color:red}-1 overall{color}*
details (if available):
(/) {color:green}+1 general checks{color}
-- For more information [see general
report|https://builds.apache.org/job/HBase%20Nightly/job/HBASE-20952/53//General_Nightly_Build_Report/]
(x) {color:red}-1 jdk8 hadoop2 checks{color}
-- For more information [see jdk8 (hadoop2)
report|https://builds.apache.org/job/HBase%20Nightly/job/HBASE-20952/53//JDK8_Nightly_Build_Report_(Hadoop2)/]
(x) {color:red}-1 jdk8 hadoop3 checks{color}
-- For more information [see jdk8 (hadoop3)
report|https://builds.apache.org/job/HBase%20Nightly/job/HBASE-20952/53//JDK8_Nightly_Build_Report_(Hadoop3)/]
(/) {color:green}+1 source release artifact{color}
-- See build output for details.
(/) {color:green}+1 client integration test{color}
> Re-visit the WAL API
>
>
> Key: HBASE-20952
> URL: https://issues.apache.org/jira/browse/HBASE-20952
> Project: HBase
> Issue Type: Improvement
> Components: wal
>Reporter: Josh Elser
>Priority: Major
> Attachments: 20952.v1.txt
>
>
> Take a step back from the current WAL implementations and think about what an
> HBase WAL API should look like. What are the primitive calls that we require
> to guarantee durability of writes with a high degree of performance?
> The API needs to take the current implementations into consideration. We
> should also have a mind for what is happening in the Ratis LogService (but
> the LogService should not dictate what HBase's WAL API looks like RATIS-272).
> Other "systems" inside of HBase that use WALs are replication and
> backup Replication has the use-case for "tail"'ing the WAL which we
> should provide via our new API. B doesn't do anything fancy (IIRC). We
> should make sure all consumers are generally going to be OK with the API we
> create.
> The API may be "OK" (or OK in a part). We need to also consider other methods
> which were "bolted" on such as {{AbstractFSWAL}} and
> {{WALFileLengthProvider}}. Other corners of "WAL use" (like the
> {{WALSplitter}} should also be looked at to use WAL-APIs only).
> We also need to make sure that adequate interface audience and stability
> annotations are chosen.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (HBASE-21141) Enable MOB in backup / restore test involving incremental backup
[
https://issues.apache.org/jira/browse/HBASE-21141?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16690505#comment-16690505
]
Hudson commented on HBASE-21141:
Results for branch master
[build #612 on
builds.a.o|https://builds.apache.org/job/HBase%20Nightly/job/master/612/]: (x)
*{color:red}-1 overall{color}*
details (if available):
(/) {color:green}+1 general checks{color}
-- For more information [see general
report|https://builds.apache.org/job/HBase%20Nightly/job/master/612//General_Nightly_Build_Report/]
(x) {color:red}-1 jdk8 hadoop2 checks{color}
-- For more information [see jdk8 (hadoop2)
report|https://builds.apache.org/job/HBase%20Nightly/job/master/612//JDK8_Nightly_Build_Report_(Hadoop2)/]
(x) {color:red}-1 jdk8 hadoop3 checks{color}
-- For more information [see jdk8 (hadoop3)
report|https://builds.apache.org/job/HBase%20Nightly/job/master/612//JDK8_Nightly_Build_Report_(Hadoop3)/]
(/) {color:green}+1 source release artifact{color}
-- See build output for details.
(/) {color:green}+1 client integration test{color}
> Enable MOB in backup / restore test involving incremental backup
>
>
> Key: HBASE-21141
> URL: https://issues.apache.org/jira/browse/HBASE-21141
> Project: HBase
> Issue Type: Test
> Components: backuprestore
>Reporter: Ted Yu
>Assignee: Artem Ervits
>Priority: Major
> Labels: mob
> Fix For: 3.0.0
>
> Attachments: HBASE-21141.v01.patch, HBASE-21141.v02.patch,
> HBASE-21141.v03.patch, HBASE-21141.v04.patch
>
>
> Currently we only have one test (TestRemoteBackup) where MOB feature is
> enabled. The test only performs full backup.
> This issue is to enable MOB in backup / restore test(s) involving incremental
> backup.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (HBASE-21480) Taking snapshot when RS crashes prevent we bring the regions online
[
https://issues.apache.org/jira/browse/HBASE-21480?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16690470#comment-16690470
]
Hadoop QA commented on HBASE-21480:
---
| (/) *{color:green}+1 overall{color}* |
\\
\\
|| Vote || Subsystem || Runtime || Comment ||
| {color:blue}0{color} | {color:blue} reexec {color} | {color:blue} 0m
15s{color} | {color:blue} Docker mode activated. {color} |
|| || || || {color:brown} Prechecks {color} ||
| {color:green}+1{color} | {color:green} hbaseanti {color} | {color:green} 0m
0s{color} | {color:green} Patch does not have any anti-patterns. {color} |
| {color:green}+1{color} | {color:green} @author {color} | {color:green} 0m
0s{color} | {color:green} The patch does not contain any @author tags. {color} |
| {color:green}+1{color} | {color:green} test4tests {color} | {color:green} 0m
0s{color} | {color:green} The patch appears to include 1 new or modified test
files. {color} |
|| || || || {color:brown} master Compile Tests {color} ||
| {color:green}+1{color} | {color:green} mvninstall {color} | {color:green} 5m
56s{color} | {color:green} master passed {color} |
| {color:green}+1{color} | {color:green} compile {color} | {color:green} 2m
13s{color} | {color:green} master passed {color} |
| {color:green}+1{color} | {color:green} checkstyle {color} | {color:green} 1m
29s{color} | {color:green} master passed {color} |
| {color:green}+1{color} | {color:green} shadedjars {color} | {color:green} 4m
32s{color} | {color:green} branch has no errors when building our shaded
downstream artifacts. {color} |
| {color:green}+1{color} | {color:green} findbugs {color} | {color:green} 2m
22s{color} | {color:green} master passed {color} |
| {color:green}+1{color} | {color:green} javadoc {color} | {color:green} 0m
39s{color} | {color:green} master passed {color} |
|| || || || {color:brown} Patch Compile Tests {color} ||
| {color:green}+1{color} | {color:green} mvninstall {color} | {color:green} 4m
50s{color} | {color:green} the patch passed {color} |
| {color:green}+1{color} | {color:green} compile {color} | {color:green} 2m
12s{color} | {color:green} the patch passed {color} |
| {color:green}+1{color} | {color:green} javac {color} | {color:green} 2m
12s{color} | {color:green} the patch passed {color} |
| {color:green}+1{color} | {color:green} checkstyle {color} | {color:green} 1m
16s{color} | {color:green} the patch passed {color} |
| {color:green}+1{color} | {color:green} whitespace {color} | {color:green} 0m
0s{color} | {color:green} The patch has no whitespace issues. {color} |
| {color:green}+1{color} | {color:green} shadedjars {color} | {color:green} 4m
34s{color} | {color:green} patch has no errors when building our shaded
downstream artifacts. {color} |
| {color:green}+1{color} | {color:green} hadoopcheck {color} | {color:green}
10m 26s{color} | {color:green} Patch does not cause any errors with Hadoop
2.7.4 or 3.0.0. {color} |
| {color:green}+1{color} | {color:green} findbugs {color} | {color:green} 2m
48s{color} | {color:green} the patch passed {color} |
| {color:green}+1{color} | {color:green} javadoc {color} | {color:green} 0m
36s{color} | {color:green} the patch passed {color} |
|| || || || {color:brown} Other Tests {color} ||
| {color:green}+1{color} | {color:green} unit {color} | {color:green}146m
30s{color} | {color:green} hbase-server in the patch passed. {color} |
| {color:green}+1{color} | {color:green} asflicense {color} | {color:green} 0m
29s{color} | {color:green} The patch does not generate ASF License warnings.
{color} |
| {color:black}{color} | {color:black} {color} | {color:black}191m 45s{color} |
{color:black} {color} |
\\
\\
|| Subsystem || Report/Notes ||
| Docker | Client=17.05.0-ce Server=17.05.0-ce Image:yetus/hbase:b002b0b |
| JIRA Issue | HBASE-21480 |
| JIRA Patch URL |
https://issues.apache.org/jira/secure/attachment/12948587/HBASE-21480-v1.patch |
| Optional Tests | dupname asflicense javac javadoc unit findbugs
shadedjars hadoopcheck hbaseanti checkstyle compile |
| uname | Linux 36e43f0f7c72 3.13.0-143-generic #192-Ubuntu SMP Tue Feb 27
10:45:36 UTC 2018 x86_64 GNU/Linux |
| Build tool | maven |
| Personality |
/home/jenkins/jenkins-slave/workspace/PreCommit-HBASE-Build@2/component/dev-support/hbase-personality.sh
|
| git revision | master / 825e14b68e |
| maven | version: Apache Maven 3.5.4
(1edded0938998edf8bf061f1ceb3cfdeccf443fe; 2018-06-17T18:33:14Z) |
| Default Java | 1.8.0_181 |
| findbugs | v3.1.0-RC3 |
| Test Results |
https://builds.apache.org/job/PreCommit-HBASE-Build/15058/testReport/ |
| Max. process+thread count | 4849 (vs. ulimit of 1) |
| modules | C: hbase-server U: hbase-server |
| Console output |
https://builds.apache.org/job/PreCommit-HBASE-Build/15058/console |
| Powered by | Apache Yetus 0.8.0 http://yetus.apache.org |
This message was automatically generated.
> Taking snapshot when RS
[jira] [Commented] (HBASE-21493) Release 1.2.9
[
https://issues.apache.org/jira/browse/HBASE-21493?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16690464#comment-16690464
]
Hudson commented on HBASE-21493:
Results for branch branch-1.2
[build #554 on
builds.a.o|https://builds.apache.org/job/HBase%20Nightly/job/branch-1.2/554/]:
(x) *{color:red}-1 overall{color}*
details (if available):
(/) {color:green}+1 general checks{color}
-- For more information [see general
report|https://builds.apache.org/job/HBase%20Nightly/job/branch-1.2/554//General_Nightly_Build_Report/]
(/) {color:green}+1 jdk7 checks{color}
-- For more information [see jdk7
report|https://builds.apache.org/job/HBase%20Nightly/job/branch-1.2/554//JDK7_Nightly_Build_Report/]
(x) {color:red}-1 jdk8 hadoop2 checks{color}
-- For more information [see jdk8 (hadoop2)
report|https://builds.apache.org/job/HBase%20Nightly/job/branch-1.2/554//JDK8_Nightly_Build_Report_(Hadoop2)/]
(/) {color:green}+1 source release artifact{color}
-- See build output for details.
> Release 1.2.9
> -
>
> Key: HBASE-21493
> URL: https://issues.apache.org/jira/browse/HBASE-21493
> Project: HBase
> Issue Type: Task
> Components: community
>Affects Versions: 1.2.9
>Reporter: Sean Busbey
>Assignee: Sean Busbey
>Priority: Major
> Fix For: 1.2.9
>
>
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (HBASE-21481) [acl] Superuser's permissions should not be granted or revoked by any non-su global admin
[
https://issues.apache.org/jira/browse/HBASE-21481?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16690445#comment-16690445
]
Hadoop QA commented on HBASE-21481:
---
| (x) *{color:red}-1 overall{color}* |
\\
\\
|| Vote || Subsystem || Runtime || Comment ||
| {color:blue}0{color} | {color:blue} reexec {color} | {color:blue} 0m
14s{color} | {color:blue} Docker mode activated. {color} |
|| || || || {color:brown} Prechecks {color} ||
| {color:green}+1{color} | {color:green} hbaseanti {color} | {color:green} 0m
0s{color} | {color:green} Patch does not have any anti-patterns. {color} |
| {color:green}+1{color} | {color:green} @author {color} | {color:green} 0m
0s{color} | {color:green} The patch does not contain any @author tags. {color} |
| {color:green}+1{color} | {color:green} test4tests {color} | {color:green} 0m
0s{color} | {color:green} The patch appears to include 2 new or modified test
files. {color} |
|| || || || {color:brown} master Compile Tests {color} ||
| {color:blue}0{color} | {color:blue} mvndep {color} | {color:blue} 0m
29s{color} | {color:blue} Maven dependency ordering for branch {color} |
| {color:green}+1{color} | {color:green} mvninstall {color} | {color:green} 4m
28s{color} | {color:green} master passed {color} |
| {color:green}+1{color} | {color:green} compile {color} | {color:green} 2m
14s{color} | {color:green} master passed {color} |
| {color:green}+1{color} | {color:green} checkstyle {color} | {color:green} 1m
34s{color} | {color:green} master passed {color} |
| {color:green}+1{color} | {color:green} shadedjars {color} | {color:green} 3m
58s{color} | {color:green} branch has no errors when building our shaded
downstream artifacts. {color} |
| {color:green}+1{color} | {color:green} findbugs {color} | {color:green} 2m
34s{color} | {color:green} master passed {color} |
| {color:green}+1{color} | {color:green} javadoc {color} | {color:green} 0m
46s{color} | {color:green} master passed {color} |
|| || || || {color:brown} Patch Compile Tests {color} ||
| {color:blue}0{color} | {color:blue} mvndep {color} | {color:blue} 0m
13s{color} | {color:blue} Maven dependency ordering for patch {color} |
| {color:green}+1{color} | {color:green} mvninstall {color} | {color:green} 4m
21s{color} | {color:green} the patch passed {color} |
| {color:green}+1{color} | {color:green} compile {color} | {color:green} 2m
12s{color} | {color:green} the patch passed {color} |
| {color:red}-1{color} | {color:red} javac {color} | {color:red} 1m 45s{color}
| {color:red} hbase-server generated 1 new + 187 unchanged - 1 fixed = 188
total (was 188) {color} |
| {color:red}-1{color} | {color:red} checkstyle {color} | {color:red} 0m
23s{color} | {color:red} hbase-common: The patch generated 1 new + 7 unchanged
- 0 fixed = 8 total (was 7) {color} |
| {color:red}-1{color} | {color:red} checkstyle {color} | {color:red} 1m
11s{color} | {color:red} hbase-server: The patch generated 3 new + 33 unchanged
- 0 fixed = 36 total (was 33) {color} |
| {color:green}+1{color} | {color:green} whitespace {color} | {color:green} 0m
0s{color} | {color:green} The patch has no whitespace issues. {color} |
| {color:green}+1{color} | {color:green} shadedjars {color} | {color:green} 3m
58s{color} | {color:green} patch has no errors when building our shaded
downstream artifacts. {color} |
| {color:green}+1{color} | {color:green} hadoopcheck {color} | {color:green}
8m 51s{color} | {color:green} Patch does not cause any errors with Hadoop 2.7.4
or 3.0.0. {color} |
| {color:green}+1{color} | {color:green} findbugs {color} | {color:green} 2m
54s{color} | {color:green} the patch passed {color} |
| {color:green}+1{color} | {color:green} javadoc {color} | {color:green} 0m
49s{color} | {color:green} the patch passed {color} |
|| || || || {color:brown} Other Tests {color} ||
| {color:green}+1{color} | {color:green} unit {color} | {color:green} 2m
52s{color} | {color:green} hbase-common in the patch passed. {color} |
| {color:red}-1{color} | {color:red} unit {color} | {color:red}145m 6s{color}
| {color:red} hbase-server in the patch failed. {color} |
| {color:green}+1{color} | {color:green} asflicense {color} | {color:green} 0m
50s{color} | {color:green} The patch does not generate ASF License warnings.
{color} |
| {color:black}{color} | {color:black} {color} | {color:black}190m 46s{color} |
{color:black} {color} |
\\
\\
|| Reason || Tests ||
| Failed junit tests | hadoop.hbase.client.TestScannerTimeout |
| | hadoop.hbase.security.visibility.TestVisibilityLablesWithGroups |
\\
\\
|| Subsystem || Report/Notes ||
| Docker | Client=17.05.0-ce Server=17.05.0-ce Image:yetus/hbase:b002b0b |
| JIRA Issue | HBASE-21481 |
| JIRA Patch URL |
https://issues.apache.org/jira/secure/attachment/12948585/HBASE-21481.master.001.patch
|
| Optional Tests | dupname asflicense javac javadoc unit findbugs
shadedjars hadoopcheck hbaseanti
[jira] [Commented] (HBASE-21493) Release 1.2.9
[ https://issues.apache.org/jira/browse/HBASE-21493?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16690439#comment-16690439 ] Sean Busbey commented on HBASE-21493: - [nightly build #553|https://builds.apache.org/view/H-L/view/HBase/job/HBase%20Nightly/job/branch-1.2/553/] covers all the code changes and got a clean bill of health. related [untrusted test report #98|https://builds.apache.org/view/H-L/view/HBase/job/HBase-Find-Flaky-Tests/job/branch-1.2/98/] shows that the exclude list was pretty small and all of those tests have gotten nothing but passes in the just-run-untrusted-tests job over the window it looks at. things look good to me. barring objection I'll dig out my signing machine and generate an RC off of fd0d55b1e5ef54eb9bf60cce1f0a8e4c1da073ef tomorrow. > Release 1.2.9 > - > > Key: HBASE-21493 > URL: https://issues.apache.org/jira/browse/HBASE-21493 > Project: HBase > Issue Type: Task > Components: community >Affects Versions: 1.2.9 >Reporter: Sean Busbey >Assignee: Sean Busbey >Priority: Major > Fix For: 1.2.9 > > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (HBASE-21357) RS should abort if OOM in Reader thread
[
https://issues.apache.org/jira/browse/HBASE-21357?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16690432#comment-16690432
]
Hudson commented on HBASE-21357:
Results for branch branch-1.2
[build #553 on
builds.a.o|https://builds.apache.org/job/HBase%20Nightly/job/branch-1.2/553/]:
(/) *{color:green}+1 overall{color}*
details (if available):
(/) {color:green}+1 general checks{color}
-- For more information [see general
report|https://builds.apache.org/job/HBase%20Nightly/job/branch-1.2/553//General_Nightly_Build_Report/]
(/) {color:green}+1 jdk7 checks{color}
-- For more information [see jdk7
report|https://builds.apache.org/job/HBase%20Nightly/job/branch-1.2/553//JDK7_Nightly_Build_Report/]
(/) {color:green}+1 jdk8 hadoop2 checks{color}
-- For more information [see jdk8 (hadoop2)
report|https://builds.apache.org/job/HBase%20Nightly/job/branch-1.2/553//JDK8_Nightly_Build_Report_(Hadoop2)/]
(/) {color:green}+1 source release artifact{color}
-- See build output for details.
> RS should abort if OOM in Reader thread
> ---
>
> Key: HBASE-21357
> URL: https://issues.apache.org/jira/browse/HBASE-21357
> Project: HBase
> Issue Type: Bug
> Components: regionserver
>Affects Versions: 1.4.8
>Reporter: Allan Yang
>Assignee: Allan Yang
>Priority: Critical
> Fix For: 1.5.0, 1.3.3, 1.4.9, 1.2.9
>
> Attachments: HBASE-21357.branch-1.001.patch,
> HBASE-21357.branch-1.001.patch
>
>
> It is a bit strange, we will abort the RS if OOM in Listener thread,
> Responder thread and in CallRunner thread, only not in Reader thread...
> We should abort RS if OOM happens in Reader thread, too. If not, the reader
> thread exists because of OOM, and the selector closes. Later connection
> select to this reader will be ignored
> {code}
> try {
> if (key.isValid()) {
> if (key.isAcceptable())
> doAccept(key);
> }
> } catch (IOException ignored) {
> if (LOG.isTraceEnabled()) LOG.trace("ignored", ignored);
> }
> {code}
> Leaving the client (or Master and other RS)'s call wait until SocketTimeout.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
