[jira] [Commented] (HBASE-5342) Grant/Revoke global permissions
[ https://issues.apache.org/jira/browse/HBASE-5342?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13273951#comment-13273951 ] Hudson commented on HBASE-5342: --- Integrated in HBase-TRUNK-on-Hadoop-2.0.0 #2 (See [https://builds.apache.org/job/HBase-TRUNK-on-Hadoop-2.0.0/2/]) HBASE-5342 Grant/Revoke global permissions (Matteo Bertozzi) (Revision 1337499) Result = FAILURE tedyu : Files : * /hbase/trunk/src/main/java/org/apache/hadoop/hbase/security/access/AccessControlLists.java * /hbase/trunk/src/main/java/org/apache/hadoop/hbase/security/access/AccessController.java * /hbase/trunk/src/main/java/org/apache/hadoop/hbase/security/access/AccessControllerProtocol.java * /hbase/trunk/src/main/java/org/apache/hadoop/hbase/security/access/TableAuthManager.java * /hbase/trunk/src/main/java/org/apache/hadoop/hbase/security/access/UserPermission.java * /hbase/trunk/src/main/java/org/apache/hadoop/hbase/security/access/ZKPermissionWatcher.java * /hbase/trunk/src/main/ruby/hbase/security.rb * /hbase/trunk/src/main/ruby/shell.rb * /hbase/trunk/src/main/ruby/shell/commands/grant.rb * /hbase/trunk/src/main/ruby/shell/commands/revoke.rb * /hbase/trunk/src/main/ruby/shell/commands/user_permission.rb * /hbase/trunk/src/main/ruby/shell/commands/whoami.rb * /hbase/trunk/src/test/java/org/apache/hadoop/hbase/security/access/TestAccessControlFilter.java * /hbase/trunk/src/test/java/org/apache/hadoop/hbase/security/access/TestAccessController.java * /hbase/trunk/src/test/java/org/apache/hadoop/hbase/security/access/TestTablePermissions.java Grant/Revoke global permissions --- Key: HBASE-5342 URL: https://issues.apache.org/jira/browse/HBASE-5342 Project: HBase Issue Type: Sub-task Reporter: Enis Soztutar Assignee: Matteo Bertozzi Attachments: HBASE-5342-draft.patch, HBASE-5342-v0.patch, HBASE-5342-v1.patch, HBASE-5342-v2.patch, HBASE-5342-v3.patch, HBASE-5342-v4.patch, HBASE-5342-v5.patch HBASE-3025 introduced simple ACLs based on coprocessors. It defines global/table/cf/cq level permissions. However, there is no way to grant/revoke global level permissions, other than the hbase.superuser conf setting. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (HBASE-5966) MapReduce based tests broken on Hadoop 2.0.0-alpha
[
https://issues.apache.org/jira/browse/HBASE-5966?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13273950#comment-13273950
]
Hudson commented on HBASE-5966:
---
Integrated in HBase-TRUNK-on-Hadoop-2.0.0 #2 (See
[https://builds.apache.org/job/HBase-TRUNK-on-Hadoop-2.0.0/2/])
HBASE-5966 MapReduce based tests broken on Hadoop 2.0.0-alpha (Revision
1337448)
Result = FAILURE
stack :
Files :
* /hbase/trunk/src/test/java/org/apache/hadoop/hbase/HBaseTestingUtility.java
MapReduce based tests broken on Hadoop 2.0.0-alpha
--
Key: HBASE-5966
URL: https://issues.apache.org/jira/browse/HBASE-5966
Project: HBase
Issue Type: Bug
Components: mapred, mapreduce, test
Affects Versions: 0.94.0, 0.96.0
Environment: Hadoop 2.0.0-alpha-SNAPSHOT, HBase 0.94.0-SNAPSHOT,
Ubuntu 12.04 LTS (GNU/Linux 3.2.0-24-generic x86_64)
Reporter: Andrew Purtell
Assignee: Jimmy Xiang
Fix For: 0.96.0
Attachments: HBASE-5966-1.patch, HBASE-5966.patch, hbase-5966.patch
Some fairly recent change in Hadoop 2.0.0-alpha has broken our MapReduce test
rigging. Below is a representative error, can be easily reproduced with:
{noformat}
mvn -PlocalTests -Psecurity \
-Dhadoop.profile=23 -Dhadoop.version=2.0.0-SNAPSHOT \
clean test \
-Dtest=org.apache.hadoop.hbase.mapreduce.TestTableMapReduce
{noformat}
And the result:
{noformat}
---
T E S T S
---
Running org.apache.hadoop.hbase.mapreduce.TestTableMapReduce
Tests run: 1, Failures: 0, Errors: 1, Skipped: 0, Time elapsed: 54.292 sec
FAILURE!
---
Test set: org.apache.hadoop.hbase.mapreduce.TestTableMapReduce
---
Tests run: 1, Failures: 0, Errors: 1, Skipped: 0, Time elapsed: 54.292 sec
FAILURE!
testMultiRegionTable(org.apache.hadoop.hbase.mapreduce.TestTableMapReduce)
Time elapsed: 21.935 sec ERROR!
java.lang.reflect.UndeclaredThrowableException
at
org.apache.hadoop.yarn.exceptions.impl.pb.YarnRemoteExceptionPBImpl.unwrapAndThrowException(YarnRemoteExceptionPBImpl.java:135)
at
org.apache.hadoop.yarn.api.impl.pb.client.ClientRMProtocolPBClientImpl.getNewApplication(ClientRMProtocolPBClientImpl.java:134)
at
org.apache.hadoop.mapred.ResourceMgrDelegate.getNewJobID(ResourceMgrDelegate.java:183)
at org.apache.hadoop.mapred.YARNRunner.getNewJobID(YARNRunner.java:216)
at
org.apache.hadoop.mapreduce.JobSubmitter.submitJobInternal(JobSubmitter.java:339)
at org.apache.hadoop.mapreduce.Job$11.run(Job.java:1226)
at org.apache.hadoop.mapreduce.Job$11.run(Job.java:1223)
at java.security.AccessController.doPrivileged(Native Method)
at javax.security.auth.Subject.doAs(Subject.java:416)
at
org.apache.hadoop.security.UserGroupInformation.doAs(UserGroupInformation.java:1232)
at org.apache.hadoop.mapreduce.Job.submit(Job.java:1223)
at org.apache.hadoop.mapreduce.Job.waitForCompletion(Job.java:1244)
at
org.apache.hadoop.hbase.mapreduce.TestTableMapReduce.runTestOnTable(TestTableMapReduce.java:151)
at
org.apache.hadoop.hbase.mapreduce.TestTableMapReduce.testMultiRegionTable(TestTableMapReduce.java:129)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:616)
at
org.junit.runners.model.FrameworkMethod$1.runReflectiveCall(FrameworkMethod.java:45)
at
org.junit.internal.runners.model.ReflectiveCallable.run(ReflectiveCallable.java:15)
at
org.junit.runners.model.FrameworkMethod.invokeExplosively(FrameworkMethod.java:42)
at
org.junit.internal.runners.statements.InvokeMethod.evaluate(InvokeMethod.java:20)
at org.junit.rules.TestWatcher$1.evaluate(TestWatcher.java:47)
at org.junit.rules.RunRules.evaluate(RunRules.java:18)
at org.junit.runners.ParentRunner.runLeaf(ParentRunner.java:263)
at
org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:68)
at
org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:47)
at org.junit.runners.ParentRunner$3.run(ParentRunner.java:231)
at org.junit.runners.ParentRunner$1.schedule(ParentRunner.java:60)
at org.junit.runners.ParentRunner.runChildren(ParentRunner.java:229)
at
[jira] [Commented] (HBASE-5385) Delete table/column should delete stored permissions on -acl- table
[ https://issues.apache.org/jira/browse/HBASE-5385?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13273973#comment-13273973 ] Hudson commented on HBASE-5385: --- Integrated in HBase-TRUNK #2876 (See [https://builds.apache.org/job/HBase-TRUNK/2876/]) HBASE-5385 Delete table/column should delete stored permissions on -acl- table (Matteo Bertozi) (Revision 1337512) Result = FAILURE tedyu : Files : * /hbase/trunk/src/main/java/org/apache/hadoop/hbase/security/access/AccessControlLists.java * /hbase/trunk/src/main/java/org/apache/hadoop/hbase/security/access/AccessController.java Delete table/column should delete stored permissions on -acl- table - Key: HBASE-5385 URL: https://issues.apache.org/jira/browse/HBASE-5385 Project: HBase Issue Type: Sub-task Components: security Affects Versions: 0.94.0 Reporter: Enis Soztutar Assignee: Matteo Bertozzi Attachments: 5385-v3.patch, HBASE-5385-v0.patch, HBASE-5385-v1.patch, HBASE-5385-v2.patch, HBASE-5385-v3.patch Deleting the table or a column does not cascade to the stored permissions at the -acl- table. We should also remove those permissions, otherwise, it can be a security leak, where freshly created tables contain permissions from previous same-named tables. We might also want to ensure, upon table creation, that no entries are already stored at the -acl- table. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (HBASE-5992) Generalization of region move implementation + manage draining servers in bulk assign
[ https://issues.apache.org/jira/browse/HBASE-5992?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13274081#comment-13274081 ] Hudson commented on HBASE-5992: --- Integrated in HBase-TRUNK #2881 (See [https://builds.apache.org/job/HBase-TRUNK/2881/]) HBASE-5992 Generalization of region move implementation + manage draining servers in bulk assign (N Keywal) (Revision 1337641) Result = SUCCESS tedyu : Files : * /hbase/trunk/src/main/java/org/apache/hadoop/hbase/master/AssignmentManager.java * /hbase/trunk/src/main/java/org/apache/hadoop/hbase/master/HMaster.java * /hbase/trunk/src/main/java/org/apache/hadoop/hbase/master/ServerManager.java * /hbase/trunk/src/main/java/org/apache/hadoop/hbase/master/handler/CreateTableHandler.java * /hbase/trunk/src/main/java/org/apache/hadoop/hbase/master/handler/ServerShutdownHandler.java * /hbase/trunk/src/main/java/org/apache/hadoop/hbase/regionserver/HRegionServer.java * /hbase/trunk/src/test/java/org/apache/hadoop/hbase/TestDrainingServer.java * /hbase/trunk/src/test/java/org/apache/hadoop/hbase/master/TestAssignmentManager.java Generalization of region move implementation + manage draining servers in bulk assign - Key: HBASE-5992 URL: https://issues.apache.org/jira/browse/HBASE-5992 Project: HBase Issue Type: Bug Components: master, regionserver Affects Versions: 0.96.0 Reporter: nkeywal Assignee: nkeywal Priority: Minor Attachments: 5992.v11.patch, 5992.v2.patch, 5992.v5.patch, 5992.v5.patch The region move implementation now has now a similar behavior whatever the destination server is specified or not. This allows: - to benefit from the improvement in HBASE-5877 - as a side effect to have the coprocessors calls when the destination server is not specified This includes various fixes around draining servers. Draining servers were not excluded during a bulk assign. This is now fixed. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (HBASE-5990) TestHCM failed with Hadoop 2.0.0
[ https://issues.apache.org/jira/browse/HBASE-5990?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13274090#comment-13274090 ] Hudson commented on HBASE-5990: --- Integrated in HBase-TRUNK #2882 (See [https://builds.apache.org/job/HBase-TRUNK/2882/]) HBASE-5990 TestHCM failed with Hadoop 2.0.0 (Revision 1337695) Result = FAILURE stack : Files : * /hbase/trunk/src/main/java/org/apache/hadoop/hbase/RegionMovedException.java TestHCM failed with Hadoop 2.0.0 Key: HBASE-5990 URL: https://issues.apache.org/jira/browse/HBASE-5990 Project: HBase Issue Type: Bug Components: client, test Affects Versions: 0.96.0 Reporter: Jimmy Xiang Assignee: Jimmy Xiang Fix For: 0.96.0 Attachments: hbase-5990.patch, hbase_5990_v2.patch Running org.apache.hadoop.hbase.client.TestHCM Tests run: 7, Failures: 1, Errors: 0, Skipped: 0, Time elapsed: 11.742 sec FAILURE! Failed tests: testRegionCaching(org.apache.hadoop.hbase.client.TestHCM) -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (HBASE-5984) TestLogRolling.testLogRollOnPipelineRestart failed with HADOOP 2.0.0
[
https://issues.apache.org/jira/browse/HBASE-5984?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13274089#comment-13274089
]
Hudson commented on HBASE-5984:
---
Integrated in HBase-TRUNK #2882 (See
[https://builds.apache.org/job/HBase-TRUNK/2882/])
HBASE-5984 TestLogRolling.testLogRollOnPipelineRestart failed with HADOOP
2.0.0 (Revision 1337697)
Result = FAILURE
stack :
Files :
*
/hbase/trunk/src/test/java/org/apache/hadoop/hbase/regionserver/wal/TestLogRolling.java
TestLogRolling.testLogRollOnPipelineRestart failed with HADOOP 2.0.0
Key: HBASE-5984
URL: https://issues.apache.org/jira/browse/HBASE-5984
Project: HBase
Issue Type: Test
Components: test
Affects Versions: 0.96.0
Reporter: Jimmy Xiang
Assignee: Jimmy Xiang
Fix For: 0.96.0
Attachments: hbase_5984.patch
java.io.IOException: Cannot obtain block length for
LocatedBlock{BP-1455809779-127.0.0.1-1336670196362:blk_-6960847342982670493_1028;
getBlockSize()=1474; corrupt=false; offset=0; locs=[127.0.0.1:58343,
127.0.0.1:48427]}
at
org.apache.hadoop.hdfs.DFSInputStream.readBlockLength(DFSInputStream.java:232)
at
org.apache.hadoop.hdfs.DFSInputStream.fetchLocatedBlocksAndGetLastBlockLength(DFSInputStream.java:177)
at
org.apache.hadoop.hdfs.DFSInputStream.openInfo(DFSInputStream.java:119)
at org.apache.hadoop.hdfs.DFSInputStream.init(DFSInputStream.java:112)
at org.apache.hadoop.hdfs.DFSClient.open(DFSClient.java:928)
at
org.apache.hadoop.hdfs.DistributedFileSystem.open(DistributedFileSystem.java:212)
at
org.apache.hadoop.hdfs.DistributedFileSystem.open(DistributedFileSystem.java:75)
at
org.apache.hadoop.io.SequenceFile$Reader.openFile(SequenceFile.java:1768)
at
org.apache.hadoop.hbase.regionserver.wal.SequenceFileLogReader$WALReader.openFile(SequenceFileLogReader.java:66)
at
org.apache.hadoop.io.SequenceFile$Reader.init(SequenceFile.java:1688)
at
org.apache.hadoop.io.SequenceFile$Reader.init(SequenceFile.java:1709)
at
org.apache.hadoop.hbase.regionserver.wal.SequenceFileLogReader$WALReader.init(SequenceFileLogReader.java:58)
at
org.apache.hadoop.hbase.regionserver.wal.SequenceFileLogReader.init(SequenceFileLogReader.java:166)
at
org.apache.hadoop.hbase.regionserver.wal.HLog.getReader(HLog.java:659)
at
org.apache.hadoop.hbase.regionserver.wal.TestLogRolling.testLogRollOnPipelineRestart(TestLogRolling.java:498)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:597)
at
org.junit.runners.model.FrameworkMethod$1.runReflectiveCall(FrameworkMethod.java:45)
at
org.junit.internal.runners.model.ReflectiveCallable.run(ReflectiveCallable.java:15)
at
org.junit.runners.model.FrameworkMethod.invokeExplosively(FrameworkMethod.java:42)
at
org.junit.internal.runners.statements.InvokeMethod.evaluate(InvokeMethod.java:20)
at
org.junit.internal.runners.statements.RunBefores.evaluate(RunBefores.java:28)
at
org.junit.internal.runners.statements.RunAfters.evaluate(RunAfters.java:30)
at org.junit.runners.ParentRunner.runLeaf(ParentRunner.java:263)
at
org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:68)
at
org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:47)
at org.junit.runners.ParentRunner$3.run(ParentRunner.java:231)
at org.junit.runners.ParentRunner$1.schedule(ParentRunner.java:60)
at org.junit.runners.ParentRunner.runChildren(ParentRunner.java:229)
at org.junit.runners.ParentRunner.access$000(ParentRunner.java:50)
at org.junit.runners.ParentRunner$2.evaluate(ParentRunner.java:222)
at
org.junit.internal.runners.statements.RunBefores.evaluate(RunBefores.java:28)
at org.junit.runners.ParentRunner.run(ParentRunner.java:300)
at
org.eclipse.jdt.internal.junit4.runner.JUnit4TestReference.run(JUnit4TestReference.java:50)
at
org.eclipse.jdt.internal.junit.runner.TestExecution.run(TestExecution.java:38)
at
org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.runTests(RemoteTestRunner.java:467)
at
org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.runTests(RemoteTestRunner.java:683)
at
org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.run(RemoteTestRunner.java:390)
at
[jira] [Commented] (HBASE-5992) Generalization of region move implementation + manage draining servers in bulk assign
[ https://issues.apache.org/jira/browse/HBASE-5992?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13274099#comment-13274099 ] Hudson commented on HBASE-5992: --- Integrated in HBase-TRUNK-on-Hadoop-2.0.0 #3 (See [https://builds.apache.org/job/HBase-TRUNK-on-Hadoop-2.0.0/3/]) HBASE-5992 Generalization of region move implementation + manage draining servers in bulk assign (N Keywal) (Revision 1337641) Result = FAILURE tedyu : Files : * /hbase/trunk/src/main/java/org/apache/hadoop/hbase/master/AssignmentManager.java * /hbase/trunk/src/main/java/org/apache/hadoop/hbase/master/HMaster.java * /hbase/trunk/src/main/java/org/apache/hadoop/hbase/master/ServerManager.java * /hbase/trunk/src/main/java/org/apache/hadoop/hbase/master/handler/CreateTableHandler.java * /hbase/trunk/src/main/java/org/apache/hadoop/hbase/master/handler/ServerShutdownHandler.java * /hbase/trunk/src/main/java/org/apache/hadoop/hbase/regionserver/HRegionServer.java * /hbase/trunk/src/test/java/org/apache/hadoop/hbase/TestDrainingServer.java * /hbase/trunk/src/test/java/org/apache/hadoop/hbase/master/TestAssignmentManager.java Generalization of region move implementation + manage draining servers in bulk assign - Key: HBASE-5992 URL: https://issues.apache.org/jira/browse/HBASE-5992 Project: HBase Issue Type: Bug Components: master, regionserver Affects Versions: 0.96.0 Reporter: nkeywal Assignee: nkeywal Priority: Minor Attachments: 5992.v11.patch, 5992.v2.patch, 5992.v5.patch, 5992.v5.patch The region move implementation now has now a similar behavior whatever the destination server is specified or not. This allows: - to benefit from the improvement in HBASE-5877 - as a side effect to have the coprocessors calls when the destination server is not specified This includes various fixes around draining servers. Draining servers were not excluded during a bulk assign. This is now fixed. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (HBASE-5984) TestLogRolling.testLogRollOnPipelineRestart failed with HADOOP 2.0.0
[
https://issues.apache.org/jira/browse/HBASE-5984?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13274098#comment-13274098
]
Hudson commented on HBASE-5984:
---
Integrated in HBase-TRUNK-on-Hadoop-2.0.0 #3 (See
[https://builds.apache.org/job/HBase-TRUNK-on-Hadoop-2.0.0/3/])
HBASE-5984 TestLogRolling.testLogRollOnPipelineRestart failed with HADOOP
2.0.0 (Revision 1337697)
Result = FAILURE
stack :
Files :
*
/hbase/trunk/src/test/java/org/apache/hadoop/hbase/regionserver/wal/TestLogRolling.java
TestLogRolling.testLogRollOnPipelineRestart failed with HADOOP 2.0.0
Key: HBASE-5984
URL: https://issues.apache.org/jira/browse/HBASE-5984
Project: HBase
Issue Type: Test
Components: test
Affects Versions: 0.96.0
Reporter: Jimmy Xiang
Assignee: Jimmy Xiang
Fix For: 0.96.0
Attachments: hbase_5984.patch
java.io.IOException: Cannot obtain block length for
LocatedBlock{BP-1455809779-127.0.0.1-1336670196362:blk_-6960847342982670493_1028;
getBlockSize()=1474; corrupt=false; offset=0; locs=[127.0.0.1:58343,
127.0.0.1:48427]}
at
org.apache.hadoop.hdfs.DFSInputStream.readBlockLength(DFSInputStream.java:232)
at
org.apache.hadoop.hdfs.DFSInputStream.fetchLocatedBlocksAndGetLastBlockLength(DFSInputStream.java:177)
at
org.apache.hadoop.hdfs.DFSInputStream.openInfo(DFSInputStream.java:119)
at org.apache.hadoop.hdfs.DFSInputStream.init(DFSInputStream.java:112)
at org.apache.hadoop.hdfs.DFSClient.open(DFSClient.java:928)
at
org.apache.hadoop.hdfs.DistributedFileSystem.open(DistributedFileSystem.java:212)
at
org.apache.hadoop.hdfs.DistributedFileSystem.open(DistributedFileSystem.java:75)
at
org.apache.hadoop.io.SequenceFile$Reader.openFile(SequenceFile.java:1768)
at
org.apache.hadoop.hbase.regionserver.wal.SequenceFileLogReader$WALReader.openFile(SequenceFileLogReader.java:66)
at
org.apache.hadoop.io.SequenceFile$Reader.init(SequenceFile.java:1688)
at
org.apache.hadoop.io.SequenceFile$Reader.init(SequenceFile.java:1709)
at
org.apache.hadoop.hbase.regionserver.wal.SequenceFileLogReader$WALReader.init(SequenceFileLogReader.java:58)
at
org.apache.hadoop.hbase.regionserver.wal.SequenceFileLogReader.init(SequenceFileLogReader.java:166)
at
org.apache.hadoop.hbase.regionserver.wal.HLog.getReader(HLog.java:659)
at
org.apache.hadoop.hbase.regionserver.wal.TestLogRolling.testLogRollOnPipelineRestart(TestLogRolling.java:498)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:597)
at
org.junit.runners.model.FrameworkMethod$1.runReflectiveCall(FrameworkMethod.java:45)
at
org.junit.internal.runners.model.ReflectiveCallable.run(ReflectiveCallable.java:15)
at
org.junit.runners.model.FrameworkMethod.invokeExplosively(FrameworkMethod.java:42)
at
org.junit.internal.runners.statements.InvokeMethod.evaluate(InvokeMethod.java:20)
at
org.junit.internal.runners.statements.RunBefores.evaluate(RunBefores.java:28)
at
org.junit.internal.runners.statements.RunAfters.evaluate(RunAfters.java:30)
at org.junit.runners.ParentRunner.runLeaf(ParentRunner.java:263)
at
org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:68)
at
org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:47)
at org.junit.runners.ParentRunner$3.run(ParentRunner.java:231)
at org.junit.runners.ParentRunner$1.schedule(ParentRunner.java:60)
at org.junit.runners.ParentRunner.runChildren(ParentRunner.java:229)
at org.junit.runners.ParentRunner.access$000(ParentRunner.java:50)
at org.junit.runners.ParentRunner$2.evaluate(ParentRunner.java:222)
at
org.junit.internal.runners.statements.RunBefores.evaluate(RunBefores.java:28)
at org.junit.runners.ParentRunner.run(ParentRunner.java:300)
at
org.eclipse.jdt.internal.junit4.runner.JUnit4TestReference.run(JUnit4TestReference.java:50)
at
org.eclipse.jdt.internal.junit.runner.TestExecution.run(TestExecution.java:38)
at
org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.runTests(RemoteTestRunner.java:467)
at
org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.runTests(RemoteTestRunner.java:683)
at
org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.run(RemoteTestRunner.java:390)
at
[jira] [Commented] (HBASE-5990) TestHCM failed with Hadoop 2.0.0
[ https://issues.apache.org/jira/browse/HBASE-5990?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13274100#comment-13274100 ] Hudson commented on HBASE-5990: --- Integrated in HBase-TRUNK-on-Hadoop-2.0.0 #3 (See [https://builds.apache.org/job/HBase-TRUNK-on-Hadoop-2.0.0/3/]) HBASE-5990 TestHCM failed with Hadoop 2.0.0 (Revision 1337695) Result = FAILURE stack : Files : * /hbase/trunk/src/main/java/org/apache/hadoop/hbase/RegionMovedException.java TestHCM failed with Hadoop 2.0.0 Key: HBASE-5990 URL: https://issues.apache.org/jira/browse/HBASE-5990 Project: HBase Issue Type: Bug Components: client, test Affects Versions: 0.96.0 Reporter: Jimmy Xiang Assignee: Jimmy Xiang Fix For: 0.96.0 Attachments: hbase-5990.patch, hbase_5990_v2.patch Running org.apache.hadoop.hbase.client.TestHCM Tests run: 7, Failures: 1, Errors: 0, Skipped: 0, Time elapsed: 11.742 sec FAILURE! Failed tests: testRegionCaching(org.apache.hadoop.hbase.client.TestHCM) -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (HBASE-5998) Bulk assignment: regionserver optimization by using a temporary cache for table descriptors when receveing an open regions request
[ https://issues.apache.org/jira/browse/HBASE-5998?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13276300#comment-13276300 ] Hudson commented on HBASE-5998: --- Integrated in HBase-TRUNK #2887 (See [https://builds.apache.org/job/HBase-TRUNK/2887/]) HBASE-5998 Bulk assignment: regionserver optimization by using a temporary cache for table descriptors when receveing an open regions request (N Keywal) (Revision 1338916) Result = SUCCESS tedyu : Files : * /hbase/trunk/src/main/java/org/apache/hadoop/hbase/regionserver/HRegionServer.java Bulk assignment: regionserver optimization by using a temporary cache for table descriptors when receveing an open regions request -- Key: HBASE-5998 URL: https://issues.apache.org/jira/browse/HBASE-5998 Project: HBase Issue Type: Improvement Components: regionserver Affects Versions: 0.96.0 Reporter: nkeywal Assignee: nkeywal Priority: Minor Fix For: 0.96.0 Attachments: 5998.v2.patch, 5998.v3.patch During the assignment, on the regionserver, before creating the handlers we load the table description. Even if there is a cache, we check the timestamps for each region, while it's not necessary. The test below is just with one node, with more nodes the benefit will improve. By limiting the time spent in HRegion#openRegion we increase the parallelization during cluster startup, as the master is using a pool of threads to call the RS. -- Without the fix 2012-05-14 11:40:52,501 DEBUG org.apache.hadoop.hbase.master.AssignmentManager: Bulk assigning 1193 region(s) to localhost,11003,1336988444043 2012-05-14 11:41:09,947 DEBUG org.apache.hadoop.hbase.master.AssignmentManager: Bulk assigning done for localhost,11003,1336988444043 -- With the fix 2012-05-14 11:34:40,444 DEBUG org.apache.hadoop.hbase.master.AssignmentManager: Bulk assigning 1193 region(s) to localhost,11003,1336988444043 2012-05-14 11:34:40,929 DEBUG org.apache.hadoop.hbase.master.AssignmentManager: Bulk assigning done for localhost,11003,1336988065948 -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (HBASE-6003) [refguide] performance.xml - fixed 2 links to Case Studies that were ???
[ https://issues.apache.org/jira/browse/HBASE-6003?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13276301#comment-13276301 ] Hudson commented on HBASE-6003: --- Integrated in HBase-TRUNK #2887 (See [https://builds.apache.org/job/HBase-TRUNK/2887/]) hbase-6003. fixed 2 links in Performance.xml that should have been going to case-studies chapter. (Revision 1338899) Result = SUCCESS [refguide] performance.xml - fixed 2 links to Case Studies that were ??? - Key: HBASE-6003 URL: https://issues.apache.org/jira/browse/HBASE-6003 Project: HBase Issue Type: Bug Reporter: Doug Meil Assignee: Doug Meil Priority: Minor Attachments: performance_hbase_6003.xml.patch There were 2 links in the performance chapter that were ??? links that should have been going to Case Studies. Corrected them so that they weren't dead links. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (HBASE-6003) [refguide] performance.xml - fixed 2 links to Case Studies that were ???
[ https://issues.apache.org/jira/browse/HBASE-6003?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13276345#comment-13276345 ] Hudson commented on HBASE-6003: --- Integrated in HBase-TRUNK-on-Hadoop-2.0.0 #5 (See [https://builds.apache.org/job/HBase-TRUNK-on-Hadoop-2.0.0/5/]) hbase-6003. fixed 2 links in Performance.xml that should have been going to case-studies chapter. (Revision 1338899) Result = FAILURE [refguide] performance.xml - fixed 2 links to Case Studies that were ??? - Key: HBASE-6003 URL: https://issues.apache.org/jira/browse/HBASE-6003 Project: HBase Issue Type: Bug Reporter: Doug Meil Assignee: Doug Meil Priority: Minor Attachments: performance_hbase_6003.xml.patch There were 2 links in the performance chapter that were ??? links that should have been going to Case Studies. Corrected them so that they weren't dead links. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (HBASE-5998) Bulk assignment: regionserver optimization by using a temporary cache for table descriptors when receveing an open regions request
[ https://issues.apache.org/jira/browse/HBASE-5998?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13276344#comment-13276344 ] Hudson commented on HBASE-5998: --- Integrated in HBase-TRUNK-on-Hadoop-2.0.0 #5 (See [https://builds.apache.org/job/HBase-TRUNK-on-Hadoop-2.0.0/5/]) HBASE-5998 Bulk assignment: regionserver optimization by using a temporary cache for table descriptors when receveing an open regions request (N Keywal) (Revision 1338916) Result = FAILURE tedyu : Files : * /hbase/trunk/src/main/java/org/apache/hadoop/hbase/regionserver/HRegionServer.java Bulk assignment: regionserver optimization by using a temporary cache for table descriptors when receveing an open regions request -- Key: HBASE-5998 URL: https://issues.apache.org/jira/browse/HBASE-5998 Project: HBase Issue Type: Improvement Components: regionserver Affects Versions: 0.96.0 Reporter: nkeywal Assignee: nkeywal Priority: Minor Fix For: 0.96.0 Attachments: 5998.v2.patch, 5998.v3.patch During the assignment, on the regionserver, before creating the handlers we load the table description. Even if there is a cache, we check the timestamps for each region, while it's not necessary. The test below is just with one node, with more nodes the benefit will improve. By limiting the time spent in HRegion#openRegion we increase the parallelization during cluster startup, as the master is using a pool of threads to call the RS. -- Without the fix 2012-05-14 11:40:52,501 DEBUG org.apache.hadoop.hbase.master.AssignmentManager: Bulk assigning 1193 region(s) to localhost,11003,1336988444043 2012-05-14 11:41:09,947 DEBUG org.apache.hadoop.hbase.master.AssignmentManager: Bulk assigning done for localhost,11003,1336988444043 -- With the fix 2012-05-14 11:34:40,444 DEBUG org.apache.hadoop.hbase.master.AssignmentManager: Bulk assigning 1193 region(s) to localhost,11003,1336988444043 2012-05-14 11:34:40,929 DEBUG org.apache.hadoop.hbase.master.AssignmentManager: Bulk assigning done for localhost,11003,1336988065948 -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (HBASE-3877) Determine Proper Defaults for Compaction ThreadPools
[ https://issues.apache.org/jira/browse/HBASE-3877?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13276346#comment-13276346 ] Hudson commented on HBASE-3877: --- Integrated in HBase-TRUNK-on-Hadoop-2.0.0 #5 (See [https://builds.apache.org/job/HBase-TRUNK-on-Hadoop-2.0.0/5/]) [HBASE-5867] Improve Compaction Throttle Default Summary: We recently had a production issue where our compactions fell behind because our compaction throttle was improperly tuned and accidentally upgraded all compactions to the large pool. The default from HBASE-3877 makes 1 bad assumption: the default number of flushed files in a compaction. MinFilesToCompact should be taken into consideration. As a default, it is less damaging for the large thread to be slightly higher than it needs to be and only get timed-majors versus having everything accidentally promoted. Test Plan: - mvn test Reviewers: JIRA, Kannan, Liyin Reviewed By: Kannan CC: stack Differential Revision: https://reviews.facebook.net/D2943 (Revision 1338809) Result = FAILURE nspiegelberg : Files : * /hbase/trunk/src/main/java/org/apache/hadoop/hbase/regionserver/CompactSplitThread.java * /hbase/trunk/src/main/java/org/apache/hadoop/hbase/regionserver/Store.java Determine Proper Defaults for Compaction ThreadPools Key: HBASE-3877 URL: https://issues.apache.org/jira/browse/HBASE-3877 Project: HBase Issue Type: Improvement Components: regionserver Affects Versions: 0.92.0 Reporter: Nicolas Spiegelberg Assignee: Nicolas Spiegelberg Priority: Trivial Labels: compaction With the introduction of HBASE-1476, we now have multithreaded compactions + 2 different ThreadPools for large and small compactions. However, this is disabled by default until we can determine a proper default throttle point. Opening this JIRA to log all discussion on how to select a good default for this case. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (HBASE-5867) Improve Compaction Throttle Default
[ https://issues.apache.org/jira/browse/HBASE-5867?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13276347#comment-13276347 ] Hudson commented on HBASE-5867: --- Integrated in HBase-TRUNK-on-Hadoop-2.0.0 #5 (See [https://builds.apache.org/job/HBase-TRUNK-on-Hadoop-2.0.0/5/]) [HBASE-5867] Improve Compaction Throttle Default Summary: We recently had a production issue where our compactions fell behind because our compaction throttle was improperly tuned and accidentally upgraded all compactions to the large pool. The default from HBASE-3877 makes 1 bad assumption: the default number of flushed files in a compaction. MinFilesToCompact should be taken into consideration. As a default, it is less damaging for the large thread to be slightly higher than it needs to be and only get timed-majors versus having everything accidentally promoted. Test Plan: - mvn test Reviewers: JIRA, Kannan, Liyin Reviewed By: Kannan CC: stack Differential Revision: https://reviews.facebook.net/D2943 (Revision 1338809) Result = FAILURE nspiegelberg : Files : * /hbase/trunk/src/main/java/org/apache/hadoop/hbase/regionserver/CompactSplitThread.java * /hbase/trunk/src/main/java/org/apache/hadoop/hbase/regionserver/Store.java Improve Compaction Throttle Default --- Key: HBASE-5867 URL: https://issues.apache.org/jira/browse/HBASE-5867 Project: HBase Issue Type: Improvement Reporter: Nicolas Spiegelberg Assignee: Nicolas Spiegelberg Priority: Minor Fix For: 0.96.0 Attachments: D2943.1.patch, HBASE-5867-trunk.patch We recently had a production issue where our compactions fell behind because our compaction throttle was improperly tuned and accidentally upgraded all compactions to the large pool. The default from HBASE-3877 makes 1 bad assumption: the default number of flushed files in a compaction. Currently the algorithm is: throttleSize ~= flushSize * 2 This assumes that the basic compaction utilizes 3 files and that all 3 files are compressed. In this case, hbase.hstore.compaction.min == 6 the values were not very compressible. Both conditions should be taken into consideration. As a default, it is less damaging for the large thread to be slightly higher than it needs to be versus having everything accidentally promoted. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (HBASE-6019) [refGuide] ported pseudo-distributed.html page to RefGuide Config chapter
[ https://issues.apache.org/jira/browse/HBASE-6019?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13276878#comment-13276878 ] Hudson commented on HBASE-6019: --- Integrated in HBase-TRUNK #2888 (See [https://builds.apache.org/job/HBase-TRUNK/2888/]) hbase-6019. porting pseudo-dist html page to RefGuide Config chapter. (Revision 1339225) Result = FAILURE [refGuide] ported pseudo-distributed.html page to RefGuide Config chapter - Key: HBASE-6019 URL: https://issues.apache.org/jira/browse/HBASE-6019 Project: HBase Issue Type: Improvement Reporter: Doug Meil Assignee: Doug Meil Priority: Minor Attachments: hbase_hbase_6019.patch Ported the separate pseudo-distributed.html page that existed outside the RefGuie into the Configuration chapter. configuration.xml * Added an example of a local pseudo-dist HDFS config file (the refguide didn't have this) * Ported pseudo-dist extras to pseudo-dist section. pseudo-distributed.xml * This is the old page. I'm leaving this backward compatibility so that the old links don't break, although the only thing this says now is the content has been moved to the RefGuide site.xml * Removing pseudo-dist extras from the left-hand nav. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (HBASE-6019) [refGuide] ported pseudo-distributed.html page to RefGuide Config chapter
[ https://issues.apache.org/jira/browse/HBASE-6019?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13277271#comment-13277271 ] Hudson commented on HBASE-6019: --- Integrated in HBase-TRUNK-on-Hadoop-2.0.0 #6 (See [https://builds.apache.org/job/HBase-TRUNK-on-Hadoop-2.0.0/6/]) hbase-6019. porting pseudo-dist html page to RefGuide Config chapter. (Revision 1339225) Result = FAILURE [refGuide] ported pseudo-distributed.html page to RefGuide Config chapter - Key: HBASE-6019 URL: https://issues.apache.org/jira/browse/HBASE-6019 Project: HBase Issue Type: Improvement Reporter: Doug Meil Assignee: Doug Meil Priority: Minor Attachments: hbase_hbase_6019.patch Ported the separate pseudo-distributed.html page that existed outside the RefGuie into the Configuration chapter. configuration.xml * Added an example of a local pseudo-dist HDFS config file (the refguide didn't have this) * Ported pseudo-dist extras to pseudo-dist section. pseudo-distributed.xml * This is the old page. I'm leaving this backward compatibility so that the old links don't break, although the only thing this says now is the content has been moved to the RefGuide site.xml * Removing pseudo-dist extras from the left-hand nav. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (HBASE-5935) Add Region-level PB-based calls to HMasterInterface
[ https://issues.apache.org/jira/browse/HBASE-5935?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13277742#comment-13277742 ] Hudson commented on HBASE-5935: --- Integrated in HBase-TRUNK-on-Hadoop-2.0.0 #7 (See [https://builds.apache.org/job/HBase-TRUNK-on-Hadoop-2.0.0/7/]) HBASE-5935 Add Region-level PB-based calls to HMasterInterface (Revision 1339488) Result = FAILURE stack : Files : * /hbase/trunk/src/main/java/org/apache/hadoop/hbase/client/HBaseAdmin.java * /hbase/trunk/src/main/java/org/apache/hadoop/hbase/ipc/HMasterInterface.java * /hbase/trunk/src/main/java/org/apache/hadoop/hbase/master/HMaster.java * /hbase/trunk/src/main/java/org/apache/hadoop/hbase/protobuf/RequestConverter.java * /hbase/trunk/src/main/java/org/apache/hadoop/hbase/protobuf/generated/MasterProtos.java * /hbase/trunk/src/main/protobuf/RegionServerStatus.proto * /hbase/trunk/src/test/java/org/apache/hadoop/hbase/TestDrainingServer.java * /hbase/trunk/src/test/java/org/apache/hadoop/hbase/coprocessor/TestMasterObserver.java Add Region-level PB-based calls to HMasterInterface --- Key: HBASE-5935 URL: https://issues.apache.org/jira/browse/HBASE-5935 Project: HBase Issue Type: Task Components: ipc, master, migration Reporter: Gregory Chanan Assignee: Gregory Chanan Fix For: 0.96.0 Attachments: HBASE-5935-v2.patch, HBASE-5935-v2.patch, HBASE-5935-v3.patch This should be a subtask of HBASE-5445, but since that is a subtask, I can't also make this a subtask (apparently). This is for converting the region-level calls, i.e.: moveRegion assignRegion unassignRegion -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (HBASE-5826) Improve sync of HLog edits
[ https://issues.apache.org/jira/browse/HBASE-5826?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13277951#comment-13277951 ] Hudson commented on HBASE-5826: --- Integrated in HBase-TRUNK #2890 (See [https://builds.apache.org/job/HBase-TRUNK/2890/]) HBASE-5826 Improve sync of HLog edits (Todd) (Revision 1339671) Result = FAILURE tedyu : Files : * /hbase/trunk/src/main/java/org/apache/hadoop/hbase/regionserver/wal/HLog.java * /hbase/trunk/src/main/java/org/apache/hadoop/hbase/regionserver/wal/SequenceFileLogWriter.java * /hbase/trunk/src/test/java/org/apache/hadoop/hbase/regionserver/wal/TestHLog.java Improve sync of HLog edits -- Key: HBASE-5826 URL: https://issues.apache.org/jira/browse/HBASE-5826 Project: HBase Issue Type: Improvement Reporter: Zhihong Yu Assignee: Todd Lipcon Fix For: 0.96.0 Attachments: 5826-v2.txt, 5826-v3.txt, 5826-v4.txt, 5826.txt HBASE-5782 solved the correctness issue for the sync of HLog edits. Todd provided a patch that would achieve higher throughput. This JIRA is a continuation of Todd's work submitted there. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (HBASE-5826) Improve sync of HLog edits
[ https://issues.apache.org/jira/browse/HBASE-5826?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13277992#comment-13277992 ] Hudson commented on HBASE-5826: --- Integrated in HBase-TRUNK #2891 (See [https://builds.apache.org/job/HBase-TRUNK/2891/]) HBASE-5826 Revert, Todd has review comments pending. (Revision 1339673) Result = SUCCESS tedyu : Files : * /hbase/trunk/src/main/java/org/apache/hadoop/hbase/regionserver/wal/HLog.java * /hbase/trunk/src/main/java/org/apache/hadoop/hbase/regionserver/wal/SequenceFileLogWriter.java * /hbase/trunk/src/test/java/org/apache/hadoop/hbase/regionserver/wal/TestHLog.java Improve sync of HLog edits -- Key: HBASE-5826 URL: https://issues.apache.org/jira/browse/HBASE-5826 Project: HBase Issue Type: Improvement Reporter: Zhihong Yu Assignee: Todd Lipcon Fix For: 0.96.0 Attachments: 5826-v2.txt, 5826-v3.txt, 5826-v4.txt, 5826.txt HBASE-5782 solved the correctness issue for the sync of HLog edits. Todd provided a patch that would achieve higher throughput. This JIRA is a continuation of Todd's work submitted there. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (HBASE-6029) HBCK doesn't recover Balance switch if exception occurs in onlineHbck()
[ https://issues.apache.org/jira/browse/HBASE-6029?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13277993#comment-13277993 ] Hudson commented on HBASE-6029: --- Integrated in HBase-TRUNK #2891 (See [https://builds.apache.org/job/HBase-TRUNK/2891/]) HBASE-6029 HBCK doesn't recover Balance switch if exception occurs in onlineHbck() (Maryann) (Revision 1339689) Result = SUCCESS tedyu : Files : * /hbase/trunk/src/main/java/org/apache/hadoop/hbase/util/HBaseFsck.java HBCK doesn't recover Balance switch if exception occurs in onlineHbck() --- Key: HBASE-6029 URL: https://issues.apache.org/jira/browse/HBASE-6029 Project: HBase Issue Type: Bug Components: hbck Affects Versions: 0.94.0 Reporter: Maryann Xue Assignee: Maryann Xue Fix For: 0.96.0, 0.94.1 Attachments: HBASE-6029.patch -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (HBASE-6029) HBCK doesn't recover Balance switch if exception occurs in onlineHbck()
[ https://issues.apache.org/jira/browse/HBASE-6029?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13278024#comment-13278024 ] Hudson commented on HBASE-6029: --- Integrated in HBase-0.94 #193 (See [https://builds.apache.org/job/HBase-0.94/193/]) HBASE-6029 HBCK doesn't recover Balance switch if exception occurs in onlineHbck() (Maryann) (Revision 1339688) Result = SUCCESS tedyu : Files : * /hbase/branches/0.94/src/main/java/org/apache/hadoop/hbase/util/HBaseFsck.java HBCK doesn't recover Balance switch if exception occurs in onlineHbck() --- Key: HBASE-6029 URL: https://issues.apache.org/jira/browse/HBASE-6029 Project: HBase Issue Type: Bug Components: hbck Affects Versions: 0.94.0 Reporter: Maryann Xue Assignee: Maryann Xue Fix For: 0.96.0, 0.94.1 Attachments: HBASE-6029.patch -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (HBASE-6001) Upgrade slf4j to 1.6.1
[ https://issues.apache.org/jira/browse/HBASE-6001?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13278165#comment-13278165 ] Hudson commented on HBASE-6001: --- Integrated in HBase-TRUNK #2892 (See [https://builds.apache.org/job/HBase-TRUNK/2892/]) HBASE-6001. Upgrade slf4j to 1.6.1 (Revision 1339788) Result = SUCCESS apurtell : Files : * /hbase/trunk/pom.xml Upgrade slf4j to 1.6.1 -- Key: HBASE-6001 URL: https://issues.apache.org/jira/browse/HBASE-6001 Project: HBase Issue Type: Task Reporter: Jimmy Xiang Assignee: Jimmy Xiang Fix For: 0.92.2, 0.96.0, 0.94.1 Attachments: hbase-6001.patch We need to upgrade slf4j to 1.6.1 since other hadoop components use 1.6.1 now. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (HBASE-6004) Adding more logging to help debugging MR job
[ https://issues.apache.org/jira/browse/HBASE-6004?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13278172#comment-13278172 ] Hudson commented on HBASE-6004: --- Integrated in HBase-0.94 #194 (See [https://builds.apache.org/job/HBase-0.94/194/]) HBASE-6004. Adding more logging to help debugging MR job (Jimmy Xiang) (Revision 1339809) Result = FAILURE apurtell : Files : * /hbase/branches/0.94/src/main/java/org/apache/hadoop/hbase/client/ScannerCallable.java * /hbase/branches/0.94/src/main/java/org/apache/hadoop/hbase/mapred/TableRecordReaderImpl.java * /hbase/branches/0.94/src/main/java/org/apache/hadoop/hbase/mapreduce/TableRecordReaderImpl.java Adding more logging to help debugging MR job Key: HBASE-6004 URL: https://issues.apache.org/jira/browse/HBASE-6004 Project: HBase Issue Type: Improvement Affects Versions: 0.94.0, 0.96.0 Reporter: Jimmy Xiang Assignee: Jimmy Xiang Priority: Minor Fix For: 0.94.0, 0.96.0 Attachments: hbase-6004.patch, hbase-6004_v2-0.94.patch, hbase-6004_v2.patch MR job sometime fails because scanner expired. In this case, it will be helpful to know the last successful row, the ip of the region sever, and so on. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (HBASE-6001) Upgrade slf4j to 1.6.1
[ https://issues.apache.org/jira/browse/HBASE-6001?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13278173#comment-13278173 ] Hudson commented on HBASE-6001: --- Integrated in HBase-0.94 #194 (See [https://builds.apache.org/job/HBase-0.94/194/]) HBASE-6001. Upgrade slf4j to 1.6.1 (Revision 1339790) Result = FAILURE apurtell : Files : * /hbase/branches/0.94/pom.xml Upgrade slf4j to 1.6.1 -- Key: HBASE-6001 URL: https://issues.apache.org/jira/browse/HBASE-6001 Project: HBase Issue Type: Task Reporter: Jimmy Xiang Assignee: Jimmy Xiang Fix For: 0.92.2, 0.96.0, 0.94.1 Attachments: hbase-6001.patch We need to upgrade slf4j to 1.6.1 since other hadoop components use 1.6.1 now. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (HBASE-6005) Broken Links on Homepages
[ https://issues.apache.org/jira/browse/HBASE-6005?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13278246#comment-13278246 ] Hudson commented on HBASE-6005: --- Integrated in HBase-TRUNK #2893 (See [https://builds.apache.org/job/HBase-TRUNK/2893/]) HBASE-6005 Broken Links on Homepages (Revision 1339805) Result = SUCCESS stack : Files : * /hbase/trunk/src/docbkx/book.xml * /hbase/trunk/src/docbkx/preface.xml * /hbase/trunk/src/main/javadoc/overview.html * /hbase/trunk/src/site/xdoc/cygwin.xml * /hbase/trunk/src/site/xdoc/old_news.xml Broken Links on Homepages - Key: HBASE-6005 URL: https://issues.apache.org/jira/browse/HBASE-6005 Project: HBase Issue Type: Task Components: documentation Reporter: Elliott Clark Assignee: Elliott Clark Priority: Minor Fix For: 0.96.0 Attachments: HBASE-6005-0.patch, HBASE-6005-addendum-0.patch I ran w3c's link checker on the homepage and there a few broken links. I'll start getting a patch to fix the links that were broken. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (HBASE-6004) Adding more logging to help debugging MR job
[ https://issues.apache.org/jira/browse/HBASE-6004?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13278245#comment-13278245 ] Hudson commented on HBASE-6004: --- Integrated in HBase-TRUNK #2893 (See [https://builds.apache.org/job/HBase-TRUNK/2893/]) HBASE-6004. Adding more logging to help debugging MR job (Jimmy Xiang) (Revision 1339806) Result = SUCCESS apurtell : Files : * /hbase/trunk/src/main/java/org/apache/hadoop/hbase/client/ScannerCallable.java * /hbase/trunk/src/main/java/org/apache/hadoop/hbase/mapred/TableRecordReaderImpl.java * /hbase/trunk/src/main/java/org/apache/hadoop/hbase/mapreduce/TableRecordReaderImpl.java Adding more logging to help debugging MR job Key: HBASE-6004 URL: https://issues.apache.org/jira/browse/HBASE-6004 Project: HBase Issue Type: Improvement Affects Versions: 0.94.0, 0.96.0 Reporter: Jimmy Xiang Assignee: Jimmy Xiang Priority: Minor Fix For: 0.94.0, 0.96.0 Attachments: hbase-6004.patch, hbase-6004_v2-0.94.patch, hbase-6004_v2.patch MR job sometime fails because scanner expired. In this case, it will be helpful to know the last successful row, the ip of the region sever, and so on. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (HBASE-6010) Security audit logger configuration for log4j
[ https://issues.apache.org/jira/browse/HBASE-6010?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13278247#comment-13278247 ] Hudson commented on HBASE-6010: --- Integrated in HBase-TRUNK #2893 (See [https://builds.apache.org/job/HBase-TRUNK/2893/]) HBASE-6010. Security audit logger configuration for log4j (Revision 1339817) Result = SUCCESS apurtell : Files : * /hbase/trunk/bin/hbase * /hbase/trunk/bin/hbase-daemon.sh * /hbase/trunk/conf/log4j.properties Security audit logger configuration for log4j - Key: HBASE-6010 URL: https://issues.apache.org/jira/browse/HBASE-6010 Project: HBase Issue Type: Improvement Affects Versions: 0.92.2, 0.96.0, 0.94.1 Reporter: Andrew Purtell Assignee: Andrew Purtell Priority: Minor Fix For: 0.96.0, 0.94.1 Attachments: 6010.patch Set up a logger for security audit messages just as Hadoop core does. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (HBASE-5802) Change the default metrics class to NullContextWithUpdateThread
[ https://issues.apache.org/jira/browse/HBASE-5802?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13278248#comment-13278248 ] Hudson commented on HBASE-5802: --- Integrated in HBase-TRUNK #2893 (See [https://builds.apache.org/job/HBase-TRUNK/2893/]) HBASE-5802 Change the default metrics class to NullContextWithUpdateThread (Revision 1339831) Result = SUCCESS stack : Files : * /hbase/trunk/conf/hadoop-metrics.properties * /hbase/trunk/src/site/xdoc/metrics.xml Change the default metrics class to NullContextWithUpdateThread --- Key: HBASE-5802 URL: https://issues.apache.org/jira/browse/HBASE-5802 Project: HBase Issue Type: Improvement Reporter: Elliott Clark Assignee: Elliott Clark Priority: Minor Fix For: 0.94.1 Attachments: HBASE-5802-0.patch, HBASE-5802-1.patch, HBASE-5802-2.patch Since lots more metrics are being placed into the Dynamic metrics bucket changing the default class to NullContextWithUpdateThread seems like it might be worth it. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (HBASE-6010) Security audit logger configuration for log4j
[ https://issues.apache.org/jira/browse/HBASE-6010?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13278253#comment-13278253 ] Hudson commented on HBASE-6010: --- Integrated in HBase-0.94 #195 (See [https://builds.apache.org/job/HBase-0.94/195/]) HBASE-6010. Security audit logger configuration for log4j (Revision 1339819) Result = SUCCESS apurtell : Files : * /hbase/branches/0.94/bin/hbase * /hbase/branches/0.94/bin/hbase-daemon.sh * /hbase/branches/0.94/conf/log4j.properties Security audit logger configuration for log4j - Key: HBASE-6010 URL: https://issues.apache.org/jira/browse/HBASE-6010 Project: HBase Issue Type: Improvement Affects Versions: 0.92.2, 0.96.0, 0.94.1 Reporter: Andrew Purtell Assignee: Andrew Purtell Priority: Minor Fix For: 0.96.0, 0.94.1 Attachments: 6010.patch Set up a logger for security audit messages just as Hadoop core does. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (HBASE-5802) Change the default metrics class to NullContextWithUpdateThread
[ https://issues.apache.org/jira/browse/HBASE-5802?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13278254#comment-13278254 ] Hudson commented on HBASE-5802: --- Integrated in HBase-0.94 #195 (See [https://builds.apache.org/job/HBase-0.94/195/]) HBASE-5802 Change the default metrics class to NullContextWithUpdateThread (Revision 1339832) Result = SUCCESS stack : Files : * /hbase/branches/0.94/conf/hadoop-metrics.properties * /hbase/branches/0.94/src/site/xdoc/metrics.xml Change the default metrics class to NullContextWithUpdateThread --- Key: HBASE-5802 URL: https://issues.apache.org/jira/browse/HBASE-5802 Project: HBase Issue Type: Improvement Reporter: Elliott Clark Assignee: Elliott Clark Priority: Minor Fix For: 0.94.1 Attachments: HBASE-5802-0.patch, HBASE-5802-1.patch, HBASE-5802-2.patch Since lots more metrics are being placed into the Dynamic metrics bucket changing the default class to NullContextWithUpdateThread seems like it might be worth it. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (HBASE-6034) Upgrade Hadoop dependencies
[ https://issues.apache.org/jira/browse/HBASE-6034?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13278309#comment-13278309 ] Hudson commented on HBASE-6034: --- Integrated in HBase-TRUNK #2894 (See [https://builds.apache.org/job/HBase-TRUNK/2894/]) HBASE-6034 Upgrade Hadoop dependencies (Revision 1339848) Result = FAILURE stack : Files : * /hbase/trunk/pom.xml Upgrade Hadoop dependencies --- Key: HBASE-6034 URL: https://issues.apache.org/jira/browse/HBASE-6034 Project: HBase Issue Type: Task Affects Versions: 0.92.2 Reporter: Andrew Purtell Assignee: stack Priority: Minor Fix For: 0.92.2, 0.94.1 Attachments: 6034.092.txt, 6034.094.txt, 6034.txt 0.92 branch currently depends on Hadoop 1.0.0, but this has been moved to the archive. The earliest release on www.apache.org/dist/ is 1.0.1. Consider moving up? -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (HBASE-6005) Broken Links on Homepages
[ https://issues.apache.org/jira/browse/HBASE-6005?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13278311#comment-13278311 ] Hudson commented on HBASE-6005: --- Integrated in HBase-TRUNK #2894 (See [https://builds.apache.org/job/HBase-TRUNK/2894/]) HBASE-6005 Addendum... fixing release links (Revision 1339837) Result = FAILURE stack : Files : * /hbase/trunk/src/site/xdoc/cygwin.xml * /hbase/trunk/src/site/xdoc/old_news.xml Broken Links on Homepages - Key: HBASE-6005 URL: https://issues.apache.org/jira/browse/HBASE-6005 Project: HBase Issue Type: Task Components: documentation Reporter: Elliott Clark Assignee: Elliott Clark Priority: Minor Fix For: 0.96.0 Attachments: HBASE-6005-0.patch, HBASE-6005-addendum-0.patch I ran w3c's link checker on the homepage and there a few broken links. I'll start getting a patch to fix the links that were broken. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (HBASE-6022) Include Junit in the libs when packaging so that TestAcidGaurntee can run
[ https://issues.apache.org/jira/browse/HBASE-6022?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13278313#comment-13278313 ] Hudson commented on HBASE-6022: --- Integrated in HBase-0.94 #196 (See [https://builds.apache.org/job/HBase-0.94/196/]) HBASE-6022 Include Junit in the libs when packaging so that TestAcidGaurntee can run (Revision 1339846) Result = SUCCESS stack : Files : * /hbase/branches/0.94/pom.xml Include Junit in the libs when packaging so that TestAcidGaurntee can run - Key: HBASE-6022 URL: https://issues.apache.org/jira/browse/HBASE-6022 Project: HBase Issue Type: Improvement Reporter: Elliott Clark Assignee: Elliott Clark Fix For: 0.94.1 Attachments: HBASE-6022-0.patch If JUnit is not in the libs folder running the test acid command fails. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (HBASE-6018) hbck fails with a RejectedExecutionException when 50 regions present
[
https://issues.apache.org/jira/browse/HBASE-6018?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13278363#comment-13278363
]
Hudson commented on HBASE-6018:
---
Integrated in HBase-TRUNK #2895 (See
[https://builds.apache.org/job/HBase-TRUNK/2895/])
HBASE-6018 hbck fails with a RejectedExecutionException when 50 regions
present (Revision 1339876)
Result = SUCCESS
jmhsieh :
Files :
* /hbase/trunk/src/main/java/org/apache/hadoop/hbase/util/HBaseFsck.java
* /hbase/trunk/src/test/java/org/apache/hadoop/hbase/util/TestHBaseFsck.java
hbck fails with a RejectedExecutionException when 50 regions present
-
Key: HBASE-6018
URL: https://issues.apache.org/jira/browse/HBASE-6018
Project: HBase
Issue Type: Bug
Affects Versions: 0.92.1, 0.94.0
Reporter: Jonathan Hsieh
Assignee: Jonathan Hsieh
Fix For: 0.92.2, 0.96.0, 0.94.1
Attachments: hbase-6018-v2.patch, hbase-6018.patch
On a long running job 0.94.0rc3 cluster, we get to a point where hbck
consistently encounters this error and fails:
{code}
Exception in thread main java.util.concurrent.RejectedExecutionException
at
java.util.concurrent.ThreadPoolExecutor$AbortPolicy.rejectedExecution(ThreadPoolExecutor.java:1768)
at
java.util.concurrent.ThreadPoolExecutor.reject(ThreadPoolExecutor.java:767)
at
java.util.concurrent.ThreadPoolExecutor.execute(ThreadPoolExecutor.java:658)
at
org.apache.hadoop.hbase.util.HBaseFsck.loadHdfsRegionInfos(HBaseFsck.java:633)
at
org.apache.hadoop.hbase.util.HBaseFsck.onlineConsistencyRepair(HBaseFsck.java:354)
at org.apache.hadoop.hbase.util.HBaseFsck.onlineHbck(HBaseFsck.java:382)
at org.apache.hadoop.hbase.util.HBaseFsck.main(HBaseFsck.java:3120)
{code}
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (HBASE-6018) hbck fails with a RejectedExecutionException when 50 regions present
[
https://issues.apache.org/jira/browse/HBASE-6018?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13278377#comment-13278377
]
Hudson commented on HBASE-6018:
---
Integrated in HBase-0.94 #197 (See
[https://builds.apache.org/job/HBase-0.94/197/])
HBASE-6018 hbck fails with a RejectedExecutionException when 50 regions
present (Revision 1339877)
Result = FAILURE
jmhsieh :
Files :
* /hbase/branches/0.94/src/main/java/org/apache/hadoop/hbase/util/HBaseFsck.java
*
/hbase/branches/0.94/src/test/java/org/apache/hadoop/hbase/util/TestHBaseFsck.java
hbck fails with a RejectedExecutionException when 50 regions present
-
Key: HBASE-6018
URL: https://issues.apache.org/jira/browse/HBASE-6018
Project: HBase
Issue Type: Bug
Affects Versions: 0.92.1, 0.94.0
Reporter: Jonathan Hsieh
Assignee: Jonathan Hsieh
Fix For: 0.92.2, 0.96.0, 0.94.1
Attachments: hbase-6018-v2.patch, hbase-6018.patch
On a long running job 0.94.0rc3 cluster, we get to a point where hbck
consistently encounters this error and fails:
{code}
Exception in thread main java.util.concurrent.RejectedExecutionException
at
java.util.concurrent.ThreadPoolExecutor$AbortPolicy.rejectedExecution(ThreadPoolExecutor.java:1768)
at
java.util.concurrent.ThreadPoolExecutor.reject(ThreadPoolExecutor.java:767)
at
java.util.concurrent.ThreadPoolExecutor.execute(ThreadPoolExecutor.java:658)
at
org.apache.hadoop.hbase.util.HBaseFsck.loadHdfsRegionInfos(HBaseFsck.java:633)
at
org.apache.hadoop.hbase.util.HBaseFsck.onlineConsistencyRepair(HBaseFsck.java:354)
at org.apache.hadoop.hbase.util.HBaseFsck.onlineHbck(HBaseFsck.java:382)
at org.apache.hadoop.hbase.util.HBaseFsck.main(HBaseFsck.java:3120)
{code}
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (HBASE-6034) Upgrade Hadoop dependencies
[ https://issues.apache.org/jira/browse/HBASE-6034?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13278395#comment-13278395 ] Hudson commented on HBASE-6034: --- Integrated in HBase-0.92 #409 (See [https://builds.apache.org/job/HBase-0.92/409/]) HBASE-6034 Upgrade Hadoop dependencies (Revision 1339852) HBASE-6034 Upgrade Hadoop dependencies (Revision 1339851) Result = FAILURE stack : Files : * /hbase/branches/0.92/CHANGES.txt stack : Files : * /hbase/branches/0.92/pom.xml Upgrade Hadoop dependencies --- Key: HBASE-6034 URL: https://issues.apache.org/jira/browse/HBASE-6034 Project: HBase Issue Type: Task Affects Versions: 0.92.2 Reporter: Andrew Purtell Assignee: stack Priority: Minor Fix For: 0.92.2, 0.94.1 Attachments: 6034.092.txt, 6034.094.txt, 6034.txt 0.92 branch currently depends on Hadoop 1.0.0, but this has been moved to the archive. The earliest release on www.apache.org/dist/ is 1.0.1. Consider moving up? -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (HBASE-5927) SSH and DisableTableHandler happening together does not clear the znode of the region and RIT map.
[
https://issues.apache.org/jira/browse/HBASE-5927?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13278405#comment-13278405
]
Hudson commented on HBASE-5927:
---
Integrated in HBase-TRUNK #2896 (See
[https://builds.apache.org/job/HBase-TRUNK/2896/])
HBASE-5927 SSH and DisableTableHandler happening together does not clear
the znode of the region and RIT map (Rajesh) (Revision 1339913)
Result = FAILURE
tedyu :
Files :
*
/hbase/trunk/src/main/java/org/apache/hadoop/hbase/master/AssignmentManager.java
*
/hbase/trunk/src/main/java/org/apache/hadoop/hbase/master/handler/ServerShutdownHandler.java
*
/hbase/trunk/src/test/java/org/apache/hadoop/hbase/master/TestAssignmentManager.java
SSH and DisableTableHandler happening together does not clear the znode of
the region and RIT map.
--
Key: HBASE-5927
URL: https://issues.apache.org/jira/browse/HBASE-5927
Project: HBase
Issue Type: Bug
Components: master
Affects Versions: 0.92.1, 0.96.0, 0.94.1
Reporter: Jieshan Bean
Assignee: rajeshbabu
Fix For: 0.92.2, 0.96.0, 0.94.1
Attachments: HBASE-5927_94.patch, HBASE-5927_94_v2.patch,
HBASE-5927_trunk.patch, HBASE-5927_trunk_2.patch, TestCaseForReProduce.txt
A possible exception: If the related regionserver was just killed(But HMaster
has not perceived that), then we will get a local exception Connection reset
by peer. If this region belongs to a disabling table. what will happen?
ServerShutdownHandler will remove this region from AM#regions. So this region
is still existing in RIT. TimeoutMonitor will take care of it after it got
timeout. Then invoke unassign again. Since this region has been removed from
AM#regions, it will return directly due to the below code:
{code}
synchronized (this.regions) {
// Check if this region is currently assigned
if (!regions.containsKey(region)) {
LOG.debug(Attempted to unassign region +
region.getRegionNameAsString() + but it is not +
currently assigned anywhere);
return;
}
}
{code}
Then it leads to an end-less loop.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (HBASE-6011) Unable to start master in local mode
[
https://issues.apache.org/jira/browse/HBASE-6011?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13278407#comment-13278407
]
Hudson commented on HBASE-6011:
---
Integrated in HBase-TRUNK #2896 (See
[https://builds.apache.org/job/HBase-TRUNK/2896/])
HBASE-6011. Unable to start master in local mode (Revision 1339902)
Result = FAILURE
apurtell :
Files :
* /hbase/trunk/src/main/java/org/apache/hadoop/hbase/LocalHBaseCluster.java
* /hbase/trunk/src/test/java/org/apache/hadoop/hbase/TestLocalHBaseCluster.java
Unable to start master in local mode
Key: HBASE-6011
URL: https://issues.apache.org/jira/browse/HBASE-6011
Project: HBase
Issue Type: Bug
Affects Versions: 0.92.2, 0.96.0, 0.94.1
Reporter: Andrew Purtell
Assignee: Andrew Purtell
Fix For: 0.92.2, 0.96.0, 0.94.1
Attachments: 6011-v2.patch, 6011.patch
Got this trying to launch head of 0.94 branch in local mode from the build
tree but it happens with trunk and 0.92 too:
{noformat}
12/05/15 19:35:45 ERROR master.HMasterCommandLine: Failed to start master
java.lang.ClassCastException: org.apache.hadoop.hbase.master.HMaster cannot
be cast to org.apache.hadoop.hbase.master.HMasterCommandLine$LocalHMaster
at
org.apache.hadoop.hbase.master.HMasterCommandLine.startMaster(HMasterCommandLine.java:142)
at
org.apache.hadoop.hbase.master.HMasterCommandLine.run(HMasterCommandLine.java:103)
at org.apache.hadoop.util.ToolRunner.run(ToolRunner.java:65)
at
org.apache.hadoop.hbase.util.ServerCommandLine.doMain(ServerCommandLine.java:76)
at org.apache.hadoop.hbase.master.HMaster.main(HMaster.java:1761)
{noformat}
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (HBASE-6021) NullPointerException when running LoadTestTool without specifying compression type
[
https://issues.apache.org/jira/browse/HBASE-6021?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13278408#comment-13278408
]
Hudson commented on HBASE-6021:
---
Integrated in HBase-TRUNK #2896 (See
[https://builds.apache.org/job/HBase-TRUNK/2896/])
HBASE-6021. NullPointerException when running LoadTestTool without
specifying compression type (Revision 1339909)
Result = FAILURE
apurtell :
Files :
* /hbase/trunk/src/test/java/org/apache/hadoop/hbase/util/LoadTestTool.java
NullPointerException when running LoadTestTool without specifying compression
type
--
Key: HBASE-6021
URL: https://issues.apache.org/jira/browse/HBASE-6021
Project: HBase
Issue Type: Bug
Components: util
Affects Versions: 0.96.0, 0.94.1
Environment: Hadoop 1.0.2, HBase 0.94.0
Reporter: Andrew Purtell
Assignee: Andrew Purtell
Priority: Minor
Fix For: 0.92.2, 0.96.0, 0.94.1
Attachments: 6021.patch
If you don't specify a compression type on the LoadTestTool command line then
this happens:
{noformat}
12/05/16 18:41:23 ERROR util.AbstractHBaseTool: Error running command-line
tool
java.lang.NullPointerException
at
org.apache.hadoop.hbase.HColumnDescriptor.setCompressionType(HColumnDescriptor.java:535)
at
org.apache.hadoop.hbase.HBaseTestingUtility.createPreSplitLoadTestTable(HBaseTestingUtility.java:1885)
at
org.apache.hadoop.hbase.util.LoadTestTool.doWork(LoadTestTool.java:297)
at
org.apache.hadoop.hbase.util.AbstractHBaseTool.run(AbstractHBaseTool.java:103)
at org.apache.hadoop.util.ToolRunner.run(ToolRunner.java:65)
at
org.apache.hadoop.hbase.util.AbstractHBaseTool.doStaticMain(AbstractHBaseTool.java:173)
at org.apache.hadoop.hbase.util.LoadTestTool.main(LoadTestTool.java:341)
{noformat}
This should be handled better.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (HBASE-5927) SSH and DisableTableHandler happening together does not clear the znode of the region and RIT map.
[
https://issues.apache.org/jira/browse/HBASE-5927?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13278410#comment-13278410
]
Hudson commented on HBASE-5927:
---
Integrated in HBase-0.94 #198 (See
[https://builds.apache.org/job/HBase-0.94/198/])
HBASE-5927 SSH and DisableTableHandler happening together does not clear
the znode of the region and RIT map (Rajesh) (Revision 1339915)
Result = FAILURE
tedyu :
Files :
*
/hbase/branches/0.94/src/main/java/org/apache/hadoop/hbase/master/AssignmentManager.java
*
/hbase/branches/0.94/src/main/java/org/apache/hadoop/hbase/master/handler/ServerShutdownHandler.java
*
/hbase/branches/0.94/src/test/java/org/apache/hadoop/hbase/master/TestAssignmentManager.java
SSH and DisableTableHandler happening together does not clear the znode of
the region and RIT map.
--
Key: HBASE-5927
URL: https://issues.apache.org/jira/browse/HBASE-5927
Project: HBase
Issue Type: Bug
Components: master
Affects Versions: 0.92.1, 0.96.0, 0.94.1
Reporter: Jieshan Bean
Assignee: rajeshbabu
Fix For: 0.92.2, 0.96.0, 0.94.1
Attachments: HBASE-5927_94.patch, HBASE-5927_94_v2.patch,
HBASE-5927_trunk.patch, HBASE-5927_trunk_2.patch, TestCaseForReProduce.txt
A possible exception: If the related regionserver was just killed(But HMaster
has not perceived that), then we will get a local exception Connection reset
by peer. If this region belongs to a disabling table. what will happen?
ServerShutdownHandler will remove this region from AM#regions. So this region
is still existing in RIT. TimeoutMonitor will take care of it after it got
timeout. Then invoke unassign again. Since this region has been removed from
AM#regions, it will return directly due to the below code:
{code}
synchronized (this.regions) {
// Check if this region is currently assigned
if (!regions.containsKey(region)) {
LOG.debug(Attempted to unassign region +
region.getRegionNameAsString() + but it is not +
currently assigned anywhere);
return;
}
}
{code}
Then it leads to an end-less loop.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (HBASE-6011) Unable to start master in local mode
[
https://issues.apache.org/jira/browse/HBASE-6011?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13278412#comment-13278412
]
Hudson commented on HBASE-6011:
---
Integrated in HBase-0.94 #198 (See
[https://builds.apache.org/job/HBase-0.94/198/])
HBASE-6011. Unable to start master in local mode (Revision 1339904)
Result = FAILURE
apurtell :
Files :
*
/hbase/branches/0.94/src/main/java/org/apache/hadoop/hbase/LocalHBaseCluster.java
*
/hbase/branches/0.94/src/test/java/org/apache/hadoop/hbase/TestLocalHBaseCluster.java
Unable to start master in local mode
Key: HBASE-6011
URL: https://issues.apache.org/jira/browse/HBASE-6011
Project: HBase
Issue Type: Bug
Affects Versions: 0.92.2, 0.96.0, 0.94.1
Reporter: Andrew Purtell
Assignee: Andrew Purtell
Fix For: 0.92.2, 0.96.0, 0.94.1
Attachments: 6011-v2.patch, 6011.patch
Got this trying to launch head of 0.94 branch in local mode from the build
tree but it happens with trunk and 0.92 too:
{noformat}
12/05/15 19:35:45 ERROR master.HMasterCommandLine: Failed to start master
java.lang.ClassCastException: org.apache.hadoop.hbase.master.HMaster cannot
be cast to org.apache.hadoop.hbase.master.HMasterCommandLine$LocalHMaster
at
org.apache.hadoop.hbase.master.HMasterCommandLine.startMaster(HMasterCommandLine.java:142)
at
org.apache.hadoop.hbase.master.HMasterCommandLine.run(HMasterCommandLine.java:103)
at org.apache.hadoop.util.ToolRunner.run(ToolRunner.java:65)
at
org.apache.hadoop.hbase.util.ServerCommandLine.doMain(ServerCommandLine.java:76)
at org.apache.hadoop.hbase.master.HMaster.main(HMaster.java:1761)
{noformat}
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (HBASE-6023) Normalize security audit logging level with Hadoop
[ https://issues.apache.org/jira/browse/HBASE-6023?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13278411#comment-13278411 ] Hudson commented on HBASE-6023: --- Integrated in HBase-0.94 #198 (See [https://builds.apache.org/job/HBase-0.94/198/]) HBASE-6023. Normalize security audit logging level with Hadoop (Revision 1339916) Result = FAILURE apurtell : Files : * /hbase/branches/0.94/security/src/main/java/org/apache/hadoop/hbase/ipc/SecureServer.java Normalize security audit logging level with Hadoop -- Key: HBASE-6023 URL: https://issues.apache.org/jira/browse/HBASE-6023 Project: HBase Issue Type: Improvement Components: ipc, security Affects Versions: 0.92.2, 0.96.0, 0.94.1 Reporter: Andrew Purtell Assignee: Andrew Purtell Priority: Minor Fix For: 0.92.2, 0.96.0, 0.94.1 Attachments: 6023.patch A pretty trivial change, we log failed authentication attempts at WARN level, as does Hadoop, but log successful authentication at TRACE level, where Hadoop instead logs it at INFO level. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (HBASE-6021) NullPointerException when running LoadTestTool without specifying compression type
[
https://issues.apache.org/jira/browse/HBASE-6021?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13278413#comment-13278413
]
Hudson commented on HBASE-6021:
---
Integrated in HBase-0.94 #198 (See
[https://builds.apache.org/job/HBase-0.94/198/])
HBASE-6021. NullPointerException when running LoadTestTool without
specifying compression type (Revision 1339911)
Result = FAILURE
apurtell :
Files :
*
/hbase/branches/0.94/src/test/java/org/apache/hadoop/hbase/util/LoadTestTool.java
NullPointerException when running LoadTestTool without specifying compression
type
--
Key: HBASE-6021
URL: https://issues.apache.org/jira/browse/HBASE-6021
Project: HBase
Issue Type: Bug
Components: util
Affects Versions: 0.96.0, 0.94.1
Environment: Hadoop 1.0.2, HBase 0.94.0
Reporter: Andrew Purtell
Assignee: Andrew Purtell
Priority: Minor
Fix For: 0.92.2, 0.96.0, 0.94.1
Attachments: 6021.patch
If you don't specify a compression type on the LoadTestTool command line then
this happens:
{noformat}
12/05/16 18:41:23 ERROR util.AbstractHBaseTool: Error running command-line
tool
java.lang.NullPointerException
at
org.apache.hadoop.hbase.HColumnDescriptor.setCompressionType(HColumnDescriptor.java:535)
at
org.apache.hadoop.hbase.HBaseTestingUtility.createPreSplitLoadTestTable(HBaseTestingUtility.java:1885)
at
org.apache.hadoop.hbase.util.LoadTestTool.doWork(LoadTestTool.java:297)
at
org.apache.hadoop.hbase.util.AbstractHBaseTool.run(AbstractHBaseTool.java:103)
at org.apache.hadoop.util.ToolRunner.run(ToolRunner.java:65)
at
org.apache.hadoop.hbase.util.AbstractHBaseTool.doStaticMain(AbstractHBaseTool.java:173)
at org.apache.hadoop.hbase.util.LoadTestTool.main(LoadTestTool.java:341)
{noformat}
This should be handled better.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (HBASE-5927) SSH and DisableTableHandler happening together does not clear the znode of the region and RIT map.
[
https://issues.apache.org/jira/browse/HBASE-5927?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13278417#comment-13278417
]
Hudson commented on HBASE-5927:
---
Integrated in HBase-TRUNK-on-Hadoop-2.0.0 #8 (See
[https://builds.apache.org/job/HBase-TRUNK-on-Hadoop-2.0.0/8/])
HBASE-5927 SSH and DisableTableHandler happening together does not clear
the znode of the region and RIT map (Rajesh) (Revision 1339913)
Result = FAILURE
tedyu :
Files :
*
/hbase/trunk/src/main/java/org/apache/hadoop/hbase/master/AssignmentManager.java
*
/hbase/trunk/src/main/java/org/apache/hadoop/hbase/master/handler/ServerShutdownHandler.java
*
/hbase/trunk/src/test/java/org/apache/hadoop/hbase/master/TestAssignmentManager.java
SSH and DisableTableHandler happening together does not clear the znode of
the region and RIT map.
--
Key: HBASE-5927
URL: https://issues.apache.org/jira/browse/HBASE-5927
Project: HBase
Issue Type: Bug
Components: master
Affects Versions: 0.92.1, 0.96.0, 0.94.1
Reporter: Jieshan Bean
Assignee: rajeshbabu
Fix For: 0.92.2, 0.96.0, 0.94.1
Attachments: HBASE-5927_94.patch, HBASE-5927_94_v2.patch,
HBASE-5927_trunk.patch, HBASE-5927_trunk_2.patch, TestCaseForReProduce.txt
A possible exception: If the related regionserver was just killed(But HMaster
has not perceived that), then we will get a local exception Connection reset
by peer. If this region belongs to a disabling table. what will happen?
ServerShutdownHandler will remove this region from AM#regions. So this region
is still existing in RIT. TimeoutMonitor will take care of it after it got
timeout. Then invoke unassign again. Since this region has been removed from
AM#regions, it will return directly due to the below code:
{code}
synchronized (this.regions) {
// Check if this region is currently assigned
if (!regions.containsKey(region)) {
LOG.debug(Attempted to unassign region +
region.getRegionNameAsString() + but it is not +
currently assigned anywhere);
return;
}
}
{code}
Then it leads to an end-less loop.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (HBASE-6004) Adding more logging to help debugging MR job
[ https://issues.apache.org/jira/browse/HBASE-6004?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13278418#comment-13278418 ] Hudson commented on HBASE-6004: --- Integrated in HBase-TRUNK-on-Hadoop-2.0.0 #8 (See [https://builds.apache.org/job/HBase-TRUNK-on-Hadoop-2.0.0/8/]) HBASE-6004. Adding more logging to help debugging MR job (Jimmy Xiang) (Revision 1339806) Result = FAILURE apurtell : Files : * /hbase/trunk/src/main/java/org/apache/hadoop/hbase/client/ScannerCallable.java * /hbase/trunk/src/main/java/org/apache/hadoop/hbase/mapred/TableRecordReaderImpl.java * /hbase/trunk/src/main/java/org/apache/hadoop/hbase/mapreduce/TableRecordReaderImpl.java Adding more logging to help debugging MR job Key: HBASE-6004 URL: https://issues.apache.org/jira/browse/HBASE-6004 Project: HBase Issue Type: Improvement Affects Versions: 0.94.0, 0.96.0 Reporter: Jimmy Xiang Assignee: Jimmy Xiang Priority: Minor Fix For: 0.94.0, 0.96.0 Attachments: hbase-6004.patch, hbase-6004_v2-0.94.patch, hbase-6004_v2.patch MR job sometime fails because scanner expired. In this case, it will be helpful to know the last successful row, the ip of the region sever, and so on. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (HBASE-6018) hbck fails with a RejectedExecutionException when 50 regions present
[
https://issues.apache.org/jira/browse/HBASE-6018?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13278420#comment-13278420
]
Hudson commented on HBASE-6018:
---
Integrated in HBase-TRUNK-on-Hadoop-2.0.0 #8 (See
[https://builds.apache.org/job/HBase-TRUNK-on-Hadoop-2.0.0/8/])
HBASE-6018 hbck fails with a RejectedExecutionException when 50 regions
present (Revision 1339876)
Result = FAILURE
jmhsieh :
Files :
* /hbase/trunk/src/main/java/org/apache/hadoop/hbase/util/HBaseFsck.java
* /hbase/trunk/src/test/java/org/apache/hadoop/hbase/util/TestHBaseFsck.java
hbck fails with a RejectedExecutionException when 50 regions present
-
Key: HBASE-6018
URL: https://issues.apache.org/jira/browse/HBASE-6018
Project: HBase
Issue Type: Bug
Affects Versions: 0.92.1, 0.94.0
Reporter: Jonathan Hsieh
Assignee: Jonathan Hsieh
Fix For: 0.92.2, 0.96.0, 0.94.1
Attachments: hbase-6018-v2.patch, hbase-6018.patch
On a long running job 0.94.0rc3 cluster, we get to a point where hbck
consistently encounters this error and fails:
{code}
Exception in thread main java.util.concurrent.RejectedExecutionException
at
java.util.concurrent.ThreadPoolExecutor$AbortPolicy.rejectedExecution(ThreadPoolExecutor.java:1768)
at
java.util.concurrent.ThreadPoolExecutor.reject(ThreadPoolExecutor.java:767)
at
java.util.concurrent.ThreadPoolExecutor.execute(ThreadPoolExecutor.java:658)
at
org.apache.hadoop.hbase.util.HBaseFsck.loadHdfsRegionInfos(HBaseFsck.java:633)
at
org.apache.hadoop.hbase.util.HBaseFsck.onlineConsistencyRepair(HBaseFsck.java:354)
at org.apache.hadoop.hbase.util.HBaseFsck.onlineHbck(HBaseFsck.java:382)
at org.apache.hadoop.hbase.util.HBaseFsck.main(HBaseFsck.java:3120)
{code}
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (HBASE-6029) HBCK doesn't recover Balance switch if exception occurs in onlineHbck()
[ https://issues.apache.org/jira/browse/HBASE-6029?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13278421#comment-13278421 ] Hudson commented on HBASE-6029: --- Integrated in HBase-TRUNK-on-Hadoop-2.0.0 #8 (See [https://builds.apache.org/job/HBase-TRUNK-on-Hadoop-2.0.0/8/]) HBASE-6029 HBCK doesn't recover Balance switch if exception occurs in onlineHbck() (Maryann) (Revision 1339689) Result = FAILURE tedyu : Files : * /hbase/trunk/src/main/java/org/apache/hadoop/hbase/util/HBaseFsck.java HBCK doesn't recover Balance switch if exception occurs in onlineHbck() --- Key: HBASE-6029 URL: https://issues.apache.org/jira/browse/HBASE-6029 Project: HBase Issue Type: Bug Components: hbck Affects Versions: 0.94.0 Reporter: Maryann Xue Assignee: Maryann Xue Fix For: 0.96.0, 0.94.1 Attachments: HBASE-6029.patch -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (HBASE-6005) Broken Links on Homepages
[ https://issues.apache.org/jira/browse/HBASE-6005?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13278419#comment-13278419 ] Hudson commented on HBASE-6005: --- Integrated in HBase-TRUNK-on-Hadoop-2.0.0 #8 (See [https://builds.apache.org/job/HBase-TRUNK-on-Hadoop-2.0.0/8/]) HBASE-6005 Addendum... fixing release links (Revision 1339837) HBASE-6005 Broken Links on Homepages (Revision 1339805) Result = FAILURE stack : Files : * /hbase/trunk/src/site/xdoc/cygwin.xml * /hbase/trunk/src/site/xdoc/old_news.xml stack : Files : * /hbase/trunk/src/docbkx/book.xml * /hbase/trunk/src/docbkx/preface.xml * /hbase/trunk/src/main/javadoc/overview.html * /hbase/trunk/src/site/xdoc/cygwin.xml * /hbase/trunk/src/site/xdoc/old_news.xml Broken Links on Homepages - Key: HBASE-6005 URL: https://issues.apache.org/jira/browse/HBASE-6005 Project: HBase Issue Type: Task Components: documentation Reporter: Elliott Clark Assignee: Elliott Clark Priority: Minor Fix For: 0.96.0 Attachments: HBASE-6005-0.patch, HBASE-6005-addendum-0.patch I ran w3c's link checker on the homepage and there a few broken links. I'll start getting a patch to fix the links that were broken. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (HBASE-5826) Improve sync of HLog edits
[ https://issues.apache.org/jira/browse/HBASE-5826?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13278422#comment-13278422 ] Hudson commented on HBASE-5826: --- Integrated in HBase-TRUNK-on-Hadoop-2.0.0 #8 (See [https://builds.apache.org/job/HBase-TRUNK-on-Hadoop-2.0.0/8/]) HBASE-5826 Revert, Todd has review comments pending. (Revision 1339673) HBASE-5826 Improve sync of HLog edits (Todd) (Revision 1339671) Result = FAILURE tedyu : Files : * /hbase/trunk/src/main/java/org/apache/hadoop/hbase/regionserver/wal/HLog.java * /hbase/trunk/src/main/java/org/apache/hadoop/hbase/regionserver/wal/SequenceFileLogWriter.java * /hbase/trunk/src/test/java/org/apache/hadoop/hbase/regionserver/wal/TestHLog.java tedyu : Files : * /hbase/trunk/src/main/java/org/apache/hadoop/hbase/regionserver/wal/HLog.java * /hbase/trunk/src/main/java/org/apache/hadoop/hbase/regionserver/wal/SequenceFileLogWriter.java * /hbase/trunk/src/test/java/org/apache/hadoop/hbase/regionserver/wal/TestHLog.java Improve sync of HLog edits -- Key: HBASE-5826 URL: https://issues.apache.org/jira/browse/HBASE-5826 Project: HBase Issue Type: Improvement Reporter: Zhihong Yu Assignee: Todd Lipcon Fix For: 0.96.0 Attachments: 5826-v2.txt, 5826-v3.txt, 5826-v4.txt, 5826.txt HBASE-5782 solved the correctness issue for the sync of HLog edits. Todd provided a patch that would achieve higher throughput. This JIRA is a continuation of Todd's work submitted there. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (HBASE-6010) Security audit logger configuration for log4j
[ https://issues.apache.org/jira/browse/HBASE-6010?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13278426#comment-13278426 ] Hudson commented on HBASE-6010: --- Integrated in HBase-TRUNK-on-Hadoop-2.0.0 #8 (See [https://builds.apache.org/job/HBase-TRUNK-on-Hadoop-2.0.0/8/]) HBASE-6010. Security audit logger configuration for log4j (Revision 1339817) Result = FAILURE apurtell : Files : * /hbase/trunk/bin/hbase * /hbase/trunk/bin/hbase-daemon.sh * /hbase/trunk/conf/log4j.properties Security audit logger configuration for log4j - Key: HBASE-6010 URL: https://issues.apache.org/jira/browse/HBASE-6010 Project: HBase Issue Type: Improvement Affects Versions: 0.92.2, 0.96.0, 0.94.1 Reporter: Andrew Purtell Assignee: Andrew Purtell Priority: Minor Fix For: 0.96.0, 0.94.1 Attachments: 6010.patch Set up a logger for security audit messages just as Hadoop core does. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (HBASE-6011) Unable to start master in local mode
[
https://issues.apache.org/jira/browse/HBASE-6011?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13278427#comment-13278427
]
Hudson commented on HBASE-6011:
---
Integrated in HBase-TRUNK-on-Hadoop-2.0.0 #8 (See
[https://builds.apache.org/job/HBase-TRUNK-on-Hadoop-2.0.0/8/])
HBASE-6011. Unable to start master in local mode (Revision 1339902)
Result = FAILURE
apurtell :
Files :
* /hbase/trunk/src/main/java/org/apache/hadoop/hbase/LocalHBaseCluster.java
* /hbase/trunk/src/test/java/org/apache/hadoop/hbase/TestLocalHBaseCluster.java
Unable to start master in local mode
Key: HBASE-6011
URL: https://issues.apache.org/jira/browse/HBASE-6011
Project: HBase
Issue Type: Bug
Affects Versions: 0.92.2, 0.96.0, 0.94.1
Reporter: Andrew Purtell
Assignee: Andrew Purtell
Fix For: 0.92.2, 0.96.0, 0.94.1
Attachments: 6011-v2.patch, 6011.patch
Got this trying to launch head of 0.94 branch in local mode from the build
tree but it happens with trunk and 0.92 too:
{noformat}
12/05/15 19:35:45 ERROR master.HMasterCommandLine: Failed to start master
java.lang.ClassCastException: org.apache.hadoop.hbase.master.HMaster cannot
be cast to org.apache.hadoop.hbase.master.HMasterCommandLine$LocalHMaster
at
org.apache.hadoop.hbase.master.HMasterCommandLine.startMaster(HMasterCommandLine.java:142)
at
org.apache.hadoop.hbase.master.HMasterCommandLine.run(HMasterCommandLine.java:103)
at org.apache.hadoop.util.ToolRunner.run(ToolRunner.java:65)
at
org.apache.hadoop.hbase.util.ServerCommandLine.doMain(ServerCommandLine.java:76)
at org.apache.hadoop.hbase.master.HMaster.main(HMaster.java:1761)
{noformat}
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (HBASE-6001) Upgrade slf4j to 1.6.1
[ https://issues.apache.org/jira/browse/HBASE-6001?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13278430#comment-13278430 ] Hudson commented on HBASE-6001: --- Integrated in HBase-TRUNK-on-Hadoop-2.0.0 #8 (See [https://builds.apache.org/job/HBase-TRUNK-on-Hadoop-2.0.0/8/]) HBASE-6001. Upgrade slf4j to 1.6.1 (Revision 1339788) Result = FAILURE apurtell : Files : * /hbase/trunk/pom.xml Upgrade slf4j to 1.6.1 -- Key: HBASE-6001 URL: https://issues.apache.org/jira/browse/HBASE-6001 Project: HBase Issue Type: Task Reporter: Jimmy Xiang Assignee: Jimmy Xiang Fix For: 0.92.2, 0.96.0, 0.94.1 Attachments: hbase-6001.patch We need to upgrade slf4j to 1.6.1 since other hadoop components use 1.6.1 now. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (HBASE-6034) Upgrade Hadoop dependencies
[ https://issues.apache.org/jira/browse/HBASE-6034?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13278423#comment-13278423 ] Hudson commented on HBASE-6034: --- Integrated in HBase-TRUNK-on-Hadoop-2.0.0 #8 (See [https://builds.apache.org/job/HBase-TRUNK-on-Hadoop-2.0.0/8/]) HBASE-6034 Upgrade Hadoop dependencies (Revision 1339848) Result = FAILURE stack : Files : * /hbase/trunk/pom.xml Upgrade Hadoop dependencies --- Key: HBASE-6034 URL: https://issues.apache.org/jira/browse/HBASE-6034 Project: HBase Issue Type: Task Affects Versions: 0.92.2 Reporter: Andrew Purtell Assignee: stack Priority: Minor Fix For: 0.92.2, 0.94.1 Attachments: 6034.092.txt, 6034.094.txt, 6034.txt 0.92 branch currently depends on Hadoop 1.0.0, but this has been moved to the archive. The earliest release on www.apache.org/dist/ is 1.0.1. Consider moving up? -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (HBASE-6022) Include Junit in the libs when packaging so that TestAcidGaurntee can run
[ https://issues.apache.org/jira/browse/HBASE-6022?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13278424#comment-13278424 ] Hudson commented on HBASE-6022: --- Integrated in HBase-TRUNK-on-Hadoop-2.0.0 #8 (See [https://builds.apache.org/job/HBase-TRUNK-on-Hadoop-2.0.0/8/]) HBASE-6022 Include Junit in the libs when packaging so that TestAcidGaurntee can run (Revision 1339845) Result = FAILURE stack : Files : * /hbase/trunk/pom.xml Include Junit in the libs when packaging so that TestAcidGaurntee can run - Key: HBASE-6022 URL: https://issues.apache.org/jira/browse/HBASE-6022 Project: HBase Issue Type: Improvement Reporter: Elliott Clark Assignee: Elliott Clark Fix For: 0.94.1 Attachments: HBASE-6022-0.patch If JUnit is not in the libs folder running the test acid command fails. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (HBASE-6023) Normalize security audit logging level with Hadoop
[ https://issues.apache.org/jira/browse/HBASE-6023?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13278425#comment-13278425 ] Hudson commented on HBASE-6023: --- Integrated in HBase-TRUNK-on-Hadoop-2.0.0 #8 (See [https://builds.apache.org/job/HBase-TRUNK-on-Hadoop-2.0.0/8/]) HBASE-6023. Normalize security audit logging level with Hadoop (Revision 1339914) Result = FAILURE apurtell : Files : * /hbase/trunk/src/main/java/org/apache/hadoop/hbase/ipc/HBaseServer.java Normalize security audit logging level with Hadoop -- Key: HBASE-6023 URL: https://issues.apache.org/jira/browse/HBASE-6023 Project: HBase Issue Type: Improvement Components: ipc, security Affects Versions: 0.92.2, 0.96.0, 0.94.1 Reporter: Andrew Purtell Assignee: Andrew Purtell Priority: Minor Fix For: 0.92.2, 0.96.0, 0.94.1 Attachments: 6023.patch A pretty trivial change, we log failed authentication attempts at WARN level, as does Hadoop, but log successful authentication at TRACE level, where Hadoop instead logs it at INFO level. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (HBASE-5802) Change the default metrics class to NullContextWithUpdateThread
[ https://issues.apache.org/jira/browse/HBASE-5802?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13278429#comment-13278429 ] Hudson commented on HBASE-5802: --- Integrated in HBase-TRUNK-on-Hadoop-2.0.0 #8 (See [https://builds.apache.org/job/HBase-TRUNK-on-Hadoop-2.0.0/8/]) HBASE-5802 Change the default metrics class to NullContextWithUpdateThread (Revision 1339831) Result = FAILURE stack : Files : * /hbase/trunk/conf/hadoop-metrics.properties * /hbase/trunk/src/site/xdoc/metrics.xml Change the default metrics class to NullContextWithUpdateThread --- Key: HBASE-5802 URL: https://issues.apache.org/jira/browse/HBASE-5802 Project: HBase Issue Type: Improvement Reporter: Elliott Clark Assignee: Elliott Clark Priority: Minor Fix For: 0.94.1 Attachments: HBASE-5802-0.patch, HBASE-5802-1.patch, HBASE-5802-2.patch Since lots more metrics are being placed into the Dynamic metrics bucket changing the default class to NullContextWithUpdateThread seems like it might be worth it. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (HBASE-6021) NullPointerException when running LoadTestTool without specifying compression type
[
https://issues.apache.org/jira/browse/HBASE-6021?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13278428#comment-13278428
]
Hudson commented on HBASE-6021:
---
Integrated in HBase-TRUNK-on-Hadoop-2.0.0 #8 (See
[https://builds.apache.org/job/HBase-TRUNK-on-Hadoop-2.0.0/8/])
HBASE-6021. NullPointerException when running LoadTestTool without
specifying compression type (Revision 1339909)
Result = FAILURE
apurtell :
Files :
* /hbase/trunk/src/test/java/org/apache/hadoop/hbase/util/LoadTestTool.java
NullPointerException when running LoadTestTool without specifying compression
type
--
Key: HBASE-6021
URL: https://issues.apache.org/jira/browse/HBASE-6021
Project: HBase
Issue Type: Bug
Components: util
Affects Versions: 0.96.0, 0.94.1
Environment: Hadoop 1.0.2, HBase 0.94.0
Reporter: Andrew Purtell
Assignee: Andrew Purtell
Priority: Minor
Fix For: 0.92.2, 0.96.0, 0.94.1
Attachments: 6021.patch
If you don't specify a compression type on the LoadTestTool command line then
this happens:
{noformat}
12/05/16 18:41:23 ERROR util.AbstractHBaseTool: Error running command-line
tool
java.lang.NullPointerException
at
org.apache.hadoop.hbase.HColumnDescriptor.setCompressionType(HColumnDescriptor.java:535)
at
org.apache.hadoop.hbase.HBaseTestingUtility.createPreSplitLoadTestTable(HBaseTestingUtility.java:1885)
at
org.apache.hadoop.hbase.util.LoadTestTool.doWork(LoadTestTool.java:297)
at
org.apache.hadoop.hbase.util.AbstractHBaseTool.run(AbstractHBaseTool.java:103)
at org.apache.hadoop.util.ToolRunner.run(ToolRunner.java:65)
at
org.apache.hadoop.hbase.util.AbstractHBaseTool.doStaticMain(AbstractHBaseTool.java:173)
at org.apache.hadoop.hbase.util.LoadTestTool.main(LoadTestTool.java:341)
{noformat}
This should be handled better.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (HBASE-6013) Polish sharp edges from CopyTable
[ https://issues.apache.org/jira/browse/HBASE-6013?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13278470#comment-13278470 ] Hudson commented on HBASE-6013: --- Integrated in HBase-TRUNK #2897 (See [https://builds.apache.org/job/HBase-TRUNK/2897/]) HBASE-6013 Polish sharp edges from CopyTable (Revision 1339929) Result = FAILURE jmhsieh : Files : * /hbase/trunk/src/main/java/org/apache/hadoop/hbase/mapreduce/CopyTable.java Polish sharp edges from CopyTable - Key: HBASE-6013 URL: https://issues.apache.org/jira/browse/HBASE-6013 Project: HBase Issue Type: Improvement Affects Versions: 0.90.6, 0.92.1, 0.94.0, 0.96.0 Reporter: Jonathan Hsieh Assignee: Jonathan Hsieh Fix For: 0.90.7, 0.92.2, 0.96.0, 0.94.1 Attachments: hbase-6013-92.patch, hbase-6013.patch CopyTable doesn't report errors when invalid arguments are specified. For example, having a typo in --peer.adr (such as --peer.addr or -peer.adr) silently uses the default cluster and does a same-cluster copy. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (HBASE-5342) Grant/Revoke global permissions
[ https://issues.apache.org/jira/browse/HBASE-5342?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13278474#comment-13278474 ] Hudson commented on HBASE-5342: --- Integrated in HBase-0.94 #199 (See [https://builds.apache.org/job/HBase-0.94/199/]) HBASE-5342 Grant/Revoke global permissions (Matteo) (Revision 1339922) Result = FAILURE tedyu : Files : * /hbase/branches/0.94/security/src/main/java/org/apache/hadoop/hbase/security/access/AccessControlLists.java * /hbase/branches/0.94/security/src/main/java/org/apache/hadoop/hbase/security/access/AccessController.java * /hbase/branches/0.94/security/src/main/java/org/apache/hadoop/hbase/security/access/AccessControllerProtocol.java * /hbase/branches/0.94/security/src/main/java/org/apache/hadoop/hbase/security/access/TableAuthManager.java * /hbase/branches/0.94/security/src/main/java/org/apache/hadoop/hbase/security/access/UserPermission.java * /hbase/branches/0.94/security/src/main/java/org/apache/hadoop/hbase/security/access/ZKPermissionWatcher.java * /hbase/branches/0.94/security/src/test/java/org/apache/hadoop/hbase/security/access/TestAccessControlFilter.java * /hbase/branches/0.94/security/src/test/java/org/apache/hadoop/hbase/security/access/TestAccessController.java * /hbase/branches/0.94/security/src/test/java/org/apache/hadoop/hbase/security/access/TestTablePermissions.java * /hbase/branches/0.94/src/main/ruby/hbase/security.rb * /hbase/branches/0.94/src/main/ruby/shell.rb * /hbase/branches/0.94/src/main/ruby/shell/commands/grant.rb * /hbase/branches/0.94/src/main/ruby/shell/commands/revoke.rb * /hbase/branches/0.94/src/main/ruby/shell/commands/user_permission.rb * /hbase/branches/0.94/src/main/ruby/shell/commands/whoami.rb Grant/Revoke global permissions --- Key: HBASE-5342 URL: https://issues.apache.org/jira/browse/HBASE-5342 Project: HBase Issue Type: Sub-task Reporter: Enis Soztutar Assignee: Matteo Bertozzi Fix For: 0.92.2, 0.96.0, 0.94.1 Attachments: HBASE-5342-0.92.patch, HBASE-5342-0.94.patch, HBASE-5342-draft.patch, HBASE-5342-v0.patch, HBASE-5342-v1.patch, HBASE-5342-v2.patch, HBASE-5342-v3.patch, HBASE-5342-v4.patch, HBASE-5342-v5.patch HBASE-3025 introduced simple ACLs based on coprocessors. It defines global/table/cf/cq level permissions. However, there is no way to grant/revoke global level permissions, other than the hbase.superuser conf setting. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (HBASE-6021) NullPointerException when running LoadTestTool without specifying compression type
[
https://issues.apache.org/jira/browse/HBASE-6021?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13278485#comment-13278485
]
Hudson commented on HBASE-6021:
---
Integrated in HBase-0.92 #410 (See
[https://builds.apache.org/job/HBase-0.92/410/])
HBASE-6021. NullPointerException when running LoadTestTool without
specifying compression type (Revision 1339912)
Result = FAILURE
apurtell :
Files :
* /hbase/branches/0.92/CHANGES.txt
*
/hbase/branches/0.92/src/test/java/org/apache/hadoop/hbase/util/LoadTestTool.java
NullPointerException when running LoadTestTool without specifying compression
type
--
Key: HBASE-6021
URL: https://issues.apache.org/jira/browse/HBASE-6021
Project: HBase
Issue Type: Bug
Components: util
Affects Versions: 0.96.0, 0.94.1
Environment: Hadoop 1.0.2, HBase 0.94.0
Reporter: Andrew Purtell
Assignee: Andrew Purtell
Priority: Minor
Fix For: 0.92.2, 0.96.0, 0.94.1
Attachments: 6021.patch
If you don't specify a compression type on the LoadTestTool command line then
this happens:
{noformat}
12/05/16 18:41:23 ERROR util.AbstractHBaseTool: Error running command-line
tool
java.lang.NullPointerException
at
org.apache.hadoop.hbase.HColumnDescriptor.setCompressionType(HColumnDescriptor.java:535)
at
org.apache.hadoop.hbase.HBaseTestingUtility.createPreSplitLoadTestTable(HBaseTestingUtility.java:1885)
at
org.apache.hadoop.hbase.util.LoadTestTool.doWork(LoadTestTool.java:297)
at
org.apache.hadoop.hbase.util.AbstractHBaseTool.run(AbstractHBaseTool.java:103)
at org.apache.hadoop.util.ToolRunner.run(ToolRunner.java:65)
at
org.apache.hadoop.hbase.util.AbstractHBaseTool.doStaticMain(AbstractHBaseTool.java:173)
at org.apache.hadoop.hbase.util.LoadTestTool.main(LoadTestTool.java:341)
{noformat}
This should be handled better.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (HBASE-5124) Backport LoadTestTool to 0.92
[ https://issues.apache.org/jira/browse/HBASE-5124?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13278486#comment-13278486 ] Hudson commented on HBASE-5124: --- Integrated in HBase-0.92 #410 (See [https://builds.apache.org/job/HBase-0.92/410/]) HBASE-5124. Backport LoadTestTool to 0.92 (Revision 1339890) Result = FAILURE apurtell : Files : * /hbase/branches/0.92/CHANGES.txt * /hbase/branches/0.92/src/main/java/org/apache/hadoop/hbase/util/AbstractHBaseTool.java * /hbase/branches/0.92/src/main/java/org/apache/hadoop/hbase/util/Threads.java * /hbase/branches/0.92/src/test/java/org/apache/hadoop/hbase/HBaseTestingUtility.java * /hbase/branches/0.92/src/test/java/org/apache/hadoop/hbase/util/LoadTestKVGenerator.java * /hbase/branches/0.92/src/test/java/org/apache/hadoop/hbase/util/LoadTestTool.java * /hbase/branches/0.92/src/test/java/org/apache/hadoop/hbase/util/MultiThreadedAction.java * /hbase/branches/0.92/src/test/java/org/apache/hadoop/hbase/util/MultiThreadedReader.java * /hbase/branches/0.92/src/test/java/org/apache/hadoop/hbase/util/MultiThreadedWriter.java * /hbase/branches/0.92/src/test/java/org/apache/hadoop/hbase/util/TestLoadTestKVGenerator.java * /hbase/branches/0.92/src/test/java/org/apache/hadoop/hbase/util/TestMiniClusterLoadParallel.java * /hbase/branches/0.92/src/test/java/org/apache/hadoop/hbase/util/TestMiniClusterLoadSequential.java Backport LoadTestTool to 0.92 - Key: HBASE-5124 URL: https://issues.apache.org/jira/browse/HBASE-5124 Project: HBase Issue Type: Task Reporter: Zhihong Yu Assignee: Andrew Purtell Fix For: 0.92.2 Attachments: 5124-v4.patch, 5124-v5.patch, hbase-5124-v3.txt, hbase-5124.txt LoadTestTool is very useful. This JIRA backports LoadTestTool to 0.92 so that users don't have to build TRUNK in order to use it against 0.92 cluster. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (HBASE-6023) Normalize security audit logging level with Hadoop
[ https://issues.apache.org/jira/browse/HBASE-6023?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13278483#comment-13278483 ] Hudson commented on HBASE-6023: --- Integrated in HBase-0.92 #410 (See [https://builds.apache.org/job/HBase-0.92/410/]) HBASE-6023. Normalize security audit logging level with Hadoop (Revision 1339918) Result = FAILURE apurtell : Files : * /hbase/branches/0.92/CHANGES.txt * /hbase/branches/0.92/security/src/main/java/org/apache/hadoop/hbase/ipc/SecureServer.java Normalize security audit logging level with Hadoop -- Key: HBASE-6023 URL: https://issues.apache.org/jira/browse/HBASE-6023 Project: HBase Issue Type: Improvement Components: ipc, security Affects Versions: 0.92.2, 0.96.0, 0.94.1 Reporter: Andrew Purtell Assignee: Andrew Purtell Priority: Minor Fix For: 0.92.2, 0.96.0, 0.94.1 Attachments: 6023.patch A pretty trivial change, we log failed authentication attempts at WARN level, as does Hadoop, but log successful authentication at TRACE level, where Hadoop instead logs it at INFO level. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (HBASE-6011) Unable to start master in local mode
[
https://issues.apache.org/jira/browse/HBASE-6011?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13278484#comment-13278484
]
Hudson commented on HBASE-6011:
---
Integrated in HBase-0.92 #410 (See
[https://builds.apache.org/job/HBase-0.92/410/])
HBASE-6011. Unable to start master in local mode (Revision 1339908)
Result = FAILURE
apurtell :
Files :
* /hbase/branches/0.92/CHANGES.txt
*
/hbase/branches/0.92/src/main/java/org/apache/hadoop/hbase/LocalHBaseCluster.java
*
/hbase/branches/0.92/src/main/java/org/apache/hadoop/hbase/zookeeper/MiniZooKeeperCluster.java
*
/hbase/branches/0.92/src/test/java/org/apache/hadoop/hbase/TestLocalHBaseCluster.java
Unable to start master in local mode
Key: HBASE-6011
URL: https://issues.apache.org/jira/browse/HBASE-6011
Project: HBase
Issue Type: Bug
Affects Versions: 0.92.2, 0.96.0, 0.94.1
Reporter: Andrew Purtell
Assignee: Andrew Purtell
Fix For: 0.92.2, 0.96.0, 0.94.1
Attachments: 6011-v2.patch, 6011.patch
Got this trying to launch head of 0.94 branch in local mode from the build
tree but it happens with trunk and 0.92 too:
{noformat}
12/05/15 19:35:45 ERROR master.HMasterCommandLine: Failed to start master
java.lang.ClassCastException: org.apache.hadoop.hbase.master.HMaster cannot
be cast to org.apache.hadoop.hbase.master.HMasterCommandLine$LocalHMaster
at
org.apache.hadoop.hbase.master.HMasterCommandLine.startMaster(HMasterCommandLine.java:142)
at
org.apache.hadoop.hbase.master.HMasterCommandLine.run(HMasterCommandLine.java:103)
at org.apache.hadoop.util.ToolRunner.run(ToolRunner.java:65)
at
org.apache.hadoop.hbase.util.ServerCommandLine.doMain(ServerCommandLine.java:76)
at org.apache.hadoop.hbase.master.HMaster.main(HMaster.java:1761)
{noformat}
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (HBASE-5973) Add ability for potentially long-running IPC calls to abort if client disconnects
[ https://issues.apache.org/jira/browse/HBASE-5973?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13278519#comment-13278519 ] Hudson commented on HBASE-5973: --- Integrated in HBase-0.92-security #107 (See [https://builds.apache.org/job/HBase-0.92-security/107/]) HBASE-5973. Add ability for potentially long-running IPC calls to abort if client disconnects. Contributed by Todd Lipcon. (Revision 1336798) Result = FAILURE todd : Files : * /hbase/branches/0.92/CHANGES.txt * /hbase/branches/0.92/src/main/java/org/apache/hadoop/hbase/ipc/CallerDisconnectedException.java * /hbase/branches/0.92/src/main/java/org/apache/hadoop/hbase/ipc/HBaseServer.java * /hbase/branches/0.92/src/main/java/org/apache/hadoop/hbase/ipc/RpcCallContext.java * /hbase/branches/0.92/src/main/java/org/apache/hadoop/hbase/ipc/RpcServer.java * /hbase/branches/0.92/src/main/java/org/apache/hadoop/hbase/regionserver/HRegion.java * /hbase/branches/0.92/src/main/ruby/hbase/table.rb * /hbase/branches/0.92/src/main/ruby/shell/commands/scan.rb * /hbase/branches/0.92/src/test/java/org/apache/hadoop/hbase/filter/TestFilter.java * /hbase/branches/0.92/src/test/java/org/apache/hadoop/hbase/ipc/TestDelayedRpc.java Add ability for potentially long-running IPC calls to abort if client disconnects - Key: HBASE-5973 URL: https://issues.apache.org/jira/browse/HBASE-5973 Project: HBase Issue Type: Improvement Components: ipc Affects Versions: 0.90.7, 0.92.1, 0.94.0, 0.96.0 Reporter: Todd Lipcon Assignee: Todd Lipcon Fix For: 0.90.7, 0.92.2, 0.96.0, 0.94.1 Attachments: HBASE-5973-0.90.txt, hbase-5973-0.92.txt, hbase-5973-0.94.txt, hbase-5973-0.94.txt, hbase-5973.txt, hbase-5973.txt, hbase-5973.txt We recently had a cluster issue where a user was submitting scanners with a very restrictive filter, and then calling next() with a high scanner caching value. The clients would generally time out the next() call and disconnect, but the IPC kept running looking to fill the requested number of rows. Since this was in the context of MR, the tasks making the calls would retry, and the retries wuld be more likely to time out due to contention with the previous still-running scanner next() call. Eventually, the system spiraled out of control. We should add a hook to the IPC system so that RPC calls can check if the client has already disconnected. In such a case, the next() call could abort processing, given any further work is wasted. I imagine coprocessor endpoints, etc, could make good use of this as well. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (HBASE-5922) HalfStoreFileReader seekBefore causes StackOverflowError
[ https://issues.apache.org/jira/browse/HBASE-5922?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13278518#comment-13278518 ] Hudson commented on HBASE-5922: --- Integrated in HBase-0.92-security #107 (See [https://builds.apache.org/job/HBase-0.92-security/107/]) HBASE-5922 HalfStoreFileReader seekBefore causes StackOverflowError (Revision 1337412) Result = FAILURE stack : Files : * /hbase/branches/0.92/CHANGES.txt * /hbase/branches/0.92/src/main/java/org/apache/hadoop/hbase/io/HalfStoreFileReader.java HalfStoreFileReader seekBefore causes StackOverflowError Key: HBASE-5922 URL: https://issues.apache.org/jira/browse/HBASE-5922 Project: HBase Issue Type: Bug Components: client, io Affects Versions: 0.90.0 Environment: HBase 0.90.4 Reporter: Nate Putnam Assignee: Nate Putnam Priority: Critical Fix For: 0.90.7, 0.92.2, 0.96.0, 0.94.1 Attachments: 5922.092.txt, HBASE-5922.patch, HBASE-5922.patch, HBASE-5922.v2.patch, HBASE-5922.v3.patch, HBASE-5922.v4.patch Calling HRegionServer.getClosestRowBefore() can cause a stack overflow if the underlying store file is a reference and the row key is in the bottom. java.io.IOException: java.io.IOException: java.lang.StackOverflowError at org.apache.hadoop.hbase.regionserver.HRegionServer.convertThrowableToIOE(HRegionServer.java:990) at org.apache.hadoop.hbase.regionserver.HRegionServer.convertThrowableToIOE(HRegionServer.java:978) at org.apache.hadoop.hbase.regionserver.HRegionServer.getClosestRowBefore(HRegionServer.java:1651) at sun.reflect.GeneratedMethodAccessor174.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:597) at org.apache.hadoop.hbase.ipc.HBaseRPC$Server.call(HBaseRPC.java:570) at org.apache.hadoop.hbase.ipc.HBaseServer$Handler.run(HBaseServer.java:1039) Caused by: java.lang.StackOverflowError at org.apache.hadoop.hbase.io.HalfStoreFileReader$1.seekBefore(HalfStoreFileReader.java:147) at org.apache.hadoop.hbase.io.HalfStoreFileReader$1.seekBefore(HalfStoreFileReader.java:149) at org.apache.hadoop.hbase.io.HalfStoreFileReader$1.seekBefore(HalfStoreFileReader.java:149) at org.apache.hadoop.hbase.io.HalfStoreFileReader$1.seekBefore(HalfStoreFileReader.java:149) at org.apache.hadoop.hbase.io.HalfStoreFileReader$1.seekBefore(HalfStoreFileReader.java:149) -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (HBASE-5342) Grant/Revoke global permissions
[ https://issues.apache.org/jira/browse/HBASE-5342?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13278520#comment-13278520 ] Hudson commented on HBASE-5342: --- Integrated in HBase-0.92-security #107 (See [https://builds.apache.org/job/HBase-0.92-security/107/]) HBASE-5342 Grant/Revoke global permissions (Matteo) (Revision 1339924) Result = FAILURE tedyu : Files : * /hbase/branches/0.92/CHANGES.txt * /hbase/branches/0.92/security/src/main/java/org/apache/hadoop/hbase/security/access/AccessControlLists.java * /hbase/branches/0.92/security/src/main/java/org/apache/hadoop/hbase/security/access/AccessController.java * /hbase/branches/0.92/security/src/main/java/org/apache/hadoop/hbase/security/access/AccessControllerProtocol.java * /hbase/branches/0.92/security/src/main/java/org/apache/hadoop/hbase/security/access/TableAuthManager.java * /hbase/branches/0.92/security/src/main/java/org/apache/hadoop/hbase/security/access/UserPermission.java * /hbase/branches/0.92/security/src/main/java/org/apache/hadoop/hbase/security/access/ZKPermissionWatcher.java * /hbase/branches/0.92/security/src/test/java/org/apache/hadoop/hbase/security/access/TestAccessControlFilter.java * /hbase/branches/0.92/security/src/test/java/org/apache/hadoop/hbase/security/access/TestAccessController.java * /hbase/branches/0.92/security/src/test/java/org/apache/hadoop/hbase/security/access/TestTablePermissions.java * /hbase/branches/0.92/src/main/ruby/hbase/security.rb * /hbase/branches/0.92/src/main/ruby/shell.rb * /hbase/branches/0.92/src/main/ruby/shell/commands/grant.rb * /hbase/branches/0.92/src/main/ruby/shell/commands/revoke.rb * /hbase/branches/0.92/src/main/ruby/shell/commands/user_permission.rb * /hbase/branches/0.92/src/main/ruby/shell/commands/whoami.rb Grant/Revoke global permissions --- Key: HBASE-5342 URL: https://issues.apache.org/jira/browse/HBASE-5342 Project: HBase Issue Type: Sub-task Reporter: Enis Soztutar Assignee: Matteo Bertozzi Fix For: 0.92.2, 0.96.0, 0.94.1 Attachments: HBASE-5342-0.92.patch, HBASE-5342-0.94.patch, HBASE-5342-draft.patch, HBASE-5342-v0.patch, HBASE-5342-v1.patch, HBASE-5342-v2.patch, HBASE-5342-v3.patch, HBASE-5342-v4.patch, HBASE-5342-v5.patch HBASE-3025 introduced simple ACLs based on coprocessors. It defines global/table/cf/cq level permissions. However, there is no way to grant/revoke global level permissions, other than the hbase.superuser conf setting. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (HBASE-5124) Backport LoadTestTool to 0.92
[ https://issues.apache.org/jira/browse/HBASE-5124?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13278521#comment-13278521 ] Hudson commented on HBASE-5124: --- Integrated in HBase-0.92-security #107 (See [https://builds.apache.org/job/HBase-0.92-security/107/]) HBASE-5124. Backport LoadTestTool to 0.92 (Revision 1339890) Result = FAILURE apurtell : Files : * /hbase/branches/0.92/CHANGES.txt * /hbase/branches/0.92/src/main/java/org/apache/hadoop/hbase/util/AbstractHBaseTool.java * /hbase/branches/0.92/src/main/java/org/apache/hadoop/hbase/util/Threads.java * /hbase/branches/0.92/src/test/java/org/apache/hadoop/hbase/HBaseTestingUtility.java * /hbase/branches/0.92/src/test/java/org/apache/hadoop/hbase/util/LoadTestKVGenerator.java * /hbase/branches/0.92/src/test/java/org/apache/hadoop/hbase/util/LoadTestTool.java * /hbase/branches/0.92/src/test/java/org/apache/hadoop/hbase/util/MultiThreadedAction.java * /hbase/branches/0.92/src/test/java/org/apache/hadoop/hbase/util/MultiThreadedReader.java * /hbase/branches/0.92/src/test/java/org/apache/hadoop/hbase/util/MultiThreadedWriter.java * /hbase/branches/0.92/src/test/java/org/apache/hadoop/hbase/util/TestLoadTestKVGenerator.java * /hbase/branches/0.92/src/test/java/org/apache/hadoop/hbase/util/TestMiniClusterLoadParallel.java * /hbase/branches/0.92/src/test/java/org/apache/hadoop/hbase/util/TestMiniClusterLoadSequential.java Backport LoadTestTool to 0.92 - Key: HBASE-5124 URL: https://issues.apache.org/jira/browse/HBASE-5124 Project: HBase Issue Type: Task Reporter: Zhihong Yu Assignee: Andrew Purtell Fix For: 0.92.2 Attachments: 5124-v4.patch, 5124-v5.patch, hbase-5124-v3.txt, hbase-5124.txt LoadTestTool is very useful. This JIRA backports LoadTestTool to 0.92 so that users don't have to build TRUNK in order to use it against 0.92 cluster. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (HBASE-6023) Normalize security audit logging level with Hadoop
[ https://issues.apache.org/jira/browse/HBASE-6023?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13278527#comment-13278527 ] Hudson commented on HBASE-6023: --- Integrated in HBase-0.92-security #107 (See [https://builds.apache.org/job/HBase-0.92-security/107/]) HBASE-6023. Normalize security audit logging level with Hadoop (Revision 1339918) Result = FAILURE apurtell : Files : * /hbase/branches/0.92/CHANGES.txt * /hbase/branches/0.92/security/src/main/java/org/apache/hadoop/hbase/ipc/SecureServer.java Normalize security audit logging level with Hadoop -- Key: HBASE-6023 URL: https://issues.apache.org/jira/browse/HBASE-6023 Project: HBase Issue Type: Improvement Components: ipc, security Affects Versions: 0.92.2, 0.96.0, 0.94.1 Reporter: Andrew Purtell Assignee: Andrew Purtell Priority: Minor Fix For: 0.92.2, 0.96.0, 0.94.1 Attachments: 6023.patch A pretty trivial change, we log failed authentication attempts at WARN level, as does Hadoop, but log successful authentication at TRACE level, where Hadoop instead logs it at INFO level. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (HBASE-6034) Upgrade Hadoop dependencies
[ https://issues.apache.org/jira/browse/HBASE-6034?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13278525#comment-13278525 ] Hudson commented on HBASE-6034: --- Integrated in HBase-0.92-security #107 (See [https://builds.apache.org/job/HBase-0.92-security/107/]) HBASE-6034 Upgrade Hadoop dependencies (Revision 1339852) HBASE-6034 Upgrade Hadoop dependencies (Revision 1339851) Result = FAILURE stack : Files : * /hbase/branches/0.92/CHANGES.txt stack : Files : * /hbase/branches/0.92/pom.xml Upgrade Hadoop dependencies --- Key: HBASE-6034 URL: https://issues.apache.org/jira/browse/HBASE-6034 Project: HBase Issue Type: Task Affects Versions: 0.92.2 Reporter: Andrew Purtell Assignee: stack Priority: Minor Fix For: 0.92.2, 0.94.1 Attachments: 6034.092.txt, 6034.094.txt, 6034.txt 0.92 branch currently depends on Hadoop 1.0.0, but this has been moved to the archive. The earliest release on www.apache.org/dist/ is 1.0.1. Consider moving up? -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (HBASE-6018) hbck fails with a RejectedExecutionException when 50 regions present
[
https://issues.apache.org/jira/browse/HBASE-6018?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13278523#comment-13278523
]
Hudson commented on HBASE-6018:
---
Integrated in HBase-0.92-security #107 (See
[https://builds.apache.org/job/HBase-0.92-security/107/])
HBASE-6018 hbck fails with a RejectedExecutionException when 50 regions
present (Revision 1339879)
Result = FAILURE
jmhsieh :
Files :
* /hbase/branches/0.92/CHANGES.txt
* /hbase/branches/0.92/src/main/java/org/apache/hadoop/hbase/util/HBaseFsck.java
*
/hbase/branches/0.92/src/test/java/org/apache/hadoop/hbase/util/TestHBaseFsck.java
hbck fails with a RejectedExecutionException when 50 regions present
-
Key: HBASE-6018
URL: https://issues.apache.org/jira/browse/HBASE-6018
Project: HBase
Issue Type: Bug
Affects Versions: 0.92.1, 0.94.0
Reporter: Jonathan Hsieh
Assignee: Jonathan Hsieh
Fix For: 0.92.2, 0.96.0, 0.94.1
Attachments: hbase-6018-v2.patch, hbase-6018.patch
On a long running job 0.94.0rc3 cluster, we get to a point where hbck
consistently encounters this error and fails:
{code}
Exception in thread main java.util.concurrent.RejectedExecutionException
at
java.util.concurrent.ThreadPoolExecutor$AbortPolicy.rejectedExecution(ThreadPoolExecutor.java:1768)
at
java.util.concurrent.ThreadPoolExecutor.reject(ThreadPoolExecutor.java:767)
at
java.util.concurrent.ThreadPoolExecutor.execute(ThreadPoolExecutor.java:658)
at
org.apache.hadoop.hbase.util.HBaseFsck.loadHdfsRegionInfos(HBaseFsck.java:633)
at
org.apache.hadoop.hbase.util.HBaseFsck.onlineConsistencyRepair(HBaseFsck.java:354)
at org.apache.hadoop.hbase.util.HBaseFsck.onlineHbck(HBaseFsck.java:382)
at org.apache.hadoop.hbase.util.HBaseFsck.main(HBaseFsck.java:3120)
{code}
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (HBASE-6021) NullPointerException when running LoadTestTool without specifying compression type
[
https://issues.apache.org/jira/browse/HBASE-6021?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13278529#comment-13278529
]
Hudson commented on HBASE-6021:
---
Integrated in HBase-0.92-security #107 (See
[https://builds.apache.org/job/HBase-0.92-security/107/])
HBASE-6021. NullPointerException when running LoadTestTool without
specifying compression type (Revision 1339912)
Result = FAILURE
apurtell :
Files :
* /hbase/branches/0.92/CHANGES.txt
*
/hbase/branches/0.92/src/test/java/org/apache/hadoop/hbase/util/LoadTestTool.java
NullPointerException when running LoadTestTool without specifying compression
type
--
Key: HBASE-6021
URL: https://issues.apache.org/jira/browse/HBASE-6021
Project: HBase
Issue Type: Bug
Components: util
Affects Versions: 0.96.0, 0.94.1
Environment: Hadoop 1.0.2, HBase 0.94.0
Reporter: Andrew Purtell
Assignee: Andrew Purtell
Priority: Minor
Fix For: 0.92.2, 0.96.0, 0.94.1
Attachments: 6021.patch
If you don't specify a compression type on the LoadTestTool command line then
this happens:
{noformat}
12/05/16 18:41:23 ERROR util.AbstractHBaseTool: Error running command-line
tool
java.lang.NullPointerException
at
org.apache.hadoop.hbase.HColumnDescriptor.setCompressionType(HColumnDescriptor.java:535)
at
org.apache.hadoop.hbase.HBaseTestingUtility.createPreSplitLoadTestTable(HBaseTestingUtility.java:1885)
at
org.apache.hadoop.hbase.util.LoadTestTool.doWork(LoadTestTool.java:297)
at
org.apache.hadoop.hbase.util.AbstractHBaseTool.run(AbstractHBaseTool.java:103)
at org.apache.hadoop.util.ToolRunner.run(ToolRunner.java:65)
at
org.apache.hadoop.hbase.util.AbstractHBaseTool.doStaticMain(AbstractHBaseTool.java:173)
at org.apache.hadoop.hbase.util.LoadTestTool.main(LoadTestTool.java:341)
{noformat}
This should be handled better.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (HBASE-5806) Handle split region related failures on master restart and RS restart
[ https://issues.apache.org/jira/browse/HBASE-5806?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13278526#comment-13278526 ] Hudson commented on HBASE-5806: --- Integrated in HBase-0.92-security #107 (See [https://builds.apache.org/job/HBase-0.92-security/107/]) HBASE-5806 Handle split region related failures on master restart and RS restart(Chinna rao) (Revision 1338335) Result = FAILURE ramkrishna : Files : * /hbase/branches/0.92/src/main/java/org/apache/hadoop/hbase/LocalHBaseCluster.java * /hbase/branches/0.92/src/main/java/org/apache/hadoop/hbase/master/AssignmentManager.java * /hbase/branches/0.92/src/main/java/org/apache/hadoop/hbase/master/HMaster.java * /hbase/branches/0.92/src/main/java/org/apache/hadoop/hbase/master/handler/ServerShutdownHandler.java * /hbase/branches/0.92/src/test/java/org/apache/hadoop/hbase/regionserver/TestSplitTransactionOnCluster.java Handle split region related failures on master restart and RS restart - Key: HBASE-5806 URL: https://issues.apache.org/jira/browse/HBASE-5806 Project: HBase Issue Type: Bug Affects Versions: 0.92.1 Reporter: ramkrishna.s.vasudevan Assignee: Chinna Rao Lalam Fix For: 0.92.2, 0.96.0, 0.94.1 Attachments: HBASE-5806.patch, HBASE-5806_0.92.patch, HBASE-5806_0.94.patch, HBASE-5806_0.94_1.patch, HBASE-5806_0.94_2.patch, HBASE-5806_trunk.patch, HBASE-5806_trunk_1.patch, HBASE-5806_trunk_2.patch, HBASE-5806_trunk_3.patch This issue is raised to solve issues that comes out of partial region split happened and the region node in the ZK which is in RS_ZK_REGION_SPLITTING and RS_ZK_REGION_SPLIT is not yet processed. This also tries to address HBASE-5615. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (HBASE-5894) Table deletion failed but HBaseAdmin#deletetable reports it as success
[
https://issues.apache.org/jira/browse/HBASE-5894?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13278524#comment-13278524
]
Hudson commented on HBASE-5894:
---
Integrated in HBase-0.92-security #107 (See
[https://builds.apache.org/job/HBase-0.92-security/107/])
HBASE-5894 Table deletion failed but HBaseAdmin#deletetable reports it as
success (Xufeng) (Revision 1334476)
Result = FAILURE
tedyu :
Files :
* /hbase/branches/0.92/CHANGES.txt
*
/hbase/branches/0.92/src/main/java/org/apache/hadoop/hbase/client/HBaseAdmin.java
Table deletion failed but HBaseAdmin#deletetable reports it as success
--
Key: HBASE-5894
URL: https://issues.apache.org/jira/browse/HBASE-5894
Project: HBase
Issue Type: Bug
Affects Versions: 0.90.7, 0.92.2, 0.94.0
Environment: all versions
Reporter: xufeng
Assignee: xufeng
Priority: Minor
Fix For: 0.90.7, 0.92.2, 0.96.0, 0.94.1
Attachments: HBASE-5894_90_patch_v1.patch,
HBASE-5894_90_patch_v1_surefire-report.html, HBASE-5894_90_patch_v2.patch,
HBASE-5894_92_patch_v1.patch, HBASE-5894_92_patch_v1_surefire-report.html,
HBASE-5894_92_patch_v2.patch, HBASE-5894_94_patch_v1.patch,
HBASE-5894_94_patch_v1_surefire-report.html, HBASE-5894_94_patch_v2.patch,
HBASE-5894_trunk_patch_v1.patch,
HBASE-5894_trunk_patch_v1_surefire-report.html,
HBASE-5894_trunk_patch_v2.patch,
HBASE-5894_trunk_patch_v2_surefire-report.html,
HBASE-5894_trunk_patch_v3.patch
Reproduce this issue by following steps:
For reproduce it I add this code in DeleteTableHandler#handleTableOperation():
{noformat}
LOG.debug(Deleting region + region.getRegionNameAsString() +
from META and FS);
+if (true) {
+ throw new IOException(ERROR);
+}
// Remove region from META
MetaEditor.deleteRegion(this.server.getCatalogTracker(), region);
{noformat}
step1:create a table and disable it.
step2:delete it by HBaseAdmin#deleteTable() API.
result:after lone time, The log say the Table has been deleted, but in fact
if we do list in shell,the table also exists.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (HBASE-6011) Unable to start master in local mode
[
https://issues.apache.org/jira/browse/HBASE-6011?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13278528#comment-13278528
]
Hudson commented on HBASE-6011:
---
Integrated in HBase-0.92-security #107 (See
[https://builds.apache.org/job/HBase-0.92-security/107/])
HBASE-6011. Unable to start master in local mode (Revision 1339908)
Result = FAILURE
apurtell :
Files :
* /hbase/branches/0.92/CHANGES.txt
*
/hbase/branches/0.92/src/main/java/org/apache/hadoop/hbase/LocalHBaseCluster.java
*
/hbase/branches/0.92/src/main/java/org/apache/hadoop/hbase/zookeeper/MiniZooKeeperCluster.java
*
/hbase/branches/0.92/src/test/java/org/apache/hadoop/hbase/TestLocalHBaseCluster.java
Unable to start master in local mode
Key: HBASE-6011
URL: https://issues.apache.org/jira/browse/HBASE-6011
Project: HBase
Issue Type: Bug
Affects Versions: 0.92.2, 0.96.0, 0.94.1
Reporter: Andrew Purtell
Assignee: Andrew Purtell
Fix For: 0.92.2, 0.96.0, 0.94.1
Attachments: 6011-v2.patch, 6011.patch
Got this trying to launch head of 0.94 branch in local mode from the build
tree but it happens with trunk and 0.92 too:
{noformat}
12/05/15 19:35:45 ERROR master.HMasterCommandLine: Failed to start master
java.lang.ClassCastException: org.apache.hadoop.hbase.master.HMaster cannot
be cast to org.apache.hadoop.hbase.master.HMasterCommandLine$LocalHMaster
at
org.apache.hadoop.hbase.master.HMasterCommandLine.startMaster(HMasterCommandLine.java:142)
at
org.apache.hadoop.hbase.master.HMasterCommandLine.run(HMasterCommandLine.java:103)
at org.apache.hadoop.util.ToolRunner.run(ToolRunner.java:65)
at
org.apache.hadoop.hbase.util.ServerCommandLine.doMain(ServerCommandLine.java:76)
at org.apache.hadoop.hbase.master.HMaster.main(HMaster.java:1761)
{noformat}
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (HBASE-5942) HConnnectionManager.getRegionServerWithRetries doesn't call afterCall properly
[
https://issues.apache.org/jira/browse/HBASE-5942?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13278522#comment-13278522
]
Hudson commented on HBASE-5942:
---
Integrated in HBase-0.92-security #107 (See
[https://builds.apache.org/job/HBase-0.92-security/107/])
HBASE-5942 HConnnectionManager.getRegionServerWithRetries doesn't call
afterCall properly (Revision 1335734)
Result = FAILURE
stack :
Files :
* /hbase/branches/0.92/CHANGES.txt
*
/hbase/branches/0.92/src/main/java/org/apache/hadoop/hbase/client/HConnectionManager.java
HConnnectionManager.getRegionServerWithRetries doesn't call afterCall properly
--
Key: HBASE-5942
URL: https://issues.apache.org/jira/browse/HBASE-5942
Project: HBase
Issue Type: Bug
Affects Versions: 0.92.1
Reporter: Zhihong Yu
Assignee: ramkrishna.s.vasudevan
Fix For: 0.92.2
Attachments: hbase-5942.patch
HConnnectionManager.getRegionServerWithRetries:
{code}
return callable.call();
} catch (Throwable t) {
callable.shouldRetry(t);
{code}
shouldRetry relies on the proper startTime and endTime to calculate the
timeout value. However, callable.afterCall() is called in finally block. Thus
callable.callTimeout will be set to negative value in callable.shouldRetry().
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (HBASE-6013) Polish sharp edges from CopyTable
[ https://issues.apache.org/jira/browse/HBASE-6013?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13278554#comment-13278554 ] Hudson commented on HBASE-6013: --- Integrated in HBase-0.92 #411 (See [https://builds.apache.org/job/HBase-0.92/411/]) HBASE-6013 Polish sharp edges from CopyTable (Revision 1339931) Result = FAILURE jmhsieh : Files : * /hbase/branches/0.92/CHANGES.txt * /hbase/branches/0.92/src/main/java/org/apache/hadoop/hbase/mapreduce/CopyTable.java Polish sharp edges from CopyTable - Key: HBASE-6013 URL: https://issues.apache.org/jira/browse/HBASE-6013 Project: HBase Issue Type: Improvement Affects Versions: 0.90.6, 0.92.1, 0.94.0, 0.96.0 Reporter: Jonathan Hsieh Assignee: Jonathan Hsieh Fix For: 0.90.7, 0.92.2, 0.96.0, 0.94.1 Attachments: hbase-6013-92.patch, hbase-6013.patch CopyTable doesn't report errors when invalid arguments are specified. For example, having a typo in --peer.adr (such as --peer.addr or -peer.adr) silently uses the default cluster and does a same-cluster copy. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (HBASE-5342) Grant/Revoke global permissions
[ https://issues.apache.org/jira/browse/HBASE-5342?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13278553#comment-13278553 ] Hudson commented on HBASE-5342: --- Integrated in HBase-0.92 #411 (See [https://builds.apache.org/job/HBase-0.92/411/]) HBASE-5342 Grant/Revoke global permissions (Matteo) (Revision 1339924) Result = FAILURE tedyu : Files : * /hbase/branches/0.92/CHANGES.txt * /hbase/branches/0.92/security/src/main/java/org/apache/hadoop/hbase/security/access/AccessControlLists.java * /hbase/branches/0.92/security/src/main/java/org/apache/hadoop/hbase/security/access/AccessController.java * /hbase/branches/0.92/security/src/main/java/org/apache/hadoop/hbase/security/access/AccessControllerProtocol.java * /hbase/branches/0.92/security/src/main/java/org/apache/hadoop/hbase/security/access/TableAuthManager.java * /hbase/branches/0.92/security/src/main/java/org/apache/hadoop/hbase/security/access/UserPermission.java * /hbase/branches/0.92/security/src/main/java/org/apache/hadoop/hbase/security/access/ZKPermissionWatcher.java * /hbase/branches/0.92/security/src/test/java/org/apache/hadoop/hbase/security/access/TestAccessControlFilter.java * /hbase/branches/0.92/security/src/test/java/org/apache/hadoop/hbase/security/access/TestAccessController.java * /hbase/branches/0.92/security/src/test/java/org/apache/hadoop/hbase/security/access/TestTablePermissions.java * /hbase/branches/0.92/src/main/ruby/hbase/security.rb * /hbase/branches/0.92/src/main/ruby/shell.rb * /hbase/branches/0.92/src/main/ruby/shell/commands/grant.rb * /hbase/branches/0.92/src/main/ruby/shell/commands/revoke.rb * /hbase/branches/0.92/src/main/ruby/shell/commands/user_permission.rb * /hbase/branches/0.92/src/main/ruby/shell/commands/whoami.rb Grant/Revoke global permissions --- Key: HBASE-5342 URL: https://issues.apache.org/jira/browse/HBASE-5342 Project: HBase Issue Type: Sub-task Reporter: Enis Soztutar Assignee: Matteo Bertozzi Fix For: 0.92.2, 0.96.0, 0.94.1 Attachments: HBASE-5342-0.92.patch, HBASE-5342-0.94.patch, HBASE-5342-draft.patch, HBASE-5342-v0.patch, HBASE-5342-v1.patch, HBASE-5342-v2.patch, HBASE-5342-v3.patch, HBASE-5342-v4.patch, HBASE-5342-v5.patch HBASE-3025 introduced simple ACLs based on coprocessors. It defines global/table/cf/cq level permissions. However, there is no way to grant/revoke global level permissions, other than the hbase.superuser conf setting. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (HBASE-6013) Polish sharp edges from CopyTable
[ https://issues.apache.org/jira/browse/HBASE-6013?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13278749#comment-13278749 ] Hudson commented on HBASE-6013: --- Integrated in HBase-TRUNK-on-Hadoop-2.0.0 #9 (See [https://builds.apache.org/job/HBase-TRUNK-on-Hadoop-2.0.0/9/]) HBASE-6013 Polish sharp edges from CopyTable (Revision 1339929) Result = FAILURE jmhsieh : Files : * /hbase/trunk/src/main/java/org/apache/hadoop/hbase/mapreduce/CopyTable.java Polish sharp edges from CopyTable - Key: HBASE-6013 URL: https://issues.apache.org/jira/browse/HBASE-6013 Project: HBase Issue Type: Improvement Affects Versions: 0.90.6, 0.92.1, 0.94.0, 0.96.0 Reporter: Jonathan Hsieh Assignee: Jonathan Hsieh Fix For: 0.90.7, 0.92.2, 0.96.0, 0.94.1 Attachments: hbase-6013-92.patch, hbase-6013.patch CopyTable doesn't report errors when invalid arguments are specified. For example, having a typo in --peer.adr (such as --peer.addr or -peer.adr) silently uses the default cluster and does a same-cluster copy. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (HBASE-6011) Unable to start master in local mode
[
https://issues.apache.org/jira/browse/HBASE-6011?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13279011#comment-13279011
]
Hudson commented on HBASE-6011:
---
Integrated in HBase-TRUNK #2898 (See
[https://builds.apache.org/job/HBase-TRUNK/2898/])
HBASE-6011. Addendum to support master mocking (Ram) (Revision 1340155)
Result = FAILURE
apurtell :
Files :
* /hbase/trunk/src/main/java/org/apache/hadoop/hbase/LocalHBaseCluster.java
Unable to start master in local mode
Key: HBASE-6011
URL: https://issues.apache.org/jira/browse/HBASE-6011
Project: HBase
Issue Type: Bug
Affects Versions: 0.92.2, 0.96.0, 0.94.1
Reporter: Andrew Purtell
Assignee: Andrew Purtell
Fix For: 0.92.2, 0.96.0, 0.94.1
Attachments: 6011-v2.patch, 6011.patch, HBASE-6011_1.patch,
HBASE-6011_addendum_0.92.patch, HBASE-6011_addendum_0.94.patch,
HBASE-6011_addendum_trunk.patch
Got this trying to launch head of 0.94 branch in local mode from the build
tree but it happens with trunk and 0.92 too:
{noformat}
12/05/15 19:35:45 ERROR master.HMasterCommandLine: Failed to start master
java.lang.ClassCastException: org.apache.hadoop.hbase.master.HMaster cannot
be cast to org.apache.hadoop.hbase.master.HMasterCommandLine$LocalHMaster
at
org.apache.hadoop.hbase.master.HMasterCommandLine.startMaster(HMasterCommandLine.java:142)
at
org.apache.hadoop.hbase.master.HMasterCommandLine.run(HMasterCommandLine.java:103)
at org.apache.hadoop.util.ToolRunner.run(ToolRunner.java:65)
at
org.apache.hadoop.hbase.util.ServerCommandLine.doMain(ServerCommandLine.java:76)
at org.apache.hadoop.hbase.master.HMaster.main(HMaster.java:1761)
{noformat}
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (HBASE-5926) Delete the master znode after a master crash
[ https://issues.apache.org/jira/browse/HBASE-5926?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13279031#comment-13279031 ] Hudson commented on HBASE-5926: --- Integrated in HBase-TRUNK #2899 (See [https://builds.apache.org/job/HBase-TRUNK/2899/]) HBASE-5926 Delete the master znode after a master crash (Revision 1340185) Result = FAILURE stack : Files : * /hbase/trunk/bin/hbase-daemon.sh * /hbase/trunk/src/main/java/org/apache/hadoop/hbase/master/ActiveMasterManager.java * /hbase/trunk/src/main/java/org/apache/hadoop/hbase/master/HMasterCommandLine.java * /hbase/trunk/src/main/java/org/apache/hadoop/hbase/regionserver/HRegionServer.java * /hbase/trunk/src/main/java/org/apache/hadoop/hbase/zookeeper/MasterAddressTracker.java * /hbase/trunk/src/test/java/org/apache/hadoop/hbase/zookeeper/TestZooKeeperNodeTracker.java Delete the master znode after a master crash Key: HBASE-5926 URL: https://issues.apache.org/jira/browse/HBASE-5926 Project: HBase Issue Type: Improvement Components: master, scripts Affects Versions: 0.96.0 Reporter: nkeywal Assignee: nkeywal Priority: Minor Fix For: 0.96.0 Attachments: 5926.v10.patch, 5926.v11.patch, 5926.v13.patch, 5926.v14.patch, 5926.v6.patch, 5926.v8.patch, 5926.v9.patch This is the continuation of the work done in HBASE-5844. But we can't apply exactly the same strategy: for the region server, there is a znode per region server, while for the master backup master there is a single znode for both. So if we apply the same strategy as for a regionserver, we may have this scenario: 1) Master starts 2) Backup master starts 3) Master dies 4) ZK detects it 5) Backup master receives the update from ZK 6) Backup master creates the new master node and become the main master 7) Previous master script continues 8) Previous master script deletes the master node in ZK 9) = issue: we deleted the node just created by the new master This should not happen often (usually the znode will be deleted soon enough), but it can happen. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (HBASE-5546) Master assigns region in the original region server when opening region failed
[ https://issues.apache.org/jira/browse/HBASE-5546?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13279032#comment-13279032 ] Hudson commented on HBASE-5546: --- Integrated in HBase-TRUNK #2899 (See [https://builds.apache.org/job/HBase-TRUNK/2899/]) HBASE-5546 Master assigns region in the original region server when opening region failed (Ashutosh) (Revision 1340187) Result = FAILURE ramkrishna : Files : * /hbase/trunk/src/main/java/org/apache/hadoop/hbase/master/AssignmentManager.java * /hbase/trunk/src/test/java/org/apache/hadoop/hbase/master/TestAssignmentManager.java Master assigns region in the original region server when opening region failed Key: HBASE-5546 URL: https://issues.apache.org/jira/browse/HBASE-5546 Project: HBase Issue Type: Bug Components: master Affects Versions: 0.92.0 Reporter: gaojinchao Assignee: Ashutosh Jindal Priority: Minor Fix For: 0.96.0, 0.94.1 Attachments: hbase-5546.patch, hbase-5546_1.patch, hbase-5546_2.patch, hbase-5546_3.patch, hbase-5546_4.patch Master assigns region in the original region server when RS_ZK_REGION_FAILED_OPEN envent was coming. Maybe we should choose other region server. [2012-03-07 10:14:21,750] [DEBUG] [main-EventThread] [org.apache.hadoop.hbase.master.AssignmentManager 553] Handling transition=RS_ZK_REGION_FAILED_OPEN, server=158-1-130-11,20020,1331108408232, region=c70e98bdca98a0657a56436741523053 [2012-03-07 10:14:31,826] [DEBUG] [main-EventThread] [org.apache.hadoop.hbase.master.AssignmentManager 553] Handling transition=RS_ZK_REGION_FAILED_OPEN, server=158-1-130-11,20020,1331108408232, region=c70e98bdca98a0657a56436741523053 [2012-03-07 10:14:41,903] [DEBUG] [main-EventThread] [org.apache.hadoop.hbase.master.AssignmentManager 553] Handling transition=RS_ZK_REGION_FAILED_OPEN, server=158-1-130-11,20020,1331108408232, region=c70e98bdca98a0657a56436741523053 [2012-03-07 10:14:51,975] [DEBUG] [main-EventThread] [org.apache.hadoop.hbase.master.AssignmentManager 553] Handling transition=RS_ZK_REGION_FAILED_OPEN, server=158-1-130-11,20020,1331108408232, region=c70e98bdca98a0657a56436741523053 [2012-03-07 10:15:02,056] [DEBUG] [main-EventThread] [org.apache.hadoop.hbase.master.AssignmentManager 553] Handling transition=RS_ZK_REGION_FAILED_OPEN, server=158-1-130-11,20020,1331108408232, region=c70e98bdca98a0657a56436741523053 [2012-03-07 10:15:12,167] [DEBUG] [main-EventThread] [org.apache.hadoop.hbase.master.AssignmentManager 553] Handling transition=RS_ZK_REGION_FAILED_OPEN, server=158-1-130-11,20020,1331108408232, region=c70e98bdca98a0657a56436741523053 [2012-03-07 10:15:22,231] [DEBUG] [main-EventThread] [org.apache.hadoop.hbase.master.AssignmentManager 553] Handling transition=RS_ZK_REGION_FAILED_OPEN, server=158-1-130-11,20020,1331108408232, region=c70e98bdca98a0657a56436741523053 [2012-03-07 10:15:32,303] [DEBUG] [main-EventThread] [org.apache.hadoop.hbase.master.AssignmentManager 553] Handling transition=RS_ZK_REGION_FAILED_OPEN, server=158-1-130-11,20020,1331108408232, region=c70e98bdca98a0657a56436741523053 [2012-03-07 10:15:42,375] [DEBUG] [main-EventThread] [org.apache.hadoop.hbase.master.AssignmentManager 553] Handling transition=RS_ZK_REGION_FAILED_OPEN, server=158-1-130-11,20020,1331108408232, region=c70e98bdca98a0657a56436741523053 [2012-03-07 10:15:52,447] [DEBUG] [main-EventThread] [org.apache.hadoop.hbase.master.AssignmentManager 553] Handling transition=RS_ZK_REGION_FAILED_OPEN, server=158-1-130-11,20020,1331108408232, region=c70e98bdca98a0657a56436741523053 [2012-03-07 10:16:02,528] [DEBUG] [main-EventThread] [org.apache.hadoop.hbase.master.AssignmentManager 553] Handling transition=RS_ZK_REGION_FAILED_OPEN, server=158-1-130-11,20020,1331108408232, region=c70e98bdca98a0657a56436741523053 [2012-03-07 10:16:12,600] [DEBUG] [main-EventThread] [org.apache.hadoop.hbase.master.AssignmentManager 553] Handling transition=RS_ZK_REGION_FAILED_OPEN, server=158-1-130-11,20020,1331108408232, region=c70e98bdca98a0657a56436741523053 [2012-03-07 10:16:22,676] [DEBUG] [main-EventThread] [org.apache.hadoop.hbase.master.AssignmentManager 553] Handling transition=RS_ZK_REGION_FAILED_OPEN, server=158-1-130-11,20020,1331108408232, region=c70e98bdca98a0657a56436741523053 -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (HBASE-6011) Unable to start master in local mode
[
https://issues.apache.org/jira/browse/HBASE-6011?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13279035#comment-13279035
]
Hudson commented on HBASE-6011:
---
Integrated in HBase-0.94 #200 (See
[https://builds.apache.org/job/HBase-0.94/200/])
HBASE-6011. Addendum to support master mocking (Ram) (Revision 1340156)
Result = FAILURE
apurtell :
Files :
*
/hbase/branches/0.94/src/main/java/org/apache/hadoop/hbase/LocalHBaseCluster.java
Unable to start master in local mode
Key: HBASE-6011
URL: https://issues.apache.org/jira/browse/HBASE-6011
Project: HBase
Issue Type: Bug
Affects Versions: 0.92.2, 0.96.0, 0.94.1
Reporter: Andrew Purtell
Assignee: Andrew Purtell
Fix For: 0.92.2, 0.96.0, 0.94.1
Attachments: 6011-v2.patch, 6011.patch, HBASE-6011_1.patch,
HBASE-6011_addendum_0.92.patch, HBASE-6011_addendum_0.94.patch,
HBASE-6011_addendum_trunk.patch
Got this trying to launch head of 0.94 branch in local mode from the build
tree but it happens with trunk and 0.92 too:
{noformat}
12/05/15 19:35:45 ERROR master.HMasterCommandLine: Failed to start master
java.lang.ClassCastException: org.apache.hadoop.hbase.master.HMaster cannot
be cast to org.apache.hadoop.hbase.master.HMasterCommandLine$LocalHMaster
at
org.apache.hadoop.hbase.master.HMasterCommandLine.startMaster(HMasterCommandLine.java:142)
at
org.apache.hadoop.hbase.master.HMasterCommandLine.run(HMasterCommandLine.java:103)
at org.apache.hadoop.util.ToolRunner.run(ToolRunner.java:65)
at
org.apache.hadoop.hbase.util.ServerCommandLine.doMain(ServerCommandLine.java:76)
at org.apache.hadoop.hbase.master.HMaster.main(HMaster.java:1761)
{noformat}
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (HBASE-5546) Master assigns region in the original region server when opening region failed
[ https://issues.apache.org/jira/browse/HBASE-5546?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13279095#comment-13279095 ] Hudson commented on HBASE-5546: --- Integrated in HBase-0.94 #201 (See [https://builds.apache.org/job/HBase-0.94/201/]) HBASE-5546 Master assigns region in the original region server when opening region failed (Ashutosh) (Revision 1340190) Result = FAILURE ramkrishna : Files : * /hbase/branches/0.94/src/main/java/org/apache/hadoop/hbase/master/AssignmentManager.java * /hbase/branches/0.94/src/test/java/org/apache/hadoop/hbase/master/TestAssignmentManager.java Master assigns region in the original region server when opening region failed Key: HBASE-5546 URL: https://issues.apache.org/jira/browse/HBASE-5546 Project: HBase Issue Type: Bug Components: master Affects Versions: 0.92.0 Reporter: gaojinchao Assignee: Ashutosh Jindal Priority: Minor Fix For: 0.96.0, 0.94.1 Attachments: hbase-5546.patch, hbase-5546_1.patch, hbase-5546_2.patch, hbase-5546_3.patch, hbase-5546_4.patch Master assigns region in the original region server when RS_ZK_REGION_FAILED_OPEN envent was coming. Maybe we should choose other region server. [2012-03-07 10:14:21,750] [DEBUG] [main-EventThread] [org.apache.hadoop.hbase.master.AssignmentManager 553] Handling transition=RS_ZK_REGION_FAILED_OPEN, server=158-1-130-11,20020,1331108408232, region=c70e98bdca98a0657a56436741523053 [2012-03-07 10:14:31,826] [DEBUG] [main-EventThread] [org.apache.hadoop.hbase.master.AssignmentManager 553] Handling transition=RS_ZK_REGION_FAILED_OPEN, server=158-1-130-11,20020,1331108408232, region=c70e98bdca98a0657a56436741523053 [2012-03-07 10:14:41,903] [DEBUG] [main-EventThread] [org.apache.hadoop.hbase.master.AssignmentManager 553] Handling transition=RS_ZK_REGION_FAILED_OPEN, server=158-1-130-11,20020,1331108408232, region=c70e98bdca98a0657a56436741523053 [2012-03-07 10:14:51,975] [DEBUG] [main-EventThread] [org.apache.hadoop.hbase.master.AssignmentManager 553] Handling transition=RS_ZK_REGION_FAILED_OPEN, server=158-1-130-11,20020,1331108408232, region=c70e98bdca98a0657a56436741523053 [2012-03-07 10:15:02,056] [DEBUG] [main-EventThread] [org.apache.hadoop.hbase.master.AssignmentManager 553] Handling transition=RS_ZK_REGION_FAILED_OPEN, server=158-1-130-11,20020,1331108408232, region=c70e98bdca98a0657a56436741523053 [2012-03-07 10:15:12,167] [DEBUG] [main-EventThread] [org.apache.hadoop.hbase.master.AssignmentManager 553] Handling transition=RS_ZK_REGION_FAILED_OPEN, server=158-1-130-11,20020,1331108408232, region=c70e98bdca98a0657a56436741523053 [2012-03-07 10:15:22,231] [DEBUG] [main-EventThread] [org.apache.hadoop.hbase.master.AssignmentManager 553] Handling transition=RS_ZK_REGION_FAILED_OPEN, server=158-1-130-11,20020,1331108408232, region=c70e98bdca98a0657a56436741523053 [2012-03-07 10:15:32,303] [DEBUG] [main-EventThread] [org.apache.hadoop.hbase.master.AssignmentManager 553] Handling transition=RS_ZK_REGION_FAILED_OPEN, server=158-1-130-11,20020,1331108408232, region=c70e98bdca98a0657a56436741523053 [2012-03-07 10:15:42,375] [DEBUG] [main-EventThread] [org.apache.hadoop.hbase.master.AssignmentManager 553] Handling transition=RS_ZK_REGION_FAILED_OPEN, server=158-1-130-11,20020,1331108408232, region=c70e98bdca98a0657a56436741523053 [2012-03-07 10:15:52,447] [DEBUG] [main-EventThread] [org.apache.hadoop.hbase.master.AssignmentManager 553] Handling transition=RS_ZK_REGION_FAILED_OPEN, server=158-1-130-11,20020,1331108408232, region=c70e98bdca98a0657a56436741523053 [2012-03-07 10:16:02,528] [DEBUG] [main-EventThread] [org.apache.hadoop.hbase.master.AssignmentManager 553] Handling transition=RS_ZK_REGION_FAILED_OPEN, server=158-1-130-11,20020,1331108408232, region=c70e98bdca98a0657a56436741523053 [2012-03-07 10:16:12,600] [DEBUG] [main-EventThread] [org.apache.hadoop.hbase.master.AssignmentManager 553] Handling transition=RS_ZK_REGION_FAILED_OPEN, server=158-1-130-11,20020,1331108408232, region=c70e98bdca98a0657a56436741523053 [2012-03-07 10:16:22,676] [DEBUG] [main-EventThread] [org.apache.hadoop.hbase.master.AssignmentManager 553] Handling transition=RS_ZK_REGION_FAILED_OPEN, server=158-1-130-11,20020,1331108408232, region=c70e98bdca98a0657a56436741523053 -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (HBASE-6011) Unable to start master in local mode
[
https://issues.apache.org/jira/browse/HBASE-6011?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13279100#comment-13279100
]
Hudson commented on HBASE-6011:
---
Integrated in HBase-0.92 #412 (See
[https://builds.apache.org/job/HBase-0.92/412/])
HBASE-6011. Addendum to support master mocking (Ram) (Revision 1340157)
Result = FAILURE
apurtell :
Files :
*
/hbase/branches/0.92/src/main/java/org/apache/hadoop/hbase/LocalHBaseCluster.java
Unable to start master in local mode
Key: HBASE-6011
URL: https://issues.apache.org/jira/browse/HBASE-6011
Project: HBase
Issue Type: Bug
Affects Versions: 0.92.2, 0.96.0, 0.94.1
Reporter: Andrew Purtell
Assignee: Andrew Purtell
Fix For: 0.92.2, 0.96.0, 0.94.1
Attachments: 6011-v2.patch, 6011.patch, HBASE-6011_1.patch,
HBASE-6011_addendum_0.92.patch, HBASE-6011_addendum_0.94.patch,
HBASE-6011_addendum_trunk.patch
Got this trying to launch head of 0.94 branch in local mode from the build
tree but it happens with trunk and 0.92 too:
{noformat}
12/05/15 19:35:45 ERROR master.HMasterCommandLine: Failed to start master
java.lang.ClassCastException: org.apache.hadoop.hbase.master.HMaster cannot
be cast to org.apache.hadoop.hbase.master.HMasterCommandLine$LocalHMaster
at
org.apache.hadoop.hbase.master.HMasterCommandLine.startMaster(HMasterCommandLine.java:142)
at
org.apache.hadoop.hbase.master.HMasterCommandLine.run(HMasterCommandLine.java:103)
at org.apache.hadoop.util.ToolRunner.run(ToolRunner.java:65)
at
org.apache.hadoop.hbase.util.ServerCommandLine.doMain(ServerCommandLine.java:76)
at org.apache.hadoop.hbase.master.HMaster.main(HMaster.java:1761)
{noformat}
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (HBASE-5926) Delete the master znode after a master crash
[ https://issues.apache.org/jira/browse/HBASE-5926?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13279122#comment-13279122 ] Hudson commented on HBASE-5926: --- Integrated in HBase-TRUNK #2900 (See [https://builds.apache.org/job/HBase-TRUNK/2900/]) HBASE-5926 Delete the master znode after a master crash (Revision 1340200) Result = SUCCESS stack : Files : * /hbase/trunk/src/main/java/org/apache/hadoop/hbase/ZNodeClearer.java Delete the master znode after a master crash Key: HBASE-5926 URL: https://issues.apache.org/jira/browse/HBASE-5926 Project: HBase Issue Type: Improvement Components: master, scripts Affects Versions: 0.96.0 Reporter: nkeywal Assignee: nkeywal Priority: Minor Fix For: 0.96.0 Attachments: 5926.v10.patch, 5926.v11.patch, 5926.v13.patch, 5926.v14.patch, 5926.v6.patch, 5926.v8.patch, 5926.v9.patch This is the continuation of the work done in HBASE-5844. But we can't apply exactly the same strategy: for the region server, there is a znode per region server, while for the master backup master there is a single znode for both. So if we apply the same strategy as for a regionserver, we may have this scenario: 1) Master starts 2) Backup master starts 3) Master dies 4) ZK detects it 5) Backup master receives the update from ZK 6) Backup master creates the new master node and become the main master 7) Previous master script continues 8) Previous master script deletes the master node in ZK 9) = issue: we deleted the node just created by the new master This should not happen often (usually the znode will be deleted soon enough), but it can happen. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (HBASE-5920) New Compactions Logic can silently prevent user-initiated compactions from occurring
[
https://issues.apache.org/jira/browse/HBASE-5920?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13279328#comment-13279328
]
Hudson commented on HBASE-5920:
---
Integrated in HBase-TRUNK #2903 (See
[https://builds.apache.org/job/HBase-TRUNK/2903/])
HBASE-5920 New Compactions Logic can silently prevent user-initiated
compactions from occurring (Revision 1340280)
Result = FAILURE
stack :
Files :
*
/hbase/trunk/src/main/java/org/apache/hadoop/hbase/regionserver/CompactSplitThread.java
*
/hbase/trunk/src/main/java/org/apache/hadoop/hbase/regionserver/HRegionServer.java
* /hbase/trunk/src/main/java/org/apache/hadoop/hbase/regionserver/Store.java
*
/hbase/trunk/src/test/java/org/apache/hadoop/hbase/regionserver/TestCompaction.java
New Compactions Logic can silently prevent user-initiated compactions from
occurring
Key: HBASE-5920
URL: https://issues.apache.org/jira/browse/HBASE-5920
Project: HBase
Issue Type: Bug
Components: client, regionserver
Affects Versions: 0.92.1
Reporter: Derek Wollenstein
Assignee: Derek Wollenstein
Priority: Minor
Labels: compaction
Attachments: 5290-094.txt, HBASE-5920-0.92.1-1.patch,
HBASE-5920-0.92.1-2.patch, HBASE-5920-0.92.1.patch, HBASE-5920-trunk-1.patch,
HBASE-5920-trunk.patch
There seem to be some tuning settings in which manually triggered major
compactions will do nothing, including loggic
From Store.java in the function
ListStoreFile compactSelection(ListStoreFile candidates)
When a user manually triggers a compaction, this follows the same logic as a
normal compaction check. when a user manually triggers a major compaction,
something similar happens. Putting this all together:
1. If a user triggers a major compaction, this is checked against a max files
threshold (hbase.hstore.compaction.max). If the number of storefiles to
compact is max files, then we downgrade to a minor compaction
2. If we are in a minor compaction, we do the following checks:
a. If the file is less than a minimum size
(hbase.hstore.compaction.min.size) we automatically include it
b. Otherwise, we check how the size compares to the next largest size.
based on hbase.hstore.compaction.ratio.
c. If the number of files included is less than a minimum count
(hbase.hstore.compaction.min) then don't compact.
In many of the exit strategies, we aren't seeing an error message.
The net-net of this is that if we have a mix of very large and very small
files, we may end up having too many files to do a major compact, but too few
files to do a minor compact.
I'm trying to go through and see if I'm understanding things correctly, but
this seems like the bug
To put it another way
2012-05-02 20:09:36,389 DEBUG
org.apache.hadoop.hbase.regionserver.CompactSplitThread: Large Compaction
requested:
regionName=str,44594594594594592,1334939064521.f7aed25b55d4d7988af763bede9ce74e.,
store
Name=c, fileCount=15, fileSize=1.5g (20.2k, 362.5m, 155.3k, 3.0m, 30.7k,
361.2m, 6.9m, 4.7m, 14.7k, 363.4m, 30.9m, 3.2m, 7.3k, 362.9m, 23.5m),
priority=-9, time=3175046817624398; Because: Recursive enqueue;
compaction_queue=(59:0), split_queue=0
When we had a minimum compaction size of 128M, and default settings for
hbase.hstore.compaction.min,hbase.hstore.compaction.max,hbase.hstore.compaction.ratio,
we were not getting a compaction to run even if we ran
major_compact
'str,44594594594594592,1334939064521.f7aed25b55d4d7988af763bede9ce74e.' from
the ruby shell. Note that we had many tiny regions (20k, 155k, 3m, 30k,..)
and several large regions (362.5m,361.2m,363.4m,362.9m). I think the bimodal
nature of the sizes prevented us from doing a compaction.
I'm not 100% sure where this errored out because when I manually triggered a
compaction, I did not see
' // if we don't have enough files to compact, just wait
if (filesToCompact.size() this.minFilesToCompact) {
if (LOG.isDebugEnabled()) {
LOG.debug(Skipped compaction of + this.storeNameStr
+ . Only + (end - start) + file(s) of size
+ StringUtils.humanReadableInt(totalSize)
+ have met compaction criteria.);
}
'
being printed in the logs (and I know DEBUG logging was enabled because I saw
this elsewhere).
I'd be happy with better error messages when we decide not to compact for
user enabled compactions.
I'd also like to see some override that says user triggered major compaction
always
[jira] [Commented] (HBASE-5926) Delete the master znode after a master crash
[ https://issues.apache.org/jira/browse/HBASE-5926?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13279333#comment-13279333 ] Hudson commented on HBASE-5926: --- Integrated in HBase-TRUNK-on-Hadoop-2.0.0 #10 (See [https://builds.apache.org/job/HBase-TRUNK-on-Hadoop-2.0.0/10/]) HBASE-5926 Delete the master znode after a master crash (Revision 1340200) HBASE-5926 Delete the master znode after a master crash (Revision 1340185) Result = FAILURE stack : Files : * /hbase/trunk/src/main/java/org/apache/hadoop/hbase/ZNodeClearer.java stack : Files : * /hbase/trunk/bin/hbase-daemon.sh * /hbase/trunk/src/main/java/org/apache/hadoop/hbase/master/ActiveMasterManager.java * /hbase/trunk/src/main/java/org/apache/hadoop/hbase/master/HMasterCommandLine.java * /hbase/trunk/src/main/java/org/apache/hadoop/hbase/regionserver/HRegionServer.java * /hbase/trunk/src/main/java/org/apache/hadoop/hbase/zookeeper/MasterAddressTracker.java * /hbase/trunk/src/test/java/org/apache/hadoop/hbase/zookeeper/TestZooKeeperNodeTracker.java Delete the master znode after a master crash Key: HBASE-5926 URL: https://issues.apache.org/jira/browse/HBASE-5926 Project: HBase Issue Type: Improvement Components: master, scripts Affects Versions: 0.96.0 Reporter: nkeywal Assignee: nkeywal Priority: Minor Fix For: 0.96.0 Attachments: 5926.v10.patch, 5926.v11.patch, 5926.v13.patch, 5926.v14.patch, 5926.v6.patch, 5926.v8.patch, 5926.v9.patch This is the continuation of the work done in HBASE-5844. But we can't apply exactly the same strategy: for the region server, there is a znode per region server, while for the master backup master there is a single znode for both. So if we apply the same strategy as for a regionserver, we may have this scenario: 1) Master starts 2) Backup master starts 3) Master dies 4) ZK detects it 5) Backup master receives the update from ZK 6) Backup master creates the new master node and become the main master 7) Previous master script continues 8) Previous master script deletes the master node in ZK 9) = issue: we deleted the node just created by the new master This should not happen often (usually the znode will be deleted soon enough), but it can happen. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (HBASE-6011) Unable to start master in local mode
[
https://issues.apache.org/jira/browse/HBASE-6011?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13279334#comment-13279334
]
Hudson commented on HBASE-6011:
---
Integrated in HBase-TRUNK-on-Hadoop-2.0.0 #10 (See
[https://builds.apache.org/job/HBase-TRUNK-on-Hadoop-2.0.0/10/])
HBASE-6011. Addendum to support master mocking (Ram) (Revision 1340155)
Result = FAILURE
apurtell :
Files :
* /hbase/trunk/src/main/java/org/apache/hadoop/hbase/LocalHBaseCluster.java
Unable to start master in local mode
Key: HBASE-6011
URL: https://issues.apache.org/jira/browse/HBASE-6011
Project: HBase
Issue Type: Bug
Affects Versions: 0.92.2, 0.96.0, 0.94.1
Reporter: Andrew Purtell
Assignee: Andrew Purtell
Fix For: 0.92.2, 0.96.0, 0.94.1
Attachments: 6011-v2.patch, 6011.patch, HBASE-6011_1.patch,
HBASE-6011_addendum_0.92.patch, HBASE-6011_addendum_0.94.patch,
HBASE-6011_addendum_trunk.patch
Got this trying to launch head of 0.94 branch in local mode from the build
tree but it happens with trunk and 0.92 too:
{noformat}
12/05/15 19:35:45 ERROR master.HMasterCommandLine: Failed to start master
java.lang.ClassCastException: org.apache.hadoop.hbase.master.HMaster cannot
be cast to org.apache.hadoop.hbase.master.HMasterCommandLine$LocalHMaster
at
org.apache.hadoop.hbase.master.HMasterCommandLine.startMaster(HMasterCommandLine.java:142)
at
org.apache.hadoop.hbase.master.HMasterCommandLine.run(HMasterCommandLine.java:103)
at org.apache.hadoop.util.ToolRunner.run(ToolRunner.java:65)
at
org.apache.hadoop.hbase.util.ServerCommandLine.doMain(ServerCommandLine.java:76)
at org.apache.hadoop.hbase.master.HMaster.main(HMaster.java:1761)
{noformat}
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (HBASE-5546) Master assigns region in the original region server when opening region failed
[ https://issues.apache.org/jira/browse/HBASE-5546?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13279335#comment-13279335 ] Hudson commented on HBASE-5546: --- Integrated in HBase-TRUNK-on-Hadoop-2.0.0 #10 (See [https://builds.apache.org/job/HBase-TRUNK-on-Hadoop-2.0.0/10/]) HBASE-5546 Master assigns region in the original region server when opening region failed (Ashutosh) (Revision 1340187) Result = FAILURE ramkrishna : Files : * /hbase/trunk/src/main/java/org/apache/hadoop/hbase/master/AssignmentManager.java * /hbase/trunk/src/test/java/org/apache/hadoop/hbase/master/TestAssignmentManager.java Master assigns region in the original region server when opening region failed Key: HBASE-5546 URL: https://issues.apache.org/jira/browse/HBASE-5546 Project: HBase Issue Type: Bug Components: master Affects Versions: 0.92.0 Reporter: gaojinchao Assignee: Ashutosh Jindal Priority: Minor Fix For: 0.96.0, 0.94.1 Attachments: hbase-5546.patch, hbase-5546_1.patch, hbase-5546_2.patch, hbase-5546_3.patch, hbase-5546_4.patch Master assigns region in the original region server when RS_ZK_REGION_FAILED_OPEN envent was coming. Maybe we should choose other region server. [2012-03-07 10:14:21,750] [DEBUG] [main-EventThread] [org.apache.hadoop.hbase.master.AssignmentManager 553] Handling transition=RS_ZK_REGION_FAILED_OPEN, server=158-1-130-11,20020,1331108408232, region=c70e98bdca98a0657a56436741523053 [2012-03-07 10:14:31,826] [DEBUG] [main-EventThread] [org.apache.hadoop.hbase.master.AssignmentManager 553] Handling transition=RS_ZK_REGION_FAILED_OPEN, server=158-1-130-11,20020,1331108408232, region=c70e98bdca98a0657a56436741523053 [2012-03-07 10:14:41,903] [DEBUG] [main-EventThread] [org.apache.hadoop.hbase.master.AssignmentManager 553] Handling transition=RS_ZK_REGION_FAILED_OPEN, server=158-1-130-11,20020,1331108408232, region=c70e98bdca98a0657a56436741523053 [2012-03-07 10:14:51,975] [DEBUG] [main-EventThread] [org.apache.hadoop.hbase.master.AssignmentManager 553] Handling transition=RS_ZK_REGION_FAILED_OPEN, server=158-1-130-11,20020,1331108408232, region=c70e98bdca98a0657a56436741523053 [2012-03-07 10:15:02,056] [DEBUG] [main-EventThread] [org.apache.hadoop.hbase.master.AssignmentManager 553] Handling transition=RS_ZK_REGION_FAILED_OPEN, server=158-1-130-11,20020,1331108408232, region=c70e98bdca98a0657a56436741523053 [2012-03-07 10:15:12,167] [DEBUG] [main-EventThread] [org.apache.hadoop.hbase.master.AssignmentManager 553] Handling transition=RS_ZK_REGION_FAILED_OPEN, server=158-1-130-11,20020,1331108408232, region=c70e98bdca98a0657a56436741523053 [2012-03-07 10:15:22,231] [DEBUG] [main-EventThread] [org.apache.hadoop.hbase.master.AssignmentManager 553] Handling transition=RS_ZK_REGION_FAILED_OPEN, server=158-1-130-11,20020,1331108408232, region=c70e98bdca98a0657a56436741523053 [2012-03-07 10:15:32,303] [DEBUG] [main-EventThread] [org.apache.hadoop.hbase.master.AssignmentManager 553] Handling transition=RS_ZK_REGION_FAILED_OPEN, server=158-1-130-11,20020,1331108408232, region=c70e98bdca98a0657a56436741523053 [2012-03-07 10:15:42,375] [DEBUG] [main-EventThread] [org.apache.hadoop.hbase.master.AssignmentManager 553] Handling transition=RS_ZK_REGION_FAILED_OPEN, server=158-1-130-11,20020,1331108408232, region=c70e98bdca98a0657a56436741523053 [2012-03-07 10:15:52,447] [DEBUG] [main-EventThread] [org.apache.hadoop.hbase.master.AssignmentManager 553] Handling transition=RS_ZK_REGION_FAILED_OPEN, server=158-1-130-11,20020,1331108408232, region=c70e98bdca98a0657a56436741523053 [2012-03-07 10:16:02,528] [DEBUG] [main-EventThread] [org.apache.hadoop.hbase.master.AssignmentManager 553] Handling transition=RS_ZK_REGION_FAILED_OPEN, server=158-1-130-11,20020,1331108408232, region=c70e98bdca98a0657a56436741523053 [2012-03-07 10:16:12,600] [DEBUG] [main-EventThread] [org.apache.hadoop.hbase.master.AssignmentManager 553] Handling transition=RS_ZK_REGION_FAILED_OPEN, server=158-1-130-11,20020,1331108408232, region=c70e98bdca98a0657a56436741523053 [2012-03-07 10:16:22,676] [DEBUG] [main-EventThread] [org.apache.hadoop.hbase.master.AssignmentManager 553] Handling transition=RS_ZK_REGION_FAILED_OPEN, server=158-1-130-11,20020,1331108408232, region=c70e98bdca98a0657a56436741523053 -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (HBASE-5920) New Compactions Logic can silently prevent user-initiated compactions from occurring
[
https://issues.apache.org/jira/browse/HBASE-5920?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13279336#comment-13279336
]
Hudson commented on HBASE-5920:
---
Integrated in HBase-TRUNK-on-Hadoop-2.0.0 #10 (See
[https://builds.apache.org/job/HBase-TRUNK-on-Hadoop-2.0.0/10/])
HBASE-5920 New Compactions Logic can silently prevent user-initiated
compactions from occurring (Revision 1340280)
Result = FAILURE
stack :
Files :
*
/hbase/trunk/src/main/java/org/apache/hadoop/hbase/regionserver/CompactSplitThread.java
*
/hbase/trunk/src/main/java/org/apache/hadoop/hbase/regionserver/HRegionServer.java
* /hbase/trunk/src/main/java/org/apache/hadoop/hbase/regionserver/Store.java
*
/hbase/trunk/src/test/java/org/apache/hadoop/hbase/regionserver/TestCompaction.java
New Compactions Logic can silently prevent user-initiated compactions from
occurring
Key: HBASE-5920
URL: https://issues.apache.org/jira/browse/HBASE-5920
Project: HBase
Issue Type: Bug
Components: client, regionserver
Affects Versions: 0.92.1
Reporter: Derek Wollenstein
Assignee: Derek Wollenstein
Priority: Minor
Labels: compaction
Attachments: 5290-094.txt, HBASE-5920-0.92.1-1.patch,
HBASE-5920-0.92.1-2.patch, HBASE-5920-0.92.1.patch, HBASE-5920-trunk-1.patch,
HBASE-5920-trunk.patch
There seem to be some tuning settings in which manually triggered major
compactions will do nothing, including loggic
From Store.java in the function
ListStoreFile compactSelection(ListStoreFile candidates)
When a user manually triggers a compaction, this follows the same logic as a
normal compaction check. when a user manually triggers a major compaction,
something similar happens. Putting this all together:
1. If a user triggers a major compaction, this is checked against a max files
threshold (hbase.hstore.compaction.max). If the number of storefiles to
compact is max files, then we downgrade to a minor compaction
2. If we are in a minor compaction, we do the following checks:
a. If the file is less than a minimum size
(hbase.hstore.compaction.min.size) we automatically include it
b. Otherwise, we check how the size compares to the next largest size.
based on hbase.hstore.compaction.ratio.
c. If the number of files included is less than a minimum count
(hbase.hstore.compaction.min) then don't compact.
In many of the exit strategies, we aren't seeing an error message.
The net-net of this is that if we have a mix of very large and very small
files, we may end up having too many files to do a major compact, but too few
files to do a minor compact.
I'm trying to go through and see if I'm understanding things correctly, but
this seems like the bug
To put it another way
2012-05-02 20:09:36,389 DEBUG
org.apache.hadoop.hbase.regionserver.CompactSplitThread: Large Compaction
requested:
regionName=str,44594594594594592,1334939064521.f7aed25b55d4d7988af763bede9ce74e.,
store
Name=c, fileCount=15, fileSize=1.5g (20.2k, 362.5m, 155.3k, 3.0m, 30.7k,
361.2m, 6.9m, 4.7m, 14.7k, 363.4m, 30.9m, 3.2m, 7.3k, 362.9m, 23.5m),
priority=-9, time=3175046817624398; Because: Recursive enqueue;
compaction_queue=(59:0), split_queue=0
When we had a minimum compaction size of 128M, and default settings for
hbase.hstore.compaction.min,hbase.hstore.compaction.max,hbase.hstore.compaction.ratio,
we were not getting a compaction to run even if we ran
major_compact
'str,44594594594594592,1334939064521.f7aed25b55d4d7988af763bede9ce74e.' from
the ruby shell. Note that we had many tiny regions (20k, 155k, 3m, 30k,..)
and several large regions (362.5m,361.2m,363.4m,362.9m). I think the bimodal
nature of the sizes prevented us from doing a compaction.
I'm not 100% sure where this errored out because when I manually triggered a
compaction, I did not see
' // if we don't have enough files to compact, just wait
if (filesToCompact.size() this.minFilesToCompact) {
if (LOG.isDebugEnabled()) {
LOG.debug(Skipped compaction of + this.storeNameStr
+ . Only + (end - start) + file(s) of size
+ StringUtils.humanReadableInt(totalSize)
+ have met compaction criteria.);
}
'
being printed in the logs (and I know DEBUG logging was enabled because I saw
this elsewhere).
I'd be happy with better error messages when we decide not to compact for
user enabled compactions.
I'd also like to see some override that says user triggered
[jira] [Commented] (HBASE-5920) New Compactions Logic can silently prevent user-initiated compactions from occurring
[
https://issues.apache.org/jira/browse/HBASE-5920?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13279348#comment-13279348
]
Hudson commented on HBASE-5920:
---
Integrated in HBase-0.94 #202 (See
[https://builds.apache.org/job/HBase-0.94/202/])
HBASE-5920 New Compactions Logic can silently prevent user-initiated
compactions from occurring (Revision 1340283)
Result = SUCCESS
stack :
Files :
*
/hbase/branches/0.94/src/main/java/org/apache/hadoop/hbase/regionserver/CompactSplitThread.java
*
/hbase/branches/0.94/src/main/java/org/apache/hadoop/hbase/regionserver/HRegionServer.java
*
/hbase/branches/0.94/src/main/java/org/apache/hadoop/hbase/regionserver/Store.java
*
/hbase/branches/0.94/src/test/java/org/apache/hadoop/hbase/regionserver/TestCompaction.java
New Compactions Logic can silently prevent user-initiated compactions from
occurring
Key: HBASE-5920
URL: https://issues.apache.org/jira/browse/HBASE-5920
Project: HBase
Issue Type: Bug
Components: client, regionserver
Affects Versions: 0.92.1
Reporter: Derek Wollenstein
Assignee: Derek Wollenstein
Priority: Minor
Labels: compaction
Attachments: 5290-094.txt, HBASE-5920-0.92.1-1.patch,
HBASE-5920-0.92.1-2.patch, HBASE-5920-0.92.1.patch, HBASE-5920-trunk-1.patch,
HBASE-5920-trunk.patch
There seem to be some tuning settings in which manually triggered major
compactions will do nothing, including loggic
From Store.java in the function
ListStoreFile compactSelection(ListStoreFile candidates)
When a user manually triggers a compaction, this follows the same logic as a
normal compaction check. when a user manually triggers a major compaction,
something similar happens. Putting this all together:
1. If a user triggers a major compaction, this is checked against a max files
threshold (hbase.hstore.compaction.max). If the number of storefiles to
compact is max files, then we downgrade to a minor compaction
2. If we are in a minor compaction, we do the following checks:
a. If the file is less than a minimum size
(hbase.hstore.compaction.min.size) we automatically include it
b. Otherwise, we check how the size compares to the next largest size.
based on hbase.hstore.compaction.ratio.
c. If the number of files included is less than a minimum count
(hbase.hstore.compaction.min) then don't compact.
In many of the exit strategies, we aren't seeing an error message.
The net-net of this is that if we have a mix of very large and very small
files, we may end up having too many files to do a major compact, but too few
files to do a minor compact.
I'm trying to go through and see if I'm understanding things correctly, but
this seems like the bug
To put it another way
2012-05-02 20:09:36,389 DEBUG
org.apache.hadoop.hbase.regionserver.CompactSplitThread: Large Compaction
requested:
regionName=str,44594594594594592,1334939064521.f7aed25b55d4d7988af763bede9ce74e.,
store
Name=c, fileCount=15, fileSize=1.5g (20.2k, 362.5m, 155.3k, 3.0m, 30.7k,
361.2m, 6.9m, 4.7m, 14.7k, 363.4m, 30.9m, 3.2m, 7.3k, 362.9m, 23.5m),
priority=-9, time=3175046817624398; Because: Recursive enqueue;
compaction_queue=(59:0), split_queue=0
When we had a minimum compaction size of 128M, and default settings for
hbase.hstore.compaction.min,hbase.hstore.compaction.max,hbase.hstore.compaction.ratio,
we were not getting a compaction to run even if we ran
major_compact
'str,44594594594594592,1334939064521.f7aed25b55d4d7988af763bede9ce74e.' from
the ruby shell. Note that we had many tiny regions (20k, 155k, 3m, 30k,..)
and several large regions (362.5m,361.2m,363.4m,362.9m). I think the bimodal
nature of the sizes prevented us from doing a compaction.
I'm not 100% sure where this errored out because when I manually triggered a
compaction, I did not see
' // if we don't have enough files to compact, just wait
if (filesToCompact.size() this.minFilesToCompact) {
if (LOG.isDebugEnabled()) {
LOG.debug(Skipped compaction of + this.storeNameStr
+ . Only + (end - start) + file(s) of size
+ StringUtils.humanReadableInt(totalSize)
+ have met compaction criteria.);
}
'
being printed in the logs (and I know DEBUG logging was enabled because I saw
this elsewhere).
I'd be happy with better error messages when we decide not to compact for
user enabled compactions.
I'd also like to see some override that says user triggered
[jira] [Commented] (HBASE-6007) Make getTableRegions return an empty list if the table does not exist
[ https://issues.apache.org/jira/browse/HBASE-6007?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13279374#comment-13279374 ] Hudson commented on HBASE-6007: --- Integrated in HBase-TRUNK #2904 (See [https://builds.apache.org/job/HBase-TRUNK/2904/]) [jira] [HBASE-6007] Make getTableRegions return an empty list if the table does not exist Summary: Making the getTableRegions Thrift API method handle TableNotFoundException and return an empty list in that case. Without this the behavior is dependent on whether an HTable object is present in the thread-local cache in case a table was deleted. Test Plan: Unit tests Reviewers: kannan, liyintang Reviewed By: liyintang CC: stack Differential Revision: https://reviews.facebook.net/D3243 (Revision 1340310) Result = FAILURE mbautin : Files : * /hbase/trunk/src/main/java/org/apache/hadoop/hbase/thrift/ThriftServerRunner.java Make getTableRegions return an empty list if the table does not exist - Key: HBASE-6007 URL: https://issues.apache.org/jira/browse/HBASE-6007 Project: HBase Issue Type: Bug Reporter: Mikhail Bautin Assignee: Mikhail Bautin Priority: Minor Attachments: D3243.1.patch, jira-HBASE-6007-Make-getTableRegions-return-an-empty-2012-05-18_17_02_40.patch Making the getTableRegions Thrift API method handle TableNotFoundException and return an empty list in that case. Without this the behavior is dependent on whether an HTable object is present in the thread-local cache in case a table was deleted. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (HBASE-5920) New Compactions Logic can silently prevent user-initiated compactions from occurring
[
https://issues.apache.org/jira/browse/HBASE-5920?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13279385#comment-13279385
]
Hudson commented on HBASE-5920:
---
Integrated in HBase-0.92 #413 (See
[https://builds.apache.org/job/HBase-0.92/413/])
HBASE-5920 New Compactions Logic can silently prevent user-initiated
compactions from occurring (Revision 1340285)
Result = FAILURE
stack :
Files :
* /hbase/branches/0.92/CHANGES.txt
*
/hbase/branches/0.92/src/main/java/org/apache/hadoop/hbase/regionserver/CompactSplitThread.java
*
/hbase/branches/0.92/src/main/java/org/apache/hadoop/hbase/regionserver/HRegionServer.java
*
/hbase/branches/0.92/src/main/java/org/apache/hadoop/hbase/regionserver/Store.java
*
/hbase/branches/0.92/src/main/java/org/apache/hadoop/hbase/regionserver/compactions/CompactionRequest.java
*
/hbase/branches/0.92/src/test/java/org/apache/hadoop/hbase/regionserver/TestCompaction.java
New Compactions Logic can silently prevent user-initiated compactions from
occurring
Key: HBASE-5920
URL: https://issues.apache.org/jira/browse/HBASE-5920
Project: HBase
Issue Type: Bug
Components: client, regionserver
Affects Versions: 0.92.1
Reporter: Derek Wollenstein
Assignee: Derek Wollenstein
Priority: Minor
Labels: compaction
Attachments: 5290-094.txt, HBASE-5920-0.92.1-1.patch,
HBASE-5920-0.92.1-2.patch, HBASE-5920-0.92.1.patch, HBASE-5920-trunk-1.patch,
HBASE-5920-trunk.patch
There seem to be some tuning settings in which manually triggered major
compactions will do nothing, including loggic
From Store.java in the function
ListStoreFile compactSelection(ListStoreFile candidates)
When a user manually triggers a compaction, this follows the same logic as a
normal compaction check. when a user manually triggers a major compaction,
something similar happens. Putting this all together:
1. If a user triggers a major compaction, this is checked against a max files
threshold (hbase.hstore.compaction.max). If the number of storefiles to
compact is max files, then we downgrade to a minor compaction
2. If we are in a minor compaction, we do the following checks:
a. If the file is less than a minimum size
(hbase.hstore.compaction.min.size) we automatically include it
b. Otherwise, we check how the size compares to the next largest size.
based on hbase.hstore.compaction.ratio.
c. If the number of files included is less than a minimum count
(hbase.hstore.compaction.min) then don't compact.
In many of the exit strategies, we aren't seeing an error message.
The net-net of this is that if we have a mix of very large and very small
files, we may end up having too many files to do a major compact, but too few
files to do a minor compact.
I'm trying to go through and see if I'm understanding things correctly, but
this seems like the bug
To put it another way
2012-05-02 20:09:36,389 DEBUG
org.apache.hadoop.hbase.regionserver.CompactSplitThread: Large Compaction
requested:
regionName=str,44594594594594592,1334939064521.f7aed25b55d4d7988af763bede9ce74e.,
store
Name=c, fileCount=15, fileSize=1.5g (20.2k, 362.5m, 155.3k, 3.0m, 30.7k,
361.2m, 6.9m, 4.7m, 14.7k, 363.4m, 30.9m, 3.2m, 7.3k, 362.9m, 23.5m),
priority=-9, time=3175046817624398; Because: Recursive enqueue;
compaction_queue=(59:0), split_queue=0
When we had a minimum compaction size of 128M, and default settings for
hbase.hstore.compaction.min,hbase.hstore.compaction.max,hbase.hstore.compaction.ratio,
we were not getting a compaction to run even if we ran
major_compact
'str,44594594594594592,1334939064521.f7aed25b55d4d7988af763bede9ce74e.' from
the ruby shell. Note that we had many tiny regions (20k, 155k, 3m, 30k,..)
and several large regions (362.5m,361.2m,363.4m,362.9m). I think the bimodal
nature of the sizes prevented us from doing a compaction.
I'm not 100% sure where this errored out because when I manually triggered a
compaction, I did not see
' // if we don't have enough files to compact, just wait
if (filesToCompact.size() this.minFilesToCompact) {
if (LOG.isDebugEnabled()) {
LOG.debug(Skipped compaction of + this.storeNameStr
+ . Only + (end - start) + file(s) of size
+ StringUtils.humanReadableInt(totalSize)
+ have met compaction criteria.);
}
'
being printed in the logs (and I know DEBUG logging was enabled because I saw
this elsewhere).
I'd be happy with
[jira] [Commented] (HBASE-5922) HalfStoreFileReader seekBefore causes StackOverflowError
[ https://issues.apache.org/jira/browse/HBASE-5922?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13279404#comment-13279404 ] Hudson commented on HBASE-5922: --- Integrated in HBase-0.94-security #27 (See [https://builds.apache.org/job/HBase-0.94-security/27/]) HBASE-5922 HalfStoreFileReader seekBefore causes StackOverflowError (Revision 1337411) Result = SUCCESS stack : Files : * /hbase/branches/0.94/src/main/java/org/apache/hadoop/hbase/io/HalfStoreFileReader.java * /hbase/branches/0.94/src/test/java/org/apache/hadoop/hbase/io/TestHalfStoreFileReader.java HalfStoreFileReader seekBefore causes StackOverflowError Key: HBASE-5922 URL: https://issues.apache.org/jira/browse/HBASE-5922 Project: HBase Issue Type: Bug Components: client, io Affects Versions: 0.90.0 Environment: HBase 0.90.4 Reporter: Nate Putnam Assignee: Nate Putnam Priority: Critical Fix For: 0.90.7, 0.92.2, 0.96.0, 0.94.1 Attachments: 5922.092.txt, HBASE-5922.patch, HBASE-5922.patch, HBASE-5922.v2.patch, HBASE-5922.v3.patch, HBASE-5922.v4.patch Calling HRegionServer.getClosestRowBefore() can cause a stack overflow if the underlying store file is a reference and the row key is in the bottom. java.io.IOException: java.io.IOException: java.lang.StackOverflowError at org.apache.hadoop.hbase.regionserver.HRegionServer.convertThrowableToIOE(HRegionServer.java:990) at org.apache.hadoop.hbase.regionserver.HRegionServer.convertThrowableToIOE(HRegionServer.java:978) at org.apache.hadoop.hbase.regionserver.HRegionServer.getClosestRowBefore(HRegionServer.java:1651) at sun.reflect.GeneratedMethodAccessor174.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:597) at org.apache.hadoop.hbase.ipc.HBaseRPC$Server.call(HBaseRPC.java:570) at org.apache.hadoop.hbase.ipc.HBaseServer$Handler.run(HBaseServer.java:1039) Caused by: java.lang.StackOverflowError at org.apache.hadoop.hbase.io.HalfStoreFileReader$1.seekBefore(HalfStoreFileReader.java:147) at org.apache.hadoop.hbase.io.HalfStoreFileReader$1.seekBefore(HalfStoreFileReader.java:149) at org.apache.hadoop.hbase.io.HalfStoreFileReader$1.seekBefore(HalfStoreFileReader.java:149) at org.apache.hadoop.hbase.io.HalfStoreFileReader$1.seekBefore(HalfStoreFileReader.java:149) at org.apache.hadoop.hbase.io.HalfStoreFileReader$1.seekBefore(HalfStoreFileReader.java:149) -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (HBASE-6004) Adding more logging to help debugging MR job
[ https://issues.apache.org/jira/browse/HBASE-6004?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13279407#comment-13279407 ] Hudson commented on HBASE-6004: --- Integrated in HBase-0.94-security #27 (See [https://builds.apache.org/job/HBase-0.94-security/27/]) HBASE-6004. Adding more logging to help debugging MR job (Jimmy Xiang) (Revision 1339809) Result = SUCCESS apurtell : Files : * /hbase/branches/0.94/src/main/java/org/apache/hadoop/hbase/client/ScannerCallable.java * /hbase/branches/0.94/src/main/java/org/apache/hadoop/hbase/mapred/TableRecordReaderImpl.java * /hbase/branches/0.94/src/main/java/org/apache/hadoop/hbase/mapreduce/TableRecordReaderImpl.java Adding more logging to help debugging MR job Key: HBASE-6004 URL: https://issues.apache.org/jira/browse/HBASE-6004 Project: HBase Issue Type: Improvement Affects Versions: 0.94.0, 0.96.0 Reporter: Jimmy Xiang Assignee: Jimmy Xiang Priority: Minor Fix For: 0.94.0, 0.96.0 Attachments: hbase-6004.patch, hbase-6004_v2-0.94.patch, hbase-6004_v2.patch MR job sometime fails because scanner expired. In this case, it will be helpful to know the last successful row, the ip of the region sever, and so on. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (HBASE-5927) SSH and DisableTableHandler happening together does not clear the znode of the region and RIT map.
[
https://issues.apache.org/jira/browse/HBASE-5927?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13279406#comment-13279406
]
Hudson commented on HBASE-5927:
---
Integrated in HBase-0.94-security #27 (See
[https://builds.apache.org/job/HBase-0.94-security/27/])
HBASE-5927 SSH and DisableTableHandler happening together does not clear
the znode of the region and RIT map (Rajesh) (Revision 1339915)
Result = SUCCESS
tedyu :
Files :
*
/hbase/branches/0.94/src/main/java/org/apache/hadoop/hbase/master/AssignmentManager.java
*
/hbase/branches/0.94/src/main/java/org/apache/hadoop/hbase/master/handler/ServerShutdownHandler.java
*
/hbase/branches/0.94/src/test/java/org/apache/hadoop/hbase/master/TestAssignmentManager.java
SSH and DisableTableHandler happening together does not clear the znode of
the region and RIT map.
--
Key: HBASE-5927
URL: https://issues.apache.org/jira/browse/HBASE-5927
Project: HBase
Issue Type: Bug
Components: master
Affects Versions: 0.92.1, 0.96.0, 0.94.1
Reporter: Jieshan Bean
Assignee: rajeshbabu
Fix For: 0.92.2, 0.96.0, 0.94.1
Attachments: HBASE-5927_94.patch, HBASE-5927_94_v2.patch,
HBASE-5927_trunk.patch, HBASE-5927_trunk_2.patch, TestCaseForReProduce.txt
A possible exception: If the related regionserver was just killed(But HMaster
has not perceived that), then we will get a local exception Connection reset
by peer. If this region belongs to a disabling table. what will happen?
ServerShutdownHandler will remove this region from AM#regions. So this region
is still existing in RIT. TimeoutMonitor will take care of it after it got
timeout. Then invoke unassign again. Since this region has been removed from
AM#regions, it will return directly due to the below code:
{code}
synchronized (this.regions) {
// Check if this region is currently assigned
if (!regions.containsKey(region)) {
LOG.debug(Attempted to unassign region +
region.getRegionNameAsString() + but it is not +
currently assigned anywhere);
return;
}
}
{code}
Then it leads to an end-less loop.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (HBASE-5975) Failed suppression of fs shutdown hook with Hadoop 2.0.0
[ https://issues.apache.org/jira/browse/HBASE-5975?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13279405#comment-13279405 ] Hudson commented on HBASE-5975: --- Integrated in HBase-0.94-security #27 (See [https://builds.apache.org/job/HBase-0.94-security/27/]) HBASE-5975 Failed suppression of fs shutdown hook with Hadoop 2.0.0 (Jimmy Xiang) (Revision 1336876) Result = SUCCESS tedyu : Files : * /hbase/branches/0.94/src/main/java/org/apache/hadoop/hbase/regionserver/ShutdownHook.java Failed suppression of fs shutdown hook with Hadoop 2.0.0 Key: HBASE-5975 URL: https://issues.apache.org/jira/browse/HBASE-5975 Project: HBase Issue Type: Bug Affects Versions: 0.96.0 Reporter: Jimmy Xiang Assignee: Jimmy Xiang Fix For: 0.96.0, 0.94.1 Attachments: 5975+5966.patch, hbase-5975.patch Unit test failed with error: Failed suppression of fs shutdown hook ShutdownHookManager.deleteShutdownHook failed to delete the hook since it should be runnable instead of a thread for HADOOP 2.0.0. For other HADOOP version, runnable should work too since thread implements runnable. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (HBASE-5342) Grant/Revoke global permissions
[ https://issues.apache.org/jira/browse/HBASE-5342?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13279411#comment-13279411 ] Hudson commented on HBASE-5342: --- Integrated in HBase-0.94-security #27 (See [https://builds.apache.org/job/HBase-0.94-security/27/]) HBASE-5342 Grant/Revoke global permissions (Matteo) (Revision 1339922) Result = SUCCESS tedyu : Files : * /hbase/branches/0.94/security/src/main/java/org/apache/hadoop/hbase/security/access/AccessControlLists.java * /hbase/branches/0.94/security/src/main/java/org/apache/hadoop/hbase/security/access/AccessController.java * /hbase/branches/0.94/security/src/main/java/org/apache/hadoop/hbase/security/access/AccessControllerProtocol.java * /hbase/branches/0.94/security/src/main/java/org/apache/hadoop/hbase/security/access/TableAuthManager.java * /hbase/branches/0.94/security/src/main/java/org/apache/hadoop/hbase/security/access/UserPermission.java * /hbase/branches/0.94/security/src/main/java/org/apache/hadoop/hbase/security/access/ZKPermissionWatcher.java * /hbase/branches/0.94/security/src/test/java/org/apache/hadoop/hbase/security/access/TestAccessControlFilter.java * /hbase/branches/0.94/security/src/test/java/org/apache/hadoop/hbase/security/access/TestAccessController.java * /hbase/branches/0.94/security/src/test/java/org/apache/hadoop/hbase/security/access/TestTablePermissions.java * /hbase/branches/0.94/src/main/ruby/hbase/security.rb * /hbase/branches/0.94/src/main/ruby/shell.rb * /hbase/branches/0.94/src/main/ruby/shell/commands/grant.rb * /hbase/branches/0.94/src/main/ruby/shell/commands/revoke.rb * /hbase/branches/0.94/src/main/ruby/shell/commands/user_permission.rb * /hbase/branches/0.94/src/main/ruby/shell/commands/whoami.rb Grant/Revoke global permissions --- Key: HBASE-5342 URL: https://issues.apache.org/jira/browse/HBASE-5342 Project: HBase Issue Type: Sub-task Reporter: Enis Soztutar Assignee: Matteo Bertozzi Fix For: 0.92.2, 0.96.0, 0.94.1 Attachments: HBASE-5342-0.92.patch, HBASE-5342-0.94.patch, HBASE-5342-draft.patch, HBASE-5342-v0.patch, HBASE-5342-v1.patch, HBASE-5342-v2.patch, HBASE-5342-v3.patch, HBASE-5342-v4.patch, HBASE-5342-v5.patch HBASE-3025 introduced simple ACLs based on coprocessors. It defines global/table/cf/cq level permissions. However, there is no way to grant/revoke global level permissions, other than the hbase.superuser conf setting. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (HBASE-5894) Table deletion failed but HBaseAdmin#deletetable reports it as success
[
https://issues.apache.org/jira/browse/HBASE-5894?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13279412#comment-13279412
]
Hudson commented on HBASE-5894:
---
Integrated in HBase-0.94-security #27 (See
[https://builds.apache.org/job/HBase-0.94-security/27/])
HBASE-5894 Table deletion failed but HBaseAdmin#deletetable reports it as
success (Xufeng) (Revision 1334475)
Result = SUCCESS
tedyu :
Files :
*
/hbase/branches/0.94/src/main/java/org/apache/hadoop/hbase/client/HBaseAdmin.java
Table deletion failed but HBaseAdmin#deletetable reports it as success
--
Key: HBASE-5894
URL: https://issues.apache.org/jira/browse/HBASE-5894
Project: HBase
Issue Type: Bug
Affects Versions: 0.90.7, 0.92.2, 0.94.0
Environment: all versions
Reporter: xufeng
Assignee: xufeng
Priority: Minor
Fix For: 0.90.7, 0.92.2, 0.96.0, 0.94.1
Attachments: HBASE-5894_90_patch_v1.patch,
HBASE-5894_90_patch_v1_surefire-report.html, HBASE-5894_90_patch_v2.patch,
HBASE-5894_92_patch_v1.patch, HBASE-5894_92_patch_v1_surefire-report.html,
HBASE-5894_92_patch_v2.patch, HBASE-5894_94_patch_v1.patch,
HBASE-5894_94_patch_v1_surefire-report.html, HBASE-5894_94_patch_v2.patch,
HBASE-5894_trunk_patch_v1.patch,
HBASE-5894_trunk_patch_v1_surefire-report.html,
HBASE-5894_trunk_patch_v2.patch,
HBASE-5894_trunk_patch_v2_surefire-report.html,
HBASE-5894_trunk_patch_v3.patch
Reproduce this issue by following steps:
For reproduce it I add this code in DeleteTableHandler#handleTableOperation():
{noformat}
LOG.debug(Deleting region + region.getRegionNameAsString() +
from META and FS);
+if (true) {
+ throw new IOException(ERROR);
+}
// Remove region from META
MetaEditor.deleteRegion(this.server.getCatalogTracker(), region);
{noformat}
step1:create a table and disable it.
step2:delete it by HBaseAdmin#deleteTable() API.
result:after lone time, The log say the Table has been deleted, but in fact
if we do list in shell,the table also exists.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
