[jira] [Updated] (HBASE-5733) AssignmentManager#processDeadServersAndRegionsInTransition can fail with NPE.
[ https://issues.apache.org/jira/browse/HBASE-5733?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Uma Maheswara Rao G updated HBASE-5733: --- Resolution: Fixed Fix Version/s: 0.96.0 Hadoop Flags: Reviewed Status: Resolved (was: Patch Available) Since it got committed, marking it as closed. > AssignmentManager#processDeadServersAndRegionsInTransition can fail with NPE. > - > > Key: HBASE-5733 > URL: https://issues.apache.org/jira/browse/HBASE-5733 > Project: HBase > Issue Type: Bug > Components: master >Affects Versions: 0.96.0 >Reporter: Uma Maheswara Rao G >Assignee: Uma Maheswara Rao G > Fix For: 0.96.0 > > Attachments: HBASE-5733.patch, HBASE-5733.patch, HBASE-5733.patch > > > Found while going through the code... > AssignmentManager#processDeadServersAndRegionsInTransition can fail with NPE > as this is directly iterating the nodes from > listChildrenAndWatchForNewChildren with-out checking for null. > Here also we need to handle with null check like other places. -- 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] [Updated] (HBASE-3585) isLegalFamilyName() can throw ArrayOutOfBoundException
[ https://issues.apache.org/jira/browse/HBASE-3585?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Uma Maheswara Rao G updated HBASE-3585: --- Affects Version/s: 0.96.0 > isLegalFamilyName() can throw ArrayOutOfBoundException > -- > > Key: HBASE-3585 > URL: https://issues.apache.org/jira/browse/HBASE-3585 > Project: HBase > Issue Type: Bug > Components: client >Affects Versions: 0.90.1, 0.96.0 >Reporter: Prakash Khemani >Assignee: Uma Maheswara Rao G >Priority: Minor > Attachments: HBASE-3585.patch > > > org.apache.hadoop.hbase.HColumnDescriptor.isLegalFamilyName(byte[]) accesses > byte[0] w/o first checking the array length. -- 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] [Updated] (HBASE-3585) isLegalFamilyName() can throw ArrayOutOfBoundException
[ https://issues.apache.org/jira/browse/HBASE-3585?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Uma Maheswara Rao G updated HBASE-3585: --- Status: Patch Available (was: Open) Still the ctor wraps it to empty array only. SO, it can throw AIOE in isLegalFamilyName. Added the preconditions check for empty FamilyName. It will throw IllegalArgumentException if the familyName empty. > isLegalFamilyName() can throw ArrayOutOfBoundException > -- > > Key: HBASE-3585 > URL: https://issues.apache.org/jira/browse/HBASE-3585 > Project: HBase > Issue Type: Bug > Components: client >Affects Versions: 0.90.1 >Reporter: Prakash Khemani >Assignee: Uma Maheswara Rao G >Priority: Minor > Attachments: HBASE-3585.patch > > > org.apache.hadoop.hbase.HColumnDescriptor.isLegalFamilyName(byte[]) accesses > byte[0] w/o first checking the array length. -- 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] [Updated] (HBASE-3585) isLegalFamilyName() can throw ArrayOutOfBoundException
[ https://issues.apache.org/jira/browse/HBASE-3585?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Uma Maheswara Rao G updated HBASE-3585: --- Attachment: HBASE-3585.patch > isLegalFamilyName() can throw ArrayOutOfBoundException > -- > > Key: HBASE-3585 > URL: https://issues.apache.org/jira/browse/HBASE-3585 > Project: HBase > Issue Type: Bug > Components: client >Affects Versions: 0.90.1 >Reporter: Prakash Khemani >Assignee: Uma Maheswara Rao G >Priority: Minor > Attachments: HBASE-3585.patch > > > org.apache.hadoop.hbase.HColumnDescriptor.isLegalFamilyName(byte[]) accesses > byte[0] w/o first checking the array length. -- 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] [Updated] (HBASE-5733) AssignmentManager#processDeadServersAndRegionsInTransition can fail with NPE.
[ https://issues.apache.org/jira/browse/HBASE-5733?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Uma Maheswara Rao G updated HBASE-5733: --- Attachment: HBASE-5733.patch Attached the same patch as previous, with removal of FATAL log. > AssignmentManager#processDeadServersAndRegionsInTransition can fail with NPE. > - > > Key: HBASE-5733 > URL: https://issues.apache.org/jira/browse/HBASE-5733 > Project: HBase > Issue Type: Bug > Components: master >Affects Versions: 0.96.0 >Reporter: Uma Maheswara Rao G >Assignee: Uma Maheswara Rao G > Attachments: HBASE-5733.patch, HBASE-5733.patch, HBASE-5733.patch > > > Found while going through the code... > AssignmentManager#processDeadServersAndRegionsInTransition can fail with NPE > as this is directly iterating the nodes from > listChildrenAndWatchForNewChildren with-out checking for null. > Here also we need to handle with null check like other places. -- 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] [Updated] (HBASE-5805) TestServerCustomProtocol failing intermittently.
[ https://issues.apache.org/jira/browse/HBASE-5805?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Uma Maheswara Rao G updated HBASE-5805: --- Attachment: TestServerCustomProtocol.log Attached the log while running the test. > TestServerCustomProtocol failing intermittently. > > > Key: HBASE-5805 > URL: https://issues.apache.org/jira/browse/HBASE-5805 > Project: HBase > Issue Type: Bug > Components: regionserver >Affects Versions: 0.96.0 >Reporter: Uma Maheswara Rao G > Attachments: TestServerCustomProtocol.log > > > Trace: > java.lang.AssertionError: Results should contain region > test,ccc,1334638013935.b9d77206f6eb226928b898e66fd1d508. for row 'ccc' > at org.junit.Assert.fail(Assert.java:93) > at org.junit.Assert.assertTrue(Assert.java:43) > at > org.apache.hadoop.hbase.regionserver.TestServerCustomProtocol.verifyRegionResults(TestServerCustomProtocol.java:363) > at > org.apache.hadoop.hbase.regionserver.TestServerCustomProtocol.testNullReturn(TestServerCustomProtocol.java:330) > 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) -- 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] [Updated] (HBASE-5733) AssignmentManager#processDeadServersAndRegionsInTransition can fail with NPE.
[ https://issues.apache.org/jira/browse/HBASE-5733?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Uma Maheswara Rao G updated HBASE-5733: --- Attachment: HBASE-5733.patch > AssignmentManager#processDeadServersAndRegionsInTransition can fail with NPE. > - > > Key: HBASE-5733 > URL: https://issues.apache.org/jira/browse/HBASE-5733 > Project: HBase > Issue Type: Bug > Components: master >Affects Versions: 0.96.0 >Reporter: Uma Maheswara Rao G >Assignee: Uma Maheswara Rao G > Attachments: HBASE-5733.patch, HBASE-5733.patch > > > Found while going through the code... > AssignmentManager#processDeadServersAndRegionsInTransition can fail with NPE > as this is directly iterating the nodes from > listChildrenAndWatchForNewChildren with-out checking for null. > Here also we need to handle with null check like other places. -- 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] [Updated] (HBASE-5733) AssignmentManager#processDeadServersAndRegionsInTransition can fail with NPE.
[ https://issues.apache.org/jira/browse/HBASE-5733?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Uma Maheswara Rao G updated HBASE-5733: --- Attachment: HBASE-5733.patch Thanks a lot, Ted for taking a look! Yep, accidentally uploaded the little older one than today's patch. Updated the latest one, which I tested with real cluster for aborting on this situation. > AssignmentManager#processDeadServersAndRegionsInTransition can fail with NPE. > - > > Key: HBASE-5733 > URL: https://issues.apache.org/jira/browse/HBASE-5733 > Project: HBase > Issue Type: Bug > Components: master >Affects Versions: 0.96.0 >Reporter: Uma Maheswara Rao G >Assignee: Uma Maheswara Rao G > Attachments: HBASE-5733.patch > > > Found while going through the code... > AssignmentManager#processDeadServersAndRegionsInTransition can fail with NPE > as this is directly iterating the nodes from > listChildrenAndWatchForNewChildren with-out checking for null. > Here also we need to handle with null check like other places. -- 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] [Updated] (HBASE-5733) AssignmentManager#processDeadServersAndRegionsInTransition can fail with NPE.
[ https://issues.apache.org/jira/browse/HBASE-5733?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Uma Maheswara Rao G updated HBASE-5733: --- Attachment: (was: HBASE-5733.patch) > AssignmentManager#processDeadServersAndRegionsInTransition can fail with NPE. > - > > Key: HBASE-5733 > URL: https://issues.apache.org/jira/browse/HBASE-5733 > Project: HBase > Issue Type: Bug > Components: master >Affects Versions: 0.96.0 >Reporter: Uma Maheswara Rao G >Assignee: Uma Maheswara Rao G > > Found while going through the code... > AssignmentManager#processDeadServersAndRegionsInTransition can fail with NPE > as this is directly iterating the nodes from > listChildrenAndWatchForNewChildren with-out checking for null. > Here also we need to handle with null check like other places. -- 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] [Updated] (HBASE-5733) AssignmentManager#processDeadServersAndRegionsInTransition can fail with NPE.
[ https://issues.apache.org/jira/browse/HBASE-5733?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Uma Maheswara Rao G updated HBASE-5733: --- Attachment: HBASE-5733.patch > AssignmentManager#processDeadServersAndRegionsInTransition can fail with NPE. > - > > Key: HBASE-5733 > URL: https://issues.apache.org/jira/browse/HBASE-5733 > Project: HBase > Issue Type: Bug > Components: master >Affects Versions: 0.96.0 >Reporter: Uma Maheswara Rao G >Assignee: Uma Maheswara Rao G > Attachments: HBASE-5733.patch > > > Found while going through the code... > AssignmentManager#processDeadServersAndRegionsInTransition can fail with NPE > as this is directly iterating the nodes from > listChildrenAndWatchForNewChildren with-out checking for null. > Here also we need to handle with null check like other places. -- 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] [Updated] (HBASE-5645) [findbugs] Fix correctness warnings
[ https://issues.apache.org/jira/browse/HBASE-5645?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Uma Maheswara Rao G updated HBASE-5645: --- Attachment: HBASE-5645-3.patch > [findbugs] Fix correctness warnings > --- > > Key: HBASE-5645 > URL: https://issues.apache.org/jira/browse/HBASE-5645 > Project: HBase > Issue Type: Sub-task > Components: scripts >Reporter: Jonathan Hsieh >Assignee: David S. Wang > Attachments: HBASE-5645-2.patch, HBASE-5645-3.patch, > HBASE-5645.patch, HBASE-5645.patch, hbase-5645-2-tweak.patch > > > See > https://builds.apache.org/job/PreCommit-HBASE-Build/1313//artifact/trunk/patchprocess/newPatchFindbugsWarnings.html > Fix the warnings in the correctness section. -- 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] [Updated] (HBASE-5653) [findbugs] fix perf warnings
[ https://issues.apache.org/jira/browse/HBASE-5653?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Uma Maheswara Rao G updated HBASE-5653: --- Attachment: HBASE-5653.patch Updated the patch, which addresses your suggestion. > [findbugs] fix perf warnings > > > Key: HBASE-5653 > URL: https://issues.apache.org/jira/browse/HBASE-5653 > Project: HBase > Issue Type: Sub-task > Components: scripts >Reporter: Jonathan Hsieh >Assignee: Uma Maheswara Rao G > Attachments: HBASE-5653.patch, HBASE-5653.patch > > > See > https://builds.apache.org/job/PreCommit-HBASE-Build/1313//artifact/trunk/patchprocess/newPatchFindbugsWarnings.html#Warnings_PERFORMANCE -- 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] [Updated] (HBASE-5726) TestSplitTransactionOnCluster occasionally failing
[
https://issues.apache.org/jira/browse/HBASE-5726?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Uma Maheswara Rao G updated HBASE-5726:
---
Attachment:
Hbase.log_testRSSplitEphemeralsDisappearButDaughtersAreOnlinedAfterShutdownHandling
Hbase.log_testExistingZnodeBlocksSplitAndWeRollback &
testShutdownFixupWhenDaughterHasSplit
> TestSplitTransactionOnCluster occasionally failing
> --
>
> Key: HBASE-5726
> URL: https://issues.apache.org/jira/browse/HBASE-5726
> Project: HBase
> Issue Type: Bug
>Reporter: Uma Maheswara Rao G
> Attachments: Hbase.log_testExistingZnodeBlocksSplitAndWeRollback &
> testShutdownFixupWhenDaughterHasSplit,
> Hbase.log_testRSSplitEphemeralsDisappearButDaughtersAreOnlinedAfterShutdownHandling
>
>
> When I ran TestSplitTransactionOnCluster, some times tests are failing.
> {quote}
> java.lang.AssertionError: expected:<1> but was:<0>
> at org.junit.Assert.fail(Assert.java:93)
> at org.junit.Assert.failNotEquals(Assert.java:647)
> at org.junit.Assert.assertEquals(Assert.java:128)
> at org.junit.Assert.assertEquals(Assert.java:472)
> at org.junit.Assert.assertEquals(Assert.java:456)
> at
> org.apache.hadoop.hbase.regionserver.TestSplitTransactionOnCluster.getAndCheckSingleTableRegion(TestSplitTransactionOnCluster.java:89)
> at
> org.apache.hadoop.hbase.regionserver.TestSplitTransactionOnCluster.testShutdownFixupWhenDaughterHasSplit(TestSplitTransactionOnCluster.java:298)
> 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.FailOnTimeout$StatementThread.run(FailOnTimeout.java:62)
> {quote}
> Seems like test is flaky, random other cases also 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] [Updated] (HBASE-5653) [findbugs] fix perf warnings
[ https://issues.apache.org/jira/browse/HBASE-5653?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Uma Maheswara Rao G updated HBASE-5653: --- Status: Patch Available (was: Open) > [findbugs] fix perf warnings > > > Key: HBASE-5653 > URL: https://issues.apache.org/jira/browse/HBASE-5653 > Project: HBase > Issue Type: Sub-task > Components: scripts >Reporter: Jonathan Hsieh >Assignee: Uma Maheswara Rao G > Attachments: HBASE-5653.patch > > > See > https://builds.apache.org/job/PreCommit-HBASE-Build/1313//artifact/trunk/patchprocess/newPatchFindbugsWarnings.html#Warnings_PERFORMANCE -- 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] [Updated] (HBASE-5653) [findbugs] fix perf warnings
[ https://issues.apache.org/jira/browse/HBASE-5653?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Uma Maheswara Rao G updated HBASE-5653: --- Attachment: HBASE-5653.patch > [findbugs] fix perf warnings > > > Key: HBASE-5653 > URL: https://issues.apache.org/jira/browse/HBASE-5653 > Project: HBase > Issue Type: Sub-task > Components: scripts >Reporter: Jonathan Hsieh >Assignee: Uma Maheswara Rao G > Attachments: HBASE-5653.patch > > > See > https://builds.apache.org/job/PreCommit-HBASE-Build/1313//artifact/trunk/patchprocess/newPatchFindbugsWarnings.html#Warnings_PERFORMANCE -- 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] [Updated] (HBASE-5733) AssignmentManager#processDeadServersAndRegionsInTransition can fail with NPE.
[ https://issues.apache.org/jira/browse/HBASE-5733?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Uma Maheswara Rao G updated HBASE-5733: --- Affects Version/s: 0.96.0 > AssignmentManager#processDeadServersAndRegionsInTransition can fail with NPE. > - > > Key: HBASE-5733 > URL: https://issues.apache.org/jira/browse/HBASE-5733 > Project: HBase > Issue Type: Bug > Components: master >Affects Versions: 0.96.0 >Reporter: Uma Maheswara Rao G >Assignee: Uma Maheswara Rao G > > Found while going through the code... > AssignmentManager#processDeadServersAndRegionsInTransition can fail with NPE > as this is directly iterating the nodes from > listChildrenAndWatchForNewChildren with-out checking for null. > Here also we need to handle with null check like other places. -- 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] [Updated] (HBASE-5722) NPE in ZKUtil#getChildDataAndWatchForNewChildren when ZK not available or NW down.
[
https://issues.apache.org/jira/browse/HBASE-5722?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Uma Maheswara Rao G updated HBASE-5722:
---
Status: Patch Available (was: Open)
> NPE in ZKUtil#getChildDataAndWatchForNewChildren when ZK not available or NW
> down.
> --
>
> Key: HBASE-5722
> URL: https://issues.apache.org/jira/browse/HBASE-5722
> Project: HBase
> Issue Type: Bug
> Components: zookeeper
>Affects Versions: 0.96.0
>Reporter: Uma Maheswara Rao G
>Assignee: Uma Maheswara Rao G
> Attachments: HBASE-5722.patch
>
>
> {code}
> List nodes =
> ZKUtil.listChildrenAndWatchForNewChildren(zkw, baseNode);
> List newNodes = new ArrayList();
> for (String node: nodes) {
> String nodePath = ZKUtil.joinZNode(baseNode, node);
> byte [] data = ZKUtil.getDataAndWatch(zkw, nodePath);
> newNodes.add(new NodeAndData(nodePath, data));
> }
> {code}
> The above code can throw NPE when listChildrenAndWatchForNewChildren returns
> null.
--
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] [Updated] (HBASE-5722) NPE in ZKUtil#getChildDataAndWatchForNewChildren when ZK not available or NW down.
[
https://issues.apache.org/jira/browse/HBASE-5722?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Uma Maheswara Rao G updated HBASE-5722:
---
Attachment: HBASE-5722.patch
> NPE in ZKUtil#getChildDataAndWatchForNewChildren when ZK not available or NW
> down.
> --
>
> Key: HBASE-5722
> URL: https://issues.apache.org/jira/browse/HBASE-5722
> Project: HBase
> Issue Type: Bug
> Components: zookeeper
>Affects Versions: 0.96.0
>Reporter: Uma Maheswara Rao G
>Assignee: Uma Maheswara Rao G
> Attachments: HBASE-5722.patch
>
>
> {code}
> List nodes =
> ZKUtil.listChildrenAndWatchForNewChildren(zkw, baseNode);
> List newNodes = new ArrayList();
> for (String node: nodes) {
> String nodePath = ZKUtil.joinZNode(baseNode, node);
> byte [] data = ZKUtil.getDataAndWatch(zkw, nodePath);
> newNodes.add(new NodeAndData(nodePath, data));
> }
> {code}
> The above code can throw NPE when listChildrenAndWatchForNewChildren returns
> null.
--
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] [Updated] (HBASE-5644) [findbugs] Fix null pointer warnings.
[ https://issues.apache.org/jira/browse/HBASE-5644?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Uma Maheswara Rao G updated HBASE-5644: --- Attachment: HBASE-5644.patch > [findbugs] Fix null pointer warnings. > - > > Key: HBASE-5644 > URL: https://issues.apache.org/jira/browse/HBASE-5644 > Project: HBase > Issue Type: Sub-task > Components: scripts >Reporter: Jonathan Hsieh >Assignee: Uma Maheswara Rao G > Attachments: HBASE-5644.patch, HBASE-5644.patch, > NullPointerFindBugs_Analysis.xlsx > > > See > https://builds.apache.org/job/PreCommit-HBASE-Build/1313//artifact/trunk/patchprocess/newPatchFindbugsWarnings.html > Fix the NP category -- 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] [Updated] (HBASE-5725) HBaseClient throws NPE while in Connection#receiveResponse call.
[ https://issues.apache.org/jira/browse/HBASE-5725?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Uma Maheswara Rao G updated HBASE-5725: --- Summary: HBaseClient throws NPE while in Connection#receiveResponse call. (was: NPE in ) > HBaseClient throws NPE while in Connection#receiveResponse call. > > > Key: HBASE-5725 > URL: https://issues.apache.org/jira/browse/HBASE-5725 > Project: HBase > Issue Type: Bug >Reporter: Uma Maheswara Rao G > > When i am running TestSplitTransactionOnCluster, it is throwing NPE from > HBaseClient > HBaseClient: > > RpcResponse response = RpcResponse.parseDelimitedFrom(in); > int id = response.getCallId(); > The above code throws NPE. -- 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] [Updated] (HBASE-5711) Tests are failing with incorrect data directory permissions.
[
https://issues.apache.org/jira/browse/HBASE-5711?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Uma Maheswara Rao G updated HBASE-5711:
---
Status: Patch Available (was: Open)
@Ram, could you please take a look?
> Tests are failing with incorrect data directory permissions.
>
>
> Key: HBASE-5711
> URL: https://issues.apache.org/jira/browse/HBASE-5711
> Project: HBase
> Issue Type: Bug
> Components: test
>Reporter: Uma Maheswara Rao G
>Assignee: Uma Maheswara Rao G
> Attachments: HBASE-5711.patch
>
>
> When we run some tests in Hbase (TestAdmin), it is failing with following
> error.
> {quote}
> Starting DataNode 0 with dfs.data.dir:
> E:\Repositories\Hbase\target\test-data\5ff23198-892e-4f1c-8022-b3d9969fcf0b\dfscluster_0ecc6984-1925-4870-ac7c-439fceede4cb\dfs\data\data1,E:\Repositories\Hbase\target\test-data\5ff23198-892e-4f1c-8022-b3d9969fcf0b\dfscluster_0ecc6984-1925-4870-ac7c-439fceede4cb\dfs\data\data2
> 2012-04-04 18:04:51,036 WARN [main] impl.MetricsSystemImpl(137): Metrics
> system not started: Cannot locate configuration: tried
> hadoop-metrics2-datanode.properties, hadoop-metrics2.properties
> 2012-04-04 18:04:51,255 WARN [main] datanode.DataNode(1548): Invalid
> directory in dfs.data.dir: Incorrect permission for
> E:/Repositories/Hbase/target/test-data/5ff23198-892e-4f1c-8022-b3d9969fcf0b/dfscluster_0ecc6984-1925-4870-ac7c-439fceede4cb/dfs/data/data1,
> expected: rwxr-xr-x, while actual: rwx--
> 2012-04-04 18:04:51,411 WARN [main] datanode.DataNode(1548): Invalid
> directory in dfs.data.dir: Incorrect permission for
> E:/Repositories/Hbase/target/test-data/5ff23198-892e-4f1c-8022-b3d9969fcf0b/dfscluster_0ecc6984-1925-4870-ac7c-439fceede4cb/dfs/data/data2,
> expected: rwxr-xr-x, while actual: rwx--
> 2012-04-04 18:04:51,411 ERROR [main] datanode.DataNode(1554): All directories
> in dfs.data.dir are invalid.
> 2012-04-04 18:04:51,411 INFO [main] hbase.HBaseTestingUtility(684): Shutting
> down minicluster
> 2012-04-04 18:04:51,646 WARN [main] hbase.HBaseTestingUtility(696): Failed
> delete of
> E:\Repositories\Hbase\target\test-data\5ff23198-892e-4f1c-8022-b3d9969fcf0b\dfscluster_0ecc6984-1925-4870-ac7c-439fceede4cb
> 2012-04-04 18:04:51,646 INFO [main] hbase.HBaseTestingUtility(700):
> Minicluster is down
> {quote}
--
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] [Updated] (HBASE-5711) Tests are failing with incorrect data directory permissions.
[
https://issues.apache.org/jira/browse/HBASE-5711?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Uma Maheswara Rao G updated HBASE-5711:
---
Attachment: HBASE-5711.patch
Attached simple patch, which sets the permission to dfs data directories with
700.
> Tests are failing with incorrect data directory permissions.
>
>
> Key: HBASE-5711
> URL: https://issues.apache.org/jira/browse/HBASE-5711
> Project: HBase
> Issue Type: Bug
> Components: test
>Reporter: Uma Maheswara Rao G
>Assignee: Uma Maheswara Rao G
> Attachments: HBASE-5711.patch
>
>
> When we run some tests in Hbase (TestAdmin), it is failing with following
> error.
> {quote}
> Starting DataNode 0 with dfs.data.dir:
> E:\Repositories\Hbase\target\test-data\5ff23198-892e-4f1c-8022-b3d9969fcf0b\dfscluster_0ecc6984-1925-4870-ac7c-439fceede4cb\dfs\data\data1,E:\Repositories\Hbase\target\test-data\5ff23198-892e-4f1c-8022-b3d9969fcf0b\dfscluster_0ecc6984-1925-4870-ac7c-439fceede4cb\dfs\data\data2
> 2012-04-04 18:04:51,036 WARN [main] impl.MetricsSystemImpl(137): Metrics
> system not started: Cannot locate configuration: tried
> hadoop-metrics2-datanode.properties, hadoop-metrics2.properties
> 2012-04-04 18:04:51,255 WARN [main] datanode.DataNode(1548): Invalid
> directory in dfs.data.dir: Incorrect permission for
> E:/Repositories/Hbase/target/test-data/5ff23198-892e-4f1c-8022-b3d9969fcf0b/dfscluster_0ecc6984-1925-4870-ac7c-439fceede4cb/dfs/data/data1,
> expected: rwxr-xr-x, while actual: rwx--
> 2012-04-04 18:04:51,411 WARN [main] datanode.DataNode(1548): Invalid
> directory in dfs.data.dir: Incorrect permission for
> E:/Repositories/Hbase/target/test-data/5ff23198-892e-4f1c-8022-b3d9969fcf0b/dfscluster_0ecc6984-1925-4870-ac7c-439fceede4cb/dfs/data/data2,
> expected: rwxr-xr-x, while actual: rwx--
> 2012-04-04 18:04:51,411 ERROR [main] datanode.DataNode(1554): All directories
> in dfs.data.dir are invalid.
> 2012-04-04 18:04:51,411 INFO [main] hbase.HBaseTestingUtility(684): Shutting
> down minicluster
> 2012-04-04 18:04:51,646 WARN [main] hbase.HBaseTestingUtility(696): Failed
> delete of
> E:\Repositories\Hbase\target\test-data\5ff23198-892e-4f1c-8022-b3d9969fcf0b\dfscluster_0ecc6984-1925-4870-ac7c-439fceede4cb
> 2012-04-04 18:04:51,646 INFO [main] hbase.HBaseTestingUtility(700):
> Minicluster is down
> {quote}
--
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] [Updated] (HBASE-5644) [findbugs] Fix null pointer warnings.
[ https://issues.apache.org/jira/browse/HBASE-5644?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Uma Maheswara Rao G updated HBASE-5644: --- Status: Patch Available (was: Open) > [findbugs] Fix null pointer warnings. > - > > Key: HBASE-5644 > URL: https://issues.apache.org/jira/browse/HBASE-5644 > Project: HBase > Issue Type: Sub-task > Components: scripts >Reporter: Jonathan Hsieh >Assignee: Uma Maheswara Rao G > Attachments: HBASE-5644.patch, NullPointerFindBugs_Analysis.xlsx > > > See > https://builds.apache.org/job/PreCommit-HBASE-Build/1313//artifact/trunk/patchprocess/newPatchFindbugsWarnings.html > Fix the NP category -- 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] [Updated] (HBASE-5644) [findbugs] Fix null pointer warnings.
[ https://issues.apache.org/jira/browse/HBASE-5644?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Uma Maheswara Rao G updated HBASE-5644: --- Attachment: HBASE-5644.patch Attached the patch and analysis sheet. > [findbugs] Fix null pointer warnings. > - > > Key: HBASE-5644 > URL: https://issues.apache.org/jira/browse/HBASE-5644 > Project: HBase > Issue Type: Sub-task > Components: scripts >Reporter: Jonathan Hsieh >Assignee: Uma Maheswara Rao G > Attachments: HBASE-5644.patch, NullPointerFindBugs_Analysis.xlsx > > > See > https://builds.apache.org/job/PreCommit-HBASE-Build/1313//artifact/trunk/patchprocess/newPatchFindbugsWarnings.html > Fix the NP category -- 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] [Updated] (HBASE-5644) [findbugs] Fix null pointer warnings.
[ https://issues.apache.org/jira/browse/HBASE-5644?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Uma Maheswara Rao G updated HBASE-5644: --- Attachment: NullPointerFindBugs_Analysis.xlsx > [findbugs] Fix null pointer warnings. > - > > Key: HBASE-5644 > URL: https://issues.apache.org/jira/browse/HBASE-5644 > Project: HBase > Issue Type: Sub-task > Components: scripts >Reporter: Jonathan Hsieh >Assignee: Uma Maheswara Rao G > Attachments: NullPointerFindBugs_Analysis.xlsx > > > See > https://builds.apache.org/job/PreCommit-HBASE-Build/1313//artifact/trunk/patchprocess/newPatchFindbugsWarnings.html > Fix the NP category -- 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] [Updated] (HBASE-5678) Dynamic configuration capability for Hbase.
[ https://issues.apache.org/jira/browse/HBASE-5678?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Uma Maheswara Rao G updated HBASE-5678: --- Component/s: (was: security) util > Dynamic configuration capability for Hbase. > --- > > Key: HBASE-5678 > URL: https://issues.apache.org/jira/browse/HBASE-5678 > Project: HBase > Issue Type: New Feature > Components: master, regionserver, util >Affects Versions: 0.96.0 >Reporter: Uma Maheswara Rao G >Assignee: Uma Maheswara Rao G > Fix For: 0.96.0 > > > I think, some preperties can be danamically configured without restart of the > nodes. > This is an umberilla JIRA for this Feature. >In Hadoop we already had such feature but not yet implemented by nodes. I > think we can have the similar base framework here and can implemented by > nodes. So, that whatever properies are allowed to reconfigurable, should be > able to reconfigure with new values with out restarting the node. > I will come up with some design doc with noeds implementation and will raise > subtasks for each. -- 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] [Updated] (HBASE-5642) [findbugs] Exclude Thrift and Protobuf warnings
[ https://issues.apache.org/jira/browse/HBASE-5642?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Uma Maheswara Rao G updated HBASE-5642: --- Status: Patch Available (was: Open) > [findbugs] Exclude Thrift and Protobuf warnings > --- > > Key: HBASE-5642 > URL: https://issues.apache.org/jira/browse/HBASE-5642 > Project: HBase > Issue Type: Sub-task > Components: build >Affects Versions: 0.96.0 >Reporter: Jonathan Hsieh >Assignee: Uma Maheswara Rao G > Attachments: HBASE-5642.patch, HBASE-5642.patch > > > Exclude thrift and protobuf warnings since these are machine generated. -- 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] [Updated] (HBASE-5642) [findbugs] Exclude Thrift and Protobuf warnings
[ https://issues.apache.org/jira/browse/HBASE-5642?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Uma Maheswara Rao G updated HBASE-5642: --- Attachment: HBASE-5642.patch Attaching the patch with updating the OK_FINDBUGS_WARNINGS to 601 in test-patch.properties. So, that QA can catch if any new bugs introduced by other patches. > [findbugs] Exclude Thrift and Protobuf warnings > --- > > Key: HBASE-5642 > URL: https://issues.apache.org/jira/browse/HBASE-5642 > Project: HBase > Issue Type: Sub-task > Components: build >Affects Versions: 0.96.0 >Reporter: Jonathan Hsieh >Assignee: Uma Maheswara Rao G > Attachments: HBASE-5642.patch, HBASE-5642.patch > > > Exclude thrift and protobuf warnings since these are machine generated. -- 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] [Updated] (HBASE-5642) [findbugs] Exclude Thrift and Protobuf warnings
[ https://issues.apache.org/jira/browse/HBASE-5642?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Uma Maheswara Rao G updated HBASE-5642: --- Attachment: HBASE-5642.patch > [findbugs] Exclude Thrift and Protobuf warnings > --- > > Key: HBASE-5642 > URL: https://issues.apache.org/jira/browse/HBASE-5642 > Project: HBase > Issue Type: Sub-task > Components: build >Affects Versions: 0.96.0 >Reporter: Jonathan Hsieh >Assignee: Uma Maheswara Rao G > Attachments: HBASE-5642.patch > > > Exclude thrift and protobuf warnings since these are machine generated. -- 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] [Updated] (HBASE-5598) Analyse and fix the findbugs reporting by QA and add invalid bugs into findbugs-excludeFilter file
[ https://issues.apache.org/jira/browse/HBASE-5598?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Uma Maheswara Rao G updated HBASE-5598: --- Release Note: Developers can generate the findbugs report for analysing the findbugs violations. Execute this maven command for running and generating the findbugs report: mvn findbugs:gui This generates the report in GUI, by which will directly show the code instances where exactly the issue is reported. If the developer finds any invalid bug, then that bug pattern can be updated in dev-support/findbugs-exclude.xml file. example: > Analyse and fix the findbugs reporting by QA and add invalid bugs into > findbugs-excludeFilter file > -- > > Key: HBASE-5598 > URL: https://issues.apache.org/jira/browse/HBASE-5598 > Project: HBase > Issue Type: Bug > Components: scripts >Affects Versions: 0.92.1, 0.94.0, 0.96.0 >Reporter: Uma Maheswara Rao G >Assignee: Uma Maheswara Rao G >Priority: Minor > Attachments: HBASE-5598.patch, findbugs-gui-report.jpg > > > There are many findbugs errors reporting by HbaseQA. HBASE-5597 is going to > up the OK count. > This may lead to other issues when we re-factor the code, if we induce new > valid ones and remove invalid bugs also can not be reported by QA. > So, I would propose to add the exclude filter file for findbugs(for the > invalid bugs). If we find any valid ones, we can fix under this JIRA. -- 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] [Updated] (HBASE-5598) Analyse and fix the findbugs reporting by QA and add invalid bugs into findbugs-excludeFilter file
[ https://issues.apache.org/jira/browse/HBASE-5598?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Uma Maheswara Rao G updated HBASE-5598: --- Attachment: findbugs-gui-report.jpg > Analyse and fix the findbugs reporting by QA and add invalid bugs into > findbugs-excludeFilter file > -- > > Key: HBASE-5598 > URL: https://issues.apache.org/jira/browse/HBASE-5598 > Project: HBase > Issue Type: Bug > Components: scripts >Affects Versions: 0.92.1, 0.94.0, 0.96.0 >Reporter: Uma Maheswara Rao G >Assignee: Uma Maheswara Rao G >Priority: Minor > Attachments: HBASE-5598.patch, findbugs-gui-report.jpg > > > There are many findbugs errors reporting by HbaseQA. HBASE-5597 is going to > up the OK count. > This may lead to other issues when we re-factor the code, if we induce new > valid ones and remove invalid bugs also can not be reported by QA. > So, I would propose to add the exclude filter file for findbugs(for the > invalid bugs). If we find any valid ones, we can fix under this JIRA. -- 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] [Updated] (HBASE-5598) Analyse and fix the findbugs reporting by QA and add invalid bugs into findbugs-excludeFilter file
[ https://issues.apache.org/jira/browse/HBASE-5598?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Uma Maheswara Rao G updated HBASE-5598: --- Status: Patch Available (was: Open) > Analyse and fix the findbugs reporting by QA and add invalid bugs into > findbugs-excludeFilter file > -- > > Key: HBASE-5598 > URL: https://issues.apache.org/jira/browse/HBASE-5598 > Project: HBase > Issue Type: Bug > Components: scripts >Affects Versions: 0.92.1, 0.94.0, 0.96.0 >Reporter: Uma Maheswara Rao G >Assignee: Uma Maheswara Rao G >Priority: Minor > Attachments: HBASE-5598.patch > > > There are many findbugs errors reporting by HbaseQA. HBASE-5597 is going to > up the OK count. > This may lead to other issues when we re-factor the code, if we induce new > valid ones and remove invalid bugs also can not be reported by QA. > So, I would propose to add the exclude filter file for findbugs(for the > invalid bugs). If we find any valid ones, we can fix under this JIRA. -- 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] [Updated] (HBASE-5598) Analyse and fix the findbugs reporting by QA and add invalid bugs into findbugs-excludeFilter file
[ https://issues.apache.org/jira/browse/HBASE-5598?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Uma Maheswara Rao G updated HBASE-5598: --- Attachment: HBASE-5598.patch > Analyse and fix the findbugs reporting by QA and add invalid bugs into > findbugs-excludeFilter file > -- > > Key: HBASE-5598 > URL: https://issues.apache.org/jira/browse/HBASE-5598 > Project: HBase > Issue Type: Bug > Components: scripts >Affects Versions: 0.92.1, 0.94.0, 0.96.0 >Reporter: Uma Maheswara Rao G >Assignee: Uma Maheswara Rao G >Priority: Minor > Attachments: HBASE-5598.patch > > > There are many findbugs errors reporting by HbaseQA. HBASE-5597 is going to > up the OK count. > This may lead to other issues when we re-factor the code, if we induce new > valid ones and remove invalid bugs also can not be reported by QA. > So, I would propose to add the exclude filter file for findbugs(for the > invalid bugs). If we find any valid ones, we can fix under this JIRA. -- 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] [Updated] (HBASE-5595) Fix NoSuchMethodException in 0.92 when running on local filesystem
[
https://issues.apache.org/jira/browse/HBASE-5595?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Uma Maheswara Rao G updated HBASE-5595:
---
Status: Patch Available (was: Open)
> Fix NoSuchMethodException in 0.92 when running on local filesystem
> --
>
> Key: HBASE-5595
> URL: https://issues.apache.org/jira/browse/HBASE-5595
> Project: HBase
> Issue Type: Bug
>Reporter: stack
>Priority: Critical
> Fix For: 0.92.2
>
> Attachments: HBASE-5595.patch
>
>
> Fix this ugly exception that shows when running 0.92.1 when on local
> filesystem:
> {code}
> 2012-03-16 10:54:48,351 INFO org.apache.hadoop.hbase.regionserver.wal.HLog:
> getNumCurrentReplicas--HDFS-826 not available;
> hdfs_out=org.apache.hadoop.fs.FSDataOutputStream@301abf87
> java.lang.NoSuchMethodException:
> org.apache.hadoop.fs.ChecksumFileSystem$ChecksumFSOutputSummer.getNumCurrentReplicas()
> at java.lang.Class.getDeclaredMethod(Class.java:1937)
> at
> org.apache.hadoop.hbase.regionserver.wal.HLog.getGetNumCurrentReplicas(HLog.java:425)
> at org.apache.hadoop.hbase.regionserver.wal.HLog.(HLog.java:408)
> at org.apache.hadoop.hbase.regionserver.wal.HLog.(HLog.java:331)
> at
> org.apache.hadoop.hbase.regionserver.HRegionServer.instantiateHLog(HRegionServer.java:1229)
> at
> org.apache.hadoop.hbase.regionserver.HRegionServer.setupWALAndReplication(HRegionServer.java:1218)
> at
> org.apache.hadoop.hbase.regionserver.HRegionServer.handleReportForDutyResponse(HRegionServer.java:937)
> at
> org.apache.hadoop.hbase.regionserver.HRegionServer.run(HRegionServer.java:648)
> at java.lang.Thread.run(Thread.java:680)
> {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] [Updated] (HBASE-5595) Fix NoSuchMethodException in 0.92 when running on local filesystem
[
https://issues.apache.org/jira/browse/HBASE-5595?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Uma Maheswara Rao G updated HBASE-5595:
---
Attachment: HBASE-5595.patch
> Fix NoSuchMethodException in 0.92 when running on local filesystem
> --
>
> Key: HBASE-5595
> URL: https://issues.apache.org/jira/browse/HBASE-5595
> Project: HBase
> Issue Type: Bug
>Reporter: stack
>Priority: Critical
> Fix For: 0.92.2
>
> Attachments: HBASE-5595.patch
>
>
> Fix this ugly exception that shows when running 0.92.1 when on local
> filesystem:
> {code}
> 2012-03-16 10:54:48,351 INFO org.apache.hadoop.hbase.regionserver.wal.HLog:
> getNumCurrentReplicas--HDFS-826 not available;
> hdfs_out=org.apache.hadoop.fs.FSDataOutputStream@301abf87
> java.lang.NoSuchMethodException:
> org.apache.hadoop.fs.ChecksumFileSystem$ChecksumFSOutputSummer.getNumCurrentReplicas()
> at java.lang.Class.getDeclaredMethod(Class.java:1937)
> at
> org.apache.hadoop.hbase.regionserver.wal.HLog.getGetNumCurrentReplicas(HLog.java:425)
> at org.apache.hadoop.hbase.regionserver.wal.HLog.(HLog.java:408)
> at org.apache.hadoop.hbase.regionserver.wal.HLog.(HLog.java:331)
> at
> org.apache.hadoop.hbase.regionserver.HRegionServer.instantiateHLog(HRegionServer.java:1229)
> at
> org.apache.hadoop.hbase.regionserver.HRegionServer.setupWALAndReplication(HRegionServer.java:1218)
> at
> org.apache.hadoop.hbase.regionserver.HRegionServer.handleReportForDutyResponse(HRegionServer.java:937)
> at
> org.apache.hadoop.hbase.regionserver.HRegionServer.run(HRegionServer.java:648)
> at java.lang.Thread.run(Thread.java:680)
> {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] [Updated] (HBASE-5598) Analyse and fix the findbugs reporting by QA and add invalid bugs into findbugs-excludeFilter file
[ https://issues.apache.org/jira/browse/HBASE-5598?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Uma Maheswara Rao G updated HBASE-5598: --- Description: There are many findbugs errors reporting by HbaseQA. HBASE-5597 is going to up the OK count. This may lead to other issues when we re-factor the code, if we induce new valid ones and remove invalid bugs also can not be reported by QA. So, I would propose to add the exclude filter file for findbugs(for the invalid bugs). If we find any valid ones, we can fix under this JIRA. was: There are many findbugs errors reporting by HbaseQA. HBASE-5597 is going to up the OK count. This may lead to other issues when we re-factor the code, if we induce new valid ones and remove invalid bugs also can not be reported by QA. So, I would propose to add the exclude filter file for findbugs for the invalid bugs. If we find any valid ond we can fix under this JIRA. > Analyse and fix the findbugs reporting by QA and add invalid bugs into > findbugs-excludeFilter file > -- > > Key: HBASE-5598 > URL: https://issues.apache.org/jira/browse/HBASE-5598 > Project: HBase > Issue Type: Bug > Components: scripts >Affects Versions: 0.92.1, 0.94.0, 0.96.0 >Reporter: Uma Maheswara Rao G >Priority: Minor > > There are many findbugs errors reporting by HbaseQA. HBASE-5597 is going to > up the OK count. > This may lead to other issues when we re-factor the code, if we induce new > valid ones and remove invalid bugs also can not be reported by QA. > So, I would propose to add the exclude filter file for findbugs(for the > invalid bugs). If we find any valid ones, we can fix under this JIRA. -- 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
