[jira] [Commented] (HBASE-8808) Use Jacoco to generate Unit Test coverage reports
[ https://issues.apache.org/jira/browse/HBASE-8808?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14158988#comment-14158988 ] Hudson commented on HBASE-8808: --- FAILURE: Integrated in HBase-TRUNK #5621 (See [https://builds.apache.org/job/HBase-TRUNK/5621/]) HBASE-8808 Use Jacoco to generate Unit Test coverage reports (Manukranth) (stack: rev 3533820efb2d0ad80b4bf0ee05c25f4ff2b59436) * pom.xml > Use Jacoco to generate Unit Test coverage reports > - > > Key: HBASE-8808 > URL: https://issues.apache.org/jira/browse/HBASE-8808 > Project: HBase > Issue Type: Bug > Components: build >Affects Versions: 0.89-fb >Reporter: Manukranth Kolloju >Assignee: Manukranth Kolloju >Priority: Trivial > Fix For: 2.0.0, 0.99.1 > > Attachments: 0001-Including-Jacoco-plugin-to-get-test-coverage.patch, > 0001-Including-Jacoco-plugin-to-get-test-coverage.patch, > 0001-Including-Jacoco-plugin-to-get-test-coverage.patch, Screen Shot > 2013-06-25 at 11.35.30 AM.png > > Original Estimate: 24h > Remaining Estimate: 24h > > Enabling the code coverage tool jacoco in maven -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (HBASE-12075) Preemptive Fast Fail
[
https://issues.apache.org/jira/browse/HBASE-12075?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14158964#comment-14158964
]
Hadoop QA commented on HBASE-12075:
---
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12672905/0001-HBASE-12075-Implement-Preemptive-Fast-Fail.patch
against trunk revision .
ATTACHMENT ID: 12672905
{color:green}+1 @author{color}. The patch does not contain any @author
tags.
{color:green}+1 tests included{color}. The patch appears to include 8 new
or modified tests.
{color:green}+1 javac{color}. The applied patch does not increase the
total number of javac compiler warnings.
{color:green}+1 javac{color}. The applied patch does not increase the
total number of javac compiler warnings.
{color:green}+1 javadoc{color}. The javadoc tool did not generate any
warning messages.
{color:green}+1 findbugs{color}. The patch does not introduce any new
Findbugs (version 2.0.3) warnings.
{color:green}+1 release audit{color}. The applied patch does not increase
the total number of release audit warnings.
{color:green}+1 lineLengths{color}. The patch does not introduce lines
longer than 100
{color:green}+1 site{color}. The mvn site goal succeeds with this patch.
{color:red}-1 core tests{color}. The patch failed these unit tests:
org.apache.hadoop.hbase.replication.regionserver.TestRegionReplicaReplicationEndpoint
{color:red}-1 core zombie tests{color}. There are 1 zombie test(s):
at
org.apache.hadoop.hbase.master.TestMasterNoCluster.testNotPullingDeadRegionServerFromZK(TestMasterNoCluster.java:306)
Test results:
https://builds.apache.org/job/PreCommit-HBASE-Build/11218//testReport/
Findbugs warnings:
https://builds.apache.org/job/PreCommit-HBASE-Build/11218//artifact/patchprocess/newPatchFindbugsWarningshbase-common.html
Findbugs warnings:
https://builds.apache.org/job/PreCommit-HBASE-Build/11218//artifact/patchprocess/newPatchFindbugsWarningshbase-client.html
Findbugs warnings:
https://builds.apache.org/job/PreCommit-HBASE-Build/11218//artifact/patchprocess/newPatchFindbugsWarningshbase-annotations.html
Findbugs warnings:
https://builds.apache.org/job/PreCommit-HBASE-Build/11218//artifact/patchprocess/newPatchFindbugsWarningshbase-hadoop-compat.html
Findbugs warnings:
https://builds.apache.org/job/PreCommit-HBASE-Build/11218//artifact/patchprocess/newPatchFindbugsWarningshbase-server.html
Findbugs warnings:
https://builds.apache.org/job/PreCommit-HBASE-Build/11218//artifact/patchprocess/newPatchFindbugsWarningshbase-prefix-tree.html
Findbugs warnings:
https://builds.apache.org/job/PreCommit-HBASE-Build/11218//artifact/patchprocess/newPatchFindbugsWarningshbase-protocol.html
Findbugs warnings:
https://builds.apache.org/job/PreCommit-HBASE-Build/11218//artifact/patchprocess/newPatchFindbugsWarningshbase-thrift.html
Findbugs warnings:
https://builds.apache.org/job/PreCommit-HBASE-Build/11218//artifact/patchprocess/newPatchFindbugsWarningshbase-examples.html
Findbugs warnings:
https://builds.apache.org/job/PreCommit-HBASE-Build/11218//artifact/patchprocess/newPatchFindbugsWarningshbase-hadoop2-compat.html
Console output:
https://builds.apache.org/job/PreCommit-HBASE-Build/11218//console
This message is automatically generated.
> Preemptive Fast Fail
>
>
> Key: HBASE-12075
> URL: https://issues.apache.org/jira/browse/HBASE-12075
> Project: HBase
> Issue Type: Sub-task
> Components: Client
>Affects Versions: 0.99.0, 2.0.0, 0.98.6.1
>Reporter: Manukranth Kolloju
>Assignee: Manukranth Kolloju
> Attachments: 0001-Add-a-test-case-for-Preemptive-Fast-Fail.patch,
> 0001-HBASE-12075-Implement-Preemptive-Fast-Fail.patch,
> 0001-HBASE-12075-Implement-Preemptive-Fast-Fail.patch,
> 0001-Implement-Preemptive-Fast-Fail.patch,
> 0001-Implement-Preemptive-Fast-Fail.patch,
> 0001-Implement-Preemptive-Fast-Fail.patch,
> 0001-Implement-Preemptive-Fast-Fail.patch,
> 0001-Implement-Preemptive-Fast-Fail.patch
>
>
> In multi threaded clients, we use a feature developed on 0.89-fb branch
> called Preemptive Fast Fail. This allows the client threads which would
> potentially fail, fail fast. The idea behind this feature is that we allow,
> among the hundreds of client threads, one thread to try and establish
> connection with the regionserver and if that succeeds, we mark it as a live
> node again. Meanwhile, other threads which are trying to establish connection
> to the same server would ideally go into the timeouts which is effectively
> unfruitful. We can in those cases return appropriate exceptions to those
> clients instead of letting them retry.
--
This message was sent by Atlassian JIRA
(v6.3
[jira] [Resolved] (HBASE-12124) Closed region could stay closed if master stops at bad time
[ https://issues.apache.org/jira/browse/HBASE-12124?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrew Purtell resolved HBASE-12124. Resolution: Fixed False alarm. Apologies for the noise > Closed region could stay closed if master stops at bad time > --- > > Key: HBASE-12124 > URL: https://issues.apache.org/jira/browse/HBASE-12124 > Project: HBase > Issue Type: Bug >Reporter: Jimmy Xiang >Assignee: Jimmy Xiang > Fix For: 0.98.7, 0.99.1 > > Attachments: hbase-12124.patch > > > This applies to RPC-based region assignment only. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (HBASE-8808) Use Jacoco to generate Unit Test coverage reports
[ https://issues.apache.org/jira/browse/HBASE-8808?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] stack updated HBASE-8808: - Resolution: Fixed Fix Version/s: (was: 0.89-fb) 0.99.1 2.0.0 Release Note: Adds jacoco plugin. Call it by defining argLine with necessary arguments. By default outputs to target dir. Status: Resolved (was: Patch Available) Committed to branch-1+ Thanks for the patch [~manukranthk] > Use Jacoco to generate Unit Test coverage reports > - > > Key: HBASE-8808 > URL: https://issues.apache.org/jira/browse/HBASE-8808 > Project: HBase > Issue Type: Bug > Components: build >Affects Versions: 0.89-fb >Reporter: Manukranth Kolloju >Assignee: Manukranth Kolloju >Priority: Trivial > Fix For: 2.0.0, 0.99.1 > > Attachments: 0001-Including-Jacoco-plugin-to-get-test-coverage.patch, > 0001-Including-Jacoco-plugin-to-get-test-coverage.patch, > 0001-Including-Jacoco-plugin-to-get-test-coverage.patch, Screen Shot > 2013-06-25 at 11.35.30 AM.png > > Original Estimate: 24h > Remaining Estimate: 24h > > Enabling the code coverage tool jacoco in maven -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (HBASE-12172) Disable flakey TestRegionReplicaReplicationEndpoint and make fixing it a blocker on 1.0
[
https://issues.apache.org/jira/browse/HBASE-12172?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14158944#comment-14158944
]
Hadoop QA commented on HBASE-12172:
---
{color:green}+1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12672903/12172.disable.txt
against trunk revision .
ATTACHMENT ID: 12672903
{color:green}+1 @author{color}. The patch does not contain any @author
tags.
{color:green}+1 tests included{color}. The patch appears to include 3 new
or modified tests.
{color:green}+1 javac{color}. The applied patch does not increase the
total number of javac compiler warnings.
{color:green}+1 javac{color}. The applied patch does not increase the
total number of javac compiler warnings.
{color:green}+1 javadoc{color}. The javadoc tool did not generate any
warning messages.
{color:green}+1 findbugs{color}. The patch does not introduce any new
Findbugs (version 2.0.3) warnings.
{color:green}+1 release audit{color}. The applied patch does not increase
the total number of release audit warnings.
{color:green}+1 lineLengths{color}. The patch does not introduce lines
longer than 100
{color:green}+1 site{color}. The mvn site goal succeeds with this patch.
{color:green}+1 core tests{color}. The patch passed unit tests in .
Test results:
https://builds.apache.org/job/PreCommit-HBASE-Build/11217//testReport/
Findbugs warnings:
https://builds.apache.org/job/PreCommit-HBASE-Build/11217//artifact/patchprocess/newPatchFindbugsWarningshbase-hadoop-compat.html
Findbugs warnings:
https://builds.apache.org/job/PreCommit-HBASE-Build/11217//artifact/patchprocess/newPatchFindbugsWarningshbase-prefix-tree.html
Findbugs warnings:
https://builds.apache.org/job/PreCommit-HBASE-Build/11217//artifact/patchprocess/newPatchFindbugsWarningshbase-examples.html
Findbugs warnings:
https://builds.apache.org/job/PreCommit-HBASE-Build/11217//artifact/patchprocess/newPatchFindbugsWarningshbase-server.html
Findbugs warnings:
https://builds.apache.org/job/PreCommit-HBASE-Build/11217//artifact/patchprocess/newPatchFindbugsWarningshbase-common.html
Findbugs warnings:
https://builds.apache.org/job/PreCommit-HBASE-Build/11217//artifact/patchprocess/newPatchFindbugsWarningshbase-protocol.html
Findbugs warnings:
https://builds.apache.org/job/PreCommit-HBASE-Build/11217//artifact/patchprocess/newPatchFindbugsWarningshbase-client.html
Findbugs warnings:
https://builds.apache.org/job/PreCommit-HBASE-Build/11217//artifact/patchprocess/newPatchFindbugsWarningshbase-thrift.html
Findbugs warnings:
https://builds.apache.org/job/PreCommit-HBASE-Build/11217//artifact/patchprocess/newPatchFindbugsWarningshbase-hadoop2-compat.html
Findbugs warnings:
https://builds.apache.org/job/PreCommit-HBASE-Build/11217//artifact/patchprocess/newPatchFindbugsWarningshbase-annotations.html
Console output:
https://builds.apache.org/job/PreCommit-HBASE-Build/11217//console
This message is automatically generated.
> Disable flakey TestRegionReplicaReplicationEndpoint and make fixing it a
> blocker on 1.0
> ---
>
> Key: HBASE-12172
> URL: https://issues.apache.org/jira/browse/HBASE-12172
> Project: HBase
> Issue Type: Bug
> Components: test
>Reporter: stack
>Assignee: stack
> Fix For: 2.0.0, 0.99.1
>
> Attachments: 12172.disable.txt
>
>
> This test is categorized FlakeyTest. It earned this sobriquet by continually
> failing from time to time.. Here is recent
> https://builds.apache.org/job/HBase-TRUNK/5619/testReport/ It is important
> test and someone needs to spend tie on it but its plain folks are a bit busy
> at mo. Meantime, lets not this test get in the way of our getting all-green
> test runs. Let me put up a patch to disable it. I'll then file blocker
> against 1.0 so it gets fixed before we release.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (HBASE-12172) Disable flakey TestRegionReplicaReplicationEndpoint and make fixing it a blocker on 1.0
[ https://issues.apache.org/jira/browse/HBASE-12172?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14158941#comment-14158941 ] stack commented on HBASE-12172: --- Yeah, I'll commit this tomorrow unless objection. It was just only test to fail on recent 1.0 build: https://builds.apache.org/job/HBase-TRUNK/5620/testReport/ > Disable flakey TestRegionReplicaReplicationEndpoint and make fixing it a > blocker on 1.0 > --- > > Key: HBASE-12172 > URL: https://issues.apache.org/jira/browse/HBASE-12172 > Project: HBase > Issue Type: Bug > Components: test >Reporter: stack >Assignee: stack > Fix For: 2.0.0, 0.99.1 > > Attachments: 12172.disable.txt > > > This test is categorized FlakeyTest. It earned this sobriquet by continually > failing from time to time.. Here is recent > https://builds.apache.org/job/HBase-TRUNK/5619/testReport/ It is important > test and someone needs to spend tie on it but its plain folks are a bit busy > at mo. Meantime, lets not this test get in the way of our getting all-green > test runs. Let me put up a patch to disable it. I'll then file blocker > against 1.0 so it gets fixed before we release. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (HBASE-12148) Remove TimeRangeTracker as point of contention when many threads writing a Store
[ https://issues.apache.org/jira/browse/HBASE-12148?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14158937#comment-14158937 ] Hudson commented on HBASE-12148: FAILURE: Integrated in HBase-TRUNK #5620 (See [https://builds.apache.org/job/HBase-TRUNK/5620/]) HBASE-12148 RegionServerTracker should escape data in log messages (stack: rev 202bc2934a14e52e009dd274ccd179aae388f131) * hbase-server/src/main/java/org/apache/hadoop/hbase/master/HMaster.java * hbase-server/src/main/java/org/apache/hadoop/hbase/zookeeper/RegionServerTracker.java * hbase-server/src/main/java/org/apache/hadoop/hbase/master/SplitLogManager.java * hbase-server/src/test/java/org/apache/hadoop/hbase/master/TestDistributedLogSplitting.java * hbase-server/src/main/java/org/apache/hadoop/hbase/zookeeper/RecoveringRegionWatcher.java * hbase-server/src/main/java/org/apache/hadoop/hbase/regionserver/RSRpcServices.java * hbase-server/src/main/java/org/apache/hadoop/hbase/regionserver/SplitLogWorker.java * hbase-server/src/main/java/org/apache/hadoop/hbase/regionserver/HRegion.java * hbase-server/src/main/java/org/apache/hadoop/hbase/coordination/ZKSplitLogManagerCoordination.java * hbase-server/src/main/java/org/apache/hadoop/hbase/master/handler/ServerShutdownHandler.java > Remove TimeRangeTracker as point of contention when many threads writing a > Store > > > Key: HBASE-12148 > URL: https://issues.apache.org/jira/browse/HBASE-12148 > Project: HBase > Issue Type: Sub-task > Components: Performance >Affects Versions: 2.0.0, 0.99.1 >Reporter: stack >Assignee: stack > Fix For: 2.0.0, 0.99.1 > > Attachments: 12148.txt, 12148.txt, 12148v2.txt, 12148v2.txt, Screen > Shot 2014-10-01 at 3.39.46 PM.png, Screen Shot 2014-10-01 at 3.41.07 PM.png > > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (HBASE-12075) Preemptive Fast Fail
[ https://issues.apache.org/jira/browse/HBASE-12075?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14158930#comment-14158930 ] stack commented on HBASE-12075: --- I don't think is going to fly in ClusterConnection [~manukranthk] + public RetryingCallerInterceptor getRetryingCallerInterceptor(); Fellas have been working on cleaning up the API making it regular, understandable. Inserting the above is going to stick out like a sore thumb IMO. It doesn't even have javadoc. Reading more I get it. The factories and the notion are sound. Makes sense. How to reveal it w/o disturbing ClusterConnection? Can you insert an implementation of ClusterConnection that has getRetryingCallerInterceptor? Or you want us to add a DevelopersClusterConnection marker Interface to CC or add a 'features' or dev tools method that you could get your RetryingCallerInterceptor from? Adding [~sduskis] and [~enis] and [~ndimiduk]... These fellas weill have better ideas than I. > Preemptive Fast Fail > > > Key: HBASE-12075 > URL: https://issues.apache.org/jira/browse/HBASE-12075 > Project: HBase > Issue Type: Sub-task > Components: Client >Affects Versions: 0.99.0, 2.0.0, 0.98.6.1 >Reporter: Manukranth Kolloju >Assignee: Manukranth Kolloju > Attachments: 0001-Add-a-test-case-for-Preemptive-Fast-Fail.patch, > 0001-HBASE-12075-Implement-Preemptive-Fast-Fail.patch, > 0001-HBASE-12075-Implement-Preemptive-Fast-Fail.patch, > 0001-Implement-Preemptive-Fast-Fail.patch, > 0001-Implement-Preemptive-Fast-Fail.patch, > 0001-Implement-Preemptive-Fast-Fail.patch, > 0001-Implement-Preemptive-Fast-Fail.patch, > 0001-Implement-Preemptive-Fast-Fail.patch > > > In multi threaded clients, we use a feature developed on 0.89-fb branch > called Preemptive Fast Fail. This allows the client threads which would > potentially fail, fail fast. The idea behind this feature is that we allow, > among the hundreds of client threads, one thread to try and establish > connection with the regionserver and if that succeeds, we mark it as a live > node again. Meanwhile, other threads which are trying to establish connection > to the same server would ideally go into the timeouts which is effectively > unfruitful. We can in those cases return appropriate exceptions to those > clients instead of letting them retry. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (HBASE-12137) Alter table add cf doesn't do compression test
[ https://issues.apache.org/jira/browse/HBASE-12137?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14158928#comment-14158928 ] Hudson commented on HBASE-12137: SUCCESS: Integrated in HBase-0.98 #570 (See [https://builds.apache.org/job/HBase-0.98/570/]) HBASE-12137 Alter table add cf doesn't do compression test (Virag Kothari) (tedyu: rev 85a60fec6e062094e3e57b8eb299a20166b86554) * hbase-server/src/main/java/org/apache/hadoop/hbase/master/HMaster.java > Alter table add cf doesn't do compression test > -- > > Key: HBASE-12137 > URL: https://issues.apache.org/jira/browse/HBASE-12137 > Project: HBase > Issue Type: Bug > Components: master >Affects Versions: 0.98.6 >Reporter: Virag Kothari >Assignee: Virag Kothari > Fix For: 2.0.0, 0.98.7, 0.99.1 > > Attachments: HBASE-12137-0.98.patch, HBASE-12137.patch, > HBASE-12137.patch > > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (HBASE-12075) Preemptive Fast Fail
[ https://issues.apache.org/jira/browse/HBASE-12075?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] stack updated HBASE-12075: -- Attachment: 0001-HBASE-12075-Implement-Preemptive-Fast-Fail.patch > Preemptive Fast Fail > > > Key: HBASE-12075 > URL: https://issues.apache.org/jira/browse/HBASE-12075 > Project: HBase > Issue Type: Sub-task > Components: Client >Affects Versions: 0.99.0, 2.0.0, 0.98.6.1 >Reporter: Manukranth Kolloju >Assignee: Manukranth Kolloju > Attachments: 0001-Add-a-test-case-for-Preemptive-Fast-Fail.patch, > 0001-HBASE-12075-Implement-Preemptive-Fast-Fail.patch, > 0001-HBASE-12075-Implement-Preemptive-Fast-Fail.patch, > 0001-Implement-Preemptive-Fast-Fail.patch, > 0001-Implement-Preemptive-Fast-Fail.patch, > 0001-Implement-Preemptive-Fast-Fail.patch, > 0001-Implement-Preemptive-Fast-Fail.patch, > 0001-Implement-Preemptive-Fast-Fail.patch > > > In multi threaded clients, we use a feature developed on 0.89-fb branch > called Preemptive Fast Fail. This allows the client threads which would > potentially fail, fail fast. The idea behind this feature is that we allow, > among the hundreds of client threads, one thread to try and establish > connection with the regionserver and if that succeeds, we mark it as a live > node again. Meanwhile, other threads which are trying to establish connection > to the same server would ideally go into the timeouts which is effectively > unfruitful. We can in those cases return appropriate exceptions to those > clients instead of letting them retry. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (HBASE-12075) Preemptive Fast Fail
[ https://issues.apache.org/jira/browse/HBASE-12075?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14158922#comment-14158922 ] stack commented on HBASE-12075: --- TestRegionReplicaReplicationEndpointNoMaster is flakey, TestDistributedLogSplitting should be fixed Let me look at TestMasterNoCluster The test run took 'Took 1 hr 46 min on' (you can see it in top right hand corner of the main test run page). Let me do another run and take a look at the patch > Preemptive Fast Fail > > > Key: HBASE-12075 > URL: https://issues.apache.org/jira/browse/HBASE-12075 > Project: HBase > Issue Type: Sub-task > Components: Client >Affects Versions: 0.99.0, 2.0.0, 0.98.6.1 >Reporter: Manukranth Kolloju >Assignee: Manukranth Kolloju > Attachments: 0001-Add-a-test-case-for-Preemptive-Fast-Fail.patch, > 0001-HBASE-12075-Implement-Preemptive-Fast-Fail.patch, > 0001-Implement-Preemptive-Fast-Fail.patch, > 0001-Implement-Preemptive-Fast-Fail.patch, > 0001-Implement-Preemptive-Fast-Fail.patch, > 0001-Implement-Preemptive-Fast-Fail.patch, > 0001-Implement-Preemptive-Fast-Fail.patch > > > In multi threaded clients, we use a feature developed on 0.89-fb branch > called Preemptive Fast Fail. This allows the client threads which would > potentially fail, fail fast. The idea behind this feature is that we allow, > among the hundreds of client threads, one thread to try and establish > connection with the regionserver and if that succeeds, we mark it as a live > node again. Meanwhile, other threads which are trying to establish connection > to the same server would ideally go into the timeouts which is effectively > unfruitful. We can in those cases return appropriate exceptions to those > clients instead of letting them retry. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (HBASE-12172) Disable flakey TestRegionReplicaReplicationEndpoint and make fixing it a blocker on 1.0
[
https://issues.apache.org/jira/browse/HBASE-12172?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14158919#comment-14158919
]
stack commented on HBASE-12172:
---
In above citation, most of the tests failed with:
Error Message
test timed out after 6 milliseconds
Stacktrace
java.lang.Exception: test timed out after 6 milliseconds
at java.lang.Thread.sleep(Native Method)
at org.apache.hadoop.hbase.Waiter.waitFor(Waiter.java:181)
at org.apache.hadoop.hbase.Waiter.waitFor(Waiter.java:128)
at
org.apache.hadoop.hbase.replication.regionserver.TestRegionReplicaReplicationEndpoint.verifyReplication(TestRegionReplicaReplicationEndpoint.java:194)
at
org.apache.hadoop.hbase.replication.regionserver.TestRegionReplicaReplicationEndpoint.testRegionReplicaReplicationIgnoresDisabledTables(TestRegionReplicaReplicationEndpoint.java:337)
at
org.apache.hadoop.hbase.replication.regionserver.TestRegionReplicaReplicationEndpoint.testRegionReplicaReplicationIgnoresDisabledTables(TestRegionReplicaReplicationEndpoint.java:264)
... but root reason is {code}
2014-10-04 02:08:58,566 WARN [Thread-265]
regionserver.TestRegionReplicaReplicationEndpoint$1(201): Verification from
secondary region is not complete yet. Got:java.lang.AssertionError: Failed
verification of row :1000 Failed verification of row :1000
2014-10-04 02:08:58,666 INFO [Thread-265]
regionserver.TestRegionReplicaReplicationEndpoint$1(197): verifying replication
for region replica:{ENCODED => 9e86318e8e64c9900c752ac6dfc47d11, NAME =>
'testRegionReplicaReplicationIgnoresDisabledTablesfalse,,1412388510571_0001.9e86318e8e64c9900c752ac6dfc47d11.',
STARTKEY => '', ENDKEY => '', REPLICA_ID => 1}
2014-10-04 02:08:58,685 WARN [Thread-265]
regionserver.TestRegionReplicaReplicationEndpoint$1(201): Verification from
secondary region is not complete yet. Got:java.lang.AssertionError: Failed
verification of row :1000 Failed verification of row :1000
2014-10-04 02:08:58,785 INFO [Thread-265]
regionserver.TestRegionReplicaReplicationEndpoint$1(197): verifying replication
for region replica:{ENCODED => 9e86318e8e64c9900c752ac6dfc47d11, NAME =>
'testRegionReplicaReplicationIgnoresDisabledTablesfalse,,1412388510571_0001.9e86318e8e64c9900c752ac6dfc47d11.',
STARTKEY => '', ENDKEY => '', REPLICA_ID => 1}
2014-10-04 02:08:58,804 WARN [Thread-265]
regionserver.TestRegionReplicaReplicationEndpoint$1(201): Verification from
secondary region is not complete yet. Got:java.lang.AssertionError: Failed
verification of row :1000 Failed verification of row :1000
2014-10-04 02:08:58,904 INFO [Thread-265]
regionserver.TestRegionReplicaReplicationEndpoint$1(197): verifying replication
for region replica:{ENCODED => 9e86318e8e64c9900c752ac6dfc47d11, NAME =>
'testRegionReplicaReplicationIgnoresDisabledTablesfalse,,1412388510571_0001.9e86318e8e64c9900c752ac6dfc47d11.',
STARTKEY => '', ENDKEY => '', REPLICA_ID => 1}
2014-10-04 02:08:58,924 WARN [Thread-265]
regionserver.TestRegionReplicaReplicationEndpoint$1(201): Verification from
secondary region is not complete yet. Got:java.lang.AssertionError: Failed
verification of row :1000 Failed verification of row :1000
2014-10-04 02:08:59,024 INFO [Thread-265]
regionserver.TestRegionReplicaReplicationEndpoint$1(197): verifying replication
for region replica:{ENCODED => 9e86318e8e64c9900c752ac6dfc47d11, NAME =>
'testRegionReplicaReplicationIgnoresDisabledTablesfalse,,1412388510571_0001.9e86318e8e64c9900c752ac6dfc47d11.',
STARTKEY => '', ENDKEY => '', REPLICA_ID => 1}
2014-10-04 02:08:59,044 WARN [Thread-265]
regionserver.TestRegionReplicaReplicationEndpoint$1(201): Verification from
secondary region is not complete yet. Got:java.lang.AssertionError: Failed
verification of row :1000 Failed verification of row :1000
...
{code}
> Disable flakey TestRegionReplicaReplicationEndpoint and make fixing it a
> blocker on 1.0
> ---
>
> Key: HBASE-12172
> URL: https://issues.apache.org/jira/browse/HBASE-12172
> Project: HBase
> Issue Type: Bug
> Components: test
>Reporter: stack
>Assignee: stack
> Fix For: 2.0.0, 0.99.1
>
> Attachments: 12172.disable.txt
>
>
> This test is categorized FlakeyTest. It earned this sobriquet by continually
> failing from time to time.. Here is recent
> https://builds.apache.org/job/HBase-TRUNK/5619/testReport/ It is important
> test and someone needs to spend tie on it but its plain folks are a bit busy
> at mo. Meantime, lets not this test get in the way of our getting all-green
> test runs. Let me put up a patch to disable it. I'll then file blocker
> against 1.0 so it gets fixed before we release.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (HBASE-12172) Disable flakey TestRegionReplicaReplicationEndpoint and make fixing it a blocker on 1.0
[ https://issues.apache.org/jira/browse/HBASE-12172?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] stack updated HBASE-12172: -- Assignee: stack Status: Patch Available (was: Open) > Disable flakey TestRegionReplicaReplicationEndpoint and make fixing it a > blocker on 1.0 > --- > > Key: HBASE-12172 > URL: https://issues.apache.org/jira/browse/HBASE-12172 > Project: HBase > Issue Type: Bug > Components: test >Reporter: stack >Assignee: stack > Fix For: 2.0.0, 0.99.1 > > Attachments: 12172.disable.txt > > > This test is categorized FlakeyTest. It earned this sobriquet by continually > failing from time to time.. Here is recent > https://builds.apache.org/job/HBase-TRUNK/5619/testReport/ It is important > test and someone needs to spend tie on it but its plain folks are a bit busy > at mo. Meantime, lets not this test get in the way of our getting all-green > test runs. Let me put up a patch to disable it. I'll then file blocker > against 1.0 so it gets fixed before we release. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (HBASE-12172) Disable flakey TestRegionReplicaReplicationEndpoint and make fixing it a blocker on 1.0
[ https://issues.apache.org/jira/browse/HBASE-12172?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] stack updated HBASE-12172: -- Attachment: 12172.disable.txt Disable the tests > Disable flakey TestRegionReplicaReplicationEndpoint and make fixing it a > blocker on 1.0 > --- > > Key: HBASE-12172 > URL: https://issues.apache.org/jira/browse/HBASE-12172 > Project: HBase > Issue Type: Bug > Components: test >Reporter: stack > Fix For: 2.0.0, 0.99.1 > > Attachments: 12172.disable.txt > > > This test is categorized FlakeyTest. It earned this sobriquet by continually > failing from time to time.. Here is recent > https://builds.apache.org/job/HBase-TRUNK/5619/testReport/ It is important > test and someone needs to spend tie on it but its plain folks are a bit busy > at mo. Meantime, lets not this test get in the way of our getting all-green > test runs. Let me put up a patch to disable it. I'll then file blocker > against 1.0 so it gets fixed before we release. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (HBASE-12148) Remove TimeRangeTracker as point of contention when many threads writing a Store
[ https://issues.apache.org/jira/browse/HBASE-12148?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14158909#comment-14158909 ] Hudson commented on HBASE-12148: FAILURE: Integrated in HBase-1.0 #274 (See [https://builds.apache.org/job/HBase-1.0/274/]) HBASE-12148 RegionServerTracker should escape data in log messages (stack: rev 136d2d21562f6adabb336abe6a1b0959da7da05e) * hbase-server/src/test/java/org/apache/hadoop/hbase/master/TestDistributedLogSplitting.java * hbase-server/src/main/java/org/apache/hadoop/hbase/zookeeper/RecoveringRegionWatcher.java * hbase-server/src/main/java/org/apache/hadoop/hbase/master/handler/ServerShutdownHandler.java * hbase-server/src/main/java/org/apache/hadoop/hbase/regionserver/HRegion.java * hbase-server/src/main/java/org/apache/hadoop/hbase/regionserver/SplitLogWorker.java * hbase-server/src/main/java/org/apache/hadoop/hbase/master/HMaster.java * hbase-server/src/main/java/org/apache/hadoop/hbase/zookeeper/RegionServerTracker.java * hbase-server/src/main/java/org/apache/hadoop/hbase/master/SplitLogManager.java * hbase-server/src/main/java/org/apache/hadoop/hbase/regionserver/RSRpcServices.java * hbase-server/src/main/java/org/apache/hadoop/hbase/coordination/ZKSplitLogManagerCoordination.java > Remove TimeRangeTracker as point of contention when many threads writing a > Store > > > Key: HBASE-12148 > URL: https://issues.apache.org/jira/browse/HBASE-12148 > Project: HBase > Issue Type: Sub-task > Components: Performance >Affects Versions: 2.0.0, 0.99.1 >Reporter: stack >Assignee: stack > Fix For: 2.0.0, 0.99.1 > > Attachments: 12148.txt, 12148.txt, 12148v2.txt, 12148v2.txt, Screen > Shot 2014-10-01 at 3.39.46 PM.png, Screen Shot 2014-10-01 at 3.41.07 PM.png > > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (HBASE-12172) Disable flakey TestRegionReplicaReplicationEndpoint and make fixing it a blocker on 1.0
stack created HBASE-12172: - Summary: Disable flakey TestRegionReplicaReplicationEndpoint and make fixing it a blocker on 1.0 Key: HBASE-12172 URL: https://issues.apache.org/jira/browse/HBASE-12172 Project: HBase Issue Type: Bug Components: test Reporter: stack Fix For: 2.0.0, 0.99.1 This test is categorized FlakeyTest. It earned this sobriquet by continually failing from time to time.. Here is recent https://builds.apache.org/job/HBase-TRUNK/5619/testReport/ It is important test and someone needs to spend tie on it but its plain folks are a bit busy at mo. Meantime, lets not this test get in the way of our getting all-green test runs. Let me put up a patch to disable it. I'll then file blocker against 1.0 so it gets fixed before we release. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (HBASE-12146) RegionServerTracker should escape data in log messages
[ https://issues.apache.org/jira/browse/HBASE-12146?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] stack updated HBASE-12146: -- Resolution: Fixed Hadoop Flags: Reviewed Status: Resolved (was: Patch Available) Thanks for review [~lhofhansl] Pushed to branch-1+ (nice all green pluses above) > RegionServerTracker should escape data in log messages > -- > > Key: HBASE-12146 > URL: https://issues.apache.org/jira/browse/HBASE-12146 > Project: HBase > Issue Type: Bug >Reporter: Lars Hofhansl >Assignee: stack >Priority: Trivial > Fix For: 2.0.0, 0.99.1 > > Attachments: 12146.txt > > > Trivial thing I observed when testing 0.94.24RC2. > I see a log message of the form: > 2014-10-01 13:52:35,632 INFO > org.apache.hadoop.hbase.zookeeper.RegionServerTracker: Rs node: > /hbase/rs/newbunny,52514,1412196754788 data: PBUο^C > Obviously the tracker does not escape the value (or maybe it shouldn't log it > in the fist place) -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (HBASE-12170) TestReplicaWithCluster.testReplicaAndReplication timeouts
[
https://issues.apache.org/jira/browse/HBASE-12170?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=1415#comment-1415
]
Hudson commented on HBASE-12170:
FAILURE: Integrated in HBase-TRUNK #5619 (See
[https://builds.apache.org/job/HBase-TRUNK/5619/])
HBASE-12170 TestReplicaWithCluster.testReplicaAndReplication timeouts (stack:
rev 3acdf06827c648764de40932454eb2eff704)
*
hbase-server/src/test/java/org/apache/hadoop/hbase/client/TestReplicaWithCluster.java
> TestReplicaWithCluster.testReplicaAndReplication timeouts
> -
>
> Key: HBASE-12170
> URL: https://issues.apache.org/jira/browse/HBASE-12170
> Project: HBase
> Issue Type: Bug
> Components: test
>Reporter: stack
>Assignee: stack
> Fix For: 2.0.0, 0.99.1
>
> Attachments: to.txt
>
>
> On our internal rig I got a timeout. Looking over the test, it looks to be
> making progress if slow. The test does a crazy amount of stuff too... so let
> me just up the timeout for now.
> {code}
> org.apache.hadoop.hbase.client.TestReplicaWithCluster.testReplicaAndReplication
> Failing for the past 1 build (Since Unstable#10 )
> Took 0.42 sec.
> Error Message
> test timed out after 12 milliseconds
> Stacktrace
> java.lang.Exception: test timed out after 12 milliseconds
> at java.lang.Thread.sleep(Native Method)
> at
> org.apache.hadoop.hbase.client.HBaseAdmin.disableTable(HBaseAdmin.java:999)
> at
> org.apache.hadoop.hbase.client.TestReplicaWithCluster.testReplicaAndReplication(TestReplicaWithCluster.java:302)
> 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:606)
> at
> org.junit.runners.model.FrameworkMethod$1.runReflectiveCall(FrameworkMethod.java:47)
> at
> org.junit.internal.runners.model.ReflectiveCallable.run(ReflectiveCallable.java:12)
> at
> org.junit.runners.model.FrameworkMethod.invokeExplosively(FrameworkMethod.java:44)
> at
> org.junit.internal.runners.statements.InvokeMethod.evaluate(InvokeMethod.java:17)
> at
> org.junit.internal.runners.statements.FailOnTimeout$StatementThread.run(FailOnTimeout.java:74)
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (HBASE-12104) Some optimization and bugfix for HTableMultiplexer
[ https://issues.apache.org/jira/browse/HBASE-12104?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14158889#comment-14158889 ] Hudson commented on HBASE-12104: FAILURE: Integrated in HBase-TRUNK #5619 (See [https://builds.apache.org/job/HBase-TRUNK/5619/]) HBASE-12104 Some optimization and bugfix for HTableMultiplexer (Yi Deng) (stack: rev bc4f25ff452da5cbb692088b51c6fd19e3f9fdc3) * hbase-client/src/main/java/org/apache/hadoop/hbase/client/HTableMultiplexer.java > Some optimization and bugfix for HTableMultiplexer > -- > > Key: HBASE-12104 > URL: https://issues.apache.org/jira/browse/HBASE-12104 > Project: HBase > Issue Type: Sub-task > Components: Client >Affects Versions: 2.0.0 >Reporter: Yi Deng >Assignee: Yi Deng > Labels: multiplexer > Fix For: 2.0.0 > > Attachments: > 0001-Make-HTableMultiplexerStatus-public-Delay-before-res.patch, > 0001-Make-HTableMultiplexerStatus-public-Delay-before-res.patch, > 0001-Make-HTableMultiplexerStatus-public-Delay-before-res.patch, > 0001-Make-HTableMultiplexerStatus-public.patch > > > Make HTableMultiplexerStatus public > Delay before resubmit. > Fix some missing counting on total failure. > Use ScheduledExecutorService to simplify the code. > Other refactoring. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (HBASE-12137) Alter table add cf doesn't do compression test
[ https://issues.apache.org/jira/browse/HBASE-12137?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14158890#comment-14158890 ] Hudson commented on HBASE-12137: FAILURE: Integrated in HBase-TRUNK #5619 (See [https://builds.apache.org/job/HBase-TRUNK/5619/]) HBASE-12137 Alter table add cf doesn't do compression test (Virag Kothari) (tedyu: rev 7972ae764b8aef1c2bc2cd07d4cd4f3b14a4aef2) * hbase-server/src/main/java/org/apache/hadoop/hbase/master/HMaster.java > Alter table add cf doesn't do compression test > -- > > Key: HBASE-12137 > URL: https://issues.apache.org/jira/browse/HBASE-12137 > Project: HBase > Issue Type: Bug > Components: master >Affects Versions: 0.98.6 >Reporter: Virag Kothari >Assignee: Virag Kothari > Fix For: 2.0.0, 0.98.7, 0.99.1 > > Attachments: HBASE-12137-0.98.patch, HBASE-12137.patch, > HBASE-12137.patch > > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (HBASE-12166) TestDistributedLogSplitting.testMasterStartsUpWithLogReplayWork
[
https://issues.apache.org/jira/browse/HBASE-12166?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14158891#comment-14158891
]
Hudson commented on HBASE-12166:
FAILURE: Integrated in HBase-TRUNK #5619 (See
[https://builds.apache.org/job/HBase-TRUNK/5619/])
HBASE-12166 TestDistributedLogSplitting.testMasterStartsUpWithLogReplayWork
(jxiang: rev ef35182f1fcb8e23566e66211f78eb5200168122)
*
hbase-server/src/test/java/org/apache/hadoop/hbase/replication/regionserver/TestRegionReplicaReplicationEndpoint.java
*
hbase-server/src/main/java/org/apache/hadoop/hbase/coordination/ZKSplitLogManagerCoordination.java
> TestDistributedLogSplitting.testMasterStartsUpWithLogReplayWork
> ---
>
> Key: HBASE-12166
> URL: https://issues.apache.org/jira/browse/HBASE-12166
> Project: HBase
> Issue Type: Bug
> Components: test, wal
>Reporter: stack
>Assignee: Jimmy Xiang
> Fix For: 2.0.0, 0.99.1
>
> Attachments: 12166.txt, hbase-12166.patch, hbase-12166_v2.patch,
> log.txt
>
>
> See
> https://builds.apache.org/job/PreCommit-HBASE-Build/11204//testReport/org.apache.hadoop.hbase.master/TestDistributedLogSplitting/testMasterStartsUpWithLogReplayWork/
> The namespace region gets stuck. It is never 'recovered' even though we have
> finished log splitting. Here is the main exception:
> {code}
> 4941 2014-10-03 02:00:36,862 DEBUG
> [B.defaultRpcServer.handler=1,queue=0,port=37113] ipc.CallRunner(111):
> B.defaultRpcServer.handler=1,queue=0,port=37113: callId: 211 service:
> ClientService methodName: Get
> size: 99 connection: 67.195.81.144:44526
> 4942 org.apache.hadoop.hbase.exceptions.RegionInRecoveryException:
> hbase:namespace,,1412301462277.eba5d23de65f2718715eeb22edf7edc2. is recovering
> 4943 at
> org.apache.hadoop.hbase.regionserver.HRegion.startRegionOperation(HRegion.java:6058)
> 4944 at
> org.apache.hadoop.hbase.regionserver.HRegion.getScanner(HRegion.java:2086)
> 4945 at
> org.apache.hadoop.hbase.regionserver.HRegion.getScanner(HRegion.java:2072)
> 4946 at org.apache.hadoop.hbase.regionserver.HRegion.get(HRegion.java:5014)
> 4947 at org.apache.hadoop.hbase.regionserver.HRegion.get(HRegion.java:4988)
> 4948 at
> org.apache.hadoop.hbase.regionserver.RSRpcServices.get(RSRpcServices.java:1690)
> 4949 at
> org.apache.hadoop.hbase.protobuf.generated.ClientProtos$ClientService$2.callBlockingMethod(ClientProtos.java:30418)
> 4950 at org.apache.hadoop.hbase.ipc.RpcServer.call(RpcServer.java:2020)
> 4951 at org.apache.hadoop.hbase.ipc.CallRunner.run(CallRunner.java:108)
> 4952 at
> org.apache.hadoop.hbase.ipc.RpcExecutor.consumerLoop(RpcExecutor.java:114)
> 4953 at org.apache.hadoop.hbase.ipc.RpcExecutor$1.run(RpcExecutor.java:94)
> 4954 at java.lang.Thread.run(Thread.java:744)
> {code}
> See how we've finished log splitting long time previous:
> {code}
> 2014-10-03 01:57:48,129 INFO [M_LOG_REPLAY_OPS-asf900:37113-1]
> master.SplitLogManager(294): finished splitting (more than or equal to)
> 197337 bytes in 1 log files in
> [hdfs://localhost:49601/user/jenkins/hbase/WALs/asf900.gq1.ygridcore.net,40732,1412301461887-splitting]
> in 379ms
> {code}
> If I grep for the deleting of znodes on recovery, which is when we set the
> recovering flag to false, I see a bunch of regions but not my namespace one:
> 2014-10-03 01:57:47,330 INFO [Thread-9216-EventThread]
> zookeeper.RecoveringRegionWatcher(66): /hbase/recovering-regions/1588230740
> znode deleted. Region: 1588230740 completes recovery.
> 2014-10-03 01:57:48,119 INFO [Thread-9216-EventThread]
> zookeeper.RecoveringRegionWatcher(66):
> /hbase/recovering-regions/adfdcf958dd958f0e2ce59072ce2209d znode deleted.
> Region: adfdcf958dd958f0e2ce59072ce2209d completes recovery.
> 2014-10-03 01:57:48,121 INFO [Thread-9216-EventThread]
> zookeeper.RecoveringRegionWatcher(66):
> /hbase/recovering-regions/41d438848305831b61d708a406d5ecde znode deleted.
> Region: 41d438848305831b61d708a406d5ecde completes recovery.
> 2014-10-03 01:57:48,122 INFO [Thread-9216-EventThread]
> zookeeper.RecoveringRegionWatcher(66):
> /hbase/recovering-regions/6a7cada80de2ae5d774fe8cd33bd4cda znode deleted.
> Region: 6a7cada80de2ae5d774fe8cd33bd4cda completes recovery.
> 2014-10-03 01:57:48,124 INFO [Thread-9216-EventThread]
> zookeeper.RecoveringRegionWatcher(66):
> /hbase/recovering-regions/65451bd5b38bd16a31e25b62b3305533 znode deleted.
> Region: 65451bd5b38bd16a31e25b62b3305533 completes recovery.
> 2014-10-03 01:57:48,125 INFO [Thread-9216-EventThread]
> zookeeper.RecoveringRegionWatcher(66):
> /hbase/recovering-regions/07afdc3748894cf2b56e0075272a95a0 znode deleted.
> Region: 07afdc3748894cf2b56e0075272a95a0 completes recovery.
> 2014-10-03 01:57:48,126 INFO [Thread-9216-EventThread]
> zook
[jira] [Commented] (HBASE-12156) TableName cache isn't used for one of valueOf methods.
[ https://issues.apache.org/jira/browse/HBASE-12156?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14158874#comment-14158874 ] Hudson commented on HBASE-12156: FAILURE: Integrated in HBase-0.98 #569 (See [https://builds.apache.org/job/HBase-0.98/569/]) Amend HBASE-12156 TableName cache isn't used for one of valueOf methods; make TestTableName a medium test (apurtell: rev 4bd09d13588f527d6a68af3b6abb481f9432cfdd) * hbase-server/src/test/java/org/apache/hadoop/hbase/util/TestTableName.java > TableName cache isn't used for one of valueOf methods. > -- > > Key: HBASE-12156 > URL: https://issues.apache.org/jira/browse/HBASE-12156 > Project: HBase > Issue Type: Bug >Reporter: Andrey Stepachev >Assignee: Andrey Stepachev > Fix For: 2.0.0, 0.98.7, 0.99.1 > > Attachments: HBASE-12156-addendum-0.98.patch, > HBASE-12156-addendum-2.branch-1.patch, HBASE-12156-addendum-2.patch, > HBASE-12156.patch > > > there is wrong comparison, copy&paste code compares namespace with qualifier > and namespace. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (HBASE-12171) PerformanceEvaluation: getSplits doesn't provide right splits.
[ https://issues.apache.org/jira/browse/HBASE-12171?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14158862#comment-14158862 ] Jean-Marc Spaggiari commented on HBASE-12171: - [~lhofhansl] For you. Patch attached. Let me you if you are +1 so I can comit it in the 0.94 branch N, I'm joking ;) Can you please do it? Back ported that from trunk. Thanks. Called the getSplit method locally, looked at the spits variable. Get the right number of elements. Content also seems to be correct. > PerformanceEvaluation: getSplits doesn't provide right splits. > -- > > Key: HBASE-12171 > URL: https://issues.apache.org/jira/browse/HBASE-12171 > Project: HBase > Issue Type: Bug >Affects Versions: 0.94.23 >Reporter: Jean-Marc Spaggiari >Assignee: Jean-Marc Spaggiari > Attachments: HBASE-12171-v0-0.94.patch > > > Only in 0.94 branch. getSplits provides an extra region. when asked 24, will > get 25. etc. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (HBASE-12171) PerformanceEvaluation: getSplits doesn't provide right splits.
[ https://issues.apache.org/jira/browse/HBASE-12171?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jean-Marc Spaggiari updated HBASE-12171: Attachment: HBASE-12171-v0-0.94.patch > PerformanceEvaluation: getSplits doesn't provide right splits. > -- > > Key: HBASE-12171 > URL: https://issues.apache.org/jira/browse/HBASE-12171 > Project: HBase > Issue Type: Bug >Affects Versions: 0.94.23 >Reporter: Jean-Marc Spaggiari >Assignee: Jean-Marc Spaggiari > Attachments: HBASE-12171-v0-0.94.patch > > > Only in 0.94 branch. getSplits provides an extra region. when asked 24, will > get 25. etc. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (HBASE-12171) PerformanceEvaluation: getSplits doesn't provide right splits.
Jean-Marc Spaggiari created HBASE-12171: --- Summary: PerformanceEvaluation: getSplits doesn't provide right splits. Key: HBASE-12171 URL: https://issues.apache.org/jira/browse/HBASE-12171 Project: HBase Issue Type: Bug Affects Versions: 0.94.23 Reporter: Jean-Marc Spaggiari Assignee: Jean-Marc Spaggiari Only in 0.94 branch. getSplits provides an extra region. when asked 24, will get 25. etc. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (HBASE-11764) Support per cell TTLs
[ https://issues.apache.org/jira/browse/HBASE-11764?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14158850#comment-14158850 ] Andrew Purtell commented on HBASE-11764: Updated without HBASE-11763 as requested [~lhofhansl] > Support per cell TTLs > - > > Key: HBASE-11764 > URL: https://issues.apache.org/jira/browse/HBASE-11764 > Project: HBase > Issue Type: Sub-task >Reporter: Andrew Purtell >Assignee: Andrew Purtell > Fix For: 2.0.0, 0.98.7, 0.99.1 > > Attachments: HBASE-11764-0.98.patch, HBASE-11764-0.98.patch, > HBASE-11764-0.98.patch, HBASE-11764.patch, HBASE-11764.patch, > HBASE-11764.patch, HBASE-11764.patch, HBASE-11764.patch, HBASE-11764.patch, > HBASE-11764.patch, HBASE-11764.patch, HBASE-11764.patch, HBASE-11764.patch > > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (HBASE-11764) Support per cell TTLs
[
https://issues.apache.org/jira/browse/HBASE-11764?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14158849#comment-14158849
]
Andrew Purtell commented on HBASE-11764:
Latest 0.98 passes all unit tests:
{noformat}
...
[INFO] Building HBase - Common 0.98.7-SNAPSHOT
...
Tests run: 164, Failures: 0, Errors: 0, Skipped: 0
...
[INFO] Building HBase - Client 0.98.7-SNAPSHOT
...
Tests run: 51, Failures: 0, Errors: 0, Skipped: 1
...
[INFO] Building HBase - Hadoop Compatibility 0.98.7-SNAPSHOT
...
Tests run: 7, Failures: 0, Errors: 0, Skipped: 0
...
[INFO] Building HBase - Hadoop Two Compatibility 0.98.7-SNAPSHOT
...
Tests run: 16, Failures: 0, Errors: 0, Skipped: 0
...
[INFO] Building HBase - Prefix Tree 0.98.7-SNAPSHOT
...
Tests run: 277, Failures: 0, Errors: 0, Skipped: 0
...
[INFO] Building HBase - Server 0.98.7-SNAPSHOT
...
Tests run: 830, Failures: 0, Errors: 0, Skipped: 2
Tests run: 1263, Failures: 0, Errors: 0, Skipped: 8
...
[INFO] Building HBase - Thrift 0.98.7-SNAPSHOT
...
Tests run: 77, Failures: 0, Errors: 0, Skipped: 0
...
[INFO]
[INFO] BUILD SUCCESS
[INFO]
[INFO] Total time: 51:02 min
[INFO] Finished at: 2014-10-03T18:27:04-08:00
[INFO] Final Memory: 49M/370M
{noformat}
> Support per cell TTLs
> -
>
> Key: HBASE-11764
> URL: https://issues.apache.org/jira/browse/HBASE-11764
> Project: HBase
> Issue Type: Sub-task
>Reporter: Andrew Purtell
>Assignee: Andrew Purtell
> Fix For: 2.0.0, 0.98.7, 0.99.1
>
> Attachments: HBASE-11764-0.98.patch, HBASE-11764-0.98.patch,
> HBASE-11764-0.98.patch, HBASE-11764.patch, HBASE-11764.patch,
> HBASE-11764.patch, HBASE-11764.patch, HBASE-11764.patch, HBASE-11764.patch,
> HBASE-11764.patch, HBASE-11764.patch, HBASE-11764.patch, HBASE-11764.patch
>
>
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (HBASE-12146) RegionServerTracker should escape data in log messages
[
https://issues.apache.org/jira/browse/HBASE-12146?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14158848#comment-14158848
]
Hadoop QA commented on HBASE-12146:
---
{color:green}+1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12672880/12146.txt
against trunk revision .
ATTACHMENT ID: 12672880
{color:green}+1 @author{color}. The patch does not contain any @author
tags.
{color:green}+1 tests included{color}. The patch appears to include 3 new
or modified tests.
{color:green}+1 javac{color}. The applied patch does not increase the
total number of javac compiler warnings.
{color:green}+1 javac{color}. The applied patch does not increase the
total number of javac compiler warnings.
{color:green}+1 javadoc{color}. The javadoc tool did not generate any
warning messages.
{color:green}+1 findbugs{color}. The patch does not introduce any new
Findbugs (version 2.0.3) warnings.
{color:green}+1 release audit{color}. The applied patch does not increase
the total number of release audit warnings.
{color:green}+1 lineLengths{color}. The patch does not introduce lines
longer than 100
{color:green}+1 site{color}. The mvn site goal succeeds with this patch.
{color:green}+1 core tests{color}. The patch passed unit tests in .
Test results:
https://builds.apache.org/job/PreCommit-HBASE-Build/11216//testReport/
Findbugs warnings:
https://builds.apache.org/job/PreCommit-HBASE-Build/11216//artifact/patchprocess/newPatchFindbugsWarningshbase-hadoop-compat.html
Findbugs warnings:
https://builds.apache.org/job/PreCommit-HBASE-Build/11216//artifact/patchprocess/newPatchFindbugsWarningshbase-prefix-tree.html
Findbugs warnings:
https://builds.apache.org/job/PreCommit-HBASE-Build/11216//artifact/patchprocess/newPatchFindbugsWarningshbase-examples.html
Findbugs warnings:
https://builds.apache.org/job/PreCommit-HBASE-Build/11216//artifact/patchprocess/newPatchFindbugsWarningshbase-server.html
Findbugs warnings:
https://builds.apache.org/job/PreCommit-HBASE-Build/11216//artifact/patchprocess/newPatchFindbugsWarningshbase-common.html
Findbugs warnings:
https://builds.apache.org/job/PreCommit-HBASE-Build/11216//artifact/patchprocess/newPatchFindbugsWarningshbase-protocol.html
Findbugs warnings:
https://builds.apache.org/job/PreCommit-HBASE-Build/11216//artifact/patchprocess/newPatchFindbugsWarningshbase-client.html
Findbugs warnings:
https://builds.apache.org/job/PreCommit-HBASE-Build/11216//artifact/patchprocess/newPatchFindbugsWarningshbase-thrift.html
Findbugs warnings:
https://builds.apache.org/job/PreCommit-HBASE-Build/11216//artifact/patchprocess/newPatchFindbugsWarningshbase-hadoop2-compat.html
Findbugs warnings:
https://builds.apache.org/job/PreCommit-HBASE-Build/11216//artifact/patchprocess/newPatchFindbugsWarningshbase-annotations.html
Console output:
https://builds.apache.org/job/PreCommit-HBASE-Build/11216//console
This message is automatically generated.
> RegionServerTracker should escape data in log messages
> --
>
> Key: HBASE-12146
> URL: https://issues.apache.org/jira/browse/HBASE-12146
> Project: HBase
> Issue Type: Bug
>Reporter: Lars Hofhansl
>Assignee: stack
>Priority: Trivial
> Fix For: 2.0.0, 0.99.1
>
> Attachments: 12146.txt
>
>
> Trivial thing I observed when testing 0.94.24RC2.
> I see a log message of the form:
> 2014-10-01 13:52:35,632 INFO
> org.apache.hadoop.hbase.zookeeper.RegionServerTracker: Rs node:
> /hbase/rs/newbunny,52514,1412196754788 data: PBUο^C
> Obviously the tracker does not escape the value (or maybe it shouldn't log it
> in the fist place)
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (HBASE-12137) Alter table add cf doesn't do compression test
[ https://issues.apache.org/jira/browse/HBASE-12137?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14158846#comment-14158846 ] Hudson commented on HBASE-12137: FAILURE: Integrated in HBase-0.98-on-Hadoop-1.1 #541 (See [https://builds.apache.org/job/HBase-0.98-on-Hadoop-1.1/541/]) HBASE-12137 Alter table add cf doesn't do compression test (Virag Kothari) (tedyu: rev 85a60fec6e062094e3e57b8eb299a20166b86554) * hbase-server/src/main/java/org/apache/hadoop/hbase/master/HMaster.java > Alter table add cf doesn't do compression test > -- > > Key: HBASE-12137 > URL: https://issues.apache.org/jira/browse/HBASE-12137 > Project: HBase > Issue Type: Bug > Components: master >Affects Versions: 0.98.6 >Reporter: Virag Kothari >Assignee: Virag Kothari > Fix For: 2.0.0, 0.98.7, 0.99.1 > > Attachments: HBASE-12137-0.98.patch, HBASE-12137.patch, > HBASE-12137.patch > > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (HBASE-12126) Region server coprocessor endpoint
[ https://issues.apache.org/jira/browse/HBASE-12126?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14158843#comment-14158843 ] Andrew Purtell commented on HBASE-12126: We can commit once there's a trunk patch > Region server coprocessor endpoint > -- > > Key: HBASE-12126 > URL: https://issues.apache.org/jira/browse/HBASE-12126 > Project: HBase > Issue Type: Bug > Components: Coprocessors >Affects Versions: 0.98.6 >Reporter: Virag Kothari >Assignee: Virag Kothari > Attachments: HBASE-12126-0.98.patch, HBASE-12126-0.98_1.patch > > > Utility to make endpoint calls against region server -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (HBASE-12156) TableName cache isn't used for one of valueOf methods.
[ https://issues.apache.org/jira/browse/HBASE-12156?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14158841#comment-14158841 ] Hudson commented on HBASE-12156: FAILURE: Integrated in HBase-TRUNK #5618 (See [https://builds.apache.org/job/HBase-TRUNK/5618/]) Amend HBASE-12156 TableName cache isn't used for one of valueOf methods; make TestTableName a medium test (apurtell: rev 0c0d7eb2419c78f9035d2565a8e6e807b0b6f605) * hbase-server/src/test/java/org/apache/hadoop/hbase/util/TestTableName.java > TableName cache isn't used for one of valueOf methods. > -- > > Key: HBASE-12156 > URL: https://issues.apache.org/jira/browse/HBASE-12156 > Project: HBase > Issue Type: Bug >Reporter: Andrey Stepachev >Assignee: Andrey Stepachev > Fix For: 2.0.0, 0.98.7, 0.99.1 > > Attachments: HBASE-12156-addendum-0.98.patch, > HBASE-12156-addendum-2.branch-1.patch, HBASE-12156-addendum-2.patch, > HBASE-12156.patch > > > there is wrong comparison, copy&paste code compares namespace with qualifier > and namespace. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (HBASE-12156) TableName cache isn't used for one of valueOf methods.
[ https://issues.apache.org/jira/browse/HBASE-12156?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14158837#comment-14158837 ] Hudson commented on HBASE-12156: FAILURE: Integrated in HBase-1.0 #273 (See [https://builds.apache.org/job/HBase-1.0/273/]) Amend HBASE-12156 TableName cache isn't used for one of valueOf methods; make TestTableName a medium test (apurtell: rev cf3b0179fb40863f70c615ac172549fe52f0a63a) * hbase-server/src/test/java/org/apache/hadoop/hbase/util/TestTableName.java > TableName cache isn't used for one of valueOf methods. > -- > > Key: HBASE-12156 > URL: https://issues.apache.org/jira/browse/HBASE-12156 > Project: HBase > Issue Type: Bug >Reporter: Andrey Stepachev >Assignee: Andrey Stepachev > Fix For: 2.0.0, 0.98.7, 0.99.1 > > Attachments: HBASE-12156-addendum-0.98.patch, > HBASE-12156-addendum-2.branch-1.patch, HBASE-12156-addendum-2.patch, > HBASE-12156.patch > > > there is wrong comparison, copy&paste code compares namespace with qualifier > and namespace. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (HBASE-12170) TestReplicaWithCluster.testReplicaAndReplication timeouts
[
https://issues.apache.org/jira/browse/HBASE-12170?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14158835#comment-14158835
]
Hudson commented on HBASE-12170:
FAILURE: Integrated in HBase-1.0 #273 (See
[https://builds.apache.org/job/HBase-1.0/273/])
HBASE-12170 TestReplicaWithCluster.testReplicaAndReplication timeouts (stack:
rev 03bb550987fd5dc82757e556bfd93c890f609dfe)
*
hbase-server/src/test/java/org/apache/hadoop/hbase/client/TestReplicaWithCluster.java
> TestReplicaWithCluster.testReplicaAndReplication timeouts
> -
>
> Key: HBASE-12170
> URL: https://issues.apache.org/jira/browse/HBASE-12170
> Project: HBase
> Issue Type: Bug
> Components: test
>Reporter: stack
>Assignee: stack
> Fix For: 2.0.0, 0.99.1
>
> Attachments: to.txt
>
>
> On our internal rig I got a timeout. Looking over the test, it looks to be
> making progress if slow. The test does a crazy amount of stuff too... so let
> me just up the timeout for now.
> {code}
> org.apache.hadoop.hbase.client.TestReplicaWithCluster.testReplicaAndReplication
> Failing for the past 1 build (Since Unstable#10 )
> Took 0.42 sec.
> Error Message
> test timed out after 12 milliseconds
> Stacktrace
> java.lang.Exception: test timed out after 12 milliseconds
> at java.lang.Thread.sleep(Native Method)
> at
> org.apache.hadoop.hbase.client.HBaseAdmin.disableTable(HBaseAdmin.java:999)
> at
> org.apache.hadoop.hbase.client.TestReplicaWithCluster.testReplicaAndReplication(TestReplicaWithCluster.java:302)
> 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:606)
> at
> org.junit.runners.model.FrameworkMethod$1.runReflectiveCall(FrameworkMethod.java:47)
> at
> org.junit.internal.runners.model.ReflectiveCallable.run(ReflectiveCallable.java:12)
> at
> org.junit.runners.model.FrameworkMethod.invokeExplosively(FrameworkMethod.java:44)
> at
> org.junit.internal.runners.statements.InvokeMethod.evaluate(InvokeMethod.java:17)
> at
> org.junit.internal.runners.statements.FailOnTimeout$StatementThread.run(FailOnTimeout.java:74)
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (HBASE-12104) Some optimization and bugfix for HTableMultiplexer
[ https://issues.apache.org/jira/browse/HBASE-12104?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14158836#comment-14158836 ] Hudson commented on HBASE-12104: FAILURE: Integrated in HBase-1.0 #273 (See [https://builds.apache.org/job/HBase-1.0/273/]) HBASE-12104 Some optimization and bugfix for HTableMultiplexer (Yi Deng) (stack: rev 073ca6a5160d2343699a93d0b35c7a5d1e5e2a47) * hbase-client/src/main/java/org/apache/hadoop/hbase/client/HTableMultiplexer.java > Some optimization and bugfix for HTableMultiplexer > -- > > Key: HBASE-12104 > URL: https://issues.apache.org/jira/browse/HBASE-12104 > Project: HBase > Issue Type: Sub-task > Components: Client >Affects Versions: 2.0.0 >Reporter: Yi Deng >Assignee: Yi Deng > Labels: multiplexer > Fix For: 2.0.0 > > Attachments: > 0001-Make-HTableMultiplexerStatus-public-Delay-before-res.patch, > 0001-Make-HTableMultiplexerStatus-public-Delay-before-res.patch, > 0001-Make-HTableMultiplexerStatus-public-Delay-before-res.patch, > 0001-Make-HTableMultiplexerStatus-public.patch > > > Make HTableMultiplexerStatus public > Delay before resubmit. > Fix some missing counting on total failure. > Use ScheduledExecutorService to simplify the code. > Other refactoring. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (HBASE-12137) Alter table add cf doesn't do compression test
[ https://issues.apache.org/jira/browse/HBASE-12137?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14158838#comment-14158838 ] Hudson commented on HBASE-12137: FAILURE: Integrated in HBase-1.0 #273 (See [https://builds.apache.org/job/HBase-1.0/273/]) HBASE-12137 Alter table add cf doesn't do compression test (Virag Kothari) (tedyu: rev 23adb7a4f75b9710723c424686510eac361098d3) * hbase-server/src/main/java/org/apache/hadoop/hbase/master/HMaster.java > Alter table add cf doesn't do compression test > -- > > Key: HBASE-12137 > URL: https://issues.apache.org/jira/browse/HBASE-12137 > Project: HBase > Issue Type: Bug > Components: master >Affects Versions: 0.98.6 >Reporter: Virag Kothari >Assignee: Virag Kothari > Fix For: 2.0.0, 0.98.7, 0.99.1 > > Attachments: HBASE-12137-0.98.patch, HBASE-12137.patch, > HBASE-12137.patch > > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (HBASE-12166) TestDistributedLogSplitting.testMasterStartsUpWithLogReplayWork
[
https://issues.apache.org/jira/browse/HBASE-12166?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14158839#comment-14158839
]
Hudson commented on HBASE-12166:
FAILURE: Integrated in HBase-1.0 #273 (See
[https://builds.apache.org/job/HBase-1.0/273/])
HBASE-12166 TestDistributedLogSplitting.testMasterStartsUpWithLogReplayWork
(jxiang: rev 12fd6d2a2495533726d84759fd6cc754b5f7eb97)
*
hbase-server/src/main/java/org/apache/hadoop/hbase/coordination/ZKSplitLogManagerCoordination.java
> TestDistributedLogSplitting.testMasterStartsUpWithLogReplayWork
> ---
>
> Key: HBASE-12166
> URL: https://issues.apache.org/jira/browse/HBASE-12166
> Project: HBase
> Issue Type: Bug
> Components: test, wal
>Reporter: stack
>Assignee: Jimmy Xiang
> Fix For: 2.0.0, 0.99.1
>
> Attachments: 12166.txt, hbase-12166.patch, hbase-12166_v2.patch,
> log.txt
>
>
> See
> https://builds.apache.org/job/PreCommit-HBASE-Build/11204//testReport/org.apache.hadoop.hbase.master/TestDistributedLogSplitting/testMasterStartsUpWithLogReplayWork/
> The namespace region gets stuck. It is never 'recovered' even though we have
> finished log splitting. Here is the main exception:
> {code}
> 4941 2014-10-03 02:00:36,862 DEBUG
> [B.defaultRpcServer.handler=1,queue=0,port=37113] ipc.CallRunner(111):
> B.defaultRpcServer.handler=1,queue=0,port=37113: callId: 211 service:
> ClientService methodName: Get
> size: 99 connection: 67.195.81.144:44526
> 4942 org.apache.hadoop.hbase.exceptions.RegionInRecoveryException:
> hbase:namespace,,1412301462277.eba5d23de65f2718715eeb22edf7edc2. is recovering
> 4943 at
> org.apache.hadoop.hbase.regionserver.HRegion.startRegionOperation(HRegion.java:6058)
> 4944 at
> org.apache.hadoop.hbase.regionserver.HRegion.getScanner(HRegion.java:2086)
> 4945 at
> org.apache.hadoop.hbase.regionserver.HRegion.getScanner(HRegion.java:2072)
> 4946 at org.apache.hadoop.hbase.regionserver.HRegion.get(HRegion.java:5014)
> 4947 at org.apache.hadoop.hbase.regionserver.HRegion.get(HRegion.java:4988)
> 4948 at
> org.apache.hadoop.hbase.regionserver.RSRpcServices.get(RSRpcServices.java:1690)
> 4949 at
> org.apache.hadoop.hbase.protobuf.generated.ClientProtos$ClientService$2.callBlockingMethod(ClientProtos.java:30418)
> 4950 at org.apache.hadoop.hbase.ipc.RpcServer.call(RpcServer.java:2020)
> 4951 at org.apache.hadoop.hbase.ipc.CallRunner.run(CallRunner.java:108)
> 4952 at
> org.apache.hadoop.hbase.ipc.RpcExecutor.consumerLoop(RpcExecutor.java:114)
> 4953 at org.apache.hadoop.hbase.ipc.RpcExecutor$1.run(RpcExecutor.java:94)
> 4954 at java.lang.Thread.run(Thread.java:744)
> {code}
> See how we've finished log splitting long time previous:
> {code}
> 2014-10-03 01:57:48,129 INFO [M_LOG_REPLAY_OPS-asf900:37113-1]
> master.SplitLogManager(294): finished splitting (more than or equal to)
> 197337 bytes in 1 log files in
> [hdfs://localhost:49601/user/jenkins/hbase/WALs/asf900.gq1.ygridcore.net,40732,1412301461887-splitting]
> in 379ms
> {code}
> If I grep for the deleting of znodes on recovery, which is when we set the
> recovering flag to false, I see a bunch of regions but not my namespace one:
> 2014-10-03 01:57:47,330 INFO [Thread-9216-EventThread]
> zookeeper.RecoveringRegionWatcher(66): /hbase/recovering-regions/1588230740
> znode deleted. Region: 1588230740 completes recovery.
> 2014-10-03 01:57:48,119 INFO [Thread-9216-EventThread]
> zookeeper.RecoveringRegionWatcher(66):
> /hbase/recovering-regions/adfdcf958dd958f0e2ce59072ce2209d znode deleted.
> Region: adfdcf958dd958f0e2ce59072ce2209d completes recovery.
> 2014-10-03 01:57:48,121 INFO [Thread-9216-EventThread]
> zookeeper.RecoveringRegionWatcher(66):
> /hbase/recovering-regions/41d438848305831b61d708a406d5ecde znode deleted.
> Region: 41d438848305831b61d708a406d5ecde completes recovery.
> 2014-10-03 01:57:48,122 INFO [Thread-9216-EventThread]
> zookeeper.RecoveringRegionWatcher(66):
> /hbase/recovering-regions/6a7cada80de2ae5d774fe8cd33bd4cda znode deleted.
> Region: 6a7cada80de2ae5d774fe8cd33bd4cda completes recovery.
> 2014-10-03 01:57:48,124 INFO [Thread-9216-EventThread]
> zookeeper.RecoveringRegionWatcher(66):
> /hbase/recovering-regions/65451bd5b38bd16a31e25b62b3305533 znode deleted.
> Region: 65451bd5b38bd16a31e25b62b3305533 completes recovery.
> 2014-10-03 01:57:48,125 INFO [Thread-9216-EventThread]
> zookeeper.RecoveringRegionWatcher(66):
> /hbase/recovering-regions/07afdc3748894cf2b56e0075272a95a0 znode deleted.
> Region: 07afdc3748894cf2b56e0075272a95a0 completes recovery.
> 2014-10-03 01:57:48,126 INFO [Thread-9216-EventThread]
> zookeeper.RecoveringRegionWatcher(66):
> /hbase/recovering-regions/a4337ad2874ee7e599ca2344fce21583 znode deleted.
> Region: a433
[jira] [Commented] (HBASE-12126) Region server coprocessor endpoint
[
https://issues.apache.org/jira/browse/HBASE-12126?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14158825#comment-14158825
]
Gary Helmling commented on HBASE-12126:
---
This looks great, Virag.
I agree that adding {{SingletonCoprocessorService}} makes sense. My only
concern is that it leaves services intended to run on master
(CoprocessorService) inconsistent with similar services on regionservers
(SingletonCoprocessorService).
Can you open a new JIRA to bring master endpoints into consistency?
Unfortunately, this would be a compatibility breaking change for master
endpoints, so we'll need to work out the deprecation strategy. All of that can
be handled in the new JIRA.
+1 on the _1.patch.
> Region server coprocessor endpoint
> --
>
> Key: HBASE-12126
> URL: https://issues.apache.org/jira/browse/HBASE-12126
> Project: HBase
> Issue Type: Bug
> Components: Coprocessors
>Affects Versions: 0.98.6
>Reporter: Virag Kothari
>Assignee: Virag Kothari
> Attachments: HBASE-12126-0.98.patch, HBASE-12126-0.98_1.patch
>
>
> Utility to make endpoint calls against region server
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (HBASE-12167) NPE in AssignmentManager
[
https://issues.apache.org/jira/browse/HBASE-12167?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14158823#comment-14158823
]
Hudson commented on HBASE-12167:
SUCCESS: Integrated in HBase-1.0 #272 (See
[https://builds.apache.org/job/HBase-1.0/272/])
HBASE-12167 addendum; fix TestMasterObserver (jxiang: rev
51ef4185347b651d08a1abe9db74544b4113791a)
*
hbase-server/src/test/java/org/apache/hadoop/hbase/coprocessor/TestMasterObserver.java
> NPE in AssignmentManager
>
>
> Key: HBASE-12167
> URL: https://issues.apache.org/jira/browse/HBASE-12167
> Project: HBase
> Issue Type: Bug
>Reporter: Jimmy Xiang
>Assignee: Jimmy Xiang
> Fix For: 2.0.0, 0.99.1
>
> Attachments: hbase-12167.patch
>
>
> If we can't find a region plan, we should check.
> {noformat}
> 2014-10-02 18:36:27,719 ERROR [MASTER_SERVER_OPERATIONS-a2424:20020-0]
> executor.EventHandler: Caught throwable while processing event
> M_SERVER_SHUTDOWN
> java.lang.NullPointerException
> at
> org.apache.hadoop.hbase.master.AssignmentManager.assign(AssignmentManager.java:1417)
> at
> org.apache.hadoop.hbase.master.AssignmentManager.assign(AssignmentManager.java:1409)
> at
> org.apache.hadoop.hbase.master.handler.ServerShutdownHandler.process(ServerShutdownHandler.java:271)
> at
> org.apache.hadoop.hbase.executor.EventHandler.run(EventHandler.java:128)
> at
> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145)
> at
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)
> at java.lang.Thread.run(Thread.java:724)
> {noformat}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (HBASE-12137) Alter table add cf doesn't do compression test
[ https://issues.apache.org/jira/browse/HBASE-12137?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ted Yu updated HBASE-12137: --- Resolution: Fixed Hadoop Flags: Reviewed Status: Resolved (was: Patch Available) Integrated to 3 branches. Thanks for the patch, Virag. > Alter table add cf doesn't do compression test > -- > > Key: HBASE-12137 > URL: https://issues.apache.org/jira/browse/HBASE-12137 > Project: HBase > Issue Type: Bug > Components: master >Affects Versions: 0.98.6 >Reporter: Virag Kothari >Assignee: Virag Kothari > Fix For: 2.0.0, 0.98.7, 0.99.1 > > Attachments: HBASE-12137-0.98.patch, HBASE-12137.patch, > HBASE-12137.patch > > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (HBASE-12104) Some optimization and bugfix for HTableMultiplexer
[ https://issues.apache.org/jira/browse/HBASE-12104?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14158806#comment-14158806 ] Yi Deng commented on HBASE-12104: - Thanks for the push. [~stack] > Some optimization and bugfix for HTableMultiplexer > -- > > Key: HBASE-12104 > URL: https://issues.apache.org/jira/browse/HBASE-12104 > Project: HBase > Issue Type: Sub-task > Components: Client >Affects Versions: 2.0.0 >Reporter: Yi Deng >Assignee: Yi Deng > Labels: multiplexer > Fix For: 2.0.0 > > Attachments: > 0001-Make-HTableMultiplexerStatus-public-Delay-before-res.patch, > 0001-Make-HTableMultiplexerStatus-public-Delay-before-res.patch, > 0001-Make-HTableMultiplexerStatus-public-Delay-before-res.patch, > 0001-Make-HTableMultiplexerStatus-public.patch > > > Make HTableMultiplexerStatus public > Delay before resubmit. > Fix some missing counting on total failure. > Use ScheduledExecutorService to simplify the code. > Other refactoring. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (HBASE-12166) TestDistributedLogSplitting.testMasterStartsUpWithLogReplayWork
[
https://issues.apache.org/jira/browse/HBASE-12166?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jimmy Xiang updated HBASE-12166:
Resolution: Fixed
Hadoop Flags: Reviewed
Status: Resolved (was: Patch Available)
Integrated into branch 1 and master. Thanks.
> TestDistributedLogSplitting.testMasterStartsUpWithLogReplayWork
> ---
>
> Key: HBASE-12166
> URL: https://issues.apache.org/jira/browse/HBASE-12166
> Project: HBase
> Issue Type: Bug
> Components: test, wal
>Reporter: stack
>Assignee: Jimmy Xiang
> Fix For: 2.0.0, 0.99.1
>
> Attachments: 12166.txt, hbase-12166.patch, hbase-12166_v2.patch,
> log.txt
>
>
> See
> https://builds.apache.org/job/PreCommit-HBASE-Build/11204//testReport/org.apache.hadoop.hbase.master/TestDistributedLogSplitting/testMasterStartsUpWithLogReplayWork/
> The namespace region gets stuck. It is never 'recovered' even though we have
> finished log splitting. Here is the main exception:
> {code}
> 4941 2014-10-03 02:00:36,862 DEBUG
> [B.defaultRpcServer.handler=1,queue=0,port=37113] ipc.CallRunner(111):
> B.defaultRpcServer.handler=1,queue=0,port=37113: callId: 211 service:
> ClientService methodName: Get
> size: 99 connection: 67.195.81.144:44526
> 4942 org.apache.hadoop.hbase.exceptions.RegionInRecoveryException:
> hbase:namespace,,1412301462277.eba5d23de65f2718715eeb22edf7edc2. is recovering
> 4943 at
> org.apache.hadoop.hbase.regionserver.HRegion.startRegionOperation(HRegion.java:6058)
> 4944 at
> org.apache.hadoop.hbase.regionserver.HRegion.getScanner(HRegion.java:2086)
> 4945 at
> org.apache.hadoop.hbase.regionserver.HRegion.getScanner(HRegion.java:2072)
> 4946 at org.apache.hadoop.hbase.regionserver.HRegion.get(HRegion.java:5014)
> 4947 at org.apache.hadoop.hbase.regionserver.HRegion.get(HRegion.java:4988)
> 4948 at
> org.apache.hadoop.hbase.regionserver.RSRpcServices.get(RSRpcServices.java:1690)
> 4949 at
> org.apache.hadoop.hbase.protobuf.generated.ClientProtos$ClientService$2.callBlockingMethod(ClientProtos.java:30418)
> 4950 at org.apache.hadoop.hbase.ipc.RpcServer.call(RpcServer.java:2020)
> 4951 at org.apache.hadoop.hbase.ipc.CallRunner.run(CallRunner.java:108)
> 4952 at
> org.apache.hadoop.hbase.ipc.RpcExecutor.consumerLoop(RpcExecutor.java:114)
> 4953 at org.apache.hadoop.hbase.ipc.RpcExecutor$1.run(RpcExecutor.java:94)
> 4954 at java.lang.Thread.run(Thread.java:744)
> {code}
> See how we've finished log splitting long time previous:
> {code}
> 2014-10-03 01:57:48,129 INFO [M_LOG_REPLAY_OPS-asf900:37113-1]
> master.SplitLogManager(294): finished splitting (more than or equal to)
> 197337 bytes in 1 log files in
> [hdfs://localhost:49601/user/jenkins/hbase/WALs/asf900.gq1.ygridcore.net,40732,1412301461887-splitting]
> in 379ms
> {code}
> If I grep for the deleting of znodes on recovery, which is when we set the
> recovering flag to false, I see a bunch of regions but not my namespace one:
> 2014-10-03 01:57:47,330 INFO [Thread-9216-EventThread]
> zookeeper.RecoveringRegionWatcher(66): /hbase/recovering-regions/1588230740
> znode deleted. Region: 1588230740 completes recovery.
> 2014-10-03 01:57:48,119 INFO [Thread-9216-EventThread]
> zookeeper.RecoveringRegionWatcher(66):
> /hbase/recovering-regions/adfdcf958dd958f0e2ce59072ce2209d znode deleted.
> Region: adfdcf958dd958f0e2ce59072ce2209d completes recovery.
> 2014-10-03 01:57:48,121 INFO [Thread-9216-EventThread]
> zookeeper.RecoveringRegionWatcher(66):
> /hbase/recovering-regions/41d438848305831b61d708a406d5ecde znode deleted.
> Region: 41d438848305831b61d708a406d5ecde completes recovery.
> 2014-10-03 01:57:48,122 INFO [Thread-9216-EventThread]
> zookeeper.RecoveringRegionWatcher(66):
> /hbase/recovering-regions/6a7cada80de2ae5d774fe8cd33bd4cda znode deleted.
> Region: 6a7cada80de2ae5d774fe8cd33bd4cda completes recovery.
> 2014-10-03 01:57:48,124 INFO [Thread-9216-EventThread]
> zookeeper.RecoveringRegionWatcher(66):
> /hbase/recovering-regions/65451bd5b38bd16a31e25b62b3305533 znode deleted.
> Region: 65451bd5b38bd16a31e25b62b3305533 completes recovery.
> 2014-10-03 01:57:48,125 INFO [Thread-9216-EventThread]
> zookeeper.RecoveringRegionWatcher(66):
> /hbase/recovering-regions/07afdc3748894cf2b56e0075272a95a0 znode deleted.
> Region: 07afdc3748894cf2b56e0075272a95a0 completes recovery.
> 2014-10-03 01:57:48,126 INFO [Thread-9216-EventThread]
> zookeeper.RecoveringRegionWatcher(66):
> /hbase/recovering-regions/a4337ad2874ee7e599ca2344fce21583 znode deleted.
> Region: a4337ad2874ee7e599ca2344fce21583 completes recovery.
> 2014-10-03 01:57:48,128 INFO [Thread-9216-EventThread]
> zookeeper.RecoveringRegionWatcher(66):
> /hbase/recovering-regions/9d91d6eafe260ce33e8d7d23ccd13192 znode deleted.
[jira] [Updated] (HBASE-12104) Some optimization and bugfix for HTableMultiplexer
[ https://issues.apache.org/jira/browse/HBASE-12104?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] stack updated HBASE-12104: -- Resolution: Fixed Hadoop Flags: Reviewed Status: Resolved (was: Patch Available) Pushed to branch-1+ Thanks for the patch [~daviddengcn] > Some optimization and bugfix for HTableMultiplexer > -- > > Key: HBASE-12104 > URL: https://issues.apache.org/jira/browse/HBASE-12104 > Project: HBase > Issue Type: Sub-task > Components: Client >Affects Versions: 2.0.0 >Reporter: Yi Deng >Assignee: Yi Deng > Labels: multiplexer > Fix For: 2.0.0 > > Attachments: > 0001-Make-HTableMultiplexerStatus-public-Delay-before-res.patch, > 0001-Make-HTableMultiplexerStatus-public-Delay-before-res.patch, > 0001-Make-HTableMultiplexerStatus-public-Delay-before-res.patch, > 0001-Make-HTableMultiplexerStatus-public.patch > > > Make HTableMultiplexerStatus public > Delay before resubmit. > Fix some missing counting on total failure. > Use ScheduledExecutorService to simplify the code. > Other refactoring. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (HBASE-12156) TableName cache isn't used for one of valueOf methods.
[ https://issues.apache.org/jira/browse/HBASE-12156?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14158784#comment-14158784 ] Hudson commented on HBASE-12156: FAILURE: Integrated in HBase-0.98-on-Hadoop-1.1 #540 (See [https://builds.apache.org/job/HBase-0.98-on-Hadoop-1.1/540/]) Amend HBASE-12156 TableName cache isn't used for one of valueOf methods; make TestTableName a medium test (apurtell: rev 4bd09d13588f527d6a68af3b6abb481f9432cfdd) * hbase-server/src/test/java/org/apache/hadoop/hbase/util/TestTableName.java > TableName cache isn't used for one of valueOf methods. > -- > > Key: HBASE-12156 > URL: https://issues.apache.org/jira/browse/HBASE-12156 > Project: HBase > Issue Type: Bug >Reporter: Andrey Stepachev >Assignee: Andrey Stepachev > Fix For: 2.0.0, 0.98.7, 0.99.1 > > Attachments: HBASE-12156-addendum-0.98.patch, > HBASE-12156-addendum-2.branch-1.patch, HBASE-12156-addendum-2.patch, > HBASE-12156.patch > > > there is wrong comparison, copy&paste code compares namespace with qualifier > and namespace. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (HBASE-12146) RegionServerTracker should escape data in log messages
[ https://issues.apache.org/jira/browse/HBASE-12146?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14158782#comment-14158782 ] Lars Hofhansl commented on HBASE-12146: --- +1 > RegionServerTracker should escape data in log messages > -- > > Key: HBASE-12146 > URL: https://issues.apache.org/jira/browse/HBASE-12146 > Project: HBase > Issue Type: Bug >Reporter: Lars Hofhansl >Assignee: stack >Priority: Trivial > Fix For: 2.0.0, 0.99.1 > > Attachments: 12146.txt > > > Trivial thing I observed when testing 0.94.24RC2. > I see a log message of the form: > 2014-10-01 13:52:35,632 INFO > org.apache.hadoop.hbase.zookeeper.RegionServerTracker: Rs node: > /hbase/rs/newbunny,52514,1412196754788 data: PBUο^C > Obviously the tracker does not escape the value (or maybe it shouldn't log it > in the fist place) -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (HBASE-11764) Support per cell TTLs
[
https://issues.apache.org/jira/browse/HBASE-11764?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14158761#comment-14158761
]
Hadoop QA commented on HBASE-11764:
---
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12672878/HBASE-11764.patch
against trunk revision .
ATTACHMENT ID: 12672878
{color:green}+1 @author{color}. The patch does not contain any @author
tags.
{color:green}+1 tests included{color}. The patch appears to include 9 new
or modified tests.
{color:green}+1 javac{color}. The applied patch does not increase the
total number of javac compiler warnings.
{color:green}+1 javac{color}. The applied patch does not increase the
total number of javac compiler warnings.
{color:green}+1 javadoc{color}. The javadoc tool did not generate any
warning messages.
{color:green}+1 findbugs{color}. The patch does not introduce any new
Findbugs (version 2.0.3) warnings.
{color:green}+1 release audit{color}. The applied patch does not increase
the total number of release audit warnings.
{color:red}-1 lineLengths{color}. The patch introduces the following lines
longer than 100:
+ Iterator tagIterator =
CellUtil.tagsIterator(cell.getTagsArray(), cell.getTagsOffset(),
+updatedCells.add(new KeyValue(cell.getRowArray(),
cell.getRowOffset(), cell.getRowLength(),
+ Iterator i =
CellUtil.tagsIterator(cell.getTagsArray(), cell.getTagsOffset(),
+if (t.getType() == TagType.TTL_TAG_TYPE &&
increment.getTTL() != Long.MAX_VALUE) {
+ long readPointToUse, long earliestPutTs, long oldestUnexpiredTS, long
now, byte[] dropDeletesFromRow,
{color:green}+1 site{color}. The mvn site goal succeeds with this patch.
{color:red}-1 core tests{color}. The patch failed these unit tests:
Test results:
https://builds.apache.org/job/PreCommit-HBASE-Build/11215//testReport/
Findbugs warnings:
https://builds.apache.org/job/PreCommit-HBASE-Build/11215//artifact/patchprocess/newPatchFindbugsWarningshbase-client.html
Findbugs warnings:
https://builds.apache.org/job/PreCommit-HBASE-Build/11215//artifact/patchprocess/newPatchFindbugsWarningshbase-examples.html
Findbugs warnings:
https://builds.apache.org/job/PreCommit-HBASE-Build/11215//artifact/patchprocess/newPatchFindbugsWarningshbase-protocol.html
Findbugs warnings:
https://builds.apache.org/job/PreCommit-HBASE-Build/11215//artifact/patchprocess/newPatchFindbugsWarningshbase-common.html
Findbugs warnings:
https://builds.apache.org/job/PreCommit-HBASE-Build/11215//artifact/patchprocess/newPatchFindbugsWarningshbase-server.html
Findbugs warnings:
https://builds.apache.org/job/PreCommit-HBASE-Build/11215//artifact/patchprocess/newPatchFindbugsWarningshbase-thrift.html
Findbugs warnings:
https://builds.apache.org/job/PreCommit-HBASE-Build/11215//artifact/patchprocess/newPatchFindbugsWarningshbase-hadoop-compat.html
Findbugs warnings:
https://builds.apache.org/job/PreCommit-HBASE-Build/11215//artifact/patchprocess/newPatchFindbugsWarningshbase-prefix-tree.html
Findbugs warnings:
https://builds.apache.org/job/PreCommit-HBASE-Build/11215//artifact/patchprocess/newPatchFindbugsWarningshbase-hadoop2-compat.html
Findbugs warnings:
https://builds.apache.org/job/PreCommit-HBASE-Build/11215//artifact/patchprocess/newPatchFindbugsWarningshbase-annotations.html
Console output:
https://builds.apache.org/job/PreCommit-HBASE-Build/11215//console
This message is automatically generated.
> Support per cell TTLs
> -
>
> Key: HBASE-11764
> URL: https://issues.apache.org/jira/browse/HBASE-11764
> Project: HBase
> Issue Type: Sub-task
>Reporter: Andrew Purtell
>Assignee: Andrew Purtell
> Fix For: 2.0.0, 0.98.7, 0.99.1
>
> Attachments: HBASE-11764-0.98.patch, HBASE-11764-0.98.patch,
> HBASE-11764-0.98.patch, HBASE-11764.patch, HBASE-11764.patch,
> HBASE-11764.patch, HBASE-11764.patch, HBASE-11764.patch, HBASE-11764.patch,
> HBASE-11764.patch, HBASE-11764.patch, HBASE-11764.patch, HBASE-11764.patch
>
>
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (HBASE-12166) TestDistributedLogSplitting.testMasterStartsUpWithLogReplayWork
[
https://issues.apache.org/jira/browse/HBASE-12166?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14158762#comment-14158762
]
stack commented on HBASE-12166:
---
+1
> TestDistributedLogSplitting.testMasterStartsUpWithLogReplayWork
> ---
>
> Key: HBASE-12166
> URL: https://issues.apache.org/jira/browse/HBASE-12166
> Project: HBase
> Issue Type: Bug
> Components: test, wal
>Reporter: stack
>Assignee: Jimmy Xiang
> Fix For: 2.0.0, 0.99.1
>
> Attachments: 12166.txt, hbase-12166.patch, hbase-12166_v2.patch,
> log.txt
>
>
> See
> https://builds.apache.org/job/PreCommit-HBASE-Build/11204//testReport/org.apache.hadoop.hbase.master/TestDistributedLogSplitting/testMasterStartsUpWithLogReplayWork/
> The namespace region gets stuck. It is never 'recovered' even though we have
> finished log splitting. Here is the main exception:
> {code}
> 4941 2014-10-03 02:00:36,862 DEBUG
> [B.defaultRpcServer.handler=1,queue=0,port=37113] ipc.CallRunner(111):
> B.defaultRpcServer.handler=1,queue=0,port=37113: callId: 211 service:
> ClientService methodName: Get
> size: 99 connection: 67.195.81.144:44526
> 4942 org.apache.hadoop.hbase.exceptions.RegionInRecoveryException:
> hbase:namespace,,1412301462277.eba5d23de65f2718715eeb22edf7edc2. is recovering
> 4943 at
> org.apache.hadoop.hbase.regionserver.HRegion.startRegionOperation(HRegion.java:6058)
> 4944 at
> org.apache.hadoop.hbase.regionserver.HRegion.getScanner(HRegion.java:2086)
> 4945 at
> org.apache.hadoop.hbase.regionserver.HRegion.getScanner(HRegion.java:2072)
> 4946 at org.apache.hadoop.hbase.regionserver.HRegion.get(HRegion.java:5014)
> 4947 at org.apache.hadoop.hbase.regionserver.HRegion.get(HRegion.java:4988)
> 4948 at
> org.apache.hadoop.hbase.regionserver.RSRpcServices.get(RSRpcServices.java:1690)
> 4949 at
> org.apache.hadoop.hbase.protobuf.generated.ClientProtos$ClientService$2.callBlockingMethod(ClientProtos.java:30418)
> 4950 at org.apache.hadoop.hbase.ipc.RpcServer.call(RpcServer.java:2020)
> 4951 at org.apache.hadoop.hbase.ipc.CallRunner.run(CallRunner.java:108)
> 4952 at
> org.apache.hadoop.hbase.ipc.RpcExecutor.consumerLoop(RpcExecutor.java:114)
> 4953 at org.apache.hadoop.hbase.ipc.RpcExecutor$1.run(RpcExecutor.java:94)
> 4954 at java.lang.Thread.run(Thread.java:744)
> {code}
> See how we've finished log splitting long time previous:
> {code}
> 2014-10-03 01:57:48,129 INFO [M_LOG_REPLAY_OPS-asf900:37113-1]
> master.SplitLogManager(294): finished splitting (more than or equal to)
> 197337 bytes in 1 log files in
> [hdfs://localhost:49601/user/jenkins/hbase/WALs/asf900.gq1.ygridcore.net,40732,1412301461887-splitting]
> in 379ms
> {code}
> If I grep for the deleting of znodes on recovery, which is when we set the
> recovering flag to false, I see a bunch of regions but not my namespace one:
> 2014-10-03 01:57:47,330 INFO [Thread-9216-EventThread]
> zookeeper.RecoveringRegionWatcher(66): /hbase/recovering-regions/1588230740
> znode deleted. Region: 1588230740 completes recovery.
> 2014-10-03 01:57:48,119 INFO [Thread-9216-EventThread]
> zookeeper.RecoveringRegionWatcher(66):
> /hbase/recovering-regions/adfdcf958dd958f0e2ce59072ce2209d znode deleted.
> Region: adfdcf958dd958f0e2ce59072ce2209d completes recovery.
> 2014-10-03 01:57:48,121 INFO [Thread-9216-EventThread]
> zookeeper.RecoveringRegionWatcher(66):
> /hbase/recovering-regions/41d438848305831b61d708a406d5ecde znode deleted.
> Region: 41d438848305831b61d708a406d5ecde completes recovery.
> 2014-10-03 01:57:48,122 INFO [Thread-9216-EventThread]
> zookeeper.RecoveringRegionWatcher(66):
> /hbase/recovering-regions/6a7cada80de2ae5d774fe8cd33bd4cda znode deleted.
> Region: 6a7cada80de2ae5d774fe8cd33bd4cda completes recovery.
> 2014-10-03 01:57:48,124 INFO [Thread-9216-EventThread]
> zookeeper.RecoveringRegionWatcher(66):
> /hbase/recovering-regions/65451bd5b38bd16a31e25b62b3305533 znode deleted.
> Region: 65451bd5b38bd16a31e25b62b3305533 completes recovery.
> 2014-10-03 01:57:48,125 INFO [Thread-9216-EventThread]
> zookeeper.RecoveringRegionWatcher(66):
> /hbase/recovering-regions/07afdc3748894cf2b56e0075272a95a0 znode deleted.
> Region: 07afdc3748894cf2b56e0075272a95a0 completes recovery.
> 2014-10-03 01:57:48,126 INFO [Thread-9216-EventThread]
> zookeeper.RecoveringRegionWatcher(66):
> /hbase/recovering-regions/a4337ad2874ee7e599ca2344fce21583 znode deleted.
> Region: a4337ad2874ee7e599ca2344fce21583 completes recovery.
> 2014-10-03 01:57:48,128 INFO [Thread-9216-EventThread]
> zookeeper.RecoveringRegionWatcher(66):
> /hbase/recovering-regions/9d91d6eafe260ce33e8d7d23ccd13192 znode deleted.
> Region: 9d91d6eafe260ce33e8d7d23ccd13192 completes recovery.
> This would seem to indicate that w
[jira] [Commented] (HBASE-12166) TestDistributedLogSplitting.testMasterStartsUpWithLogReplayWork
[
https://issues.apache.org/jira/browse/HBASE-12166?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14158760#comment-14158760
]
Hadoop QA commented on HBASE-12166:
---
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12672876/hbase-12166_v2.patch
against trunk revision .
ATTACHMENT ID: 12672876
{color:green}+1 @author{color}. The patch does not contain any @author
tags.
{color:green}+1 tests included{color}. The patch appears to include 3 new
or modified tests.
{color:green}+1 javac{color}. The applied patch does not increase the
total number of javac compiler warnings.
{color:green}+1 javac{color}. The applied patch does not increase the
total number of javac compiler warnings.
{color:green}+1 javadoc{color}. The javadoc tool did not generate any
warning messages.
{color:green}+1 findbugs{color}. The patch does not introduce any new
Findbugs (version 2.0.3) warnings.
{color:green}+1 release audit{color}. The applied patch does not increase
the total number of release audit warnings.
{color:green}+1 lineLengths{color}. The patch does not introduce lines
longer than 100
{color:green}+1 site{color}. The mvn site goal succeeds with this patch.
{color:red}-1 core tests{color}. The patch failed these unit tests:
{color:red}-1 core zombie tests{color}. There are 2 zombie test(s):
at
org.apache.hadoop.hbase.io.crypto.TestCipherProvider.testCustomProvider(TestCipherProvider.java:132)
at
org.apache.karaf.main.MainStartTest.testStopWithTimeout(MainStartTest.java:94)
Test results:
https://builds.apache.org/job/PreCommit-HBASE-Build/11214//testReport/
Findbugs warnings:
https://builds.apache.org/job/PreCommit-HBASE-Build/11214//artifact/patchprocess/newPatchFindbugsWarningshbase-client.html
Findbugs warnings:
https://builds.apache.org/job/PreCommit-HBASE-Build/11214//artifact/patchprocess/newPatchFindbugsWarningshbase-examples.html
Findbugs warnings:
https://builds.apache.org/job/PreCommit-HBASE-Build/11214//artifact/patchprocess/newPatchFindbugsWarningshbase-protocol.html
Findbugs warnings:
https://builds.apache.org/job/PreCommit-HBASE-Build/11214//artifact/patchprocess/newPatchFindbugsWarningshbase-common.html
Findbugs warnings:
https://builds.apache.org/job/PreCommit-HBASE-Build/11214//artifact/patchprocess/newPatchFindbugsWarningshbase-server.html
Findbugs warnings:
https://builds.apache.org/job/PreCommit-HBASE-Build/11214//artifact/patchprocess/newPatchFindbugsWarningshbase-thrift.html
Findbugs warnings:
https://builds.apache.org/job/PreCommit-HBASE-Build/11214//artifact/patchprocess/newPatchFindbugsWarningshbase-hadoop-compat.html
Findbugs warnings:
https://builds.apache.org/job/PreCommit-HBASE-Build/11214//artifact/patchprocess/newPatchFindbugsWarningshbase-prefix-tree.html
Findbugs warnings:
https://builds.apache.org/job/PreCommit-HBASE-Build/11214//artifact/patchprocess/newPatchFindbugsWarningshbase-hadoop2-compat.html
Findbugs warnings:
https://builds.apache.org/job/PreCommit-HBASE-Build/11214//artifact/patchprocess/newPatchFindbugsWarningshbase-annotations.html
Console output:
https://builds.apache.org/job/PreCommit-HBASE-Build/11214//console
This message is automatically generated.
> TestDistributedLogSplitting.testMasterStartsUpWithLogReplayWork
> ---
>
> Key: HBASE-12166
> URL: https://issues.apache.org/jira/browse/HBASE-12166
> Project: HBase
> Issue Type: Bug
> Components: test, wal
>Reporter: stack
>Assignee: Jimmy Xiang
> Fix For: 2.0.0, 0.99.1
>
> Attachments: 12166.txt, hbase-12166.patch, hbase-12166_v2.patch,
> log.txt
>
>
> See
> https://builds.apache.org/job/PreCommit-HBASE-Build/11204//testReport/org.apache.hadoop.hbase.master/TestDistributedLogSplitting/testMasterStartsUpWithLogReplayWork/
> The namespace region gets stuck. It is never 'recovered' even though we have
> finished log splitting. Here is the main exception:
> {code}
> 4941 2014-10-03 02:00:36,862 DEBUG
> [B.defaultRpcServer.handler=1,queue=0,port=37113] ipc.CallRunner(111):
> B.defaultRpcServer.handler=1,queue=0,port=37113: callId: 211 service:
> ClientService methodName: Get
> size: 99 connection: 67.195.81.144:44526
> 4942 org.apache.hadoop.hbase.exceptions.RegionInRecoveryException:
> hbase:namespace,,1412301462277.eba5d23de65f2718715eeb22edf7edc2. is recovering
> 4943 at
> org.apache.hadoop.hbase.regionserver.HRegion.startRegionOperation(HRegion.java:6058)
> 4944 at
> org.apache.hadoop.hbase.regionserver.HRegion.getScanner(HRegion.java:2086)
> 4945 at
> org.apache.hadoop.hbase.regionserver.HRegion.getScanner(HRegion.java:2072)
> 4946 at org.apache.hadoop.hbas
[jira] [Commented] (HBASE-12170) TestReplicaWithCluster.testReplicaAndReplication timeouts
[
https://issues.apache.org/jira/browse/HBASE-12170?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14158758#comment-14158758
]
stack commented on HBASE-12170:
---
Applied the patch to branch-1+
- @Test (timeout=12)
+ @Test (timeout=30)
Leaving open in case this does not fix.
> TestReplicaWithCluster.testReplicaAndReplication timeouts
> -
>
> Key: HBASE-12170
> URL: https://issues.apache.org/jira/browse/HBASE-12170
> Project: HBase
> Issue Type: Bug
> Components: test
>Reporter: stack
>Assignee: stack
> Fix For: 2.0.0, 0.99.1
>
> Attachments: to.txt
>
>
> On our internal rig I got a timeout. Looking over the test, it looks to be
> making progress if slow. The test does a crazy amount of stuff too... so let
> me just up the timeout for now.
> {code}
> org.apache.hadoop.hbase.client.TestReplicaWithCluster.testReplicaAndReplication
> Failing for the past 1 build (Since Unstable#10 )
> Took 0.42 sec.
> Error Message
> test timed out after 12 milliseconds
> Stacktrace
> java.lang.Exception: test timed out after 12 milliseconds
> at java.lang.Thread.sleep(Native Method)
> at
> org.apache.hadoop.hbase.client.HBaseAdmin.disableTable(HBaseAdmin.java:999)
> at
> org.apache.hadoop.hbase.client.TestReplicaWithCluster.testReplicaAndReplication(TestReplicaWithCluster.java:302)
> 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:606)
> at
> org.junit.runners.model.FrameworkMethod$1.runReflectiveCall(FrameworkMethod.java:47)
> at
> org.junit.internal.runners.model.ReflectiveCallable.run(ReflectiveCallable.java:12)
> at
> org.junit.runners.model.FrameworkMethod.invokeExplosively(FrameworkMethod.java:44)
> at
> org.junit.internal.runners.statements.InvokeMethod.evaluate(InvokeMethod.java:17)
> at
> org.junit.internal.runners.statements.FailOnTimeout$StatementThread.run(FailOnTimeout.java:74)
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (HBASE-12136) Race condition between client adding tableCF replication znode and server triggering TableCFsTracker
[ https://issues.apache.org/jira/browse/HBASE-12136?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14158757#comment-14158757 ] Hudson commented on HBASE-12136: FAILURE: Integrated in HBase-0.98 #568 (See [https://builds.apache.org/job/HBase-0.98/568/]) HBASE-12136 Race condition between client adding tableCF replication znode and server triggering TableCFsTracker (Virag Kothari) (tedyu: rev a9138d7f96910f09e52b226248ccb169c98d6bd4) * hbase-client/src/main/java/org/apache/hadoop/hbase/replication/ReplicationPeersZKImpl.java > Race condition between client adding tableCF replication znode and server > triggering TableCFsTracker > - > > Key: HBASE-12136 > URL: https://issues.apache.org/jira/browse/HBASE-12136 > Project: HBase > Issue Type: Bug > Components: Replication >Affects Versions: 0.98.6 >Reporter: Virag Kothari >Assignee: Virag Kothari > Fix For: 2.0.0, 0.98.7, 0.99.1 > > Attachments: HBASE-12136-0.98.patch, HBASE-12136.patch > > > In ReplicationPeersZKImpl.addPeer(), there is a race between client creating > tableCf znode and the server triggering TableCFsTracker. If the server wins, > it wont be able to read the data set on tableCF znode and replication will > be misconfigured -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (HBASE-12170) TestReplicaWithCluster.testReplicaAndReplication timeouts
[
https://issues.apache.org/jira/browse/HBASE-12170?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
stack updated HBASE-12170:
--
Attachment: to.txt
Just up the timeout from 2mins to 5.
> TestReplicaWithCluster.testReplicaAndReplication timeouts
> -
>
> Key: HBASE-12170
> URL: https://issues.apache.org/jira/browse/HBASE-12170
> Project: HBase
> Issue Type: Bug
> Components: test
>Reporter: stack
>Assignee: stack
> Fix For: 2.0.0, 0.99.1
>
> Attachments: to.txt
>
>
> On our internal rig I got a timeout. Looking over the test, it looks to be
> making progress if slow. The test does a crazy amount of stuff too... so let
> me just up the timeout for now.
> {code}
> org.apache.hadoop.hbase.client.TestReplicaWithCluster.testReplicaAndReplication
> Failing for the past 1 build (Since Unstable#10 )
> Took 0.42 sec.
> Error Message
> test timed out after 12 milliseconds
> Stacktrace
> java.lang.Exception: test timed out after 12 milliseconds
> at java.lang.Thread.sleep(Native Method)
> at
> org.apache.hadoop.hbase.client.HBaseAdmin.disableTable(HBaseAdmin.java:999)
> at
> org.apache.hadoop.hbase.client.TestReplicaWithCluster.testReplicaAndReplication(TestReplicaWithCluster.java:302)
> 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:606)
> at
> org.junit.runners.model.FrameworkMethod$1.runReflectiveCall(FrameworkMethod.java:47)
> at
> org.junit.internal.runners.model.ReflectiveCallable.run(ReflectiveCallable.java:12)
> at
> org.junit.runners.model.FrameworkMethod.invokeExplosively(FrameworkMethod.java:44)
> at
> org.junit.internal.runners.statements.InvokeMethod.evaluate(InvokeMethod.java:17)
> at
> org.junit.internal.runners.statements.FailOnTimeout$StatementThread.run(FailOnTimeout.java:74)
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Created] (HBASE-12170) TestReplicaWithCluster.testReplicaAndReplication timeouts
stack created HBASE-12170:
-
Summary: TestReplicaWithCluster.testReplicaAndReplication timeouts
Key: HBASE-12170
URL: https://issues.apache.org/jira/browse/HBASE-12170
Project: HBase
Issue Type: Bug
Components: test
Reporter: stack
Assignee: stack
Fix For: 2.0.0, 0.99.1
On our internal rig I got a timeout. Looking over the test, it looks to be
making progress if slow. The test does a crazy amount of stuff too... so let
me just up the timeout for now.
{code}
org.apache.hadoop.hbase.client.TestReplicaWithCluster.testReplicaAndReplication
Failing for the past 1 build (Since Unstable#10 )
Took 0.42 sec.
Error Message
test timed out after 12 milliseconds
Stacktrace
java.lang.Exception: test timed out after 12 milliseconds
at java.lang.Thread.sleep(Native Method)
at
org.apache.hadoop.hbase.client.HBaseAdmin.disableTable(HBaseAdmin.java:999)
at
org.apache.hadoop.hbase.client.TestReplicaWithCluster.testReplicaAndReplication(TestReplicaWithCluster.java:302)
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:606)
at
org.junit.runners.model.FrameworkMethod$1.runReflectiveCall(FrameworkMethod.java:47)
at
org.junit.internal.runners.model.ReflectiveCallable.run(ReflectiveCallable.java:12)
at
org.junit.runners.model.FrameworkMethod.invokeExplosively(FrameworkMethod.java:44)
at
org.junit.internal.runners.statements.InvokeMethod.evaluate(InvokeMethod.java:17)
at
org.junit.internal.runners.statements.FailOnTimeout$StatementThread.run(FailOnTimeout.java:74)
{code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Resolved] (HBASE-12156) TableName cache isn't used for one of valueOf methods.
[ https://issues.apache.org/jira/browse/HBASE-12156?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrew Purtell resolved HBASE-12156. Resolution: Fixed Pushed addendum 2 to 0.98+ > TableName cache isn't used for one of valueOf methods. > -- > > Key: HBASE-12156 > URL: https://issues.apache.org/jira/browse/HBASE-12156 > Project: HBase > Issue Type: Bug >Reporter: Andrey Stepachev >Assignee: Andrey Stepachev > Fix For: 2.0.0, 0.98.7, 0.99.1 > > Attachments: HBASE-12156-addendum-0.98.patch, > HBASE-12156-addendum-2.branch-1.patch, HBASE-12156-addendum-2.patch, > HBASE-12156.patch > > > there is wrong comparison, copy&paste code compares namespace with qualifier > and namespace. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (HBASE-12156) TableName cache isn't used for one of valueOf methods.
[ https://issues.apache.org/jira/browse/HBASE-12156?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrew Purtell updated HBASE-12156: --- Attachment: HBASE-12156-addendum-2.patch HBASE-12156-addendum-2.branch-1.patch The addendum for branch-1 and 0.98 is the same > TableName cache isn't used for one of valueOf methods. > -- > > Key: HBASE-12156 > URL: https://issues.apache.org/jira/browse/HBASE-12156 > Project: HBase > Issue Type: Bug >Reporter: Andrey Stepachev >Assignee: Andrey Stepachev > Fix For: 2.0.0, 0.98.7, 0.99.1 > > Attachments: HBASE-12156-addendum-0.98.patch, > HBASE-12156-addendum-2.branch-1.patch, HBASE-12156-addendum-2.patch, > HBASE-12156.patch > > > there is wrong comparison, copy&paste code compares namespace with qualifier > and namespace. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (HBASE-12156) TableName cache isn't used for one of valueOf methods.
[ https://issues.apache.org/jira/browse/HBASE-12156?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14158744#comment-14158744 ] stack commented on HBASE-12156: --- Thanks [~apurtell] and I like [~mbertozzi] suggestion > TableName cache isn't used for one of valueOf methods. > -- > > Key: HBASE-12156 > URL: https://issues.apache.org/jira/browse/HBASE-12156 > Project: HBase > Issue Type: Bug >Reporter: Andrey Stepachev >Assignee: Andrey Stepachev > Fix For: 2.0.0, 0.98.7, 0.99.1 > > Attachments: HBASE-12156-addendum-0.98.patch, HBASE-12156.patch > > > there is wrong comparison, copy&paste code compares namespace with qualifier > and namespace. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (HBASE-12156) TableName cache isn't used for one of valueOf methods.
[
https://issues.apache.org/jira/browse/HBASE-12156?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14158742#comment-14158742
]
Andrew Purtell commented on HBASE-12156:
I'm going to commit an addendum to 0.98+ shortly that does the equivalent of:
{code}
--- a/hbase-server/src/test/java/org/apache/hadoop/hbase/util/TestTableName.java
+++ b/hbase-server/src/test/java/org/apache/hadoop/hbase/util/TestTableName.java
@@ -28,7 +28,7 @@ import static org.junit.Assert.assertSame;
import static org.junit.Assert.fail;
import org.apache.hadoop.hbase.testclassification.MiscTests;
-import org.apache.hadoop.hbase.testclassification.SmallTests;
+import org.apache.hadoop.hbase.testclassification.MediumTests;
import org.apache.hadoop.hbase.TableName;
import org.junit.Test;
import org.junit.experimental.categories.Category;
@@ -38,7 +38,7 @@ import org.junit.runner.Description;
/**
* Returns a {@code byte[]} containing the name of the currently running test m
*/
-@Category({MiscTests.class, SmallTests.class})
+@Category({MiscTests.class, MediumTests.class})
public class TestTableName extends TestWatcher {
private TableName tableName;
{code}
on each branch (the imports are different). Let me know if you have any
concerns.
> TableName cache isn't used for one of valueOf methods.
> --
>
> Key: HBASE-12156
> URL: https://issues.apache.org/jira/browse/HBASE-12156
> Project: HBase
> Issue Type: Bug
>Reporter: Andrey Stepachev
>Assignee: Andrey Stepachev
> Fix For: 2.0.0, 0.98.7, 0.99.1
>
> Attachments: HBASE-12156-addendum-0.98.patch, HBASE-12156.patch
>
>
> there is wrong comparison, copy&paste code compares namespace with qualifier
> and namespace.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (HBASE-12124) Closed region could stay closed if master stops at bad time
[ https://issues.apache.org/jira/browse/HBASE-12124?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14158736#comment-14158736 ] Andrew Purtell commented on HBASE-12124: Let me see if I can get it to happen again and post more info > Closed region could stay closed if master stops at bad time > --- > > Key: HBASE-12124 > URL: https://issues.apache.org/jira/browse/HBASE-12124 > Project: HBase > Issue Type: Bug >Reporter: Jimmy Xiang >Assignee: Jimmy Xiang > Fix For: 0.98.7, 0.99.1 > > Attachments: hbase-12124.patch > > > This applies to RPC-based region assignment only. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Reopened] (HBASE-12124) Closed region could stay closed if master stops at bad time
[ https://issues.apache.org/jira/browse/HBASE-12124?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrew Purtell reopened HBASE-12124: TestAssignmentManager is timing out on 0.98 after this change. Considering a revert. > Closed region could stay closed if master stops at bad time > --- > > Key: HBASE-12124 > URL: https://issues.apache.org/jira/browse/HBASE-12124 > Project: HBase > Issue Type: Bug >Reporter: Jimmy Xiang >Assignee: Jimmy Xiang > Fix For: 0.98.7, 0.99.1 > > Attachments: hbase-12124.patch > > > This applies to RPC-based region assignment only. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (HBASE-12156) TableName cache isn't used for one of valueOf methods.
[ https://issues.apache.org/jira/browse/HBASE-12156?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14158733#comment-14158733 ] Andrew Purtell commented on HBASE-12156: bq. should we just switch this test to medium to run it in its own jvm Yeah we could do that. > TableName cache isn't used for one of valueOf methods. > -- > > Key: HBASE-12156 > URL: https://issues.apache.org/jira/browse/HBASE-12156 > Project: HBase > Issue Type: Bug >Reporter: Andrey Stepachev >Assignee: Andrey Stepachev > Fix For: 2.0.0, 0.98.7, 0.99.1 > > Attachments: HBASE-12156-addendum-0.98.patch, HBASE-12156.patch > > > there is wrong comparison, copy&paste code compares namespace with qualifier > and namespace. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (HBASE-11764) Support per cell TTLs
[ https://issues.apache.org/jira/browse/HBASE-11764?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrew Purtell updated HBASE-11764: --- Status: Patch Available (was: Open) Test result from previous patch version? Resubmit > Support per cell TTLs > - > > Key: HBASE-11764 > URL: https://issues.apache.org/jira/browse/HBASE-11764 > Project: HBase > Issue Type: Sub-task >Reporter: Andrew Purtell >Assignee: Andrew Purtell > Fix For: 2.0.0, 0.98.7, 0.99.1 > > Attachments: HBASE-11764-0.98.patch, HBASE-11764-0.98.patch, > HBASE-11764-0.98.patch, HBASE-11764.patch, HBASE-11764.patch, > HBASE-11764.patch, HBASE-11764.patch, HBASE-11764.patch, HBASE-11764.patch, > HBASE-11764.patch, HBASE-11764.patch, HBASE-11764.patch, HBASE-11764.patch > > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (HBASE-11764) Support per cell TTLs
[ https://issues.apache.org/jira/browse/HBASE-11764?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrew Purtell updated HBASE-11764: --- Status: Open (was: Patch Available) > Support per cell TTLs > - > > Key: HBASE-11764 > URL: https://issues.apache.org/jira/browse/HBASE-11764 > Project: HBase > Issue Type: Sub-task >Reporter: Andrew Purtell >Assignee: Andrew Purtell > Fix For: 2.0.0, 0.98.7, 0.99.1 > > Attachments: HBASE-11764-0.98.patch, HBASE-11764-0.98.patch, > HBASE-11764-0.98.patch, HBASE-11764.patch, HBASE-11764.patch, > HBASE-11764.patch, HBASE-11764.patch, HBASE-11764.patch, HBASE-11764.patch, > HBASE-11764.patch, HBASE-11764.patch, HBASE-11764.patch, HBASE-11764.patch > > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (HBASE-12156) TableName cache isn't used for one of valueOf methods.
[ https://issues.apache.org/jira/browse/HBASE-12156?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14158722#comment-14158722 ] Matteo Bertozzi commented on HBASE-12156: - since the TableName cache is shared for tests on the same jvm should we just switch this test to medium to run it in its own jvm? > TableName cache isn't used for one of valueOf methods. > -- > > Key: HBASE-12156 > URL: https://issues.apache.org/jira/browse/HBASE-12156 > Project: HBase > Issue Type: Bug >Reporter: Andrey Stepachev >Assignee: Andrey Stepachev > Fix For: 2.0.0, 0.98.7, 0.99.1 > > Attachments: HBASE-12156-addendum-0.98.patch, HBASE-12156.patch > > > there is wrong comparison, copy&paste code compares namespace with qualifier > and namespace. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (HBASE-12146) RegionServerTracker should escape data in log messages
[ https://issues.apache.org/jira/browse/HBASE-12146?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] stack updated HBASE-12146: -- Fix Version/s: 0.99.1 2.0.0 Assignee: stack Status: Patch Available (was: Open) > RegionServerTracker should escape data in log messages > -- > > Key: HBASE-12146 > URL: https://issues.apache.org/jira/browse/HBASE-12146 > Project: HBase > Issue Type: Bug >Reporter: Lars Hofhansl >Assignee: stack >Priority: Trivial > Fix For: 2.0.0, 0.99.1 > > Attachments: 12146.txt > > > Trivial thing I observed when testing 0.94.24RC2. > I see a log message of the form: > 2014-10-01 13:52:35,632 INFO > org.apache.hadoop.hbase.zookeeper.RegionServerTracker: Rs node: > /hbase/rs/newbunny,52514,1412196754788 data: PBUο^C > Obviously the tracker does not escape the value (or maybe it shouldn't log it > in the fist place) -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (HBASE-12146) RegionServerTracker should escape data in log messages
[ https://issues.apache.org/jira/browse/HBASE-12146?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] stack updated HBASE-12146: -- Attachment: 12146.txt Some cleanup that came of log splunking chasing down HBASE-12166 Addresses the issue raised here and then some, renaming threads, putting strings behind DEBUG checks, adding more info to logs. Not important. Just clean up. > RegionServerTracker should escape data in log messages > -- > > Key: HBASE-12146 > URL: https://issues.apache.org/jira/browse/HBASE-12146 > Project: HBase > Issue Type: Bug >Reporter: Lars Hofhansl >Priority: Trivial > Fix For: 2.0.0, 0.99.1 > > Attachments: 12146.txt > > > Trivial thing I observed when testing 0.94.24RC2. > I see a log message of the form: > 2014-10-01 13:52:35,632 INFO > org.apache.hadoop.hbase.zookeeper.RegionServerTracker: Rs node: > /hbase/rs/newbunny,52514,1412196754788 data: PBUο^C > Obviously the tracker does not escape the value (or maybe it shouldn't log it > in the fist place) -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (HBASE-12156) TableName cache isn't used for one of valueOf methods.
[
https://issues.apache.org/jira/browse/HBASE-12156?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14158716#comment-14158716
]
Andrew Purtell commented on HBASE-12156:
TestTableName is failing on 0.98. I can only get this test to pass reliably
after the change on this issue if I run TestTableName in its own JVM.
Definitely this change in TableName is good:
{code}
@@ -446,7 +446,7 @@ public final class TableName implements
Comparable {
}
for (TableName tn : tableCache) {
- if (Arrays.equals(tn.getQualifier(), namespace) &&
+ if (Arrays.equals(tn.getQualifier(), qualifier) &&
Arrays.equals(tn.getNamespace(), namespace)) {
return tn;
}
{code}
I am considering keeping this but reverting the test change. Should we do this
in all branches? [~stack]
> TableName cache isn't used for one of valueOf methods.
> --
>
> Key: HBASE-12156
> URL: https://issues.apache.org/jira/browse/HBASE-12156
> Project: HBase
> Issue Type: Bug
>Reporter: Andrey Stepachev
>Assignee: Andrey Stepachev
> Fix For: 2.0.0, 0.98.7, 0.99.1
>
> Attachments: HBASE-12156-addendum-0.98.patch, HBASE-12156.patch
>
>
> there is wrong comparison, copy&paste code compares namespace with qualifier
> and namespace.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Reopened] (HBASE-12156) TableName cache isn't used for one of valueOf methods.
[ https://issues.apache.org/jira/browse/HBASE-12156?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrew Purtell reopened HBASE-12156: > TableName cache isn't used for one of valueOf methods. > -- > > Key: HBASE-12156 > URL: https://issues.apache.org/jira/browse/HBASE-12156 > Project: HBase > Issue Type: Bug >Reporter: Andrey Stepachev >Assignee: Andrey Stepachev > Fix For: 2.0.0, 0.98.7, 0.99.1 > > Attachments: HBASE-12156-addendum-0.98.patch, HBASE-12156.patch > > > there is wrong comparison, copy&paste code compares namespace with qualifier > and namespace. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (HBASE-11350) [PE] Allow random value size
[ https://issues.apache.org/jira/browse/HBASE-11350?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14158705#comment-14158705 ] Andrew Purtell commented on HBASE-11350: +1 > [PE] Allow random value size > > > Key: HBASE-11350 > URL: https://issues.apache.org/jira/browse/HBASE-11350 > Project: HBase > Issue Type: Improvement > Components: Performance >Reporter: stack >Assignee: stack > Fix For: 0.99.0 > > Attachments: 11348.txt > > > Allow PE to write random value sizes. Helpful mimic'ing 'real' sizings. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (HBASE-11764) Support per cell TTLs
[
https://issues.apache.org/jira/browse/HBASE-11764?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14158706#comment-14158706
]
Hadoop QA commented on HBASE-11764:
---
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12672858/HBASE-11764.patch
against trunk revision .
ATTACHMENT ID: 12672858
{color:green}+1 @author{color}. The patch does not contain any @author
tags.
{color:green}+1 tests included{color}. The patch appears to include 9 new
or modified tests.
{color:green}+1 javac{color}. The applied patch does not increase the
total number of javac compiler warnings.
{color:green}+1 javac{color}. The applied patch does not increase the
total number of javac compiler warnings.
{color:green}+1 javadoc{color}. The javadoc tool did not generate any
warning messages.
{color:green}+1 findbugs{color}. The patch does not introduce any new
Findbugs (version 2.0.3) warnings.
{color:green}+1 release audit{color}. The applied patch does not increase
the total number of release audit warnings.
{color:red}-1 lineLengths{color}. The patch introduces the following lines
longer than 100:
+ Iterator tagIterator =
CellUtil.tagsIterator(cell.getTagsArray(), cell.getTagsOffset(),
+updatedCells.add(new KeyValue(cell.getRowArray(),
cell.getRowOffset(), cell.getRowLength(),
+ Iterator i =
CellUtil.tagsIterator(cell.getTagsArray(), cell.getTagsOffset(),
+if (t.getType() == TagType.TTL_TAG_TYPE &&
increment.getTTL() != Long.MAX_VALUE) {
+ long readPointToUse, long earliestPutTs, long oldestUnexpiredTS, long
now, byte[] dropDeletesFromRow,
{color:green}+1 site{color}. The mvn site goal succeeds with this patch.
{color:red}-1 core tests{color}. The patch failed these unit tests:
org.apache.hadoop.hbase.regionserver.TestKeepDeletes
org.apache.hadoop.hbase.regionserver.TestMinVersions
Test results:
https://builds.apache.org/job/PreCommit-HBASE-Build/11213//testReport/
Findbugs warnings:
https://builds.apache.org/job/PreCommit-HBASE-Build/11213//artifact/patchprocess/newPatchFindbugsWarningshbase-hadoop-compat.html
Findbugs warnings:
https://builds.apache.org/job/PreCommit-HBASE-Build/11213//artifact/patchprocess/newPatchFindbugsWarningshbase-prefix-tree.html
Findbugs warnings:
https://builds.apache.org/job/PreCommit-HBASE-Build/11213//artifact/patchprocess/newPatchFindbugsWarningshbase-examples.html
Findbugs warnings:
https://builds.apache.org/job/PreCommit-HBASE-Build/11213//artifact/patchprocess/newPatchFindbugsWarningshbase-server.html
Findbugs warnings:
https://builds.apache.org/job/PreCommit-HBASE-Build/11213//artifact/patchprocess/newPatchFindbugsWarningshbase-common.html
Findbugs warnings:
https://builds.apache.org/job/PreCommit-HBASE-Build/11213//artifact/patchprocess/newPatchFindbugsWarningshbase-protocol.html
Findbugs warnings:
https://builds.apache.org/job/PreCommit-HBASE-Build/11213//artifact/patchprocess/newPatchFindbugsWarningshbase-client.html
Findbugs warnings:
https://builds.apache.org/job/PreCommit-HBASE-Build/11213//artifact/patchprocess/newPatchFindbugsWarningshbase-thrift.html
Findbugs warnings:
https://builds.apache.org/job/PreCommit-HBASE-Build/11213//artifact/patchprocess/newPatchFindbugsWarningshbase-hadoop2-compat.html
Findbugs warnings:
https://builds.apache.org/job/PreCommit-HBASE-Build/11213//artifact/patchprocess/newPatchFindbugsWarningshbase-annotations.html
Console output:
https://builds.apache.org/job/PreCommit-HBASE-Build/11213//console
This message is automatically generated.
> Support per cell TTLs
> -
>
> Key: HBASE-11764
> URL: https://issues.apache.org/jira/browse/HBASE-11764
> Project: HBase
> Issue Type: Sub-task
>Reporter: Andrew Purtell
>Assignee: Andrew Purtell
> Fix For: 2.0.0, 0.98.7, 0.99.1
>
> Attachments: HBASE-11764-0.98.patch, HBASE-11764-0.98.patch,
> HBASE-11764-0.98.patch, HBASE-11764.patch, HBASE-11764.patch,
> HBASE-11764.patch, HBASE-11764.patch, HBASE-11764.patch, HBASE-11764.patch,
> HBASE-11764.patch, HBASE-11764.patch, HBASE-11764.patch, HBASE-11764.patch
>
>
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (HBASE-11764) Support per cell TTLs
[ https://issues.apache.org/jira/browse/HBASE-11764?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrew Purtell updated HBASE-11764: --- Status: Patch Available (was: Open) > Support per cell TTLs > - > > Key: HBASE-11764 > URL: https://issues.apache.org/jira/browse/HBASE-11764 > Project: HBase > Issue Type: Sub-task >Reporter: Andrew Purtell >Assignee: Andrew Purtell > Fix For: 2.0.0, 0.98.7, 0.99.1 > > Attachments: HBASE-11764-0.98.patch, HBASE-11764-0.98.patch, > HBASE-11764-0.98.patch, HBASE-11764.patch, HBASE-11764.patch, > HBASE-11764.patch, HBASE-11764.patch, HBASE-11764.patch, HBASE-11764.patch, > HBASE-11764.patch, HBASE-11764.patch, HBASE-11764.patch, HBASE-11764.patch > > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (HBASE-11764) Support per cell TTLs
[ https://issues.apache.org/jira/browse/HBASE-11764?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrew Purtell updated HBASE-11764: --- Attachment: HBASE-11764.patch I carried one hunk too many over from the previous approach. This is better. Also updated reviewboard, see https://reviews.apache.org/r/25016/ > Support per cell TTLs > - > > Key: HBASE-11764 > URL: https://issues.apache.org/jira/browse/HBASE-11764 > Project: HBase > Issue Type: Sub-task >Reporter: Andrew Purtell >Assignee: Andrew Purtell > Fix For: 2.0.0, 0.98.7, 0.99.1 > > Attachments: HBASE-11764-0.98.patch, HBASE-11764-0.98.patch, > HBASE-11764-0.98.patch, HBASE-11764.patch, HBASE-11764.patch, > HBASE-11764.patch, HBASE-11764.patch, HBASE-11764.patch, HBASE-11764.patch, > HBASE-11764.patch, HBASE-11764.patch, HBASE-11764.patch, HBASE-11764.patch > > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (HBASE-11350) [PE] Allow random value size
[ https://issues.apache.org/jira/browse/HBASE-11350?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14158697#comment-14158697 ] Lars Hofhansl commented on HBASE-11350: --- I agree. This'd be useful in 0.94, 0.98, and 1.0 as well. [~apurtell], [~enis], I assume you have no objections. This is PE only. > [PE] Allow random value size > > > Key: HBASE-11350 > URL: https://issues.apache.org/jira/browse/HBASE-11350 > Project: HBase > Issue Type: Improvement > Components: Performance >Reporter: stack >Assignee: stack > Fix For: 0.99.0 > > Attachments: 11348.txt > > > Allow PE to write random value sizes. Helpful mimic'ing 'real' sizings. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (HBASE-12166) TestDistributedLogSplitting.testMasterStartsUpWithLogReplayWork
[
https://issues.apache.org/jira/browse/HBASE-12166?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jimmy Xiang updated HBASE-12166:
Attachment: hbase-12166_v2.patch
Attched v2 that fixed the issue Stack found.
> TestDistributedLogSplitting.testMasterStartsUpWithLogReplayWork
> ---
>
> Key: HBASE-12166
> URL: https://issues.apache.org/jira/browse/HBASE-12166
> Project: HBase
> Issue Type: Bug
> Components: test, wal
>Reporter: stack
>Assignee: Jimmy Xiang
> Fix For: 2.0.0, 0.99.1
>
> Attachments: 12166.txt, hbase-12166.patch, hbase-12166_v2.patch,
> log.txt
>
>
> See
> https://builds.apache.org/job/PreCommit-HBASE-Build/11204//testReport/org.apache.hadoop.hbase.master/TestDistributedLogSplitting/testMasterStartsUpWithLogReplayWork/
> The namespace region gets stuck. It is never 'recovered' even though we have
> finished log splitting. Here is the main exception:
> {code}
> 4941 2014-10-03 02:00:36,862 DEBUG
> [B.defaultRpcServer.handler=1,queue=0,port=37113] ipc.CallRunner(111):
> B.defaultRpcServer.handler=1,queue=0,port=37113: callId: 211 service:
> ClientService methodName: Get
> size: 99 connection: 67.195.81.144:44526
> 4942 org.apache.hadoop.hbase.exceptions.RegionInRecoveryException:
> hbase:namespace,,1412301462277.eba5d23de65f2718715eeb22edf7edc2. is recovering
> 4943 at
> org.apache.hadoop.hbase.regionserver.HRegion.startRegionOperation(HRegion.java:6058)
> 4944 at
> org.apache.hadoop.hbase.regionserver.HRegion.getScanner(HRegion.java:2086)
> 4945 at
> org.apache.hadoop.hbase.regionserver.HRegion.getScanner(HRegion.java:2072)
> 4946 at org.apache.hadoop.hbase.regionserver.HRegion.get(HRegion.java:5014)
> 4947 at org.apache.hadoop.hbase.regionserver.HRegion.get(HRegion.java:4988)
> 4948 at
> org.apache.hadoop.hbase.regionserver.RSRpcServices.get(RSRpcServices.java:1690)
> 4949 at
> org.apache.hadoop.hbase.protobuf.generated.ClientProtos$ClientService$2.callBlockingMethod(ClientProtos.java:30418)
> 4950 at org.apache.hadoop.hbase.ipc.RpcServer.call(RpcServer.java:2020)
> 4951 at org.apache.hadoop.hbase.ipc.CallRunner.run(CallRunner.java:108)
> 4952 at
> org.apache.hadoop.hbase.ipc.RpcExecutor.consumerLoop(RpcExecutor.java:114)
> 4953 at org.apache.hadoop.hbase.ipc.RpcExecutor$1.run(RpcExecutor.java:94)
> 4954 at java.lang.Thread.run(Thread.java:744)
> {code}
> See how we've finished log splitting long time previous:
> {code}
> 2014-10-03 01:57:48,129 INFO [M_LOG_REPLAY_OPS-asf900:37113-1]
> master.SplitLogManager(294): finished splitting (more than or equal to)
> 197337 bytes in 1 log files in
> [hdfs://localhost:49601/user/jenkins/hbase/WALs/asf900.gq1.ygridcore.net,40732,1412301461887-splitting]
> in 379ms
> {code}
> If I grep for the deleting of znodes on recovery, which is when we set the
> recovering flag to false, I see a bunch of regions but not my namespace one:
> 2014-10-03 01:57:47,330 INFO [Thread-9216-EventThread]
> zookeeper.RecoveringRegionWatcher(66): /hbase/recovering-regions/1588230740
> znode deleted. Region: 1588230740 completes recovery.
> 2014-10-03 01:57:48,119 INFO [Thread-9216-EventThread]
> zookeeper.RecoveringRegionWatcher(66):
> /hbase/recovering-regions/adfdcf958dd958f0e2ce59072ce2209d znode deleted.
> Region: adfdcf958dd958f0e2ce59072ce2209d completes recovery.
> 2014-10-03 01:57:48,121 INFO [Thread-9216-EventThread]
> zookeeper.RecoveringRegionWatcher(66):
> /hbase/recovering-regions/41d438848305831b61d708a406d5ecde znode deleted.
> Region: 41d438848305831b61d708a406d5ecde completes recovery.
> 2014-10-03 01:57:48,122 INFO [Thread-9216-EventThread]
> zookeeper.RecoveringRegionWatcher(66):
> /hbase/recovering-regions/6a7cada80de2ae5d774fe8cd33bd4cda znode deleted.
> Region: 6a7cada80de2ae5d774fe8cd33bd4cda completes recovery.
> 2014-10-03 01:57:48,124 INFO [Thread-9216-EventThread]
> zookeeper.RecoveringRegionWatcher(66):
> /hbase/recovering-regions/65451bd5b38bd16a31e25b62b3305533 znode deleted.
> Region: 65451bd5b38bd16a31e25b62b3305533 completes recovery.
> 2014-10-03 01:57:48,125 INFO [Thread-9216-EventThread]
> zookeeper.RecoveringRegionWatcher(66):
> /hbase/recovering-regions/07afdc3748894cf2b56e0075272a95a0 znode deleted.
> Region: 07afdc3748894cf2b56e0075272a95a0 completes recovery.
> 2014-10-03 01:57:48,126 INFO [Thread-9216-EventThread]
> zookeeper.RecoveringRegionWatcher(66):
> /hbase/recovering-regions/a4337ad2874ee7e599ca2344fce21583 znode deleted.
> Region: a4337ad2874ee7e599ca2344fce21583 completes recovery.
> 2014-10-03 01:57:48,128 INFO [Thread-9216-EventThread]
> zookeeper.RecoveringRegionWatcher(66):
> /hbase/recovering-regions/9d91d6eafe260ce33e8d7d23ccd13192 znode deleted.
> Region: 9d91d6eafe260ce33e8d7d23ccd13192 completes recovery.
>
[jira] [Updated] (HBASE-11764) Support per cell TTLs
[ https://issues.apache.org/jira/browse/HBASE-11764?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrew Purtell updated HBASE-11764: --- Attachment: HBASE-11764-0.98.patch > Support per cell TTLs > - > > Key: HBASE-11764 > URL: https://issues.apache.org/jira/browse/HBASE-11764 > Project: HBase > Issue Type: Sub-task >Reporter: Andrew Purtell >Assignee: Andrew Purtell > Fix For: 2.0.0, 0.98.7, 0.99.1 > > Attachments: HBASE-11764-0.98.patch, HBASE-11764-0.98.patch, > HBASE-11764-0.98.patch, HBASE-11764.patch, HBASE-11764.patch, > HBASE-11764.patch, HBASE-11764.patch, HBASE-11764.patch, HBASE-11764.patch, > HBASE-11764.patch, HBASE-11764.patch, HBASE-11764.patch > > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (HBASE-12166) TestDistributedLogSplitting.testMasterStartsUpWithLogReplayWork
[
https://issues.apache.org/jira/browse/HBASE-12166?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14158679#comment-14158679
]
Jimmy Xiang commented on HBASE-12166:
-
[~stack], good catch! Unbeliveable!
> TestDistributedLogSplitting.testMasterStartsUpWithLogReplayWork
> ---
>
> Key: HBASE-12166
> URL: https://issues.apache.org/jira/browse/HBASE-12166
> Project: HBase
> Issue Type: Bug
> Components: test, wal
>Reporter: stack
>Assignee: Jimmy Xiang
> Fix For: 2.0.0, 0.99.1
>
> Attachments: 12166.txt, hbase-12166.patch, log.txt
>
>
> See
> https://builds.apache.org/job/PreCommit-HBASE-Build/11204//testReport/org.apache.hadoop.hbase.master/TestDistributedLogSplitting/testMasterStartsUpWithLogReplayWork/
> The namespace region gets stuck. It is never 'recovered' even though we have
> finished log splitting. Here is the main exception:
> {code}
> 4941 2014-10-03 02:00:36,862 DEBUG
> [B.defaultRpcServer.handler=1,queue=0,port=37113] ipc.CallRunner(111):
> B.defaultRpcServer.handler=1,queue=0,port=37113: callId: 211 service:
> ClientService methodName: Get
> size: 99 connection: 67.195.81.144:44526
> 4942 org.apache.hadoop.hbase.exceptions.RegionInRecoveryException:
> hbase:namespace,,1412301462277.eba5d23de65f2718715eeb22edf7edc2. is recovering
> 4943 at
> org.apache.hadoop.hbase.regionserver.HRegion.startRegionOperation(HRegion.java:6058)
> 4944 at
> org.apache.hadoop.hbase.regionserver.HRegion.getScanner(HRegion.java:2086)
> 4945 at
> org.apache.hadoop.hbase.regionserver.HRegion.getScanner(HRegion.java:2072)
> 4946 at org.apache.hadoop.hbase.regionserver.HRegion.get(HRegion.java:5014)
> 4947 at org.apache.hadoop.hbase.regionserver.HRegion.get(HRegion.java:4988)
> 4948 at
> org.apache.hadoop.hbase.regionserver.RSRpcServices.get(RSRpcServices.java:1690)
> 4949 at
> org.apache.hadoop.hbase.protobuf.generated.ClientProtos$ClientService$2.callBlockingMethod(ClientProtos.java:30418)
> 4950 at org.apache.hadoop.hbase.ipc.RpcServer.call(RpcServer.java:2020)
> 4951 at org.apache.hadoop.hbase.ipc.CallRunner.run(CallRunner.java:108)
> 4952 at
> org.apache.hadoop.hbase.ipc.RpcExecutor.consumerLoop(RpcExecutor.java:114)
> 4953 at org.apache.hadoop.hbase.ipc.RpcExecutor$1.run(RpcExecutor.java:94)
> 4954 at java.lang.Thread.run(Thread.java:744)
> {code}
> See how we've finished log splitting long time previous:
> {code}
> 2014-10-03 01:57:48,129 INFO [M_LOG_REPLAY_OPS-asf900:37113-1]
> master.SplitLogManager(294): finished splitting (more than or equal to)
> 197337 bytes in 1 log files in
> [hdfs://localhost:49601/user/jenkins/hbase/WALs/asf900.gq1.ygridcore.net,40732,1412301461887-splitting]
> in 379ms
> {code}
> If I grep for the deleting of znodes on recovery, which is when we set the
> recovering flag to false, I see a bunch of regions but not my namespace one:
> 2014-10-03 01:57:47,330 INFO [Thread-9216-EventThread]
> zookeeper.RecoveringRegionWatcher(66): /hbase/recovering-regions/1588230740
> znode deleted. Region: 1588230740 completes recovery.
> 2014-10-03 01:57:48,119 INFO [Thread-9216-EventThread]
> zookeeper.RecoveringRegionWatcher(66):
> /hbase/recovering-regions/adfdcf958dd958f0e2ce59072ce2209d znode deleted.
> Region: adfdcf958dd958f0e2ce59072ce2209d completes recovery.
> 2014-10-03 01:57:48,121 INFO [Thread-9216-EventThread]
> zookeeper.RecoveringRegionWatcher(66):
> /hbase/recovering-regions/41d438848305831b61d708a406d5ecde znode deleted.
> Region: 41d438848305831b61d708a406d5ecde completes recovery.
> 2014-10-03 01:57:48,122 INFO [Thread-9216-EventThread]
> zookeeper.RecoveringRegionWatcher(66):
> /hbase/recovering-regions/6a7cada80de2ae5d774fe8cd33bd4cda znode deleted.
> Region: 6a7cada80de2ae5d774fe8cd33bd4cda completes recovery.
> 2014-10-03 01:57:48,124 INFO [Thread-9216-EventThread]
> zookeeper.RecoveringRegionWatcher(66):
> /hbase/recovering-regions/65451bd5b38bd16a31e25b62b3305533 znode deleted.
> Region: 65451bd5b38bd16a31e25b62b3305533 completes recovery.
> 2014-10-03 01:57:48,125 INFO [Thread-9216-EventThread]
> zookeeper.RecoveringRegionWatcher(66):
> /hbase/recovering-regions/07afdc3748894cf2b56e0075272a95a0 znode deleted.
> Region: 07afdc3748894cf2b56e0075272a95a0 completes recovery.
> 2014-10-03 01:57:48,126 INFO [Thread-9216-EventThread]
> zookeeper.RecoveringRegionWatcher(66):
> /hbase/recovering-regions/a4337ad2874ee7e599ca2344fce21583 znode deleted.
> Region: a4337ad2874ee7e599ca2344fce21583 completes recovery.
> 2014-10-03 01:57:48,128 INFO [Thread-9216-EventThread]
> zookeeper.RecoveringRegionWatcher(66):
> /hbase/recovering-regions/9d91d6eafe260ce33e8d7d23ccd13192 znode deleted.
> Region: 9d91d6eafe260ce33e8d7d23ccd13192 completes recovery.
> This would see
[jira] [Commented] (HBASE-12166) TestDistributedLogSplitting.testMasterStartsUpWithLogReplayWork
[
https://issues.apache.org/jira/browse/HBASE-12166?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14158673#comment-14158673
]
stack commented on HBASE-12166:
---
There is another bomb in that same class [~jxiang]
> TestDistributedLogSplitting.testMasterStartsUpWithLogReplayWork
> ---
>
> Key: HBASE-12166
> URL: https://issues.apache.org/jira/browse/HBASE-12166
> Project: HBase
> Issue Type: Bug
> Components: test, wal
>Reporter: stack
>Assignee: Jimmy Xiang
> Fix For: 2.0.0, 0.99.1
>
> Attachments: 12166.txt, hbase-12166.patch, log.txt
>
>
> See
> https://builds.apache.org/job/PreCommit-HBASE-Build/11204//testReport/org.apache.hadoop.hbase.master/TestDistributedLogSplitting/testMasterStartsUpWithLogReplayWork/
> The namespace region gets stuck. It is never 'recovered' even though we have
> finished log splitting. Here is the main exception:
> {code}
> 4941 2014-10-03 02:00:36,862 DEBUG
> [B.defaultRpcServer.handler=1,queue=0,port=37113] ipc.CallRunner(111):
> B.defaultRpcServer.handler=1,queue=0,port=37113: callId: 211 service:
> ClientService methodName: Get
> size: 99 connection: 67.195.81.144:44526
> 4942 org.apache.hadoop.hbase.exceptions.RegionInRecoveryException:
> hbase:namespace,,1412301462277.eba5d23de65f2718715eeb22edf7edc2. is recovering
> 4943 at
> org.apache.hadoop.hbase.regionserver.HRegion.startRegionOperation(HRegion.java:6058)
> 4944 at
> org.apache.hadoop.hbase.regionserver.HRegion.getScanner(HRegion.java:2086)
> 4945 at
> org.apache.hadoop.hbase.regionserver.HRegion.getScanner(HRegion.java:2072)
> 4946 at org.apache.hadoop.hbase.regionserver.HRegion.get(HRegion.java:5014)
> 4947 at org.apache.hadoop.hbase.regionserver.HRegion.get(HRegion.java:4988)
> 4948 at
> org.apache.hadoop.hbase.regionserver.RSRpcServices.get(RSRpcServices.java:1690)
> 4949 at
> org.apache.hadoop.hbase.protobuf.generated.ClientProtos$ClientService$2.callBlockingMethod(ClientProtos.java:30418)
> 4950 at org.apache.hadoop.hbase.ipc.RpcServer.call(RpcServer.java:2020)
> 4951 at org.apache.hadoop.hbase.ipc.CallRunner.run(CallRunner.java:108)
> 4952 at
> org.apache.hadoop.hbase.ipc.RpcExecutor.consumerLoop(RpcExecutor.java:114)
> 4953 at org.apache.hadoop.hbase.ipc.RpcExecutor$1.run(RpcExecutor.java:94)
> 4954 at java.lang.Thread.run(Thread.java:744)
> {code}
> See how we've finished log splitting long time previous:
> {code}
> 2014-10-03 01:57:48,129 INFO [M_LOG_REPLAY_OPS-asf900:37113-1]
> master.SplitLogManager(294): finished splitting (more than or equal to)
> 197337 bytes in 1 log files in
> [hdfs://localhost:49601/user/jenkins/hbase/WALs/asf900.gq1.ygridcore.net,40732,1412301461887-splitting]
> in 379ms
> {code}
> If I grep for the deleting of znodes on recovery, which is when we set the
> recovering flag to false, I see a bunch of regions but not my namespace one:
> 2014-10-03 01:57:47,330 INFO [Thread-9216-EventThread]
> zookeeper.RecoveringRegionWatcher(66): /hbase/recovering-regions/1588230740
> znode deleted. Region: 1588230740 completes recovery.
> 2014-10-03 01:57:48,119 INFO [Thread-9216-EventThread]
> zookeeper.RecoveringRegionWatcher(66):
> /hbase/recovering-regions/adfdcf958dd958f0e2ce59072ce2209d znode deleted.
> Region: adfdcf958dd958f0e2ce59072ce2209d completes recovery.
> 2014-10-03 01:57:48,121 INFO [Thread-9216-EventThread]
> zookeeper.RecoveringRegionWatcher(66):
> /hbase/recovering-regions/41d438848305831b61d708a406d5ecde znode deleted.
> Region: 41d438848305831b61d708a406d5ecde completes recovery.
> 2014-10-03 01:57:48,122 INFO [Thread-9216-EventThread]
> zookeeper.RecoveringRegionWatcher(66):
> /hbase/recovering-regions/6a7cada80de2ae5d774fe8cd33bd4cda znode deleted.
> Region: 6a7cada80de2ae5d774fe8cd33bd4cda completes recovery.
> 2014-10-03 01:57:48,124 INFO [Thread-9216-EventThread]
> zookeeper.RecoveringRegionWatcher(66):
> /hbase/recovering-regions/65451bd5b38bd16a31e25b62b3305533 znode deleted.
> Region: 65451bd5b38bd16a31e25b62b3305533 completes recovery.
> 2014-10-03 01:57:48,125 INFO [Thread-9216-EventThread]
> zookeeper.RecoveringRegionWatcher(66):
> /hbase/recovering-regions/07afdc3748894cf2b56e0075272a95a0 znode deleted.
> Region: 07afdc3748894cf2b56e0075272a95a0 completes recovery.
> 2014-10-03 01:57:48,126 INFO [Thread-9216-EventThread]
> zookeeper.RecoveringRegionWatcher(66):
> /hbase/recovering-regions/a4337ad2874ee7e599ca2344fce21583 znode deleted.
> Region: a4337ad2874ee7e599ca2344fce21583 completes recovery.
> 2014-10-03 01:57:48,128 INFO [Thread-9216-EventThread]
> zookeeper.RecoveringRegionWatcher(66):
> /hbase/recovering-regions/9d91d6eafe260ce33e8d7d23ccd13192 znode deleted.
> Region: 9d91d6eafe260ce33e8d7d23ccd13192 completes recovery.
> This would
[jira] [Commented] (HBASE-12166) TestDistributedLogSplitting.testMasterStartsUpWithLogReplayWork
[
https://issues.apache.org/jira/browse/HBASE-12166?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14158667#comment-14158667
]
Jeffrey Zhong commented on HBASE-12166:
---
[~jxiang]Good catch! Looks good to me(+1). Better change the variable name
listSize2 to tmpFailedServerSizse though.
> TestDistributedLogSplitting.testMasterStartsUpWithLogReplayWork
> ---
>
> Key: HBASE-12166
> URL: https://issues.apache.org/jira/browse/HBASE-12166
> Project: HBase
> Issue Type: Bug
> Components: test, wal
>Reporter: stack
>Assignee: Jimmy Xiang
> Fix For: 2.0.0, 0.99.1
>
> Attachments: 12166.txt, hbase-12166.patch, log.txt
>
>
> See
> https://builds.apache.org/job/PreCommit-HBASE-Build/11204//testReport/org.apache.hadoop.hbase.master/TestDistributedLogSplitting/testMasterStartsUpWithLogReplayWork/
> The namespace region gets stuck. It is never 'recovered' even though we have
> finished log splitting. Here is the main exception:
> {code}
> 4941 2014-10-03 02:00:36,862 DEBUG
> [B.defaultRpcServer.handler=1,queue=0,port=37113] ipc.CallRunner(111):
> B.defaultRpcServer.handler=1,queue=0,port=37113: callId: 211 service:
> ClientService methodName: Get
> size: 99 connection: 67.195.81.144:44526
> 4942 org.apache.hadoop.hbase.exceptions.RegionInRecoveryException:
> hbase:namespace,,1412301462277.eba5d23de65f2718715eeb22edf7edc2. is recovering
> 4943 at
> org.apache.hadoop.hbase.regionserver.HRegion.startRegionOperation(HRegion.java:6058)
> 4944 at
> org.apache.hadoop.hbase.regionserver.HRegion.getScanner(HRegion.java:2086)
> 4945 at
> org.apache.hadoop.hbase.regionserver.HRegion.getScanner(HRegion.java:2072)
> 4946 at org.apache.hadoop.hbase.regionserver.HRegion.get(HRegion.java:5014)
> 4947 at org.apache.hadoop.hbase.regionserver.HRegion.get(HRegion.java:4988)
> 4948 at
> org.apache.hadoop.hbase.regionserver.RSRpcServices.get(RSRpcServices.java:1690)
> 4949 at
> org.apache.hadoop.hbase.protobuf.generated.ClientProtos$ClientService$2.callBlockingMethod(ClientProtos.java:30418)
> 4950 at org.apache.hadoop.hbase.ipc.RpcServer.call(RpcServer.java:2020)
> 4951 at org.apache.hadoop.hbase.ipc.CallRunner.run(CallRunner.java:108)
> 4952 at
> org.apache.hadoop.hbase.ipc.RpcExecutor.consumerLoop(RpcExecutor.java:114)
> 4953 at org.apache.hadoop.hbase.ipc.RpcExecutor$1.run(RpcExecutor.java:94)
> 4954 at java.lang.Thread.run(Thread.java:744)
> {code}
> See how we've finished log splitting long time previous:
> {code}
> 2014-10-03 01:57:48,129 INFO [M_LOG_REPLAY_OPS-asf900:37113-1]
> master.SplitLogManager(294): finished splitting (more than or equal to)
> 197337 bytes in 1 log files in
> [hdfs://localhost:49601/user/jenkins/hbase/WALs/asf900.gq1.ygridcore.net,40732,1412301461887-splitting]
> in 379ms
> {code}
> If I grep for the deleting of znodes on recovery, which is when we set the
> recovering flag to false, I see a bunch of regions but not my namespace one:
> 2014-10-03 01:57:47,330 INFO [Thread-9216-EventThread]
> zookeeper.RecoveringRegionWatcher(66): /hbase/recovering-regions/1588230740
> znode deleted. Region: 1588230740 completes recovery.
> 2014-10-03 01:57:48,119 INFO [Thread-9216-EventThread]
> zookeeper.RecoveringRegionWatcher(66):
> /hbase/recovering-regions/adfdcf958dd958f0e2ce59072ce2209d znode deleted.
> Region: adfdcf958dd958f0e2ce59072ce2209d completes recovery.
> 2014-10-03 01:57:48,121 INFO [Thread-9216-EventThread]
> zookeeper.RecoveringRegionWatcher(66):
> /hbase/recovering-regions/41d438848305831b61d708a406d5ecde znode deleted.
> Region: 41d438848305831b61d708a406d5ecde completes recovery.
> 2014-10-03 01:57:48,122 INFO [Thread-9216-EventThread]
> zookeeper.RecoveringRegionWatcher(66):
> /hbase/recovering-regions/6a7cada80de2ae5d774fe8cd33bd4cda znode deleted.
> Region: 6a7cada80de2ae5d774fe8cd33bd4cda completes recovery.
> 2014-10-03 01:57:48,124 INFO [Thread-9216-EventThread]
> zookeeper.RecoveringRegionWatcher(66):
> /hbase/recovering-regions/65451bd5b38bd16a31e25b62b3305533 znode deleted.
> Region: 65451bd5b38bd16a31e25b62b3305533 completes recovery.
> 2014-10-03 01:57:48,125 INFO [Thread-9216-EventThread]
> zookeeper.RecoveringRegionWatcher(66):
> /hbase/recovering-regions/07afdc3748894cf2b56e0075272a95a0 znode deleted.
> Region: 07afdc3748894cf2b56e0075272a95a0 completes recovery.
> 2014-10-03 01:57:48,126 INFO [Thread-9216-EventThread]
> zookeeper.RecoveringRegionWatcher(66):
> /hbase/recovering-regions/a4337ad2874ee7e599ca2344fce21583 znode deleted.
> Region: a4337ad2874ee7e599ca2344fce21583 completes recovery.
> 2014-10-03 01:57:48,128 INFO [Thread-9216-EventThread]
> zookeeper.RecoveringRegionWatcher(66):
> /hbase/recovering-regions/9d91d6eafe260ce33e8d7d23ccd13192 znode del
[jira] [Commented] (HBASE-12166) TestDistributedLogSplitting.testMasterStartsUpWithLogReplayWork
[
https://issues.apache.org/jira/browse/HBASE-12166?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14158663#comment-14158663
]
stack commented on HBASE-12166:
---
[~jxiang] Yeah, thats it. I just ran into it (Didn't believe it...). Test
passed for me when I made the change, +1 and +1 to upping timeout (Am checking
other uses of 'listSize' -- smile).
> TestDistributedLogSplitting.testMasterStartsUpWithLogReplayWork
> ---
>
> Key: HBASE-12166
> URL: https://issues.apache.org/jira/browse/HBASE-12166
> Project: HBase
> Issue Type: Bug
> Components: test, wal
>Reporter: stack
>Assignee: Jimmy Xiang
> Fix For: 2.0.0, 0.99.1
>
> Attachments: 12166.txt, hbase-12166.patch, log.txt
>
>
> See
> https://builds.apache.org/job/PreCommit-HBASE-Build/11204//testReport/org.apache.hadoop.hbase.master/TestDistributedLogSplitting/testMasterStartsUpWithLogReplayWork/
> The namespace region gets stuck. It is never 'recovered' even though we have
> finished log splitting. Here is the main exception:
> {code}
> 4941 2014-10-03 02:00:36,862 DEBUG
> [B.defaultRpcServer.handler=1,queue=0,port=37113] ipc.CallRunner(111):
> B.defaultRpcServer.handler=1,queue=0,port=37113: callId: 211 service:
> ClientService methodName: Get
> size: 99 connection: 67.195.81.144:44526
> 4942 org.apache.hadoop.hbase.exceptions.RegionInRecoveryException:
> hbase:namespace,,1412301462277.eba5d23de65f2718715eeb22edf7edc2. is recovering
> 4943 at
> org.apache.hadoop.hbase.regionserver.HRegion.startRegionOperation(HRegion.java:6058)
> 4944 at
> org.apache.hadoop.hbase.regionserver.HRegion.getScanner(HRegion.java:2086)
> 4945 at
> org.apache.hadoop.hbase.regionserver.HRegion.getScanner(HRegion.java:2072)
> 4946 at org.apache.hadoop.hbase.regionserver.HRegion.get(HRegion.java:5014)
> 4947 at org.apache.hadoop.hbase.regionserver.HRegion.get(HRegion.java:4988)
> 4948 at
> org.apache.hadoop.hbase.regionserver.RSRpcServices.get(RSRpcServices.java:1690)
> 4949 at
> org.apache.hadoop.hbase.protobuf.generated.ClientProtos$ClientService$2.callBlockingMethod(ClientProtos.java:30418)
> 4950 at org.apache.hadoop.hbase.ipc.RpcServer.call(RpcServer.java:2020)
> 4951 at org.apache.hadoop.hbase.ipc.CallRunner.run(CallRunner.java:108)
> 4952 at
> org.apache.hadoop.hbase.ipc.RpcExecutor.consumerLoop(RpcExecutor.java:114)
> 4953 at org.apache.hadoop.hbase.ipc.RpcExecutor$1.run(RpcExecutor.java:94)
> 4954 at java.lang.Thread.run(Thread.java:744)
> {code}
> See how we've finished log splitting long time previous:
> {code}
> 2014-10-03 01:57:48,129 INFO [M_LOG_REPLAY_OPS-asf900:37113-1]
> master.SplitLogManager(294): finished splitting (more than or equal to)
> 197337 bytes in 1 log files in
> [hdfs://localhost:49601/user/jenkins/hbase/WALs/asf900.gq1.ygridcore.net,40732,1412301461887-splitting]
> in 379ms
> {code}
> If I grep for the deleting of znodes on recovery, which is when we set the
> recovering flag to false, I see a bunch of regions but not my namespace one:
> 2014-10-03 01:57:47,330 INFO [Thread-9216-EventThread]
> zookeeper.RecoveringRegionWatcher(66): /hbase/recovering-regions/1588230740
> znode deleted. Region: 1588230740 completes recovery.
> 2014-10-03 01:57:48,119 INFO [Thread-9216-EventThread]
> zookeeper.RecoveringRegionWatcher(66):
> /hbase/recovering-regions/adfdcf958dd958f0e2ce59072ce2209d znode deleted.
> Region: adfdcf958dd958f0e2ce59072ce2209d completes recovery.
> 2014-10-03 01:57:48,121 INFO [Thread-9216-EventThread]
> zookeeper.RecoveringRegionWatcher(66):
> /hbase/recovering-regions/41d438848305831b61d708a406d5ecde znode deleted.
> Region: 41d438848305831b61d708a406d5ecde completes recovery.
> 2014-10-03 01:57:48,122 INFO [Thread-9216-EventThread]
> zookeeper.RecoveringRegionWatcher(66):
> /hbase/recovering-regions/6a7cada80de2ae5d774fe8cd33bd4cda znode deleted.
> Region: 6a7cada80de2ae5d774fe8cd33bd4cda completes recovery.
> 2014-10-03 01:57:48,124 INFO [Thread-9216-EventThread]
> zookeeper.RecoveringRegionWatcher(66):
> /hbase/recovering-regions/65451bd5b38bd16a31e25b62b3305533 znode deleted.
> Region: 65451bd5b38bd16a31e25b62b3305533 completes recovery.
> 2014-10-03 01:57:48,125 INFO [Thread-9216-EventThread]
> zookeeper.RecoveringRegionWatcher(66):
> /hbase/recovering-regions/07afdc3748894cf2b56e0075272a95a0 znode deleted.
> Region: 07afdc3748894cf2b56e0075272a95a0 completes recovery.
> 2014-10-03 01:57:48,126 INFO [Thread-9216-EventThread]
> zookeeper.RecoveringRegionWatcher(66):
> /hbase/recovering-regions/a4337ad2874ee7e599ca2344fce21583 znode deleted.
> Region: a4337ad2874ee7e599ca2344fce21583 completes recovery.
> 2014-10-03 01:57:48,128 INFO [Thread-9216-EventThread]
> zookeeper.RecoveringRegionWatcher(66):
> /hbase/rec
[jira] [Commented] (HBASE-12167) NPE in AssignmentManager
[
https://issues.apache.org/jira/browse/HBASE-12167?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14158660#comment-14158660
]
Hudson commented on HBASE-12167:
FAILURE: Integrated in HBase-TRUNK #5617 (See
[https://builds.apache.org/job/HBase-TRUNK/5617/])
HBASE-12167 addendum; fix TestMasterObserver (jxiang: rev
dbef2bdafe5500c0abc8fc61d3539d3b7a2132b9)
*
hbase-server/src/test/java/org/apache/hadoop/hbase/coprocessor/TestMasterObserver.java
> NPE in AssignmentManager
>
>
> Key: HBASE-12167
> URL: https://issues.apache.org/jira/browse/HBASE-12167
> Project: HBase
> Issue Type: Bug
>Reporter: Jimmy Xiang
>Assignee: Jimmy Xiang
> Fix For: 2.0.0, 0.99.1
>
> Attachments: hbase-12167.patch
>
>
> If we can't find a region plan, we should check.
> {noformat}
> 2014-10-02 18:36:27,719 ERROR [MASTER_SERVER_OPERATIONS-a2424:20020-0]
> executor.EventHandler: Caught throwable while processing event
> M_SERVER_SHUTDOWN
> java.lang.NullPointerException
> at
> org.apache.hadoop.hbase.master.AssignmentManager.assign(AssignmentManager.java:1417)
> at
> org.apache.hadoop.hbase.master.AssignmentManager.assign(AssignmentManager.java:1409)
> at
> org.apache.hadoop.hbase.master.handler.ServerShutdownHandler.process(ServerShutdownHandler.java:271)
> at
> org.apache.hadoop.hbase.executor.EventHandler.run(EventHandler.java:128)
> at
> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145)
> at
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)
> at java.lang.Thread.run(Thread.java:724)
> {noformat}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (HBASE-12136) Race condition between client adding tableCF replication znode and server triggering TableCFsTracker
[ https://issues.apache.org/jira/browse/HBASE-12136?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14158659#comment-14158659 ] Hudson commented on HBASE-12136: FAILURE: Integrated in HBase-TRUNK #5617 (See [https://builds.apache.org/job/HBase-TRUNK/5617/]) HBASE-12136 Race condition between client adding tableCF replication znode and server triggering TableCFsTracker (Virag Kothari) (tedyu: rev efe0787c87ca03e548bec13d8ae24200f582b438) * hbase-client/src/main/java/org/apache/hadoop/hbase/replication/ReplicationPeerZKImpl.java * hbase-client/src/main/java/org/apache/hadoop/hbase/replication/ReplicationPeersZKImpl.java > Race condition between client adding tableCF replication znode and server > triggering TableCFsTracker > - > > Key: HBASE-12136 > URL: https://issues.apache.org/jira/browse/HBASE-12136 > Project: HBase > Issue Type: Bug > Components: Replication >Affects Versions: 0.98.6 >Reporter: Virag Kothari >Assignee: Virag Kothari > Fix For: 2.0.0, 0.98.7, 0.99.1 > > Attachments: HBASE-12136-0.98.patch, HBASE-12136.patch > > > In ReplicationPeersZKImpl.addPeer(), there is a race between client creating > tableCf znode and the server triggering TableCFsTracker. If the server wins, > it wont be able to read the data set on tableCF znode and replication will > be misconfigured -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (HBASE-11764) Support per cell TTLs
[ https://issues.apache.org/jira/browse/HBASE-11764?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrew Purtell updated HBASE-11764: --- Status: Open (was: Patch Available) > Support per cell TTLs > - > > Key: HBASE-11764 > URL: https://issues.apache.org/jira/browse/HBASE-11764 > Project: HBase > Issue Type: Sub-task >Reporter: Andrew Purtell >Assignee: Andrew Purtell > Fix For: 2.0.0, 0.98.7, 0.99.1 > > Attachments: HBASE-11764-0.98.patch, HBASE-11764-0.98.patch, > HBASE-11764.patch, HBASE-11764.patch, HBASE-11764.patch, HBASE-11764.patch, > HBASE-11764.patch, HBASE-11764.patch, HBASE-11764.patch, HBASE-11764.patch, > HBASE-11764.patch > > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Comment Edited] (HBASE-12166) TestDistributedLogSplitting.testMasterStartsUpWithLogReplayWork
[
https://issues.apache.org/jira/browse/HBASE-12166?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14158515#comment-14158515
]
Jimmy Xiang edited comment on HBASE-12166 at 10/3/14 11:08 PM:
---
I think I found out the cause. In
ZKSplitLogManagerCoordination#removeRecoveringRegions:
{noformat}
listSize = failedServers.size();
for (int j = 0; j < listSize; j++) {
{noformat}
The listSize is redefined.
was (Author: jxiang):
I think I found out the cause. In
ZKSplitLogManagerCoordination#removeRecoveringRegions:
{noformat}
listSize = failedServers.size();
for (int j = 0; j < listSize; j++) {
{noformat}
The listSize is redefined. That's not a bug, it is a hidden bomb :)
> TestDistributedLogSplitting.testMasterStartsUpWithLogReplayWork
> ---
>
> Key: HBASE-12166
> URL: https://issues.apache.org/jira/browse/HBASE-12166
> Project: HBase
> Issue Type: Bug
> Components: test, wal
>Reporter: stack
>Assignee: Jimmy Xiang
> Fix For: 2.0.0, 0.99.1
>
> Attachments: 12166.txt, hbase-12166.patch, log.txt
>
>
> See
> https://builds.apache.org/job/PreCommit-HBASE-Build/11204//testReport/org.apache.hadoop.hbase.master/TestDistributedLogSplitting/testMasterStartsUpWithLogReplayWork/
> The namespace region gets stuck. It is never 'recovered' even though we have
> finished log splitting. Here is the main exception:
> {code}
> 4941 2014-10-03 02:00:36,862 DEBUG
> [B.defaultRpcServer.handler=1,queue=0,port=37113] ipc.CallRunner(111):
> B.defaultRpcServer.handler=1,queue=0,port=37113: callId: 211 service:
> ClientService methodName: Get
> size: 99 connection: 67.195.81.144:44526
> 4942 org.apache.hadoop.hbase.exceptions.RegionInRecoveryException:
> hbase:namespace,,1412301462277.eba5d23de65f2718715eeb22edf7edc2. is recovering
> 4943 at
> org.apache.hadoop.hbase.regionserver.HRegion.startRegionOperation(HRegion.java:6058)
> 4944 at
> org.apache.hadoop.hbase.regionserver.HRegion.getScanner(HRegion.java:2086)
> 4945 at
> org.apache.hadoop.hbase.regionserver.HRegion.getScanner(HRegion.java:2072)
> 4946 at org.apache.hadoop.hbase.regionserver.HRegion.get(HRegion.java:5014)
> 4947 at org.apache.hadoop.hbase.regionserver.HRegion.get(HRegion.java:4988)
> 4948 at
> org.apache.hadoop.hbase.regionserver.RSRpcServices.get(RSRpcServices.java:1690)
> 4949 at
> org.apache.hadoop.hbase.protobuf.generated.ClientProtos$ClientService$2.callBlockingMethod(ClientProtos.java:30418)
> 4950 at org.apache.hadoop.hbase.ipc.RpcServer.call(RpcServer.java:2020)
> 4951 at org.apache.hadoop.hbase.ipc.CallRunner.run(CallRunner.java:108)
> 4952 at
> org.apache.hadoop.hbase.ipc.RpcExecutor.consumerLoop(RpcExecutor.java:114)
> 4953 at org.apache.hadoop.hbase.ipc.RpcExecutor$1.run(RpcExecutor.java:94)
> 4954 at java.lang.Thread.run(Thread.java:744)
> {code}
> See how we've finished log splitting long time previous:
> {code}
> 2014-10-03 01:57:48,129 INFO [M_LOG_REPLAY_OPS-asf900:37113-1]
> master.SplitLogManager(294): finished splitting (more than or equal to)
> 197337 bytes in 1 log files in
> [hdfs://localhost:49601/user/jenkins/hbase/WALs/asf900.gq1.ygridcore.net,40732,1412301461887-splitting]
> in 379ms
> {code}
> If I grep for the deleting of znodes on recovery, which is when we set the
> recovering flag to false, I see a bunch of regions but not my namespace one:
> 2014-10-03 01:57:47,330 INFO [Thread-9216-EventThread]
> zookeeper.RecoveringRegionWatcher(66): /hbase/recovering-regions/1588230740
> znode deleted. Region: 1588230740 completes recovery.
> 2014-10-03 01:57:48,119 INFO [Thread-9216-EventThread]
> zookeeper.RecoveringRegionWatcher(66):
> /hbase/recovering-regions/adfdcf958dd958f0e2ce59072ce2209d znode deleted.
> Region: adfdcf958dd958f0e2ce59072ce2209d completes recovery.
> 2014-10-03 01:57:48,121 INFO [Thread-9216-EventThread]
> zookeeper.RecoveringRegionWatcher(66):
> /hbase/recovering-regions/41d438848305831b61d708a406d5ecde znode deleted.
> Region: 41d438848305831b61d708a406d5ecde completes recovery.
> 2014-10-03 01:57:48,122 INFO [Thread-9216-EventThread]
> zookeeper.RecoveringRegionWatcher(66):
> /hbase/recovering-regions/6a7cada80de2ae5d774fe8cd33bd4cda znode deleted.
> Region: 6a7cada80de2ae5d774fe8cd33bd4cda completes recovery.
> 2014-10-03 01:57:48,124 INFO [Thread-9216-EventThread]
> zookeeper.RecoveringRegionWatcher(66):
> /hbase/recovering-regions/65451bd5b38bd16a31e25b62b3305533 znode deleted.
> Region: 65451bd5b38bd16a31e25b62b3305533 completes recovery.
> 2014-10-03 01:57:48,125 INFO [Thread-9216-EventThread]
> zookeeper.RecoveringRegionWatcher(66):
> /hbase/recovering-regions/07afdc3748894cf2b56e0075272a95a0 znode deleted.
> R
[jira] [Commented] (HBASE-12137) Alter table add cf doesn't do compression test
[
https://issues.apache.org/jira/browse/HBASE-12137?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14158655#comment-14158655
]
Hadoop QA commented on HBASE-12137:
---
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12672842/HBASE-12137.patch
against trunk revision .
ATTACHMENT ID: 12672842
{color:green}+1 @author{color}. The patch does not contain any @author
tags.
{color:red}-1 tests included{color}. The patch doesn't appear to include
any new or modified tests.
Please justify why no new tests are needed for this
patch.
Also please list what manual steps were performed to
verify this patch.
{color:green}+1 javac{color}. The applied patch does not increase the
total number of javac compiler warnings.
{color:green}+1 javac{color}. The applied patch does not increase the
total number of javac compiler warnings.
{color:green}+1 javadoc{color}. The javadoc tool did not generate any
warning messages.
{color:green}+1 findbugs{color}. The patch does not introduce any new
Findbugs (version 2.0.3) warnings.
{color:green}+1 release audit{color}. The applied patch does not increase
the total number of release audit warnings.
{color:green}+1 lineLengths{color}. The patch does not introduce lines
longer than 100
{color:green}+1 site{color}. The mvn site goal succeeds with this patch.
{color:red}-1 core tests{color}. The patch failed these unit tests:
org.apache.hadoop.hbase.util.TestHBaseFsck
org.apache.hadoop.hbase.master.TestDistributedLogSplitting
Test results:
https://builds.apache.org/job/PreCommit-HBASE-Build/11212//testReport/
Findbugs warnings:
https://builds.apache.org/job/PreCommit-HBASE-Build/11212//artifact/patchprocess/newPatchFindbugsWarningshbase-client.html
Findbugs warnings:
https://builds.apache.org/job/PreCommit-HBASE-Build/11212//artifact/patchprocess/newPatchFindbugsWarningshbase-examples.html
Findbugs warnings:
https://builds.apache.org/job/PreCommit-HBASE-Build/11212//artifact/patchprocess/newPatchFindbugsWarningshbase-protocol.html
Findbugs warnings:
https://builds.apache.org/job/PreCommit-HBASE-Build/11212//artifact/patchprocess/newPatchFindbugsWarningshbase-common.html
Findbugs warnings:
https://builds.apache.org/job/PreCommit-HBASE-Build/11212//artifact/patchprocess/newPatchFindbugsWarningshbase-server.html
Findbugs warnings:
https://builds.apache.org/job/PreCommit-HBASE-Build/11212//artifact/patchprocess/newPatchFindbugsWarningshbase-thrift.html
Findbugs warnings:
https://builds.apache.org/job/PreCommit-HBASE-Build/11212//artifact/patchprocess/newPatchFindbugsWarningshbase-hadoop-compat.html
Findbugs warnings:
https://builds.apache.org/job/PreCommit-HBASE-Build/11212//artifact/patchprocess/newPatchFindbugsWarningshbase-prefix-tree.html
Findbugs warnings:
https://builds.apache.org/job/PreCommit-HBASE-Build/11212//artifact/patchprocess/newPatchFindbugsWarningshbase-hadoop2-compat.html
Findbugs warnings:
https://builds.apache.org/job/PreCommit-HBASE-Build/11212//artifact/patchprocess/newPatchFindbugsWarningshbase-annotations.html
Console output:
https://builds.apache.org/job/PreCommit-HBASE-Build/11212//console
This message is automatically generated.
> Alter table add cf doesn't do compression test
> --
>
> Key: HBASE-12137
> URL: https://issues.apache.org/jira/browse/HBASE-12137
> Project: HBase
> Issue Type: Bug
> Components: master
>Affects Versions: 0.98.6
>Reporter: Virag Kothari
>Assignee: Virag Kothari
> Fix For: 2.0.0, 0.98.7, 0.99.1
>
> Attachments: HBASE-12137-0.98.patch, HBASE-12137.patch,
> HBASE-12137.patch
>
>
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (HBASE-12166) TestDistributedLogSplitting.testMasterStartsUpWithLogReplayWork
[
https://issues.apache.org/jira/browse/HBASE-12166?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14158649#comment-14158649
]
Jimmy Xiang commented on HBASE-12166:
-
TestRegionReplicaReplicationEndpoint is ok locally. I can increase the timeout
a little at checkin (from 1000 to 6000?).
> TestDistributedLogSplitting.testMasterStartsUpWithLogReplayWork
> ---
>
> Key: HBASE-12166
> URL: https://issues.apache.org/jira/browse/HBASE-12166
> Project: HBase
> Issue Type: Bug
> Components: test, wal
>Reporter: stack
>Assignee: Jimmy Xiang
> Fix For: 2.0.0, 0.99.1
>
> Attachments: 12166.txt, hbase-12166.patch, log.txt
>
>
> See
> https://builds.apache.org/job/PreCommit-HBASE-Build/11204//testReport/org.apache.hadoop.hbase.master/TestDistributedLogSplitting/testMasterStartsUpWithLogReplayWork/
> The namespace region gets stuck. It is never 'recovered' even though we have
> finished log splitting. Here is the main exception:
> {code}
> 4941 2014-10-03 02:00:36,862 DEBUG
> [B.defaultRpcServer.handler=1,queue=0,port=37113] ipc.CallRunner(111):
> B.defaultRpcServer.handler=1,queue=0,port=37113: callId: 211 service:
> ClientService methodName: Get
> size: 99 connection: 67.195.81.144:44526
> 4942 org.apache.hadoop.hbase.exceptions.RegionInRecoveryException:
> hbase:namespace,,1412301462277.eba5d23de65f2718715eeb22edf7edc2. is recovering
> 4943 at
> org.apache.hadoop.hbase.regionserver.HRegion.startRegionOperation(HRegion.java:6058)
> 4944 at
> org.apache.hadoop.hbase.regionserver.HRegion.getScanner(HRegion.java:2086)
> 4945 at
> org.apache.hadoop.hbase.regionserver.HRegion.getScanner(HRegion.java:2072)
> 4946 at org.apache.hadoop.hbase.regionserver.HRegion.get(HRegion.java:5014)
> 4947 at org.apache.hadoop.hbase.regionserver.HRegion.get(HRegion.java:4988)
> 4948 at
> org.apache.hadoop.hbase.regionserver.RSRpcServices.get(RSRpcServices.java:1690)
> 4949 at
> org.apache.hadoop.hbase.protobuf.generated.ClientProtos$ClientService$2.callBlockingMethod(ClientProtos.java:30418)
> 4950 at org.apache.hadoop.hbase.ipc.RpcServer.call(RpcServer.java:2020)
> 4951 at org.apache.hadoop.hbase.ipc.CallRunner.run(CallRunner.java:108)
> 4952 at
> org.apache.hadoop.hbase.ipc.RpcExecutor.consumerLoop(RpcExecutor.java:114)
> 4953 at org.apache.hadoop.hbase.ipc.RpcExecutor$1.run(RpcExecutor.java:94)
> 4954 at java.lang.Thread.run(Thread.java:744)
> {code}
> See how we've finished log splitting long time previous:
> {code}
> 2014-10-03 01:57:48,129 INFO [M_LOG_REPLAY_OPS-asf900:37113-1]
> master.SplitLogManager(294): finished splitting (more than or equal to)
> 197337 bytes in 1 log files in
> [hdfs://localhost:49601/user/jenkins/hbase/WALs/asf900.gq1.ygridcore.net,40732,1412301461887-splitting]
> in 379ms
> {code}
> If I grep for the deleting of znodes on recovery, which is when we set the
> recovering flag to false, I see a bunch of regions but not my namespace one:
> 2014-10-03 01:57:47,330 INFO [Thread-9216-EventThread]
> zookeeper.RecoveringRegionWatcher(66): /hbase/recovering-regions/1588230740
> znode deleted. Region: 1588230740 completes recovery.
> 2014-10-03 01:57:48,119 INFO [Thread-9216-EventThread]
> zookeeper.RecoveringRegionWatcher(66):
> /hbase/recovering-regions/adfdcf958dd958f0e2ce59072ce2209d znode deleted.
> Region: adfdcf958dd958f0e2ce59072ce2209d completes recovery.
> 2014-10-03 01:57:48,121 INFO [Thread-9216-EventThread]
> zookeeper.RecoveringRegionWatcher(66):
> /hbase/recovering-regions/41d438848305831b61d708a406d5ecde znode deleted.
> Region: 41d438848305831b61d708a406d5ecde completes recovery.
> 2014-10-03 01:57:48,122 INFO [Thread-9216-EventThread]
> zookeeper.RecoveringRegionWatcher(66):
> /hbase/recovering-regions/6a7cada80de2ae5d774fe8cd33bd4cda znode deleted.
> Region: 6a7cada80de2ae5d774fe8cd33bd4cda completes recovery.
> 2014-10-03 01:57:48,124 INFO [Thread-9216-EventThread]
> zookeeper.RecoveringRegionWatcher(66):
> /hbase/recovering-regions/65451bd5b38bd16a31e25b62b3305533 znode deleted.
> Region: 65451bd5b38bd16a31e25b62b3305533 completes recovery.
> 2014-10-03 01:57:48,125 INFO [Thread-9216-EventThread]
> zookeeper.RecoveringRegionWatcher(66):
> /hbase/recovering-regions/07afdc3748894cf2b56e0075272a95a0 znode deleted.
> Region: 07afdc3748894cf2b56e0075272a95a0 completes recovery.
> 2014-10-03 01:57:48,126 INFO [Thread-9216-EventThread]
> zookeeper.RecoveringRegionWatcher(66):
> /hbase/recovering-regions/a4337ad2874ee7e599ca2344fce21583 znode deleted.
> Region: a4337ad2874ee7e599ca2344fce21583 completes recovery.
> 2014-10-03 01:57:48,128 INFO [Thread-9216-EventThread]
> zookeeper.RecoveringRegionWatcher(66):
> /hbase/recovering-regions/9d91d6eafe260ce33e8d7d23ccd13192 znode del
[jira] [Commented] (HBASE-12166) TestDistributedLogSplitting.testMasterStartsUpWithLogReplayWork
[
https://issues.apache.org/jira/browse/HBASE-12166?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14158645#comment-14158645
]
Jimmy Xiang commented on HBASE-12166:
-
[~stack], [~jeffreyz], could you take a look the patch? Thanks.
> TestDistributedLogSplitting.testMasterStartsUpWithLogReplayWork
> ---
>
> Key: HBASE-12166
> URL: https://issues.apache.org/jira/browse/HBASE-12166
> Project: HBase
> Issue Type: Bug
> Components: test, wal
>Reporter: stack
>Assignee: Jimmy Xiang
> Fix For: 2.0.0, 0.99.1
>
> Attachments: 12166.txt, hbase-12166.patch, log.txt
>
>
> See
> https://builds.apache.org/job/PreCommit-HBASE-Build/11204//testReport/org.apache.hadoop.hbase.master/TestDistributedLogSplitting/testMasterStartsUpWithLogReplayWork/
> The namespace region gets stuck. It is never 'recovered' even though we have
> finished log splitting. Here is the main exception:
> {code}
> 4941 2014-10-03 02:00:36,862 DEBUG
> [B.defaultRpcServer.handler=1,queue=0,port=37113] ipc.CallRunner(111):
> B.defaultRpcServer.handler=1,queue=0,port=37113: callId: 211 service:
> ClientService methodName: Get
> size: 99 connection: 67.195.81.144:44526
> 4942 org.apache.hadoop.hbase.exceptions.RegionInRecoveryException:
> hbase:namespace,,1412301462277.eba5d23de65f2718715eeb22edf7edc2. is recovering
> 4943 at
> org.apache.hadoop.hbase.regionserver.HRegion.startRegionOperation(HRegion.java:6058)
> 4944 at
> org.apache.hadoop.hbase.regionserver.HRegion.getScanner(HRegion.java:2086)
> 4945 at
> org.apache.hadoop.hbase.regionserver.HRegion.getScanner(HRegion.java:2072)
> 4946 at org.apache.hadoop.hbase.regionserver.HRegion.get(HRegion.java:5014)
> 4947 at org.apache.hadoop.hbase.regionserver.HRegion.get(HRegion.java:4988)
> 4948 at
> org.apache.hadoop.hbase.regionserver.RSRpcServices.get(RSRpcServices.java:1690)
> 4949 at
> org.apache.hadoop.hbase.protobuf.generated.ClientProtos$ClientService$2.callBlockingMethod(ClientProtos.java:30418)
> 4950 at org.apache.hadoop.hbase.ipc.RpcServer.call(RpcServer.java:2020)
> 4951 at org.apache.hadoop.hbase.ipc.CallRunner.run(CallRunner.java:108)
> 4952 at
> org.apache.hadoop.hbase.ipc.RpcExecutor.consumerLoop(RpcExecutor.java:114)
> 4953 at org.apache.hadoop.hbase.ipc.RpcExecutor$1.run(RpcExecutor.java:94)
> 4954 at java.lang.Thread.run(Thread.java:744)
> {code}
> See how we've finished log splitting long time previous:
> {code}
> 2014-10-03 01:57:48,129 INFO [M_LOG_REPLAY_OPS-asf900:37113-1]
> master.SplitLogManager(294): finished splitting (more than or equal to)
> 197337 bytes in 1 log files in
> [hdfs://localhost:49601/user/jenkins/hbase/WALs/asf900.gq1.ygridcore.net,40732,1412301461887-splitting]
> in 379ms
> {code}
> If I grep for the deleting of znodes on recovery, which is when we set the
> recovering flag to false, I see a bunch of regions but not my namespace one:
> 2014-10-03 01:57:47,330 INFO [Thread-9216-EventThread]
> zookeeper.RecoveringRegionWatcher(66): /hbase/recovering-regions/1588230740
> znode deleted. Region: 1588230740 completes recovery.
> 2014-10-03 01:57:48,119 INFO [Thread-9216-EventThread]
> zookeeper.RecoveringRegionWatcher(66):
> /hbase/recovering-regions/adfdcf958dd958f0e2ce59072ce2209d znode deleted.
> Region: adfdcf958dd958f0e2ce59072ce2209d completes recovery.
> 2014-10-03 01:57:48,121 INFO [Thread-9216-EventThread]
> zookeeper.RecoveringRegionWatcher(66):
> /hbase/recovering-regions/41d438848305831b61d708a406d5ecde znode deleted.
> Region: 41d438848305831b61d708a406d5ecde completes recovery.
> 2014-10-03 01:57:48,122 INFO [Thread-9216-EventThread]
> zookeeper.RecoveringRegionWatcher(66):
> /hbase/recovering-regions/6a7cada80de2ae5d774fe8cd33bd4cda znode deleted.
> Region: 6a7cada80de2ae5d774fe8cd33bd4cda completes recovery.
> 2014-10-03 01:57:48,124 INFO [Thread-9216-EventThread]
> zookeeper.RecoveringRegionWatcher(66):
> /hbase/recovering-regions/65451bd5b38bd16a31e25b62b3305533 znode deleted.
> Region: 65451bd5b38bd16a31e25b62b3305533 completes recovery.
> 2014-10-03 01:57:48,125 INFO [Thread-9216-EventThread]
> zookeeper.RecoveringRegionWatcher(66):
> /hbase/recovering-regions/07afdc3748894cf2b56e0075272a95a0 znode deleted.
> Region: 07afdc3748894cf2b56e0075272a95a0 completes recovery.
> 2014-10-03 01:57:48,126 INFO [Thread-9216-EventThread]
> zookeeper.RecoveringRegionWatcher(66):
> /hbase/recovering-regions/a4337ad2874ee7e599ca2344fce21583 znode deleted.
> Region: a4337ad2874ee7e599ca2344fce21583 completes recovery.
> 2014-10-03 01:57:48,128 INFO [Thread-9216-EventThread]
> zookeeper.RecoveringRegionWatcher(66):
> /hbase/recovering-regions/9d91d6eafe260ce33e8d7d23ccd13192 znode deleted.
> Region: 9d91d6eafe260ce33e8d7d23ccd13192 complete
[jira] [Commented] (HBASE-12166) TestDistributedLogSplitting.testMasterStartsUpWithLogReplayWork
[
https://issues.apache.org/jira/browse/HBASE-12166?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14158641#comment-14158641
]
Jimmy Xiang commented on HBASE-12166:
-
TestMasterObserver should be fixed by the addendumo of HBASE-12167.
> TestDistributedLogSplitting.testMasterStartsUpWithLogReplayWork
> ---
>
> Key: HBASE-12166
> URL: https://issues.apache.org/jira/browse/HBASE-12166
> Project: HBase
> Issue Type: Bug
> Components: test, wal
>Reporter: stack
>Assignee: Jimmy Xiang
> Fix For: 2.0.0, 0.99.1
>
> Attachments: 12166.txt, hbase-12166.patch, log.txt
>
>
> See
> https://builds.apache.org/job/PreCommit-HBASE-Build/11204//testReport/org.apache.hadoop.hbase.master/TestDistributedLogSplitting/testMasterStartsUpWithLogReplayWork/
> The namespace region gets stuck. It is never 'recovered' even though we have
> finished log splitting. Here is the main exception:
> {code}
> 4941 2014-10-03 02:00:36,862 DEBUG
> [B.defaultRpcServer.handler=1,queue=0,port=37113] ipc.CallRunner(111):
> B.defaultRpcServer.handler=1,queue=0,port=37113: callId: 211 service:
> ClientService methodName: Get
> size: 99 connection: 67.195.81.144:44526
> 4942 org.apache.hadoop.hbase.exceptions.RegionInRecoveryException:
> hbase:namespace,,1412301462277.eba5d23de65f2718715eeb22edf7edc2. is recovering
> 4943 at
> org.apache.hadoop.hbase.regionserver.HRegion.startRegionOperation(HRegion.java:6058)
> 4944 at
> org.apache.hadoop.hbase.regionserver.HRegion.getScanner(HRegion.java:2086)
> 4945 at
> org.apache.hadoop.hbase.regionserver.HRegion.getScanner(HRegion.java:2072)
> 4946 at org.apache.hadoop.hbase.regionserver.HRegion.get(HRegion.java:5014)
> 4947 at org.apache.hadoop.hbase.regionserver.HRegion.get(HRegion.java:4988)
> 4948 at
> org.apache.hadoop.hbase.regionserver.RSRpcServices.get(RSRpcServices.java:1690)
> 4949 at
> org.apache.hadoop.hbase.protobuf.generated.ClientProtos$ClientService$2.callBlockingMethod(ClientProtos.java:30418)
> 4950 at org.apache.hadoop.hbase.ipc.RpcServer.call(RpcServer.java:2020)
> 4951 at org.apache.hadoop.hbase.ipc.CallRunner.run(CallRunner.java:108)
> 4952 at
> org.apache.hadoop.hbase.ipc.RpcExecutor.consumerLoop(RpcExecutor.java:114)
> 4953 at org.apache.hadoop.hbase.ipc.RpcExecutor$1.run(RpcExecutor.java:94)
> 4954 at java.lang.Thread.run(Thread.java:744)
> {code}
> See how we've finished log splitting long time previous:
> {code}
> 2014-10-03 01:57:48,129 INFO [M_LOG_REPLAY_OPS-asf900:37113-1]
> master.SplitLogManager(294): finished splitting (more than or equal to)
> 197337 bytes in 1 log files in
> [hdfs://localhost:49601/user/jenkins/hbase/WALs/asf900.gq1.ygridcore.net,40732,1412301461887-splitting]
> in 379ms
> {code}
> If I grep for the deleting of znodes on recovery, which is when we set the
> recovering flag to false, I see a bunch of regions but not my namespace one:
> 2014-10-03 01:57:47,330 INFO [Thread-9216-EventThread]
> zookeeper.RecoveringRegionWatcher(66): /hbase/recovering-regions/1588230740
> znode deleted. Region: 1588230740 completes recovery.
> 2014-10-03 01:57:48,119 INFO [Thread-9216-EventThread]
> zookeeper.RecoveringRegionWatcher(66):
> /hbase/recovering-regions/adfdcf958dd958f0e2ce59072ce2209d znode deleted.
> Region: adfdcf958dd958f0e2ce59072ce2209d completes recovery.
> 2014-10-03 01:57:48,121 INFO [Thread-9216-EventThread]
> zookeeper.RecoveringRegionWatcher(66):
> /hbase/recovering-regions/41d438848305831b61d708a406d5ecde znode deleted.
> Region: 41d438848305831b61d708a406d5ecde completes recovery.
> 2014-10-03 01:57:48,122 INFO [Thread-9216-EventThread]
> zookeeper.RecoveringRegionWatcher(66):
> /hbase/recovering-regions/6a7cada80de2ae5d774fe8cd33bd4cda znode deleted.
> Region: 6a7cada80de2ae5d774fe8cd33bd4cda completes recovery.
> 2014-10-03 01:57:48,124 INFO [Thread-9216-EventThread]
> zookeeper.RecoveringRegionWatcher(66):
> /hbase/recovering-regions/65451bd5b38bd16a31e25b62b3305533 znode deleted.
> Region: 65451bd5b38bd16a31e25b62b3305533 completes recovery.
> 2014-10-03 01:57:48,125 INFO [Thread-9216-EventThread]
> zookeeper.RecoveringRegionWatcher(66):
> /hbase/recovering-regions/07afdc3748894cf2b56e0075272a95a0 znode deleted.
> Region: 07afdc3748894cf2b56e0075272a95a0 completes recovery.
> 2014-10-03 01:57:48,126 INFO [Thread-9216-EventThread]
> zookeeper.RecoveringRegionWatcher(66):
> /hbase/recovering-regions/a4337ad2874ee7e599ca2344fce21583 znode deleted.
> Region: a4337ad2874ee7e599ca2344fce21583 completes recovery.
> 2014-10-03 01:57:48,128 INFO [Thread-9216-EventThread]
> zookeeper.RecoveringRegionWatcher(66):
> /hbase/recovering-regions/9d91d6eafe260ce33e8d7d23ccd13192 znode deleted.
> Region: 9d91d6eafe260ce33e8d7d23ccd13192 comp
[jira] [Updated] (HBASE-11764) Support per cell TTLs
[ https://issues.apache.org/jira/browse/HBASE-11764?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrew Purtell updated HBASE-11764: --- Attachment: HBASE-11764.patch Updated patches for master and 0.98 that adjust implementation of cell TTLs to avoid changes to ColumnTrackers (HBASE-11763, moved out) > Support per cell TTLs > - > > Key: HBASE-11764 > URL: https://issues.apache.org/jira/browse/HBASE-11764 > Project: HBase > Issue Type: Sub-task >Reporter: Andrew Purtell >Assignee: Andrew Purtell > Fix For: 2.0.0, 0.98.7, 0.99.1 > > Attachments: HBASE-11764-0.98.patch, HBASE-11764-0.98.patch, > HBASE-11764.patch, HBASE-11764.patch, HBASE-11764.patch, HBASE-11764.patch, > HBASE-11764.patch, HBASE-11764.patch, HBASE-11764.patch, HBASE-11764.patch, > HBASE-11764.patch > > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (HBASE-11764) Support per cell TTLs
[ https://issues.apache.org/jira/browse/HBASE-11764?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrew Purtell updated HBASE-11764: --- Status: Patch Available (was: Open) > Support per cell TTLs > - > > Key: HBASE-11764 > URL: https://issues.apache.org/jira/browse/HBASE-11764 > Project: HBase > Issue Type: Sub-task >Reporter: Andrew Purtell >Assignee: Andrew Purtell > Fix For: 2.0.0, 0.98.7, 0.99.1 > > Attachments: HBASE-11764-0.98.patch, HBASE-11764-0.98.patch, > HBASE-11764.patch, HBASE-11764.patch, HBASE-11764.patch, HBASE-11764.patch, > HBASE-11764.patch, HBASE-11764.patch, HBASE-11764.patch, HBASE-11764.patch, > HBASE-11764.patch > > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (HBASE-11764) Support per cell TTLs
[ https://issues.apache.org/jira/browse/HBASE-11764?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrew Purtell updated HBASE-11764: --- Attachment: HBASE-11764-0.98.patch > Support per cell TTLs > - > > Key: HBASE-11764 > URL: https://issues.apache.org/jira/browse/HBASE-11764 > Project: HBase > Issue Type: Sub-task >Reporter: Andrew Purtell >Assignee: Andrew Purtell > Fix For: 2.0.0, 0.98.7, 0.99.1 > > Attachments: HBASE-11764-0.98.patch, HBASE-11764-0.98.patch, > HBASE-11764.patch, HBASE-11764.patch, HBASE-11764.patch, HBASE-11764.patch, > HBASE-11764.patch, HBASE-11764.patch, HBASE-11764.patch, HBASE-11764.patch > > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (HBASE-12166) TestDistributedLogSplitting.testMasterStartsUpWithLogReplayWork
[
https://issues.apache.org/jira/browse/HBASE-12166?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14158621#comment-14158621
]
Hadoop QA commented on HBASE-12166:
---
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12672838/hbase-12166.patch
against trunk revision .
ATTACHMENT ID: 12672838
{color:green}+1 @author{color}. The patch does not contain any @author
tags.
{color:red}-1 tests included{color}. The patch doesn't appear to include
any new or modified tests.
Please justify why no new tests are needed for this
patch.
Also please list what manual steps were performed to
verify this patch.
{color:green}+1 javac{color}. The applied patch does not increase the
total number of javac compiler warnings.
{color:green}+1 javac{color}. The applied patch does not increase the
total number of javac compiler warnings.
{color:green}+1 javadoc{color}. The javadoc tool did not generate any
warning messages.
{color:green}+1 findbugs{color}. The patch does not introduce any new
Findbugs (version 2.0.3) warnings.
{color:green}+1 release audit{color}. The applied patch does not increase
the total number of release audit warnings.
{color:green}+1 lineLengths{color}. The patch does not introduce lines
longer than 100
{color:green}+1 site{color}. The mvn site goal succeeds with this patch.
{color:red}-1 core tests{color}. The patch failed these unit tests:
org.apache.hadoop.hbase.coprocessor.TestMasterObserver
org.apache.hadoop.hbase.replication.regionserver.TestRegionReplicaReplicationEndpoint
Test results:
https://builds.apache.org/job/PreCommit-HBASE-Build/11211//testReport/
Findbugs warnings:
https://builds.apache.org/job/PreCommit-HBASE-Build/11211//artifact/patchprocess/newPatchFindbugsWarningshbase-common.html
Findbugs warnings:
https://builds.apache.org/job/PreCommit-HBASE-Build/11211//artifact/patchprocess/newPatchFindbugsWarningshbase-client.html
Findbugs warnings:
https://builds.apache.org/job/PreCommit-HBASE-Build/11211//artifact/patchprocess/newPatchFindbugsWarningshbase-annotations.html
Findbugs warnings:
https://builds.apache.org/job/PreCommit-HBASE-Build/11211//artifact/patchprocess/newPatchFindbugsWarningshbase-hadoop-compat.html
Findbugs warnings:
https://builds.apache.org/job/PreCommit-HBASE-Build/11211//artifact/patchprocess/newPatchFindbugsWarningshbase-server.html
Findbugs warnings:
https://builds.apache.org/job/PreCommit-HBASE-Build/11211//artifact/patchprocess/newPatchFindbugsWarningshbase-prefix-tree.html
Findbugs warnings:
https://builds.apache.org/job/PreCommit-HBASE-Build/11211//artifact/patchprocess/newPatchFindbugsWarningshbase-protocol.html
Findbugs warnings:
https://builds.apache.org/job/PreCommit-HBASE-Build/11211//artifact/patchprocess/newPatchFindbugsWarningshbase-thrift.html
Findbugs warnings:
https://builds.apache.org/job/PreCommit-HBASE-Build/11211//artifact/patchprocess/newPatchFindbugsWarningshbase-examples.html
Findbugs warnings:
https://builds.apache.org/job/PreCommit-HBASE-Build/11211//artifact/patchprocess/newPatchFindbugsWarningshbase-hadoop2-compat.html
Console output:
https://builds.apache.org/job/PreCommit-HBASE-Build/11211//console
This message is automatically generated.
> TestDistributedLogSplitting.testMasterStartsUpWithLogReplayWork
> ---
>
> Key: HBASE-12166
> URL: https://issues.apache.org/jira/browse/HBASE-12166
> Project: HBase
> Issue Type: Bug
> Components: test, wal
>Reporter: stack
>Assignee: Jimmy Xiang
> Fix For: 2.0.0, 0.99.1
>
> Attachments: 12166.txt, hbase-12166.patch, log.txt
>
>
> See
> https://builds.apache.org/job/PreCommit-HBASE-Build/11204//testReport/org.apache.hadoop.hbase.master/TestDistributedLogSplitting/testMasterStartsUpWithLogReplayWork/
> The namespace region gets stuck. It is never 'recovered' even though we have
> finished log splitting. Here is the main exception:
> {code}
> 4941 2014-10-03 02:00:36,862 DEBUG
> [B.defaultRpcServer.handler=1,queue=0,port=37113] ipc.CallRunner(111):
> B.defaultRpcServer.handler=1,queue=0,port=37113: callId: 211 service:
> ClientService methodName: Get
> size: 99 connection: 67.195.81.144:44526
> 4942 org.apache.hadoop.hbase.exceptions.RegionInRecoveryException:
> hbase:namespace,,1412301462277.eba5d23de65f2718715eeb22edf7edc2. is recovering
> 4943 at
> org.apache.hadoop.hbase.regionserver.HRegion.startRegionOperation(HRegion.java:6058)
> 4944 at
> org.apache.hadoop.hbase.regionserver.HRegion.getScanner(HRegion.java:2086)
> 4945 at
> org.apache.hadoop.hbase.regionserver.HRegion.getSc
[jira] [Commented] (HBASE-12075) Preemptive Fast Fail
[ https://issues.apache.org/jira/browse/HBASE-12075?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14158613#comment-14158613 ] Manukranth Kolloju commented on HBASE-12075: Is 900 for surefire.timeout too low? > Preemptive Fast Fail > > > Key: HBASE-12075 > URL: https://issues.apache.org/jira/browse/HBASE-12075 > Project: HBase > Issue Type: Sub-task > Components: Client >Affects Versions: 0.99.0, 2.0.0, 0.98.6.1 >Reporter: Manukranth Kolloju >Assignee: Manukranth Kolloju > Attachments: 0001-Add-a-test-case-for-Preemptive-Fast-Fail.patch, > 0001-HBASE-12075-Implement-Preemptive-Fast-Fail.patch, > 0001-Implement-Preemptive-Fast-Fail.patch, > 0001-Implement-Preemptive-Fast-Fail.patch, > 0001-Implement-Preemptive-Fast-Fail.patch, > 0001-Implement-Preemptive-Fast-Fail.patch, > 0001-Implement-Preemptive-Fast-Fail.patch > > > In multi threaded clients, we use a feature developed on 0.89-fb branch > called Preemptive Fast Fail. This allows the client threads which would > potentially fail, fail fast. The idea behind this feature is that we allow, > among the hundreds of client threads, one thread to try and establish > connection with the regionserver and if that succeeds, we mark it as a live > node again. Meanwhile, other threads which are trying to establish connection > to the same server would ideally go into the timeouts which is effectively > unfruitful. We can in those cases return appropriate exceptions to those > clients instead of letting them retry. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (HBASE-12136) Race condition between client adding tableCF replication znode and server triggering TableCFsTracker
[ https://issues.apache.org/jira/browse/HBASE-12136?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14158610#comment-14158610 ] Hudson commented on HBASE-12136: FAILURE: Integrated in HBase-0.98-on-Hadoop-1.1 #539 (See [https://builds.apache.org/job/HBase-0.98-on-Hadoop-1.1/539/]) HBASE-12136 Race condition between client adding tableCF replication znode and server triggering TableCFsTracker (Virag Kothari) (tedyu: rev a9138d7f96910f09e52b226248ccb169c98d6bd4) * hbase-client/src/main/java/org/apache/hadoop/hbase/replication/ReplicationPeersZKImpl.java > Race condition between client adding tableCF replication znode and server > triggering TableCFsTracker > - > > Key: HBASE-12136 > URL: https://issues.apache.org/jira/browse/HBASE-12136 > Project: HBase > Issue Type: Bug > Components: Replication >Affects Versions: 0.98.6 >Reporter: Virag Kothari >Assignee: Virag Kothari > Fix For: 2.0.0, 0.98.7, 0.99.1 > > Attachments: HBASE-12136-0.98.patch, HBASE-12136.patch > > > In ReplicationPeersZKImpl.addPeer(), there is a race between client creating > tableCf znode and the server triggering TableCFsTracker. If the server wins, > it wont be able to read the data set on tableCF znode and replication will > be misconfigured -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (HBASE-12167) NPE in AssignmentManager
[
https://issues.apache.org/jira/browse/HBASE-12167?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14158598#comment-14158598
]
Jimmy Xiang commented on HBASE-12167:
-
Checked in an addendum to fix TestMasterObserver.
> NPE in AssignmentManager
>
>
> Key: HBASE-12167
> URL: https://issues.apache.org/jira/browse/HBASE-12167
> Project: HBase
> Issue Type: Bug
>Reporter: Jimmy Xiang
>Assignee: Jimmy Xiang
> Fix For: 2.0.0, 0.99.1
>
> Attachments: hbase-12167.patch
>
>
> If we can't find a region plan, we should check.
> {noformat}
> 2014-10-02 18:36:27,719 ERROR [MASTER_SERVER_OPERATIONS-a2424:20020-0]
> executor.EventHandler: Caught throwable while processing event
> M_SERVER_SHUTDOWN
> java.lang.NullPointerException
> at
> org.apache.hadoop.hbase.master.AssignmentManager.assign(AssignmentManager.java:1417)
> at
> org.apache.hadoop.hbase.master.AssignmentManager.assign(AssignmentManager.java:1409)
> at
> org.apache.hadoop.hbase.master.handler.ServerShutdownHandler.process(ServerShutdownHandler.java:271)
> at
> org.apache.hadoop.hbase.executor.EventHandler.run(EventHandler.java:128)
> at
> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145)
> at
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)
> at java.lang.Thread.run(Thread.java:724)
> {noformat}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (HBASE-12167) NPE in AssignmentManager
[
https://issues.apache.org/jira/browse/HBASE-12167?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jimmy Xiang updated HBASE-12167:
Resolution: Fixed
Hadoop Flags: Reviewed
Status: Resolved (was: Patch Available)
Integrated into branch 1 and master. Thanks.
> NPE in AssignmentManager
>
>
> Key: HBASE-12167
> URL: https://issues.apache.org/jira/browse/HBASE-12167
> Project: HBase
> Issue Type: Bug
>Reporter: Jimmy Xiang
>Assignee: Jimmy Xiang
> Fix For: 2.0.0, 0.99.1
>
> Attachments: hbase-12167.patch
>
>
> If we can't find a region plan, we should check.
> {noformat}
> 2014-10-02 18:36:27,719 ERROR [MASTER_SERVER_OPERATIONS-a2424:20020-0]
> executor.EventHandler: Caught throwable while processing event
> M_SERVER_SHUTDOWN
> java.lang.NullPointerException
> at
> org.apache.hadoop.hbase.master.AssignmentManager.assign(AssignmentManager.java:1417)
> at
> org.apache.hadoop.hbase.master.AssignmentManager.assign(AssignmentManager.java:1409)
> at
> org.apache.hadoop.hbase.master.handler.ServerShutdownHandler.process(ServerShutdownHandler.java:271)
> at
> org.apache.hadoop.hbase.executor.EventHandler.run(EventHandler.java:128)
> at
> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145)
> at
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)
> at java.lang.Thread.run(Thread.java:724)
> {noformat}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Resolved] (HBASE-12136) Race condition between client adding tableCF replication znode and server triggering TableCFsTracker
[ https://issues.apache.org/jira/browse/HBASE-12136?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ted Yu resolved HBASE-12136. Resolution: Fixed Oops, TestTableName is not related to the change in this JIRA. > Race condition between client adding tableCF replication znode and server > triggering TableCFsTracker > - > > Key: HBASE-12136 > URL: https://issues.apache.org/jira/browse/HBASE-12136 > Project: HBase > Issue Type: Bug > Components: Replication >Affects Versions: 0.98.6 >Reporter: Virag Kothari >Assignee: Virag Kothari > Fix For: 2.0.0, 0.98.7, 0.99.1 > > Attachments: HBASE-12136-0.98.patch, HBASE-12136.patch > > > In ReplicationPeersZKImpl.addPeer(), there is a race between client creating > tableCf znode and the server triggering TableCFsTracker. If the server wins, > it wont be able to read the data set on tableCF znode and replication will > be misconfigured -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (HBASE-12136) Race condition between client adding tableCF replication znode and server triggering TableCFsTracker
[ https://issues.apache.org/jira/browse/HBASE-12136?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14158590#comment-14158590 ] Virag Kothari commented on HBASE-12136: --- In https://builds.apache.org/job/HBase-1.0/271, org.apache.hadoop.hbase.util.TestTableName.testValueOf fails. That might be related to HBASE-12156 > Race condition between client adding tableCF replication znode and server > triggering TableCFsTracker > - > > Key: HBASE-12136 > URL: https://issues.apache.org/jira/browse/HBASE-12136 > Project: HBase > Issue Type: Bug > Components: Replication >Affects Versions: 0.98.6 >Reporter: Virag Kothari >Assignee: Virag Kothari > Fix For: 2.0.0, 0.98.7, 0.99.1 > > Attachments: HBASE-12136-0.98.patch, HBASE-12136.patch > > > In ReplicationPeersZKImpl.addPeer(), there is a race between client creating > tableCf znode and the server triggering TableCFsTracker. If the server wins, > it wont be able to read the data set on tableCF znode and replication will > be misconfigured -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (HBASE-12075) Preemptive Fast Fail
[
https://issues.apache.org/jira/browse/HBASE-12075?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14158584#comment-14158584
]
Hadoop QA commented on HBASE-12075:
---
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12671882/0001-HBASE-12075-Implement-Preemptive-Fast-Fail.patch
against trunk revision .
ATTACHMENT ID: 12671882
{color:green}+1 @author{color}. The patch does not contain any @author
tags.
{color:green}+1 tests included{color}. The patch appears to include 8 new
or modified tests.
{color:green}+1 javac{color}. The applied patch does not increase the
total number of javac compiler warnings.
{color:green}+1 javac{color}. The applied patch does not increase the
total number of javac compiler warnings.
{color:green}+1 javadoc{color}. The javadoc tool did not generate any
warning messages.
{color:green}+1 findbugs{color}. The patch does not introduce any new
Findbugs (version 2.0.3) warnings.
{color:green}+1 release audit{color}. The applied patch does not increase
the total number of release audit warnings.
{color:green}+1 lineLengths{color}. The patch does not introduce lines
longer than 100
{color:green}+1 site{color}. The mvn site goal succeeds with this patch.
{color:red}-1 core tests{color}. The patch failed these unit tests:
org.apache.hadoop.hbase.replication.regionserver.TestRegionReplicaReplicationEndpointNoMaster
org.apache.hadoop.hbase.master.TestDistributedLogSplitting
{color:red}-1 core zombie tests{color}. There are 1 zombie test(s):
at
org.apache.hadoop.hbase.master.TestMasterNoCluster.testNotPullingDeadRegionServerFromZK(TestMasterNoCluster.java:306)
Test results:
https://builds.apache.org/job/PreCommit-HBASE-Build/11209//testReport/
Findbugs warnings:
https://builds.apache.org/job/PreCommit-HBASE-Build/11209//artifact/patchprocess/newPatchFindbugsWarningshbase-hadoop-compat.html
Findbugs warnings:
https://builds.apache.org/job/PreCommit-HBASE-Build/11209//artifact/patchprocess/newPatchFindbugsWarningshbase-prefix-tree.html
Findbugs warnings:
https://builds.apache.org/job/PreCommit-HBASE-Build/11209//artifact/patchprocess/newPatchFindbugsWarningshbase-examples.html
Findbugs warnings:
https://builds.apache.org/job/PreCommit-HBASE-Build/11209//artifact/patchprocess/newPatchFindbugsWarningshbase-server.html
Findbugs warnings:
https://builds.apache.org/job/PreCommit-HBASE-Build/11209//artifact/patchprocess/newPatchFindbugsWarningshbase-common.html
Findbugs warnings:
https://builds.apache.org/job/PreCommit-HBASE-Build/11209//artifact/patchprocess/newPatchFindbugsWarningshbase-protocol.html
Findbugs warnings:
https://builds.apache.org/job/PreCommit-HBASE-Build/11209//artifact/patchprocess/newPatchFindbugsWarningshbase-client.html
Findbugs warnings:
https://builds.apache.org/job/PreCommit-HBASE-Build/11209//artifact/patchprocess/newPatchFindbugsWarningshbase-thrift.html
Findbugs warnings:
https://builds.apache.org/job/PreCommit-HBASE-Build/11209//artifact/patchprocess/newPatchFindbugsWarningshbase-hadoop2-compat.html
Findbugs warnings:
https://builds.apache.org/job/PreCommit-HBASE-Build/11209//artifact/patchprocess/newPatchFindbugsWarningshbase-annotations.html
Console output:
https://builds.apache.org/job/PreCommit-HBASE-Build/11209//console
This message is automatically generated.
> Preemptive Fast Fail
>
>
> Key: HBASE-12075
> URL: https://issues.apache.org/jira/browse/HBASE-12075
> Project: HBase
> Issue Type: Sub-task
> Components: Client
>Affects Versions: 0.99.0, 2.0.0, 0.98.6.1
>Reporter: Manukranth Kolloju
>Assignee: Manukranth Kolloju
> Attachments: 0001-Add-a-test-case-for-Preemptive-Fast-Fail.patch,
> 0001-HBASE-12075-Implement-Preemptive-Fast-Fail.patch,
> 0001-Implement-Preemptive-Fast-Fail.patch,
> 0001-Implement-Preemptive-Fast-Fail.patch,
> 0001-Implement-Preemptive-Fast-Fail.patch,
> 0001-Implement-Preemptive-Fast-Fail.patch,
> 0001-Implement-Preemptive-Fast-Fail.patch
>
>
> In multi threaded clients, we use a feature developed on 0.89-fb branch
> called Preemptive Fast Fail. This allows the client threads which would
> potentially fail, fail fast. The idea behind this feature is that we allow,
> among the hundreds of client threads, one thread to try and establish
> connection with the regionserver and if that succeeds, we mark it as a live
> node again. Meanwhile, other threads which are trying to establish connection
> to the same server would ideally go into the timeouts which is effectively
> unfruitful. We can in those cases return appropriate exceptions to those
> clients instead of letting them retry.
--
This message was s
[jira] [Reopened] (HBASE-12136) Race condition between client adding tableCF replication znode and server triggering TableCFsTracker
[ https://issues.apache.org/jira/browse/HBASE-12136?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ted Yu reopened HBASE-12136: Virag: Any idea of the test failure in branch-1 ? I couldn't reproduce locally. > Race condition between client adding tableCF replication znode and server > triggering TableCFsTracker > - > > Key: HBASE-12136 > URL: https://issues.apache.org/jira/browse/HBASE-12136 > Project: HBase > Issue Type: Bug > Components: Replication >Affects Versions: 0.98.6 >Reporter: Virag Kothari >Assignee: Virag Kothari > Fix For: 2.0.0, 0.98.7, 0.99.1 > > Attachments: HBASE-12136-0.98.patch, HBASE-12136.patch > > > In ReplicationPeersZKImpl.addPeer(), there is a race between client creating > tableCf znode and the server triggering TableCFsTracker. If the server wins, > it wont be able to read the data set on tableCF znode and replication will > be misconfigured -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (HBASE-12136) Race condition between client adding tableCF replication znode and server triggering TableCFsTracker
[ https://issues.apache.org/jira/browse/HBASE-12136?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14158575#comment-14158575 ] Hudson commented on HBASE-12136: FAILURE: Integrated in HBase-1.0 #271 (See [https://builds.apache.org/job/HBase-1.0/271/]) HBASE-12136 Race condition between client adding tableCF replication znode and server triggering TableCFsTracker (Virag Kothari) (tedyu: rev 6b95b4a8a4a49dc7877271118c36d5e916d336ab) * hbase-client/src/main/java/org/apache/hadoop/hbase/replication/ReplicationPeerZKImpl.java * hbase-client/src/main/java/org/apache/hadoop/hbase/replication/ReplicationPeersZKImpl.java > Race condition between client adding tableCF replication znode and server > triggering TableCFsTracker > - > > Key: HBASE-12136 > URL: https://issues.apache.org/jira/browse/HBASE-12136 > Project: HBase > Issue Type: Bug > Components: Replication >Affects Versions: 0.98.6 >Reporter: Virag Kothari >Assignee: Virag Kothari > Fix For: 2.0.0, 0.98.7, 0.99.1 > > Attachments: HBASE-12136-0.98.patch, HBASE-12136.patch > > > In ReplicationPeersZKImpl.addPeer(), there is a race between client creating > tableCf znode and the server triggering TableCFsTracker. If the server wins, > it wont be able to read the data set on tableCF znode and replication will > be misconfigured -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (HBASE-12126) Region server coprocessor endpoint
[ https://issues.apache.org/jira/browse/HBASE-12126?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Virag Kothari updated HBASE-12126: -- Attachment: HBASE-12126-0.98_1.patch Updated the 98 patch with SingletonCoprocessorService interface > Region server coprocessor endpoint > -- > > Key: HBASE-12126 > URL: https://issues.apache.org/jira/browse/HBASE-12126 > Project: HBase > Issue Type: Bug > Components: Coprocessors >Affects Versions: 0.98.6 >Reporter: Virag Kothari >Assignee: Virag Kothari > Attachments: HBASE-12126-0.98.patch, HBASE-12126-0.98_1.patch > > > Utility to make endpoint calls against region server -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (HBASE-12136) Race condition between client adding tableCF replication znode and server triggering TableCFsTracker
[ https://issues.apache.org/jira/browse/HBASE-12136?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14158556#comment-14158556 ] Ted Yu commented on HBASE-12136: There was a conflict in hbase-client/src/main/java/org/apache/hadoop/hbase/replication/ReplicationPeersZKImpl.java which I resolved. Integrated to 0.98, branch-1 and master Thanks for the contribution, Virag > Race condition between client adding tableCF replication znode and server > triggering TableCFsTracker > - > > Key: HBASE-12136 > URL: https://issues.apache.org/jira/browse/HBASE-12136 > Project: HBase > Issue Type: Bug > Components: Replication >Affects Versions: 0.98.6 >Reporter: Virag Kothari >Assignee: Virag Kothari > Fix For: 2.0.0, 0.98.7, 0.99.1 > > Attachments: HBASE-12136-0.98.patch, HBASE-12136.patch > > > In ReplicationPeersZKImpl.addPeer(), there is a race between client creating > tableCf znode and the server triggering TableCFsTracker. If the server wins, > it wont be able to read the data set on tableCF znode and replication will > be misconfigured -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (HBASE-12136) Race condition between client adding tableCF replication znode and server triggering TableCFsTracker
[ https://issues.apache.org/jira/browse/HBASE-12136?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ted Yu updated HBASE-12136: --- Resolution: Fixed Hadoop Flags: Reviewed Status: Resolved (was: Patch Available) > Race condition between client adding tableCF replication znode and server > triggering TableCFsTracker > - > > Key: HBASE-12136 > URL: https://issues.apache.org/jira/browse/HBASE-12136 > Project: HBase > Issue Type: Bug > Components: Replication >Affects Versions: 0.98.6 >Reporter: Virag Kothari >Assignee: Virag Kothari > Fix For: 2.0.0, 0.98.7, 0.99.1 > > Attachments: HBASE-12136-0.98.patch, HBASE-12136.patch > > > In ReplicationPeersZKImpl.addPeer(), there is a race between client creating > tableCf znode and the server triggering TableCFsTracker. If the server wins, > it wont be able to read the data set on tableCF znode and replication will > be misconfigured -- This message was sent by Atlassian JIRA (v6.3.4#6332)
