[jira] [Commented] (HBASE-9387) Region could get lost during assignment
[
https://issues.apache.org/jira/browse/HBASE-9387?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13755444#comment-13755444
]
Hadoop QA commented on HBASE-9387:
--
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12600925/9387-v7.txt
against trunk revision .
{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 hadoop1.0{color}. The patch compiles against the hadoop
1.0 profile.
{color:green}+1 hadoop2.0{color}. The patch compiles against the hadoop
2.0 profile.
{color:green}+1 javadoc{color}. The javadoc tool did not generate any
warning messages.
{color:green}+1 javac{color}. The applied patch does not increase the
total number of javac compiler warnings.
{color:red}-1 findbugs{color}. The patch appears to introduce 1 new
Findbugs (version 1.3.9) 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/7003//testReport/
Findbugs warnings:
https://builds.apache.org/job/PreCommit-HBASE-Build/7003//artifact/trunk/patchprocess/newPatchFindbugsWarningshbase-protocol.html
Findbugs warnings:
https://builds.apache.org/job/PreCommit-HBASE-Build/7003//artifact/trunk/patchprocess/newPatchFindbugsWarningshbase-client.html
Findbugs warnings:
https://builds.apache.org/job/PreCommit-HBASE-Build/7003//artifact/trunk/patchprocess/newPatchFindbugsWarningshbase-examples.html
Findbugs warnings:
https://builds.apache.org/job/PreCommit-HBASE-Build/7003//artifact/trunk/patchprocess/newPatchFindbugsWarningshbase-hadoop1-compat.html
Findbugs warnings:
https://builds.apache.org/job/PreCommit-HBASE-Build/7003//artifact/trunk/patchprocess/newPatchFindbugsWarningshbase-prefix-tree.html
Findbugs warnings:
https://builds.apache.org/job/PreCommit-HBASE-Build/7003//artifact/trunk/patchprocess/newPatchFindbugsWarningshbase-common.html
Findbugs warnings:
https://builds.apache.org/job/PreCommit-HBASE-Build/7003//artifact/trunk/patchprocess/newPatchFindbugsWarningshbase-server.html
Findbugs warnings:
https://builds.apache.org/job/PreCommit-HBASE-Build/7003//artifact/trunk/patchprocess/newPatchFindbugsWarningshbase-hadoop-compat.html
Console output:
https://builds.apache.org/job/PreCommit-HBASE-Build/7003//console
This message is automatically generated.
> Region could get lost during assignment
> ---
>
> Key: HBASE-9387
> URL: https://issues.apache.org/jira/browse/HBASE-9387
> Project: HBase
> Issue Type: Bug
> Components: Region Assignment
>Affects Versions: 0.95.2
>Reporter: Ted Yu
>Assignee: Ted Yu
>Priority: Critical
> Attachments: 9387-v1.txt, 9387-v3.txt, 9387-v4.2.txt, 9387-v4.3.txt,
> 9387-v4.4.txt, 9387-v4.txt, 9387-v5.txt, 9387-v6.txt, 9387-v7.txt,
> hbase-9387.patch, org.apache.hadoop.hbase.TestFullLogReconstruction-output.txt
>
>
> I observed test timeout running against hadoop 2.1.0 with distributed log
> replay turned on.
> Looks like region state for 1588230740 became inconsistent between master and
> the surviving region server:
> {code}
> 2013-08-29 22:15:34,180 INFO [AM.ZK.Worker-pool2-t4]
> master.RegionStates(299): Onlined 1588230740 on
> kiyo.gq1.ygridcore.net,57016,1377814510039
> ...
> 2013-08-29 22:15:34,587 DEBUG [Thread-221]
> client.HConnectionManager$HConnectionImplementation(1269): locateRegionInMeta
> parentTable=hbase:meta, metaLocation={region=hbase:meta,,1.1588230740,
> hostname=kiyo.gq1.ygridcore.net,57016,1377814510039, seqNum=0}, attempt=2 of
> 35 failed; retrying after sleep of 302 because:
> org.apache.hadoop.hbase.exceptions.RegionOpeningException: Region is being
> opened: 1588230740
> at
> org.apache.hadoop.hbase.regionserver.HRegionServer.getRegionByEncodedName(HRegionServer.java:2574)
> at
> org.apache.hadoop.hbase.regionserver.HRegionServer.getRegion(HRegionServer.java:3949)
> at
> org.apache.hadoop.hbase.regionserver.HRegionServer.get(HRegionServer.java:2733)
> at
> org.apache.hadoop.hbase.protobuf.generated.ClientProtos$ClientService$2.callBlockingMethod(ClientProtos.java:26965)
> at org.apache.hadoop.hbase.ipc.RpcServer.call(RpcServer.java:2063)
> at
> org.apache.hadoop.hbase.ipc.RpcServer$CallRunner.run(RpcServer.java:1800)
>
[jira] [Resolved] (HBASE-1473) Detach UI from servers or "Where is my cluster summary when 10 masters and current one died"?
[ https://issues.apache.org/jira/browse/HBASE-1473?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] stack resolved HBASE-1473. -- Resolution: Duplicate Resolving as duplicate of HBASE-9404. It has more detail. > Detach UI from servers or "Where is my cluster summary when 10 masters and > current one died"? > - > > Key: HBASE-1473 > URL: https://issues.apache.org/jira/browse/HBASE-1473 > Project: HBase > Issue Type: Improvement >Reporter: stack > > UI can run distinct from master. Can ask zk who master is then ask master > questions to display data (JMX?). Could probably do same for the > regionserver UIs. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (HBASE-9404) Create Monitor Daemon instead of current web ui's
[ https://issues.apache.org/jira/browse/HBASE-9404?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13755419#comment-13755419 ] Nick Dimiduk commented on HBASE-9404: - See also ElasticSearch Head console thingy, or Mesos UI. > Create Monitor Daemon instead of current web ui's > - > > Key: HBASE-9404 > URL: https://issues.apache.org/jira/browse/HBASE-9404 > Project: HBase > Issue Type: Improvement > Components: UI >Affects Versions: 0.98.0 >Reporter: Elliott Clark > > It's hard to get designers and front end developers to iterate on our web ui, > partly because it's not well separated, and partly because it's in java > jsp/jamon. It would be awesome to have something like Accumulo's monitor. > Have all of the current daemons just publish everything through json and > remove the current UI. Then we can separate the ui out into a monitor daemon > that's just UI. > This would do a couple of things: > * force us to publish everything that's interesting though the > metrics system. (Lots of stuff is there but some stuff isn't there.) > * remove a lot of resources from our hbase-server jar. > * make it easier to add graphing other features to the ui. > * allow us to remove some things from the rs -> master heart beat. > * encourage front end developers to get involved (wishful ?) -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (HBASE-9387) Region could get lost during assignment
[
https://issues.apache.org/jira/browse/HBASE-9387?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13755415#comment-13755415
]
Hadoop QA commented on HBASE-9387:
--
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12600921/9387-v6.txt
against trunk revision .
{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 hadoop1.0{color}. The patch compiles against the hadoop
1.0 profile.
{color:green}+1 hadoop2.0{color}. The patch compiles against the hadoop
2.0 profile.
{color:green}+1 javadoc{color}. The javadoc tool did not generate any
warning messages.
{color:green}+1 javac{color}. The applied patch does not increase the
total number of javac compiler warnings.
{color:red}-1 findbugs{color}. The patch appears to introduce 1 new
Findbugs (version 1.3.9) 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/7002//testReport/
Findbugs warnings:
https://builds.apache.org/job/PreCommit-HBASE-Build/7002//artifact/trunk/patchprocess/newPatchFindbugsWarningshbase-prefix-tree.html
Findbugs warnings:
https://builds.apache.org/job/PreCommit-HBASE-Build/7002//artifact/trunk/patchprocess/newPatchFindbugsWarningshbase-client.html
Findbugs warnings:
https://builds.apache.org/job/PreCommit-HBASE-Build/7002//artifact/trunk/patchprocess/newPatchFindbugsWarningshbase-common.html
Findbugs warnings:
https://builds.apache.org/job/PreCommit-HBASE-Build/7002//artifact/trunk/patchprocess/newPatchFindbugsWarningshbase-protocol.html
Findbugs warnings:
https://builds.apache.org/job/PreCommit-HBASE-Build/7002//artifact/trunk/patchprocess/newPatchFindbugsWarningshbase-server.html
Findbugs warnings:
https://builds.apache.org/job/PreCommit-HBASE-Build/7002//artifact/trunk/patchprocess/newPatchFindbugsWarningshbase-hadoop1-compat.html
Findbugs warnings:
https://builds.apache.org/job/PreCommit-HBASE-Build/7002//artifact/trunk/patchprocess/newPatchFindbugsWarningshbase-examples.html
Findbugs warnings:
https://builds.apache.org/job/PreCommit-HBASE-Build/7002//artifact/trunk/patchprocess/newPatchFindbugsWarningshbase-hadoop-compat.html
Console output:
https://builds.apache.org/job/PreCommit-HBASE-Build/7002//console
This message is automatically generated.
> Region could get lost during assignment
> ---
>
> Key: HBASE-9387
> URL: https://issues.apache.org/jira/browse/HBASE-9387
> Project: HBase
> Issue Type: Bug
> Components: Region Assignment
>Affects Versions: 0.95.2
>Reporter: Ted Yu
>Assignee: Ted Yu
>Priority: Critical
> Attachments: 9387-v1.txt, 9387-v3.txt, 9387-v4.2.txt, 9387-v4.3.txt,
> 9387-v4.4.txt, 9387-v4.txt, 9387-v5.txt, 9387-v6.txt, 9387-v7.txt,
> hbase-9387.patch, org.apache.hadoop.hbase.TestFullLogReconstruction-output.txt
>
>
> I observed test timeout running against hadoop 2.1.0 with distributed log
> replay turned on.
> Looks like region state for 1588230740 became inconsistent between master and
> the surviving region server:
> {code}
> 2013-08-29 22:15:34,180 INFO [AM.ZK.Worker-pool2-t4]
> master.RegionStates(299): Onlined 1588230740 on
> kiyo.gq1.ygridcore.net,57016,1377814510039
> ...
> 2013-08-29 22:15:34,587 DEBUG [Thread-221]
> client.HConnectionManager$HConnectionImplementation(1269): locateRegionInMeta
> parentTable=hbase:meta, metaLocation={region=hbase:meta,,1.1588230740,
> hostname=kiyo.gq1.ygridcore.net,57016,1377814510039, seqNum=0}, attempt=2 of
> 35 failed; retrying after sleep of 302 because:
> org.apache.hadoop.hbase.exceptions.RegionOpeningException: Region is being
> opened: 1588230740
> at
> org.apache.hadoop.hbase.regionserver.HRegionServer.getRegionByEncodedName(HRegionServer.java:2574)
> at
> org.apache.hadoop.hbase.regionserver.HRegionServer.getRegion(HRegionServer.java:3949)
> at
> org.apache.hadoop.hbase.regionserver.HRegionServer.get(HRegionServer.java:2733)
> at
> org.apache.hadoop.hbase.protobuf.generated.ClientProtos$ClientService$2.callBlockingMethod(ClientProtos.java:26965)
> at org.apache.hadoop.hbase.ipc.RpcServer.call(RpcServer.java:2063)
> at
> org.apache.hadoop.hbase.ipc.RpcServer$CallRunner.run(RpcServer.java:1800)
>
[jira] [Updated] (HBASE-9387) Region could get lost during assignment
[
https://issues.apache.org/jira/browse/HBASE-9387?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ted Yu updated HBASE-9387:
--
Attachment: 9387-v7.txt
Patch v7 adds testRegionServerAbortionDueToFailureTransitioningToOpened in
TestOpenRegionHandler which simulates the scenario described in this JIRA
> Region could get lost during assignment
> ---
>
> Key: HBASE-9387
> URL: https://issues.apache.org/jira/browse/HBASE-9387
> Project: HBase
> Issue Type: Bug
> Components: Region Assignment
>Affects Versions: 0.95.2
>Reporter: Ted Yu
>Assignee: Ted Yu
>Priority: Critical
> Attachments: 9387-v1.txt, 9387-v3.txt, 9387-v4.2.txt, 9387-v4.3.txt,
> 9387-v4.4.txt, 9387-v4.txt, 9387-v5.txt, 9387-v6.txt, 9387-v7.txt,
> hbase-9387.patch, org.apache.hadoop.hbase.TestFullLogReconstruction-output.txt
>
>
> I observed test timeout running against hadoop 2.1.0 with distributed log
> replay turned on.
> Looks like region state for 1588230740 became inconsistent between master and
> the surviving region server:
> {code}
> 2013-08-29 22:15:34,180 INFO [AM.ZK.Worker-pool2-t4]
> master.RegionStates(299): Onlined 1588230740 on
> kiyo.gq1.ygridcore.net,57016,1377814510039
> ...
> 2013-08-29 22:15:34,587 DEBUG [Thread-221]
> client.HConnectionManager$HConnectionImplementation(1269): locateRegionInMeta
> parentTable=hbase:meta, metaLocation={region=hbase:meta,,1.1588230740,
> hostname=kiyo.gq1.ygridcore.net,57016,1377814510039, seqNum=0}, attempt=2 of
> 35 failed; retrying after sleep of 302 because:
> org.apache.hadoop.hbase.exceptions.RegionOpeningException: Region is being
> opened: 1588230740
> at
> org.apache.hadoop.hbase.regionserver.HRegionServer.getRegionByEncodedName(HRegionServer.java:2574)
> at
> org.apache.hadoop.hbase.regionserver.HRegionServer.getRegion(HRegionServer.java:3949)
> at
> org.apache.hadoop.hbase.regionserver.HRegionServer.get(HRegionServer.java:2733)
> at
> org.apache.hadoop.hbase.protobuf.generated.ClientProtos$ClientService$2.callBlockingMethod(ClientProtos.java:26965)
> at org.apache.hadoop.hbase.ipc.RpcServer.call(RpcServer.java:2063)
> at
> org.apache.hadoop.hbase.ipc.RpcServer$CallRunner.run(RpcServer.java:1800)
> at
> org.apache.hadoop.hbase.ipc.SimpleRpcScheduler.consumerLoop(SimpleRpcScheduler.java:165)
> at
> org.apache.hadoop.hbase.ipc.SimpleRpcScheduler.access$000(SimpleRpcScheduler.java:41)
> {code}
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (HBASE-5954) Allow proper fsync support for HBase
[ https://issues.apache.org/jira/browse/HBASE-5954?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13755411#comment-13755411 ] haosdent commented on HBASE-5954: - When we use the hsync of HDFS, the JVM in datanode will call fsync or fdatasync to ensure the dirty data of file is flush to stable storage. When I do the test as same as [~lhofhansl], I have this test result: Without WAL/HFile sync: ~13s With WAL sync, Without HFile sync: ~120s (Sorry, I make some input mistakes before.) I think you may unclear about the differences between "data=writeback" and "data=order, barrier=1". These posts may be help you understand them. 1.https://access.redhat.com/site/documentation/en-US/Red_Hat_Enterprise_Linux/6/html/Storage_Administration_Guide/writebarr.html 2.http://lwn.net/Articles/457667/ > Allow proper fsync support for HBase > > > Key: HBASE-5954 > URL: https://issues.apache.org/jira/browse/HBASE-5954 > Project: HBase > Issue Type: Improvement >Reporter: Lars Hofhansl >Assignee: Lars Hofhansl >Priority: Critical > Fix For: 0.98.0 > > Attachments: 5954-trunk-hdfs-trunk.txt, 5954-trunk-hdfs-trunk-v2.txt, > 5954-trunk-hdfs-trunk-v3.txt, 5954-trunk-hdfs-trunk-v4.txt, > 5954-trunk-hdfs-trunk-v5.txt, 5954-trunk-hdfs-trunk-v6.txt, hbase-hdfs-744.txt > > > At least get recommendation into 0.96 doc and some numbers running w/ this > hdfs feature enabled. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Resolved] (HBASE-9406) Document 0.96 migration
[ https://issues.apache.org/jira/browse/HBASE-9406?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] stack resolved HBASE-9406. -- Resolution: Fixed Hadoop Flags: Reviewed Committed to trunk. > Document 0.96 migration > --- > > Key: HBASE-9406 > URL: https://issues.apache.org/jira/browse/HBASE-9406 > Project: HBase > Issue Type: Sub-task > Components: documentation >Reporter: stack >Assignee: Himanshu Vashishtha > Fix For: 0.96.0 > > Attachments: 9406.txt > > > [~himan...@cloudera.com] posted doc on the parent issue. This is about > integrating it into the refguide. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Created] (HBASE-9406) Document 0.96 migration
stack created HBASE-9406: Summary: Document 0.96 migration Key: HBASE-9406 URL: https://issues.apache.org/jira/browse/HBASE-9406 Project: HBase Issue Type: Sub-task Components: documentation Reporter: stack Assignee: Himanshu Vashishtha [~himan...@cloudera.com] posted doc on the parent issue. This is about integrating it into the refguide. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (HBASE-9406) Document 0.96 migration
[ https://issues.apache.org/jira/browse/HBASE-9406?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] stack updated HBASE-9406: - Attachment: 9406.txt docbook patch based on himanshu's xdoc patch attached to parent w/ some edits. > Document 0.96 migration > --- > > Key: HBASE-9406 > URL: https://issues.apache.org/jira/browse/HBASE-9406 > Project: HBase > Issue Type: Sub-task > Components: documentation >Reporter: stack >Assignee: Himanshu Vashishtha > Fix For: 0.96.0 > > Attachments: 9406.txt > > > [~himan...@cloudera.com] posted doc on the parent issue. This is about > integrating it into the refguide. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (HBASE-9400) [UI] Catalog tables section isn't aligned
[ https://issues.apache.org/jira/browse/HBASE-9400?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13755401#comment-13755401 ] Elliott Clark commented on HBASE-9400: -- bq.Without manual refresh, a new table doesn't show up even after more than 1 hour. Oh sorry I misunderstood what you were asking for. Yeah that's never happened and probably won't happen with our current ui framework. bq.But the description is still not on the right-side. The description is in the correct location. It's just that there's no description. I'll add some next patch. > [UI] Catalog tables section isn't aligned > - > > Key: HBASE-9400 > URL: https://issues.apache.org/jira/browse/HBASE-9400 > Project: HBase > Issue Type: Bug > Components: UI >Affects Versions: 0.95.2, 0.96.0 >Reporter: Jimmy Xiang >Assignee: Elliott Clark >Priority: Minor > Attachments: catalog-tables.png, HBASE-9400-0.patch > > > I attached a picture of what I got. You can see it doesn't look right. > One more thing is that the page doesn't auto-refresh when you switch tabs. > For example, click Catalog tables, create a new table, click User tables, you > don't see the new table. You need to refresh the page to see it. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (HBASE-9387) Region could get lost during assignment
[
https://issues.apache.org/jira/browse/HBASE-9387?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ted Yu updated HBASE-9387:
--
Attachment: 9387-v6.txt
> Region could get lost during assignment
> ---
>
> Key: HBASE-9387
> URL: https://issues.apache.org/jira/browse/HBASE-9387
> Project: HBase
> Issue Type: Bug
> Components: Region Assignment
>Affects Versions: 0.95.2
>Reporter: Ted Yu
>Assignee: Ted Yu
>Priority: Critical
> Attachments: 9387-v1.txt, 9387-v3.txt, 9387-v4.2.txt, 9387-v4.3.txt,
> 9387-v4.4.txt, 9387-v4.txt, 9387-v5.txt, 9387-v6.txt, hbase-9387.patch,
> org.apache.hadoop.hbase.TestFullLogReconstruction-output.txt
>
>
> I observed test timeout running against hadoop 2.1.0 with distributed log
> replay turned on.
> Looks like region state for 1588230740 became inconsistent between master and
> the surviving region server:
> {code}
> 2013-08-29 22:15:34,180 INFO [AM.ZK.Worker-pool2-t4]
> master.RegionStates(299): Onlined 1588230740 on
> kiyo.gq1.ygridcore.net,57016,1377814510039
> ...
> 2013-08-29 22:15:34,587 DEBUG [Thread-221]
> client.HConnectionManager$HConnectionImplementation(1269): locateRegionInMeta
> parentTable=hbase:meta, metaLocation={region=hbase:meta,,1.1588230740,
> hostname=kiyo.gq1.ygridcore.net,57016,1377814510039, seqNum=0}, attempt=2 of
> 35 failed; retrying after sleep of 302 because:
> org.apache.hadoop.hbase.exceptions.RegionOpeningException: Region is being
> opened: 1588230740
> at
> org.apache.hadoop.hbase.regionserver.HRegionServer.getRegionByEncodedName(HRegionServer.java:2574)
> at
> org.apache.hadoop.hbase.regionserver.HRegionServer.getRegion(HRegionServer.java:3949)
> at
> org.apache.hadoop.hbase.regionserver.HRegionServer.get(HRegionServer.java:2733)
> at
> org.apache.hadoop.hbase.protobuf.generated.ClientProtos$ClientService$2.callBlockingMethod(ClientProtos.java:26965)
> at org.apache.hadoop.hbase.ipc.RpcServer.call(RpcServer.java:2063)
> at
> org.apache.hadoop.hbase.ipc.RpcServer$CallRunner.run(RpcServer.java:1800)
> at
> org.apache.hadoop.hbase.ipc.SimpleRpcScheduler.consumerLoop(SimpleRpcScheduler.java:165)
> at
> org.apache.hadoop.hbase.ipc.SimpleRpcScheduler.access$000(SimpleRpcScheduler.java:41)
> {code}
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (HBASE-9387) Region could get lost during assignment
[
https://issues.apache.org/jira/browse/HBASE-9387?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13755391#comment-13755391
]
stack commented on HBASE-9387:
--
[~jxiang] I was thinking.
Should we just make a patch ourselves? As is, we are telling another what to
do and it is more cumbersome than just doing it ourselves (It also is taking
more time)? I am not convinced that the 'test' does as is expected -- there is
no 'proof' in the comment provided nor a log snippet showing it works as wanted.
> Region could get lost during assignment
> ---
>
> Key: HBASE-9387
> URL: https://issues.apache.org/jira/browse/HBASE-9387
> Project: HBase
> Issue Type: Bug
> Components: Region Assignment
>Affects Versions: 0.95.2
>Reporter: Ted Yu
>Assignee: Ted Yu
>Priority: Critical
> Attachments: 9387-v1.txt, 9387-v3.txt, 9387-v4.2.txt, 9387-v4.3.txt,
> 9387-v4.4.txt, 9387-v4.txt, 9387-v5.txt, hbase-9387.patch,
> org.apache.hadoop.hbase.TestFullLogReconstruction-output.txt
>
>
> I observed test timeout running against hadoop 2.1.0 with distributed log
> replay turned on.
> Looks like region state for 1588230740 became inconsistent between master and
> the surviving region server:
> {code}
> 2013-08-29 22:15:34,180 INFO [AM.ZK.Worker-pool2-t4]
> master.RegionStates(299): Onlined 1588230740 on
> kiyo.gq1.ygridcore.net,57016,1377814510039
> ...
> 2013-08-29 22:15:34,587 DEBUG [Thread-221]
> client.HConnectionManager$HConnectionImplementation(1269): locateRegionInMeta
> parentTable=hbase:meta, metaLocation={region=hbase:meta,,1.1588230740,
> hostname=kiyo.gq1.ygridcore.net,57016,1377814510039, seqNum=0}, attempt=2 of
> 35 failed; retrying after sleep of 302 because:
> org.apache.hadoop.hbase.exceptions.RegionOpeningException: Region is being
> opened: 1588230740
> at
> org.apache.hadoop.hbase.regionserver.HRegionServer.getRegionByEncodedName(HRegionServer.java:2574)
> at
> org.apache.hadoop.hbase.regionserver.HRegionServer.getRegion(HRegionServer.java:3949)
> at
> org.apache.hadoop.hbase.regionserver.HRegionServer.get(HRegionServer.java:2733)
> at
> org.apache.hadoop.hbase.protobuf.generated.ClientProtos$ClientService$2.callBlockingMethod(ClientProtos.java:26965)
> at org.apache.hadoop.hbase.ipc.RpcServer.call(RpcServer.java:2063)
> at
> org.apache.hadoop.hbase.ipc.RpcServer$CallRunner.run(RpcServer.java:1800)
> at
> org.apache.hadoop.hbase.ipc.SimpleRpcScheduler.consumerLoop(SimpleRpcScheduler.java:165)
> at
> org.apache.hadoop.hbase.ipc.SimpleRpcScheduler.access$000(SimpleRpcScheduler.java:41)
> {code}
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (HBASE-6581) Build with hadoop.profile=3.0
[ https://issues.apache.org/jira/browse/HBASE-6581?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13755390#comment-13755390 ] Eric Charles commented on HBASE-6581: - We already have a FSDataOutputStream as field. This one is not synchronized and not thread-safe by nature (I guess). So caller are thus supposed to do the safety job. [~saint@gmail.com] Waiting on your green light to submit a new patch without further synchronization on the method object call. > Build with hadoop.profile=3.0 > - > > Key: HBASE-6581 > URL: https://issues.apache.org/jira/browse/HBASE-6581 > Project: HBase > Issue Type: Bug >Reporter: Eric Charles >Assignee: Eric Charles > Attachments: HBASE-6581-1.patch, HBASE-6581-20130821.patch, > HBASE-6581-2.patch, HBASE-6581-3.patch, HBASE-6581-4.patch, HBASE-6581.diff, > HBASE-6581.diff > > > Building trunk with hadoop.profile=3.0 gives exceptions (see [1]) due to > change in the hadoop maven modules naming (and also usage of 3.0-SNAPSHOT > instead of 3.0.0-SNAPSHOT in hbase-common). > I can provide a patch that would move most of hadoop dependencies in their > respective profiles and will define the correct hadoop deps in the 3.0 > profile. > Please tell me if that's ok to go this way. > Thx, Eric > [1] > $ mvn clean install -Dhadoop.profile=3.0 > [INFO] Scanning for projects... > [ERROR] The build could not read 3 projects -> [Help 1] > [ERROR] > [ERROR] The project org.apache.hbase:hbase-server:0.95-SNAPSHOT > (/d/hbase.svn/hbase-server/pom.xml) has 3 errors > [ERROR] 'dependencies.dependency.version' for > org.apache.hadoop:hadoop-common:jar is missing. @ line 655, column 21 > [ERROR] 'dependencies.dependency.version' for > org.apache.hadoop:hadoop-annotations:jar is missing. @ line 659, column 21 > [ERROR] 'dependencies.dependency.version' for > org.apache.hadoop:hadoop-minicluster:jar is missing. @ line 663, column 21 > [ERROR] > [ERROR] The project org.apache.hbase:hbase-common:0.95-SNAPSHOT > (/d/hbase.svn/hbase-common/pom.xml) has 3 errors > [ERROR] 'dependencies.dependency.version' for > org.apache.hadoop:hadoop-common:jar is missing. @ line 170, column 21 > [ERROR] 'dependencies.dependency.version' for > org.apache.hadoop:hadoop-annotations:jar is missing. @ line 174, column 21 > [ERROR] 'dependencies.dependency.version' for > org.apache.hadoop:hadoop-minicluster:jar is missing. @ line 178, column 21 > [ERROR] > [ERROR] The project org.apache.hbase:hbase-it:0.95-SNAPSHOT > (/d/hbase.svn/hbase-it/pom.xml) has 3 errors > [ERROR] 'dependencies.dependency.version' for > org.apache.hadoop:hadoop-common:jar is missing. @ line 220, column 18 > [ERROR] 'dependencies.dependency.version' for > org.apache.hadoop:hadoop-annotations:jar is missing. @ line 224, column 21 > [ERROR] 'dependencies.dependency.version' for > org.apache.hadoop:hadoop-minicluster:jar is missing. @ line 228, column 21 > [ERROR] -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (HBASE-9400) [UI] Catalog tables section isn't aligned
[
https://issues.apache.org/jira/browse/HBASE-9400?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13755339#comment-13755339
]
Hadoop QA commented on HBASE-9400:
--
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12600888/HBASE-9400-0.patch
against trunk revision .
{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 hadoop1.0{color}. The patch compiles against the hadoop
1.0 profile.
{color:green}+1 hadoop2.0{color}. The patch compiles against the hadoop
2.0 profile.
{color:green}+1 javadoc{color}. The javadoc tool did not generate any
warning messages.
{color:green}+1 javac{color}. The applied patch does not increase the
total number of javac compiler warnings.
{color:red}-1 findbugs{color}. The patch appears to introduce 1 new
Findbugs (version 1.3.9) 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/7000//testReport/
Findbugs warnings:
https://builds.apache.org/job/PreCommit-HBASE-Build/7000//artifact/trunk/patchprocess/newPatchFindbugsWarningshbase-protocol.html
Findbugs warnings:
https://builds.apache.org/job/PreCommit-HBASE-Build/7000//artifact/trunk/patchprocess/newPatchFindbugsWarningshbase-client.html
Findbugs warnings:
https://builds.apache.org/job/PreCommit-HBASE-Build/7000//artifact/trunk/patchprocess/newPatchFindbugsWarningshbase-examples.html
Findbugs warnings:
https://builds.apache.org/job/PreCommit-HBASE-Build/7000//artifact/trunk/patchprocess/newPatchFindbugsWarningshbase-hadoop1-compat.html
Findbugs warnings:
https://builds.apache.org/job/PreCommit-HBASE-Build/7000//artifact/trunk/patchprocess/newPatchFindbugsWarningshbase-prefix-tree.html
Findbugs warnings:
https://builds.apache.org/job/PreCommit-HBASE-Build/7000//artifact/trunk/patchprocess/newPatchFindbugsWarningshbase-common.html
Findbugs warnings:
https://builds.apache.org/job/PreCommit-HBASE-Build/7000//artifact/trunk/patchprocess/newPatchFindbugsWarningshbase-server.html
Findbugs warnings:
https://builds.apache.org/job/PreCommit-HBASE-Build/7000//artifact/trunk/patchprocess/newPatchFindbugsWarningshbase-hadoop-compat.html
Console output:
https://builds.apache.org/job/PreCommit-HBASE-Build/7000//console
This message is automatically generated.
> [UI] Catalog tables section isn't aligned
> -
>
> Key: HBASE-9400
> URL: https://issues.apache.org/jira/browse/HBASE-9400
> Project: HBase
> Issue Type: Bug
> Components: UI
>Affects Versions: 0.95.2, 0.96.0
>Reporter: Jimmy Xiang
>Assignee: Elliott Clark
>Priority: Minor
> Attachments: catalog-tables.png, HBASE-9400-0.patch
>
>
> I attached a picture of what I got. You can see it doesn't look right.
> One more thing is that the page doesn't auto-refresh when you switch tabs.
> For example, click Catalog tables, create a new table, click User tables, you
> don't see the new table. You need to refresh the page to see it.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (HBASE-9375) [REST] Querying row data gives all the available versions of a column
[
https://issues.apache.org/jira/browse/HBASE-9375?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13755335#comment-13755335
]
Hadoop QA commented on HBASE-9375:
--
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12600908/HBASE-9375.00.patch
against trunk revision .
{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:red}-1 patch{color}. The patch command could not apply the patch.
Console output:
https://builds.apache.org/job/PreCommit-HBASE-Build/7001//console
This message is automatically generated.
> [REST] Querying row data gives all the available versions of a column
> -
>
> Key: HBASE-9375
> URL: https://issues.apache.org/jira/browse/HBASE-9375
> Project: HBase
> Issue Type: Bug
> Components: REST
>Affects Versions: 0.94.11
>Reporter: Vandana Ayyalasomayajula
>Assignee: Vandana Ayyalasomayajula
>Priority: Minor
> Attachments: HBASE-9375.00.patch
>
>
> In the hbase shell, when a user tries to get a value related to a column,
> hbase returns only the latest value. But using the REST API returns
> HColumnDescriptor.DEFAULT_VERSIONS versions by default.
> The behavior should be consistent with the hbase shell.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (HBASE-9375) [REST] Querying row data gives all the available versions of a column
[ https://issues.apache.org/jira/browse/HBASE-9375?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vandana Ayyalasomayajula updated HBASE-9375: Affects Version/s: 0.94.11 Status: Patch Available (was: Open) > [REST] Querying row data gives all the available versions of a column > - > > Key: HBASE-9375 > URL: https://issues.apache.org/jira/browse/HBASE-9375 > Project: HBase > Issue Type: Bug > Components: REST >Affects Versions: 0.94.11 >Reporter: Vandana Ayyalasomayajula >Assignee: Vandana Ayyalasomayajula >Priority: Minor > Attachments: HBASE-9375.00.patch > > > In the hbase shell, when a user tries to get a value related to a column, > hbase returns only the latest value. But using the REST API returns > HColumnDescriptor.DEFAULT_VERSIONS versions by default. > The behavior should be consistent with the hbase shell. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (HBASE-9375) [REST] Querying row data gives all the available versions of a column
[ https://issues.apache.org/jira/browse/HBASE-9375?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vandana Ayyalasomayajula updated HBASE-9375: Attachment: HBASE-9375.00.patch > [REST] Querying row data gives all the available versions of a column > - > > Key: HBASE-9375 > URL: https://issues.apache.org/jira/browse/HBASE-9375 > Project: HBase > Issue Type: Bug > Components: REST >Reporter: Vandana Ayyalasomayajula >Assignee: Vandana Ayyalasomayajula >Priority: Minor > Attachments: HBASE-9375.00.patch > > > In the hbase shell, when a user tries to get a value related to a column, > hbase returns only the latest value. But using the REST API returns > HColumnDescriptor.DEFAULT_VERSIONS versions by default. > The behavior should be consistent with the hbase shell. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (HBASE-9387) Region could get lost during assignment
[
https://issues.apache.org/jira/browse/HBASE-9387?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13755325#comment-13755325
]
Jimmy Xiang commented on HBASE-9387:
Looked v5, the first part is good. For FAILED_OPEN, we don't need to abort the
RS. We should leave it as before.
> Region could get lost during assignment
> ---
>
> Key: HBASE-9387
> URL: https://issues.apache.org/jira/browse/HBASE-9387
> Project: HBase
> Issue Type: Bug
> Components: Region Assignment
>Affects Versions: 0.95.2
>Reporter: Ted Yu
>Assignee: Ted Yu
>Priority: Critical
> Attachments: 9387-v1.txt, 9387-v3.txt, 9387-v4.2.txt, 9387-v4.3.txt,
> 9387-v4.4.txt, 9387-v4.txt, 9387-v5.txt, hbase-9387.patch,
> org.apache.hadoop.hbase.TestFullLogReconstruction-output.txt
>
>
> I observed test timeout running against hadoop 2.1.0 with distributed log
> replay turned on.
> Looks like region state for 1588230740 became inconsistent between master and
> the surviving region server:
> {code}
> 2013-08-29 22:15:34,180 INFO [AM.ZK.Worker-pool2-t4]
> master.RegionStates(299): Onlined 1588230740 on
> kiyo.gq1.ygridcore.net,57016,1377814510039
> ...
> 2013-08-29 22:15:34,587 DEBUG [Thread-221]
> client.HConnectionManager$HConnectionImplementation(1269): locateRegionInMeta
> parentTable=hbase:meta, metaLocation={region=hbase:meta,,1.1588230740,
> hostname=kiyo.gq1.ygridcore.net,57016,1377814510039, seqNum=0}, attempt=2 of
> 35 failed; retrying after sleep of 302 because:
> org.apache.hadoop.hbase.exceptions.RegionOpeningException: Region is being
> opened: 1588230740
> at
> org.apache.hadoop.hbase.regionserver.HRegionServer.getRegionByEncodedName(HRegionServer.java:2574)
> at
> org.apache.hadoop.hbase.regionserver.HRegionServer.getRegion(HRegionServer.java:3949)
> at
> org.apache.hadoop.hbase.regionserver.HRegionServer.get(HRegionServer.java:2733)
> at
> org.apache.hadoop.hbase.protobuf.generated.ClientProtos$ClientService$2.callBlockingMethod(ClientProtos.java:26965)
> at org.apache.hadoop.hbase.ipc.RpcServer.call(RpcServer.java:2063)
> at
> org.apache.hadoop.hbase.ipc.RpcServer$CallRunner.run(RpcServer.java:1800)
> at
> org.apache.hadoop.hbase.ipc.SimpleRpcScheduler.consumerLoop(SimpleRpcScheduler.java:165)
> at
> org.apache.hadoop.hbase.ipc.SimpleRpcScheduler.access$000(SimpleRpcScheduler.java:41)
> {code}
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (HBASE-7954) Fix the retrying logic of memstore flushes to avoid extra sleep
[ https://issues.apache.org/jira/browse/HBASE-7954?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13755322#comment-13755322 ] Hudson commented on HBASE-7954: --- SUCCESS: Integrated in HBase-TRUNK-on-Hadoop-2.0.0 #705 (See [https://builds.apache.org/job/HBase-TRUNK-on-Hadoop-2.0.0/705/]) HBASE-7954 Fix the retrying logic of memstore flushes to avoid extra sleep (stack: rev 1519010) * /hbase/trunk/hbase-server/src/main/java/org/apache/hadoop/hbase/regionserver/HStore.java > Fix the retrying logic of memstore flushes to avoid extra sleep > --- > > Key: HBASE-7954 > URL: https://issues.apache.org/jira/browse/HBASE-7954 > Project: HBase > Issue Type: Bug > Components: regionserver >Affects Versions: 0.94.5, 0.95.0 >Reporter: Himanshu Vashishtha >Assignee: Himanshu Vashishtha >Priority: Minor > Fix For: 0.98.0, 0.94.12 > > Attachments: HBase-7954-94.patch, HBase-7954-v0.patch > > > Matteo pointed out: > "We can avoid the redundant sleep in the retrying logic." -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (HBASE-9359) Convert KeyValue to Cell in hbase-client module - Result/Put/Delete, ColumnInterpreter
[ https://issues.apache.org/jira/browse/HBASE-9359?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13755318#comment-13755318 ] Hudson commented on HBASE-9359: --- SUCCESS: Integrated in HBase-TRUNK-on-Hadoop-2.0.0 #705 (See [https://builds.apache.org/job/HBase-TRUNK-on-Hadoop-2.0.0/705/]) HBASE-9334 Convert KeyValue to Cell in hbase-client module - Filters HBASE-9359 Convert KeyValue to Cell in hbase-client module - Result/Put/Delete, ColumnInterpreter (jmhsieh: rev 1519077) * /hbase/trunk/hbase-client/src/main/java/org/apache/hadoop/hbase/Coprocessor.java * /hbase/trunk/hbase-client/src/main/java/org/apache/hadoop/hbase/client/ClientScanner.java * /hbase/trunk/hbase-client/src/main/java/org/apache/hadoop/hbase/client/Delete.java * /hbase/trunk/hbase-client/src/main/java/org/apache/hadoop/hbase/client/Get.java * /hbase/trunk/hbase-client/src/main/java/org/apache/hadoop/hbase/client/Put.java * /hbase/trunk/hbase-client/src/main/java/org/apache/hadoop/hbase/client/Result.java * /hbase/trunk/hbase-client/src/main/java/org/apache/hadoop/hbase/client/ScannerCallable.java * /hbase/trunk/hbase-client/src/main/java/org/apache/hadoop/hbase/client/coprocessor/AggregationClient.java * /hbase/trunk/hbase-client/src/main/java/org/apache/hadoop/hbase/client/coprocessor/BigDecimalColumnInterpreter.java * /hbase/trunk/hbase-client/src/main/java/org/apache/hadoop/hbase/client/coprocessor/LongColumnInterpreter.java * /hbase/trunk/hbase-client/src/main/java/org/apache/hadoop/hbase/coprocessor/ColumnInterpreter.java * /hbase/trunk/hbase-client/src/main/java/org/apache/hadoop/hbase/filter/ColumnCountGetFilter.java * /hbase/trunk/hbase-client/src/main/java/org/apache/hadoop/hbase/filter/ColumnPaginationFilter.java * /hbase/trunk/hbase-client/src/main/java/org/apache/hadoop/hbase/filter/ColumnPrefixFilter.java * /hbase/trunk/hbase-client/src/main/java/org/apache/hadoop/hbase/filter/ColumnRangeFilter.java * /hbase/trunk/hbase-client/src/main/java/org/apache/hadoop/hbase/filter/CompareFilter.java * /hbase/trunk/hbase-client/src/main/java/org/apache/hadoop/hbase/filter/DependentColumnFilter.java * /hbase/trunk/hbase-client/src/main/java/org/apache/hadoop/hbase/filter/FamilyFilter.java * /hbase/trunk/hbase-client/src/main/java/org/apache/hadoop/hbase/filter/Filter.java * /hbase/trunk/hbase-client/src/main/java/org/apache/hadoop/hbase/filter/FilterBase.java * /hbase/trunk/hbase-client/src/main/java/org/apache/hadoop/hbase/filter/FilterList.java * /hbase/trunk/hbase-client/src/main/java/org/apache/hadoop/hbase/filter/FilterWrapper.java * /hbase/trunk/hbase-client/src/main/java/org/apache/hadoop/hbase/filter/FirstKeyOnlyFilter.java * /hbase/trunk/hbase-client/src/main/java/org/apache/hadoop/hbase/filter/FirstKeyValueMatchingQualifiersFilter.java * /hbase/trunk/hbase-client/src/main/java/org/apache/hadoop/hbase/filter/FuzzyRowFilter.java * /hbase/trunk/hbase-client/src/main/java/org/apache/hadoop/hbase/filter/KeyOnlyFilter.java * /hbase/trunk/hbase-client/src/main/java/org/apache/hadoop/hbase/filter/MultipleColumnPrefixFilter.java * /hbase/trunk/hbase-client/src/main/java/org/apache/hadoop/hbase/filter/NullComparator.java * /hbase/trunk/hbase-client/src/main/java/org/apache/hadoop/hbase/filter/ParseFilter.java * /hbase/trunk/hbase-client/src/main/java/org/apache/hadoop/hbase/filter/QualifierFilter.java * /hbase/trunk/hbase-client/src/main/java/org/apache/hadoop/hbase/filter/RandomRowFilter.java * /hbase/trunk/hbase-client/src/main/java/org/apache/hadoop/hbase/filter/RowFilter.java * /hbase/trunk/hbase-client/src/main/java/org/apache/hadoop/hbase/filter/SingleColumnValueExcludeFilter.java * /hbase/trunk/hbase-client/src/main/java/org/apache/hadoop/hbase/filter/SingleColumnValueFilter.java * /hbase/trunk/hbase-client/src/main/java/org/apache/hadoop/hbase/filter/SkipFilter.java * /hbase/trunk/hbase-client/src/main/java/org/apache/hadoop/hbase/filter/TimestampsFilter.java * /hbase/trunk/hbase-client/src/main/java/org/apache/hadoop/hbase/filter/ValueFilter.java * /hbase/trunk/hbase-client/src/main/java/org/apache/hadoop/hbase/filter/WhileMatchFilter.java * /hbase/trunk/hbase-client/src/test/java/org/apache/hadoop/hbase/ipc/TestPayloadCarryingRpcController.java * /hbase/trunk/hbase-common/src/main/java/org/apache/hadoop/hbase/Cell.java * /hbase/trunk/hbase-common/src/main/java/org/apache/hadoop/hbase/CellUtil.java * /hbase/trunk/hbase-common/src/main/java/org/apache/hadoop/hbase/KeyValue.java * /hbase/trunk/hbase-common/src/main/java/org/apache/hadoop/hbase/KeyValueTestUtil.java * /hbase/trunk/hbase-common/src/main/java/org/apache/hadoop/hbase/io/encoding/EncodedDataBlock.java * /hbase/trunk/hbase-examples/src/main/java/org/apache/hadoop/hbase/coprocessor/example/BulkDeleteEndpoint.java * /hbase/trunk/hbase-examples/src/main/java/org/apache/hadoop/hbase/coprocessor/example/RowCountEndpoint.java * /hbase/trunk/hbase-examp
[jira] [Commented] (HBASE-9382) replicateWALEntry doesn't use the replication handlers
[ https://issues.apache.org/jira/browse/HBASE-9382?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13755317#comment-13755317 ] Hudson commented on HBASE-9382: --- SUCCESS: Integrated in HBase-TRUNK-on-Hadoop-2.0.0 #705 (See [https://builds.apache.org/job/HBase-TRUNK-on-Hadoop-2.0.0/705/]) HBASE-9382 replicateWALEntry doesn't use the replication handlers (stack: rev 1519017) * /hbase/trunk/hbase-server/src/main/java/org/apache/hadoop/hbase/ipc/SimpleRpcScheduler.java * /hbase/trunk/hbase-server/src/main/java/org/apache/hadoop/hbase/regionserver/QosFunction.java * /hbase/trunk/hbase-server/src/test/java/org/apache/hadoop/hbase/regionserver/TestQosFunction.java > replicateWALEntry doesn't use the replication handlers > -- > > Key: HBASE-9382 > URL: https://issues.apache.org/jira/browse/HBASE-9382 > Project: HBase > Issue Type: Bug >Affects Versions: 0.95.2 >Reporter: Jean-Daniel Cryans >Assignee: stack > Fix For: 0.98.0, 0.96.0 > > Attachments: 9382.trunk.txt, 9382.txt > > > By default we assign 3 handlers for replication, but as far as I can tell the > replication traffic uses the normal handlers in 0.96 -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (HBASE-9373) [replication] data loss because replication doesn't expect partial reads
[
https://issues.apache.org/jira/browse/HBASE-9373?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13755315#comment-13755315
]
Hudson commented on HBASE-9373:
---
SUCCESS: Integrated in HBase-TRUNK-on-Hadoop-2.0.0 #705 (See
[https://builds.apache.org/job/HBase-TRUNK-on-Hadoop-2.0.0/705/])
HBASE-9373 [replication] data loss because replication doesn't expect partial
reads (jdcryans: rev 1519037)
*
/hbase/trunk/hbase-server/src/main/java/org/apache/hadoop/hbase/regionserver/wal/ProtobufLogReader.java
> [replication] data loss because replication doesn't expect partial reads
>
>
> Key: HBASE-9373
> URL: https://issues.apache.org/jira/browse/HBASE-9373
> Project: HBase
> Issue Type: Improvement
>Affects Versions: 0.95.2
>Reporter: Jean-Daniel Cryans
>Assignee: Jean-Daniel Cryans
>Priority: Blocker
> Fix For: 0.98.0, 0.96.0
>
> Attachments: 9373.txt, 9373-v2.txt, 9373-v3.txt, 9373-v4.patch
>
>
> When I see this in the logs it often means we got a partial read and then we
> have the wrong offset when reading the rest of the file
> {noformat}
> 2013-08-28 23:16:07,182 ERROR
> [ReplicationExecutor-0.replicationSource,1-jdec2hbase0403-5,60020,1377730319617]
> org.apache.hadoop.hbase.regionserver.wal.ProtobufLogReader: Invalid PB while
> reading WAL, probably an unexpected EOF, ignoring
> com.google.protobuf.InvalidProtocolBufferException: Protocol message tag had
> invalid wire type.
> at
> com.google.protobuf.InvalidProtocolBufferException.invalidWireType(InvalidProtocolBufferException.java:99)
> at
> com.google.protobuf.UnknownFieldSet$Builder.mergeFieldFrom(UnknownFieldSet.java:498)
> at
> com.google.protobuf.GeneratedMessage.parseUnknownField(GeneratedMessage.java:193)
> at
> org.apache.hadoop.hbase.protobuf.generated.WALProtos$WALKey.(WALProtos.java:686)
> at
> org.apache.hadoop.hbase.protobuf.generated.WALProtos$WALKey.(WALProtos.java:644)
> at
> org.apache.hadoop.hbase.protobuf.generated.WALProtos$WALKey$1.parsePartialFrom(WALProtos.java:771)
> at
> org.apache.hadoop.hbase.protobuf.generated.WALProtos$WALKey$1.parsePartialFrom(WALProtos.java:766)
> at
> org.apache.hadoop.hbase.protobuf.generated.WALProtos$WALKey$Builder.mergeFrom(WALProtos.java:1444)
> at
> org.apache.hadoop.hbase.protobuf.generated.WALProtos$WALKey$Builder.mergeFrom(WALProtos.java:1218)
> at
> com.google.protobuf.AbstractMessageLite$Builder.mergeFrom(AbstractMessageLite.java:220)
> at
> com.google.protobuf.AbstractMessage$Builder.mergeFrom(AbstractMessage.java:912)
> at
> com.google.protobuf.AbstractMessage$Builder.mergeFrom(AbstractMessage.java:267)
> at
> com.google.protobuf.AbstractMessageLite$Builder.mergeDelimitedFrom(AbstractMessageLite.java:290)
> at
> com.google.protobuf.AbstractMessage$Builder.mergeDelimitedFrom(AbstractMessage.java:926)
> at
> com.google.protobuf.AbstractMessageLite$Builder.mergeDelimitedFrom(AbstractMessageLite.java:296)
> at
> com.google.protobuf.AbstractMessage$Builder.mergeDelimitedFrom(AbstractMessage.java:918)
> at
> org.apache.hadoop.hbase.regionserver.wal.ProtobufLogReader.readNext(ProtobufLogReader.java:197)
> at
> org.apache.hadoop.hbase.regionserver.wal.ReaderBase.next(ReaderBase.java:98)
> at
> org.apache.hadoop.hbase.replication.regionserver.ReplicationHLogReaderManager.readNextAndSetPosition(ReplicationHLogReaderManager.java:89)
> at
> org.apache.hadoop.hbase.replication.regionserver.ReplicationSource.readAllEntriesToReplicateOrNextFile(ReplicationSource.java:390)
> at
> org.apache.hadoop.hbase.replication.regionserver.ReplicationSource.run(ReplicationSource.java:298)
> {noformat}
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (HBASE-9386) [WINDOWS] Small improvements to .cmd scripts
[ https://issues.apache.org/jira/browse/HBASE-9386?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13755314#comment-13755314 ] Hudson commented on HBASE-9386: --- SUCCESS: Integrated in HBase-TRUNK-on-Hadoop-2.0.0 #705 (See [https://builds.apache.org/job/HBase-TRUNK-on-Hadoop-2.0.0/705/]) HBASE-9386 [WINDOWS] Small improvements to .cmd scripts (enis: rev 1519028) * /hbase/trunk/bin/hbase-config.cmd * /hbase/trunk/bin/hbase.cmd * /hbase/trunk/conf/hbase-env.cmd > [WINDOWS] Small improvements to .cmd scripts > > > Key: HBASE-9386 > URL: https://issues.apache.org/jira/browse/HBASE-9386 > Project: HBase > Issue Type: Bug >Reporter: Enis Soztutar >Assignee: Enis Soztutar > Fix For: 0.98.0, 0.96.0 > > Attachments: hbase-9386_v1.patch > > > A collection of small improvements to the .cmd scripts are needed: > - Have hbase.cmd honor --config option > - Fix log4j default appenders for standalone or service mode > - classpath fixes > - Honor JRuby options -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (HBASE-9394) [replication] size accounting is completely off in the source
[
https://issues.apache.org/jira/browse/HBASE-9394?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13755320#comment-13755320
]
Hudson commented on HBASE-9394:
---
SUCCESS: Integrated in HBase-TRUNK-on-Hadoop-2.0.0 #705 (See
[https://builds.apache.org/job/HBase-TRUNK-on-Hadoop-2.0.0/705/])
HBASE-9394 [replication] size accounting is completely off in the source
(jdcryans: rev 1519040)
*
/hbase/trunk/hbase-server/src/main/java/org/apache/hadoop/hbase/replication/regionserver/ReplicationSource.java
> [replication] size accounting is completely off in the source
> -
>
> Key: HBASE-9394
> URL: https://issues.apache.org/jira/browse/HBASE-9394
> Project: HBase
> Issue Type: Bug
>Affects Versions: 0.95.2
>Reporter: Jean-Daniel Cryans
>Assignee: Jean-Daniel Cryans
> Fix For: 0.98.0, 0.96.0
>
> Attachments: HBASE-9394.patch
>
>
> I was under the impression that I was sending way more data than I was
> expecting, so adding some more tracing I can see how much data I read VS how
> I much I think I'm sending:
> {noformat}
> Seeking at position 163771687
> Replicating 2 entries of total size 2790
> Seeking at position 166723643
> {noformat}
> That's about 2MB of data, not 2KB.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (HBASE-9389) Favorednodes command line not verifying assignments correctly
[ https://issues.apache.org/jira/browse/HBASE-9389?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13755316#comment-13755316 ] Hudson commented on HBASE-9389: --- SUCCESS: Integrated in HBase-TRUNK-on-Hadoop-2.0.0 #705 (See [https://builds.apache.org/job/HBase-TRUNK-on-Hadoop-2.0.0/705/]) HBASE-9389. Fixes the verification part of favored node assignments (ddas: rev 1519030) * /hbase/trunk/hbase-server/src/main/java/org/apache/hadoop/hbase/master/AssignmentVerificationReport.java * /hbase/trunk/hbase-server/src/main/java/org/apache/hadoop/hbase/master/RegionPlacementMaintainer.java * /hbase/trunk/hbase-server/src/main/java/org/apache/hadoop/hbase/master/balancer/FavoredNodesPlan.java * /hbase/trunk/hbase-server/src/main/java/org/apache/hadoop/hbase/util/FSRegionScanner.java * /hbase/trunk/hbase-server/src/main/java/org/apache/hadoop/hbase/util/FSUtils.java * /hbase/trunk/hbase-server/src/test/java/org/apache/hadoop/hbase/master/TestRegionPlacement.java > Favorednodes command line not verifying assignments correctly > - > > Key: HBASE-9389 > URL: https://issues.apache.org/jira/browse/HBASE-9389 > Project: HBase > Issue Type: Bug >Affects Versions: 0.96.0 >Reporter: Devaraj Das >Assignee: Devaraj Das >Priority: Critical > Fix For: 0.96.0 > > Attachments: 9389-1.txt, verification-fix.1.txt > > > In manual testing, encountered an issue to do with the command line tool > (HBASE-9116) not verifying the assignments correctly. Although the regions > are assigned to the favored nodes, the verification/print showed otherwise. > The command to reproduce the problem (after having created the tables, and > loading some data): > bin/hbase org.apache.hadoop.hbase.master.RegionPlacementMaintainer -tables > cluster_test1,cluster_test2 -hbase_root /apps/hbase/data -v -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (HBASE-9384) [WINDOWS] Using file://{hbase.tmp.dir}/hbase for hbase.rootdir causes illegal argument exception on windows
[
https://issues.apache.org/jira/browse/HBASE-9384?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13755319#comment-13755319
]
Hudson commented on HBASE-9384:
---
SUCCESS: Integrated in HBase-TRUNK-on-Hadoop-2.0.0 #705 (See
[https://builds.apache.org/job/HBase-TRUNK-on-Hadoop-2.0.0/705/])
HBASE-9384 [WINDOWS] Using file://{hbase.tmp.dir}/hbase for hbase.rootdir
causes illegal argument exception on windows (enis: rev 1519021)
* /hbase/trunk/hbase-common/src/main/resources/hbase-default.xml
> [WINDOWS] Using file://{hbase.tmp.dir}/hbase for hbase.rootdir causes illegal
> argument exception on windows
> ---
>
> Key: HBASE-9384
> URL: https://issues.apache.org/jira/browse/HBASE-9384
> Project: HBase
> Issue Type: Bug
>Reporter: Enis Soztutar
>Assignee: Enis Soztutar
> Fix For: 0.98.0, 0.96.0
>
> Attachments: hbase-9384_v1.patch
>
>
> We define hbase.rootdir as follows in hbase-default.xml:
> {code}
>
> hbase.tmp.dir
> ${java.io.tmpdir}/hbase-${user.name}
>
>
> hbase.rootdir
> file://${hbase.tmp.dir}/hbase
>
> {code}
> This causes an
> java.lang.IllegalArgumentException: Wrong FS:
> file://C:\Users\Administrator\AppData\Local\Temp\2\/hbase-Administrator/hbase,
> expected: file:///
> on windows.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (HBASE-9334) Convert KeyValue to Cell in hbase-client module - Filters
[ https://issues.apache.org/jira/browse/HBASE-9334?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13755321#comment-13755321 ] Hudson commented on HBASE-9334: --- SUCCESS: Integrated in HBase-TRUNK-on-Hadoop-2.0.0 #705 (See [https://builds.apache.org/job/HBase-TRUNK-on-Hadoop-2.0.0/705/]) HBASE-9334 Convert KeyValue to Cell in hbase-client module - Filters HBASE-9359 Convert KeyValue to Cell in hbase-client module - Result/Put/Delete, ColumnInterpreter (jmhsieh: rev 1519077) * /hbase/trunk/hbase-client/src/main/java/org/apache/hadoop/hbase/Coprocessor.java * /hbase/trunk/hbase-client/src/main/java/org/apache/hadoop/hbase/client/ClientScanner.java * /hbase/trunk/hbase-client/src/main/java/org/apache/hadoop/hbase/client/Delete.java * /hbase/trunk/hbase-client/src/main/java/org/apache/hadoop/hbase/client/Get.java * /hbase/trunk/hbase-client/src/main/java/org/apache/hadoop/hbase/client/Put.java * /hbase/trunk/hbase-client/src/main/java/org/apache/hadoop/hbase/client/Result.java * /hbase/trunk/hbase-client/src/main/java/org/apache/hadoop/hbase/client/ScannerCallable.java * /hbase/trunk/hbase-client/src/main/java/org/apache/hadoop/hbase/client/coprocessor/AggregationClient.java * /hbase/trunk/hbase-client/src/main/java/org/apache/hadoop/hbase/client/coprocessor/BigDecimalColumnInterpreter.java * /hbase/trunk/hbase-client/src/main/java/org/apache/hadoop/hbase/client/coprocessor/LongColumnInterpreter.java * /hbase/trunk/hbase-client/src/main/java/org/apache/hadoop/hbase/coprocessor/ColumnInterpreter.java * /hbase/trunk/hbase-client/src/main/java/org/apache/hadoop/hbase/filter/ColumnCountGetFilter.java * /hbase/trunk/hbase-client/src/main/java/org/apache/hadoop/hbase/filter/ColumnPaginationFilter.java * /hbase/trunk/hbase-client/src/main/java/org/apache/hadoop/hbase/filter/ColumnPrefixFilter.java * /hbase/trunk/hbase-client/src/main/java/org/apache/hadoop/hbase/filter/ColumnRangeFilter.java * /hbase/trunk/hbase-client/src/main/java/org/apache/hadoop/hbase/filter/CompareFilter.java * /hbase/trunk/hbase-client/src/main/java/org/apache/hadoop/hbase/filter/DependentColumnFilter.java * /hbase/trunk/hbase-client/src/main/java/org/apache/hadoop/hbase/filter/FamilyFilter.java * /hbase/trunk/hbase-client/src/main/java/org/apache/hadoop/hbase/filter/Filter.java * /hbase/trunk/hbase-client/src/main/java/org/apache/hadoop/hbase/filter/FilterBase.java * /hbase/trunk/hbase-client/src/main/java/org/apache/hadoop/hbase/filter/FilterList.java * /hbase/trunk/hbase-client/src/main/java/org/apache/hadoop/hbase/filter/FilterWrapper.java * /hbase/trunk/hbase-client/src/main/java/org/apache/hadoop/hbase/filter/FirstKeyOnlyFilter.java * /hbase/trunk/hbase-client/src/main/java/org/apache/hadoop/hbase/filter/FirstKeyValueMatchingQualifiersFilter.java * /hbase/trunk/hbase-client/src/main/java/org/apache/hadoop/hbase/filter/FuzzyRowFilter.java * /hbase/trunk/hbase-client/src/main/java/org/apache/hadoop/hbase/filter/KeyOnlyFilter.java * /hbase/trunk/hbase-client/src/main/java/org/apache/hadoop/hbase/filter/MultipleColumnPrefixFilter.java * /hbase/trunk/hbase-client/src/main/java/org/apache/hadoop/hbase/filter/NullComparator.java * /hbase/trunk/hbase-client/src/main/java/org/apache/hadoop/hbase/filter/ParseFilter.java * /hbase/trunk/hbase-client/src/main/java/org/apache/hadoop/hbase/filter/QualifierFilter.java * /hbase/trunk/hbase-client/src/main/java/org/apache/hadoop/hbase/filter/RandomRowFilter.java * /hbase/trunk/hbase-client/src/main/java/org/apache/hadoop/hbase/filter/RowFilter.java * /hbase/trunk/hbase-client/src/main/java/org/apache/hadoop/hbase/filter/SingleColumnValueExcludeFilter.java * /hbase/trunk/hbase-client/src/main/java/org/apache/hadoop/hbase/filter/SingleColumnValueFilter.java * /hbase/trunk/hbase-client/src/main/java/org/apache/hadoop/hbase/filter/SkipFilter.java * /hbase/trunk/hbase-client/src/main/java/org/apache/hadoop/hbase/filter/TimestampsFilter.java * /hbase/trunk/hbase-client/src/main/java/org/apache/hadoop/hbase/filter/ValueFilter.java * /hbase/trunk/hbase-client/src/main/java/org/apache/hadoop/hbase/filter/WhileMatchFilter.java * /hbase/trunk/hbase-client/src/test/java/org/apache/hadoop/hbase/ipc/TestPayloadCarryingRpcController.java * /hbase/trunk/hbase-common/src/main/java/org/apache/hadoop/hbase/Cell.java * /hbase/trunk/hbase-common/src/main/java/org/apache/hadoop/hbase/CellUtil.java * /hbase/trunk/hbase-common/src/main/java/org/apache/hadoop/hbase/KeyValue.java * /hbase/trunk/hbase-common/src/main/java/org/apache/hadoop/hbase/KeyValueTestUtil.java * /hbase/trunk/hbase-common/src/main/java/org/apache/hadoop/hbase/io/encoding/EncodedDataBlock.java * /hbase/trunk/hbase-examples/src/main/java/org/apache/hadoop/hbase/coprocessor/example/BulkDeleteEndpoint.java * /hbase/trunk/hbase-examples/src/main/java/org/apache/hadoop/hbase/coprocessor/example/RowCountEndpoint.java * /hbase/trunk/hbase-examp
[jira] [Commented] (HBASE-9400) [UI] Catalog tables section isn't aligned
[ https://issues.apache.org/jira/browse/HBASE-9400?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13755310#comment-13755310 ] Jimmy Xiang commented on HBASE-9400: The margin looks better. But the description is still not on the right-side. Should we remove the header "System Tables"? > [UI] Catalog tables section isn't aligned > - > > Key: HBASE-9400 > URL: https://issues.apache.org/jira/browse/HBASE-9400 > Project: HBase > Issue Type: Bug > Components: UI >Affects Versions: 0.95.2, 0.96.0 >Reporter: Jimmy Xiang >Assignee: Elliott Clark >Priority: Minor > Attachments: catalog-tables.png, HBASE-9400-0.patch > > > I attached a picture of what I got. You can see it doesn't look right. > One more thing is that the page doesn't auto-refresh when you switch tabs. > For example, click Catalog tables, create a new table, click User tables, you > don't see the new table. You need to refresh the page to see it. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (HBASE-9401) Add getQualifierBufferShallowCopy to Cell Utility.
[
https://issues.apache.org/jira/browse/HBASE-9401?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13755307#comment-13755307
]
Hadoop QA commented on HBASE-9401:
--
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12600887/HBASE-9401-0.patch
against trunk revision .
{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 hadoop1.0{color}. The patch compiles against the hadoop
1.0 profile.
{color:green}+1 hadoop2.0{color}. The patch compiles against the hadoop
2.0 profile.
{color:green}+1 javadoc{color}. The javadoc tool did not generate any
warning messages.
{color:green}+1 javac{color}. The applied patch does not increase the
total number of javac compiler warnings.
{color:red}-1 findbugs{color}. The patch appears to introduce 1 new
Findbugs (version 1.3.9) 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.mapreduce.TestHFileOutputFormat
Test results:
https://builds.apache.org/job/PreCommit-HBASE-Build/6999//testReport/
Findbugs warnings:
https://builds.apache.org/job/PreCommit-HBASE-Build/6999//artifact/trunk/patchprocess/newPatchFindbugsWarningshbase-prefix-tree.html
Findbugs warnings:
https://builds.apache.org/job/PreCommit-HBASE-Build/6999//artifact/trunk/patchprocess/newPatchFindbugsWarningshbase-client.html
Findbugs warnings:
https://builds.apache.org/job/PreCommit-HBASE-Build/6999//artifact/trunk/patchprocess/newPatchFindbugsWarningshbase-common.html
Findbugs warnings:
https://builds.apache.org/job/PreCommit-HBASE-Build/6999//artifact/trunk/patchprocess/newPatchFindbugsWarningshbase-protocol.html
Findbugs warnings:
https://builds.apache.org/job/PreCommit-HBASE-Build/6999//artifact/trunk/patchprocess/newPatchFindbugsWarningshbase-server.html
Findbugs warnings:
https://builds.apache.org/job/PreCommit-HBASE-Build/6999//artifact/trunk/patchprocess/newPatchFindbugsWarningshbase-hadoop1-compat.html
Findbugs warnings:
https://builds.apache.org/job/PreCommit-HBASE-Build/6999//artifact/trunk/patchprocess/newPatchFindbugsWarningshbase-examples.html
Findbugs warnings:
https://builds.apache.org/job/PreCommit-HBASE-Build/6999//artifact/trunk/patchprocess/newPatchFindbugsWarningshbase-hadoop-compat.html
Console output:
https://builds.apache.org/job/PreCommit-HBASE-Build/6999//console
This message is automatically generated.
> Add getQualifierBufferShallowCopy to Cell Utility.
> --
>
> Key: HBASE-9401
> URL: https://issues.apache.org/jira/browse/HBASE-9401
> Project: HBase
> Issue Type: Task
> Components: Client
>Affects Versions: 0.96.0
>Reporter: Elliott Clark
>Assignee: Elliott Clark
> Attachments: HBASE-9401-0.patch
>
>
> Right now if your qualifier is large and you need to access it, copying is
> your only option. We should allow a shallow buffer copy.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (HBASE-9400) [UI] Catalog tables section isn't aligned
[ https://issues.apache.org/jira/browse/HBASE-9400?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13755299#comment-13755299 ] Jimmy Xiang commented on HBASE-9400: I don't see any js errors. I used firefox 23.0. Without manual refresh, a new table doesn't show up even after more than 1 hour. Let me try the new css. > [UI] Catalog tables section isn't aligned > - > > Key: HBASE-9400 > URL: https://issues.apache.org/jira/browse/HBASE-9400 > Project: HBase > Issue Type: Bug > Components: UI >Affects Versions: 0.95.2, 0.96.0 >Reporter: Jimmy Xiang >Assignee: Elliott Clark >Priority: Minor > Attachments: catalog-tables.png, HBASE-9400-0.patch > > > I attached a picture of what I got. You can see it doesn't look right. > One more thing is that the page doesn't auto-refresh when you switch tabs. > For example, click Catalog tables, create a new table, click User tables, you > don't see the new table. You need to refresh the page to see it. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (HBASE-9402) initCause() uses wrong exception in ProtobufLogReader#readNext(HLog$Entry)
[
https://issues.apache.org/jira/browse/HBASE-9402?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13755296#comment-13755296
]
Hadoop QA commented on HBASE-9402:
--
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12600883/9402.patch
against trunk revision .
{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 hadoop1.0{color}. The patch compiles against the hadoop
1.0 profile.
{color:green}+1 hadoop2.0{color}. The patch compiles against the hadoop
2.0 profile.
{color:green}+1 javadoc{color}. The javadoc tool did not generate any
warning messages.
{color:green}+1 javac{color}. The applied patch does not increase the
total number of javac compiler warnings.
{color:green}+1 findbugs{color}. The patch does not introduce any new
Findbugs (version 1.3.9) 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/6998//testReport/
Findbugs warnings:
https://builds.apache.org/job/PreCommit-HBASE-Build/6998//artifact/trunk/patchprocess/newPatchFindbugsWarningshbase-protocol.html
Findbugs warnings:
https://builds.apache.org/job/PreCommit-HBASE-Build/6998//artifact/trunk/patchprocess/newPatchFindbugsWarningshbase-client.html
Findbugs warnings:
https://builds.apache.org/job/PreCommit-HBASE-Build/6998//artifact/trunk/patchprocess/newPatchFindbugsWarningshbase-examples.html
Findbugs warnings:
https://builds.apache.org/job/PreCommit-HBASE-Build/6998//artifact/trunk/patchprocess/newPatchFindbugsWarningshbase-hadoop1-compat.html
Findbugs warnings:
https://builds.apache.org/job/PreCommit-HBASE-Build/6998//artifact/trunk/patchprocess/newPatchFindbugsWarningshbase-prefix-tree.html
Findbugs warnings:
https://builds.apache.org/job/PreCommit-HBASE-Build/6998//artifact/trunk/patchprocess/newPatchFindbugsWarningshbase-common.html
Findbugs warnings:
https://builds.apache.org/job/PreCommit-HBASE-Build/6998//artifact/trunk/patchprocess/newPatchFindbugsWarningshbase-server.html
Findbugs warnings:
https://builds.apache.org/job/PreCommit-HBASE-Build/6998//artifact/trunk/patchprocess/newPatchFindbugsWarningshbase-hadoop-compat.html
Console output:
https://builds.apache.org/job/PreCommit-HBASE-Build/6998//console
This message is automatically generated.
> initCause() uses wrong exception in ProtobufLogReader#readNext(HLog$Entry)
> --
>
> Key: HBASE-9402
> URL: https://issues.apache.org/jira/browse/HBASE-9402
> Project: HBase
> Issue Type: Bug
>Reporter: Ted Yu
>Assignee: Ted Yu
>Priority: Minor
> Attachments: 9402.patch
>
>
> At line 250:
> {code}
> throw (EOFException) new EOFException("EOF " + message).
> initCause(realEofEx != null ? ex : realEofEx);
> {code}
> Looks like the position of realEofEx and ex should be like this:
> {code}
> initCause(realEofEx != null ? realEofEx : ex);
> {code}
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (HBASE-9334) Convert KeyValue to Cell in hbase-client module - Filters
[ https://issues.apache.org/jira/browse/HBASE-9334?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13755286#comment-13755286 ] Hudson commented on HBASE-9334: --- SUCCESS: Integrated in hbase-0.95-on-hadoop2 #283 (See [https://builds.apache.org/job/hbase-0.95-on-hadoop2/283/]) HBASE-9334 Convert KeyValue to Cell in hbase-client module - Filters HBASE-9359 Convert KeyValue to Cell in hbase-client module - Result/Put/Delete, ColumnInterpreter (jmhsieh: rev 1519076) * /hbase/branches/0.95/hbase-client/src/main/java/org/apache/hadoop/hbase/Coprocessor.java * /hbase/branches/0.95/hbase-client/src/main/java/org/apache/hadoop/hbase/client/ClientScanner.java * /hbase/branches/0.95/hbase-client/src/main/java/org/apache/hadoop/hbase/client/Delete.java * /hbase/branches/0.95/hbase-client/src/main/java/org/apache/hadoop/hbase/client/Get.java * /hbase/branches/0.95/hbase-client/src/main/java/org/apache/hadoop/hbase/client/Put.java * /hbase/branches/0.95/hbase-client/src/main/java/org/apache/hadoop/hbase/client/Result.java * /hbase/branches/0.95/hbase-client/src/main/java/org/apache/hadoop/hbase/client/ScannerCallable.java * /hbase/branches/0.95/hbase-client/src/main/java/org/apache/hadoop/hbase/client/coprocessor/BigDecimalColumnInterpreter.java * /hbase/branches/0.95/hbase-client/src/main/java/org/apache/hadoop/hbase/client/coprocessor/LongColumnInterpreter.java * /hbase/branches/0.95/hbase-client/src/main/java/org/apache/hadoop/hbase/coprocessor/ColumnInterpreter.java * /hbase/branches/0.95/hbase-client/src/main/java/org/apache/hadoop/hbase/filter/ColumnCountGetFilter.java * /hbase/branches/0.95/hbase-client/src/main/java/org/apache/hadoop/hbase/filter/ColumnPaginationFilter.java * /hbase/branches/0.95/hbase-client/src/main/java/org/apache/hadoop/hbase/filter/ColumnPrefixFilter.java * /hbase/branches/0.95/hbase-client/src/main/java/org/apache/hadoop/hbase/filter/ColumnRangeFilter.java * /hbase/branches/0.95/hbase-client/src/main/java/org/apache/hadoop/hbase/filter/CompareFilter.java * /hbase/branches/0.95/hbase-client/src/main/java/org/apache/hadoop/hbase/filter/DependentColumnFilter.java * /hbase/branches/0.95/hbase-client/src/main/java/org/apache/hadoop/hbase/filter/FamilyFilter.java * /hbase/branches/0.95/hbase-client/src/main/java/org/apache/hadoop/hbase/filter/Filter.java * /hbase/branches/0.95/hbase-client/src/main/java/org/apache/hadoop/hbase/filter/FilterBase.java * /hbase/branches/0.95/hbase-client/src/main/java/org/apache/hadoop/hbase/filter/FilterList.java * /hbase/branches/0.95/hbase-client/src/main/java/org/apache/hadoop/hbase/filter/FilterWrapper.java * /hbase/branches/0.95/hbase-client/src/main/java/org/apache/hadoop/hbase/filter/FirstKeyOnlyFilter.java * /hbase/branches/0.95/hbase-client/src/main/java/org/apache/hadoop/hbase/filter/FirstKeyValueMatchingQualifiersFilter.java * /hbase/branches/0.95/hbase-client/src/main/java/org/apache/hadoop/hbase/filter/FuzzyRowFilter.java * /hbase/branches/0.95/hbase-client/src/main/java/org/apache/hadoop/hbase/filter/KeyOnlyFilter.java * /hbase/branches/0.95/hbase-client/src/main/java/org/apache/hadoop/hbase/filter/MultipleColumnPrefixFilter.java * /hbase/branches/0.95/hbase-client/src/main/java/org/apache/hadoop/hbase/filter/NullComparator.java * /hbase/branches/0.95/hbase-client/src/main/java/org/apache/hadoop/hbase/filter/ParseFilter.java * /hbase/branches/0.95/hbase-client/src/main/java/org/apache/hadoop/hbase/filter/QualifierFilter.java * /hbase/branches/0.95/hbase-client/src/main/java/org/apache/hadoop/hbase/filter/RandomRowFilter.java * /hbase/branches/0.95/hbase-client/src/main/java/org/apache/hadoop/hbase/filter/RowFilter.java * /hbase/branches/0.95/hbase-client/src/main/java/org/apache/hadoop/hbase/filter/SingleColumnValueExcludeFilter.java * /hbase/branches/0.95/hbase-client/src/main/java/org/apache/hadoop/hbase/filter/SingleColumnValueFilter.java * /hbase/branches/0.95/hbase-client/src/main/java/org/apache/hadoop/hbase/filter/SkipFilter.java * /hbase/branches/0.95/hbase-client/src/main/java/org/apache/hadoop/hbase/filter/TimestampsFilter.java * /hbase/branches/0.95/hbase-client/src/main/java/org/apache/hadoop/hbase/filter/ValueFilter.java * /hbase/branches/0.95/hbase-client/src/main/java/org/apache/hadoop/hbase/filter/WhileMatchFilter.java * /hbase/branches/0.95/hbase-client/src/test/java/org/apache/hadoop/hbase/ipc/TestPayloadCarryingRpcController.java * /hbase/branches/0.95/hbase-common/src/main/java/org/apache/hadoop/hbase/Cell.java * /hbase/branches/0.95/hbase-common/src/main/java/org/apache/hadoop/hbase/CellUtil.java * /hbase/branches/0.95/hbase-common/src/main/java/org/apache/hadoop/hbase/KeyValue.java * /hbase/branches/0.95/hbase-common/src/main/java/org/apache/hadoop/hbase/KeyValueTestUtil.java * /hbase/branches/0.95/hbase-common/src/main/java/org/apache/hadoop/hbase/io/encoding/EncodedDataBlock.java * /hbase/branches/0.95/
[jira] [Commented] (HBASE-9395) Disable Schema Change on 0.96
[ https://issues.apache.org/jira/browse/HBASE-9395?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13755284#comment-13755284 ] Hudson commented on HBASE-9395: --- SUCCESS: Integrated in hbase-0.95-on-hadoop2 #283 (See [https://builds.apache.org/job/hbase-0.95-on-hadoop2/283/]) HBASE-9395 Disable Schema Change on 0.96 (eclark: rev 1519055) * /hbase/branches/0.95/hbase-common/src/main/resources/hbase-default.xml * /hbase/branches/0.95/hbase-it/src/test/java/org/apache/hadoop/hbase/chaos/factories/SlowDeterministicMonkeyFactory.java > Disable Schema Change on 0.96 > - > > Key: HBASE-9395 > URL: https://issues.apache.org/jira/browse/HBASE-9395 > Project: HBase > Issue Type: Bug > Components: master >Affects Versions: 0.98.0 >Reporter: Elliott Clark >Assignee: Elliott Clark >Priority: Blocker > Fix For: 0.96.0 > > Attachments: HBASE-9395-95-0.patch > > > Running LoadTestAndVerify fails when the chaos monkey is slowDeterministic. > When commenting out all of the schema change actions everything passes. We > should disable the schema change until we can be 100% sure of data integrity. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (HBASE-9359) Convert KeyValue to Cell in hbase-client module - Result/Put/Delete, ColumnInterpreter
[ https://issues.apache.org/jira/browse/HBASE-9359?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13755285#comment-13755285 ] Hudson commented on HBASE-9359: --- SUCCESS: Integrated in hbase-0.95-on-hadoop2 #283 (See [https://builds.apache.org/job/hbase-0.95-on-hadoop2/283/]) HBASE-9334 Convert KeyValue to Cell in hbase-client module - Filters HBASE-9359 Convert KeyValue to Cell in hbase-client module - Result/Put/Delete, ColumnInterpreter (jmhsieh: rev 1519076) * /hbase/branches/0.95/hbase-client/src/main/java/org/apache/hadoop/hbase/Coprocessor.java * /hbase/branches/0.95/hbase-client/src/main/java/org/apache/hadoop/hbase/client/ClientScanner.java * /hbase/branches/0.95/hbase-client/src/main/java/org/apache/hadoop/hbase/client/Delete.java * /hbase/branches/0.95/hbase-client/src/main/java/org/apache/hadoop/hbase/client/Get.java * /hbase/branches/0.95/hbase-client/src/main/java/org/apache/hadoop/hbase/client/Put.java * /hbase/branches/0.95/hbase-client/src/main/java/org/apache/hadoop/hbase/client/Result.java * /hbase/branches/0.95/hbase-client/src/main/java/org/apache/hadoop/hbase/client/ScannerCallable.java * /hbase/branches/0.95/hbase-client/src/main/java/org/apache/hadoop/hbase/client/coprocessor/BigDecimalColumnInterpreter.java * /hbase/branches/0.95/hbase-client/src/main/java/org/apache/hadoop/hbase/client/coprocessor/LongColumnInterpreter.java * /hbase/branches/0.95/hbase-client/src/main/java/org/apache/hadoop/hbase/coprocessor/ColumnInterpreter.java * /hbase/branches/0.95/hbase-client/src/main/java/org/apache/hadoop/hbase/filter/ColumnCountGetFilter.java * /hbase/branches/0.95/hbase-client/src/main/java/org/apache/hadoop/hbase/filter/ColumnPaginationFilter.java * /hbase/branches/0.95/hbase-client/src/main/java/org/apache/hadoop/hbase/filter/ColumnPrefixFilter.java * /hbase/branches/0.95/hbase-client/src/main/java/org/apache/hadoop/hbase/filter/ColumnRangeFilter.java * /hbase/branches/0.95/hbase-client/src/main/java/org/apache/hadoop/hbase/filter/CompareFilter.java * /hbase/branches/0.95/hbase-client/src/main/java/org/apache/hadoop/hbase/filter/DependentColumnFilter.java * /hbase/branches/0.95/hbase-client/src/main/java/org/apache/hadoop/hbase/filter/FamilyFilter.java * /hbase/branches/0.95/hbase-client/src/main/java/org/apache/hadoop/hbase/filter/Filter.java * /hbase/branches/0.95/hbase-client/src/main/java/org/apache/hadoop/hbase/filter/FilterBase.java * /hbase/branches/0.95/hbase-client/src/main/java/org/apache/hadoop/hbase/filter/FilterList.java * /hbase/branches/0.95/hbase-client/src/main/java/org/apache/hadoop/hbase/filter/FilterWrapper.java * /hbase/branches/0.95/hbase-client/src/main/java/org/apache/hadoop/hbase/filter/FirstKeyOnlyFilter.java * /hbase/branches/0.95/hbase-client/src/main/java/org/apache/hadoop/hbase/filter/FirstKeyValueMatchingQualifiersFilter.java * /hbase/branches/0.95/hbase-client/src/main/java/org/apache/hadoop/hbase/filter/FuzzyRowFilter.java * /hbase/branches/0.95/hbase-client/src/main/java/org/apache/hadoop/hbase/filter/KeyOnlyFilter.java * /hbase/branches/0.95/hbase-client/src/main/java/org/apache/hadoop/hbase/filter/MultipleColumnPrefixFilter.java * /hbase/branches/0.95/hbase-client/src/main/java/org/apache/hadoop/hbase/filter/NullComparator.java * /hbase/branches/0.95/hbase-client/src/main/java/org/apache/hadoop/hbase/filter/ParseFilter.java * /hbase/branches/0.95/hbase-client/src/main/java/org/apache/hadoop/hbase/filter/QualifierFilter.java * /hbase/branches/0.95/hbase-client/src/main/java/org/apache/hadoop/hbase/filter/RandomRowFilter.java * /hbase/branches/0.95/hbase-client/src/main/java/org/apache/hadoop/hbase/filter/RowFilter.java * /hbase/branches/0.95/hbase-client/src/main/java/org/apache/hadoop/hbase/filter/SingleColumnValueExcludeFilter.java * /hbase/branches/0.95/hbase-client/src/main/java/org/apache/hadoop/hbase/filter/SingleColumnValueFilter.java * /hbase/branches/0.95/hbase-client/src/main/java/org/apache/hadoop/hbase/filter/SkipFilter.java * /hbase/branches/0.95/hbase-client/src/main/java/org/apache/hadoop/hbase/filter/TimestampsFilter.java * /hbase/branches/0.95/hbase-client/src/main/java/org/apache/hadoop/hbase/filter/ValueFilter.java * /hbase/branches/0.95/hbase-client/src/main/java/org/apache/hadoop/hbase/filter/WhileMatchFilter.java * /hbase/branches/0.95/hbase-client/src/test/java/org/apache/hadoop/hbase/ipc/TestPayloadCarryingRpcController.java * /hbase/branches/0.95/hbase-common/src/main/java/org/apache/hadoop/hbase/Cell.java * /hbase/branches/0.95/hbase-common/src/main/java/org/apache/hadoop/hbase/CellUtil.java * /hbase/branches/0.95/hbase-common/src/main/java/org/apache/hadoop/hbase/KeyValue.java * /hbase/branches/0.95/hbase-common/src/main/java/org/apache/hadoop/hbase/KeyValueTestUtil.java * /hbase/branches/0.95/hbase-common/src/main/java/org/apache/hadoop/hbase/io/encoding/EncodedDataBlock.java * /hbase/branches/0.95/
[jira] [Commented] (HBASE-9404) Create Monitor Daemon instead of current web ui's
[ https://issues.apache.org/jira/browse/HBASE-9404?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13755276#comment-13755276 ] Elliott Clark commented on HBASE-9404: -- Some additional thoughts: * Could make it easier to get something like hannibal into main line hbase. * If you make it modular enough it's possible to use tsdb as one backend for stats. (with different backends for other systems and polling on json for fallback ) > Create Monitor Daemon instead of current web ui's > - > > Key: HBASE-9404 > URL: https://issues.apache.org/jira/browse/HBASE-9404 > Project: HBase > Issue Type: Improvement > Components: UI >Affects Versions: 0.98.0 >Reporter: Elliott Clark > > It's hard to get designers and front end developers to iterate on our web ui, > partly because it's not well separated, and partly because it's in java > jsp/jamon. It would be awesome to have something like Accumulo's monitor. > Have all of the current daemons just publish everything through json and > remove the current UI. Then we can separate the ui out into a monitor daemon > that's just UI. > This would do a couple of things: > * force us to publish everything that's interesting though the > metrics system. (Lots of stuff is there but some stuff isn't there.) > * remove a lot of resources from our hbase-server jar. > * make it easier to add graphing other features to the ui. > * allow us to remove some things from the rs -> master heart beat. > * encourage front end developers to get involved (wishful ?) -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Created] (HBASE-9405) Remove shim stuff from Filter
Jonathan Hsieh created HBASE-9405: - Summary: Remove shim stuff from Filter Key: HBASE-9405 URL: https://issues.apache.org/jira/browse/HBASE-9405 Project: HBase Issue Type: Sub-task Reporter: Jonathan Hsieh Aleks's compat report shows that Filter was an interface in 0.94 and is now an abstract class in 0.95/0.96. That means the shims aren't useful at all. Might as well remove them and add release notes requiring 3rd party filters to be modified to work on 0.96. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Created] (HBASE-9404) Create Monitor Daemon instead of current web ui's
Elliott Clark created HBASE-9404: Summary: Create Monitor Daemon instead of current web ui's Key: HBASE-9404 URL: https://issues.apache.org/jira/browse/HBASE-9404 Project: HBase Issue Type: Improvement Components: UI Affects Versions: 0.98.0 Reporter: Elliott Clark It's hard to get designers and front end developers to iterate on our web ui, partly because it's not well separated, and partly because it's in java jsp/jamon. It would be awesome to have something like Accumulo's monitor. Have all of the current daemons just publish everything through json and remove the current UI. Then we can separate the ui out into a monitor daemon that's just UI. This would do a couple of things: * force us to publish everything that's interesting though the metrics system. (Lots of stuff is there but some stuff isn't there.) * remove a lot of resources from our hbase-server jar. * make it easier to add graphing other features to the ui. * allow us to remove some things from the rs -> master heart beat. * encourage front end developers to get involved (wishful ?) -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (HBASE-9400) [UI] Catalog tables section isn't aligned
[ https://issues.apache.org/jira/browse/HBASE-9400?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Elliott Clark updated HBASE-9400: - Attachment: HBASE-9400-0.patch How does this look for you ? > [UI] Catalog tables section isn't aligned > - > > Key: HBASE-9400 > URL: https://issues.apache.org/jira/browse/HBASE-9400 > Project: HBase > Issue Type: Bug > Components: UI >Affects Versions: 0.95.2 >Reporter: Jimmy Xiang >Assignee: Elliott Clark >Priority: Minor > Attachments: catalog-tables.png, HBASE-9400-0.patch > > > I attached a picture of what I got. You can see it doesn't look right. > One more thing is that the page doesn't auto-refresh when you switch tabs. > For example, click Catalog tables, create a new table, click User tables, you > don't see the new table. You need to refresh the page to see it. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (HBASE-9400) [UI] Catalog tables section isn't aligned
[ https://issues.apache.org/jira/browse/HBASE-9400?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Elliott Clark updated HBASE-9400: - Affects Version/s: 0.96.0 Status: Patch Available (was: Open) > [UI] Catalog tables section isn't aligned > - > > Key: HBASE-9400 > URL: https://issues.apache.org/jira/browse/HBASE-9400 > Project: HBase > Issue Type: Bug > Components: UI >Affects Versions: 0.95.2, 0.96.0 >Reporter: Jimmy Xiang >Assignee: Elliott Clark >Priority: Minor > Attachments: catalog-tables.png, HBASE-9400-0.patch > > > I attached a picture of what I got. You can see it doesn't look right. > One more thing is that the page doesn't auto-refresh when you switch tabs. > For example, click Catalog tables, create a new table, click User tables, you > don't see the new table. You need to refresh the page to see it. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Assigned] (HBASE-9400) [UI] Catalog tables section isn't aligned
[ https://issues.apache.org/jira/browse/HBASE-9400?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Elliott Clark reassigned HBASE-9400: Assignee: Elliott Clark > [UI] Catalog tables section isn't aligned > - > > Key: HBASE-9400 > URL: https://issues.apache.org/jira/browse/HBASE-9400 > Project: HBase > Issue Type: Bug > Components: UI >Affects Versions: 0.95.2 >Reporter: Jimmy Xiang >Assignee: Elliott Clark >Priority: Minor > Attachments: catalog-tables.png, HBASE-9400-0.patch > > > I attached a picture of what I got. You can see it doesn't look right. > One more thing is that the page doesn't auto-refresh when you switch tabs. > For example, click Catalog tables, create a new table, click User tables, you > don't see the new table. You need to refresh the page to see it. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (HBASE-9387) Region could get lost during assignment
[
https://issues.apache.org/jira/browse/HBASE-9387?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13755262#comment-13755262
]
Hadoop QA commented on HBASE-9387:
--
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12600869/9387-v4.4.txt
against trunk revision .
{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 hadoop1.0{color}. The patch compiles against the hadoop
1.0 profile.
{color:green}+1 hadoop2.0{color}. The patch compiles against the hadoop
2.0 profile.
{color:green}+1 javadoc{color}. The javadoc tool did not generate any
warning messages.
{color:green}+1 javac{color}. The applied patch does not increase the
total number of javac compiler warnings.
{color:red}-1 findbugs{color}. The patch appears to introduce 1 new
Findbugs (version 1.3.9) 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/6997//testReport/
Findbugs warnings:
https://builds.apache.org/job/PreCommit-HBASE-Build/6997//artifact/trunk/patchprocess/newPatchFindbugsWarningshbase-prefix-tree.html
Findbugs warnings:
https://builds.apache.org/job/PreCommit-HBASE-Build/6997//artifact/trunk/patchprocess/newPatchFindbugsWarningshbase-client.html
Findbugs warnings:
https://builds.apache.org/job/PreCommit-HBASE-Build/6997//artifact/trunk/patchprocess/newPatchFindbugsWarningshbase-common.html
Findbugs warnings:
https://builds.apache.org/job/PreCommit-HBASE-Build/6997//artifact/trunk/patchprocess/newPatchFindbugsWarningshbase-protocol.html
Findbugs warnings:
https://builds.apache.org/job/PreCommit-HBASE-Build/6997//artifact/trunk/patchprocess/newPatchFindbugsWarningshbase-server.html
Findbugs warnings:
https://builds.apache.org/job/PreCommit-HBASE-Build/6997//artifact/trunk/patchprocess/newPatchFindbugsWarningshbase-hadoop1-compat.html
Findbugs warnings:
https://builds.apache.org/job/PreCommit-HBASE-Build/6997//artifact/trunk/patchprocess/newPatchFindbugsWarningshbase-examples.html
Findbugs warnings:
https://builds.apache.org/job/PreCommit-HBASE-Build/6997//artifact/trunk/patchprocess/newPatchFindbugsWarningshbase-hadoop-compat.html
Console output:
https://builds.apache.org/job/PreCommit-HBASE-Build/6997//console
This message is automatically generated.
> Region could get lost during assignment
> ---
>
> Key: HBASE-9387
> URL: https://issues.apache.org/jira/browse/HBASE-9387
> Project: HBase
> Issue Type: Bug
> Components: Region Assignment
>Affects Versions: 0.95.2
>Reporter: Ted Yu
>Assignee: Ted Yu
>Priority: Critical
> Attachments: 9387-v1.txt, 9387-v3.txt, 9387-v4.2.txt, 9387-v4.3.txt,
> 9387-v4.4.txt, 9387-v4.txt, 9387-v5.txt, hbase-9387.patch,
> org.apache.hadoop.hbase.TestFullLogReconstruction-output.txt
>
>
> I observed test timeout running against hadoop 2.1.0 with distributed log
> replay turned on.
> Looks like region state for 1588230740 became inconsistent between master and
> the surviving region server:
> {code}
> 2013-08-29 22:15:34,180 INFO [AM.ZK.Worker-pool2-t4]
> master.RegionStates(299): Onlined 1588230740 on
> kiyo.gq1.ygridcore.net,57016,1377814510039
> ...
> 2013-08-29 22:15:34,587 DEBUG [Thread-221]
> client.HConnectionManager$HConnectionImplementation(1269): locateRegionInMeta
> parentTable=hbase:meta, metaLocation={region=hbase:meta,,1.1588230740,
> hostname=kiyo.gq1.ygridcore.net,57016,1377814510039, seqNum=0}, attempt=2 of
> 35 failed; retrying after sleep of 302 because:
> org.apache.hadoop.hbase.exceptions.RegionOpeningException: Region is being
> opened: 1588230740
> at
> org.apache.hadoop.hbase.regionserver.HRegionServer.getRegionByEncodedName(HRegionServer.java:2574)
> at
> org.apache.hadoop.hbase.regionserver.HRegionServer.getRegion(HRegionServer.java:3949)
> at
> org.apache.hadoop.hbase.regionserver.HRegionServer.get(HRegionServer.java:2733)
> at
> org.apache.hadoop.hbase.protobuf.generated.ClientProtos$ClientService$2.callBlockingMethod(ClientProtos.java:26965)
> at org.apache.hadoop.hbase.ipc.RpcServer.call(RpcServer.java:2063)
> at
> org.apache.hadoop.hbase.ipc.RpcServer$CallRunner.run(RpcServer.java:1800)
> at
> org.apache.ha
[jira] [Created] (HBASE-9403) Build improvements
stack created HBASE-9403: Summary: Build improvements Key: HBASE-9403 URL: https://issues.apache.org/jira/browse/HBASE-9403 Project: HBase Issue Type: Task Reporter: stack Here are some improvements we could make to the build. Will list them as I think of them. Can do them individually as subtasks of this one. When I undo the hbase-X.Y.Z-hadoop1-bin.tar.gz tarball and look at the doc, the version is hbase-X.Y.Z-hadoop1 in the javadoc. Should be just hbase-X.Y.Z. This is so in the xref src and in javadoc. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (HBASE-9403) Build improvements
[ https://issues.apache.org/jira/browse/HBASE-9403?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] stack updated HBASE-9403: - Component/s: build > Build improvements > -- > > Key: HBASE-9403 > URL: https://issues.apache.org/jira/browse/HBASE-9403 > Project: HBase > Issue Type: Task > Components: build >Reporter: stack > > Here are some improvements we could make to the build. Will list them as I > think of them. Can do them individually as subtasks of this one. > When I undo the hbase-X.Y.Z-hadoop1-bin.tar.gz tarball and look at the doc, > the version is hbase-X.Y.Z-hadoop1 in the javadoc. Should be just > hbase-X.Y.Z. This is so in the xref src and in javadoc. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (HBASE-9401) Add getQualifierBufferShallowCopy to Cell Utility.
[ https://issues.apache.org/jira/browse/HBASE-9401?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Elliott Clark updated HBASE-9401: - Assignee: Elliott Clark Status: Patch Available (was: Open) > Add getQualifierBufferShallowCopy to Cell Utility. > -- > > Key: HBASE-9401 > URL: https://issues.apache.org/jira/browse/HBASE-9401 > Project: HBase > Issue Type: Task > Components: Client >Affects Versions: 0.96.0 >Reporter: Elliott Clark >Assignee: Elliott Clark > Attachments: HBASE-9401-0.patch > > > Right now if your qualifier is large and you need to access it, copying is > your only option. We should allow a shallow buffer copy. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (HBASE-9401) Add getQualifierBufferShallowCopy to Cell Utility.
[ https://issues.apache.org/jira/browse/HBASE-9401?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Elliott Clark updated HBASE-9401: - Attachment: HBASE-9401-0.patch > Add getQualifierBufferShallowCopy to Cell Utility. > -- > > Key: HBASE-9401 > URL: https://issues.apache.org/jira/browse/HBASE-9401 > Project: HBase > Issue Type: Task > Components: Client >Affects Versions: 0.96.0 >Reporter: Elliott Clark > Attachments: HBASE-9401-0.patch > > > Right now if your qualifier is large and you need to access it, copying is > your only option. We should allow a shallow buffer copy. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (HBASE-9402) initCause() uses wrong exception in ProtobufLogReader#readNext(HLog$Entry)
[
https://issues.apache.org/jira/browse/HBASE-9402?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ted Yu updated HBASE-9402:
--
Status: Patch Available (was: Open)
> initCause() uses wrong exception in ProtobufLogReader#readNext(HLog$Entry)
> --
>
> Key: HBASE-9402
> URL: https://issues.apache.org/jira/browse/HBASE-9402
> Project: HBase
> Issue Type: Bug
>Reporter: Ted Yu
>Assignee: Ted Yu
>Priority: Minor
> Attachments: 9402.patch
>
>
> At line 250:
> {code}
> throw (EOFException) new EOFException("EOF " + message).
> initCause(realEofEx != null ? ex : realEofEx);
> {code}
> Looks like the position of realEofEx and ex should be like this:
> {code}
> initCause(realEofEx != null ? realEofEx : ex);
> {code}
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (HBASE-9402) initCause() uses wrong exception in ProtobufLogReader#readNext(HLog$Entry)
[
https://issues.apache.org/jira/browse/HBASE-9402?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ted Yu updated HBASE-9402:
--
Attachment: 9402.patch
> initCause() uses wrong exception in ProtobufLogReader#readNext(HLog$Entry)
> --
>
> Key: HBASE-9402
> URL: https://issues.apache.org/jira/browse/HBASE-9402
> Project: HBase
> Issue Type: Bug
>Reporter: Ted Yu
>Assignee: Ted Yu
>Priority: Minor
> Attachments: 9402.patch
>
>
> At line 250:
> {code}
> throw (EOFException) new EOFException("EOF " + message).
> initCause(realEofEx != null ? ex : realEofEx);
> {code}
> Looks like the position of realEofEx and ex should be like this:
> {code}
> initCause(realEofEx != null ? realEofEx : ex);
> {code}
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Created] (HBASE-9402) initCause() uses wrong exception in ProtobufLogReader#readNext(HLog$Entry)
Ted Yu created HBASE-9402:
-
Summary: initCause() uses wrong exception in
ProtobufLogReader#readNext(HLog$Entry)
Key: HBASE-9402
URL: https://issues.apache.org/jira/browse/HBASE-9402
Project: HBase
Issue Type: Bug
Reporter: Ted Yu
Assignee: Ted Yu
Priority: Minor
At line 250:
{code}
throw (EOFException) new EOFException("EOF " + message).
initCause(realEofEx != null ? ex : realEofEx);
{code}
Looks like the position of realEofEx and ex should be like this:
{code}
initCause(realEofEx != null ? realEofEx : ex);
{code}
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Created] (HBASE-9401) Add getQualifierBufferShallowCopy to Cell Utility.
Elliott Clark created HBASE-9401: Summary: Add getQualifierBufferShallowCopy to Cell Utility. Key: HBASE-9401 URL: https://issues.apache.org/jira/browse/HBASE-9401 Project: HBase Issue Type: Task Components: Client Affects Versions: 0.96.0 Reporter: Elliott Clark Right now if your qualifier is large and you need to access it, copying is your only option. We should allow a shallow buffer copy. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (HBASE-9387) Region could get lost during assignment
[
https://issues.apache.org/jira/browse/HBASE-9387?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13755234#comment-13755234
]
stack commented on HBASE-9387:
--
[~jxiang] What you think boss?
> Region could get lost during assignment
> ---
>
> Key: HBASE-9387
> URL: https://issues.apache.org/jira/browse/HBASE-9387
> Project: HBase
> Issue Type: Bug
> Components: Region Assignment
>Affects Versions: 0.95.2
>Reporter: Ted Yu
>Assignee: Ted Yu
>Priority: Critical
> Attachments: 9387-v1.txt, 9387-v3.txt, 9387-v4.2.txt, 9387-v4.3.txt,
> 9387-v4.4.txt, 9387-v4.txt, 9387-v5.txt, hbase-9387.patch,
> org.apache.hadoop.hbase.TestFullLogReconstruction-output.txt
>
>
> I observed test timeout running against hadoop 2.1.0 with distributed log
> replay turned on.
> Looks like region state for 1588230740 became inconsistent between master and
> the surviving region server:
> {code}
> 2013-08-29 22:15:34,180 INFO [AM.ZK.Worker-pool2-t4]
> master.RegionStates(299): Onlined 1588230740 on
> kiyo.gq1.ygridcore.net,57016,1377814510039
> ...
> 2013-08-29 22:15:34,587 DEBUG [Thread-221]
> client.HConnectionManager$HConnectionImplementation(1269): locateRegionInMeta
> parentTable=hbase:meta, metaLocation={region=hbase:meta,,1.1588230740,
> hostname=kiyo.gq1.ygridcore.net,57016,1377814510039, seqNum=0}, attempt=2 of
> 35 failed; retrying after sleep of 302 because:
> org.apache.hadoop.hbase.exceptions.RegionOpeningException: Region is being
> opened: 1588230740
> at
> org.apache.hadoop.hbase.regionserver.HRegionServer.getRegionByEncodedName(HRegionServer.java:2574)
> at
> org.apache.hadoop.hbase.regionserver.HRegionServer.getRegion(HRegionServer.java:3949)
> at
> org.apache.hadoop.hbase.regionserver.HRegionServer.get(HRegionServer.java:2733)
> at
> org.apache.hadoop.hbase.protobuf.generated.ClientProtos$ClientService$2.callBlockingMethod(ClientProtos.java:26965)
> at org.apache.hadoop.hbase.ipc.RpcServer.call(RpcServer.java:2063)
> at
> org.apache.hadoop.hbase.ipc.RpcServer$CallRunner.run(RpcServer.java:1800)
> at
> org.apache.hadoop.hbase.ipc.SimpleRpcScheduler.consumerLoop(SimpleRpcScheduler.java:165)
> at
> org.apache.hadoop.hbase.ipc.SimpleRpcScheduler.access$000(SimpleRpcScheduler.java:41)
> {code}
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (HBASE-9334) Convert KeyValue to Cell in hbase-client module - Filters
[ https://issues.apache.org/jira/browse/HBASE-9334?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13755231#comment-13755231 ] Hudson commented on HBASE-9334: --- SUCCESS: Integrated in HBase-TRUNK #4452 (See [https://builds.apache.org/job/HBase-TRUNK/4452/]) HBASE-9334 Convert KeyValue to Cell in hbase-client module - Filters HBASE-9359 Convert KeyValue to Cell in hbase-client module - Result/Put/Delete, ColumnInterpreter (jmhsieh: rev 1519077) * /hbase/trunk/hbase-client/src/main/java/org/apache/hadoop/hbase/Coprocessor.java * /hbase/trunk/hbase-client/src/main/java/org/apache/hadoop/hbase/client/ClientScanner.java * /hbase/trunk/hbase-client/src/main/java/org/apache/hadoop/hbase/client/Delete.java * /hbase/trunk/hbase-client/src/main/java/org/apache/hadoop/hbase/client/Get.java * /hbase/trunk/hbase-client/src/main/java/org/apache/hadoop/hbase/client/Put.java * /hbase/trunk/hbase-client/src/main/java/org/apache/hadoop/hbase/client/Result.java * /hbase/trunk/hbase-client/src/main/java/org/apache/hadoop/hbase/client/ScannerCallable.java * /hbase/trunk/hbase-client/src/main/java/org/apache/hadoop/hbase/client/coprocessor/AggregationClient.java * /hbase/trunk/hbase-client/src/main/java/org/apache/hadoop/hbase/client/coprocessor/BigDecimalColumnInterpreter.java * /hbase/trunk/hbase-client/src/main/java/org/apache/hadoop/hbase/client/coprocessor/LongColumnInterpreter.java * /hbase/trunk/hbase-client/src/main/java/org/apache/hadoop/hbase/coprocessor/ColumnInterpreter.java * /hbase/trunk/hbase-client/src/main/java/org/apache/hadoop/hbase/filter/ColumnCountGetFilter.java * /hbase/trunk/hbase-client/src/main/java/org/apache/hadoop/hbase/filter/ColumnPaginationFilter.java * /hbase/trunk/hbase-client/src/main/java/org/apache/hadoop/hbase/filter/ColumnPrefixFilter.java * /hbase/trunk/hbase-client/src/main/java/org/apache/hadoop/hbase/filter/ColumnRangeFilter.java * /hbase/trunk/hbase-client/src/main/java/org/apache/hadoop/hbase/filter/CompareFilter.java * /hbase/trunk/hbase-client/src/main/java/org/apache/hadoop/hbase/filter/DependentColumnFilter.java * /hbase/trunk/hbase-client/src/main/java/org/apache/hadoop/hbase/filter/FamilyFilter.java * /hbase/trunk/hbase-client/src/main/java/org/apache/hadoop/hbase/filter/Filter.java * /hbase/trunk/hbase-client/src/main/java/org/apache/hadoop/hbase/filter/FilterBase.java * /hbase/trunk/hbase-client/src/main/java/org/apache/hadoop/hbase/filter/FilterList.java * /hbase/trunk/hbase-client/src/main/java/org/apache/hadoop/hbase/filter/FilterWrapper.java * /hbase/trunk/hbase-client/src/main/java/org/apache/hadoop/hbase/filter/FirstKeyOnlyFilter.java * /hbase/trunk/hbase-client/src/main/java/org/apache/hadoop/hbase/filter/FirstKeyValueMatchingQualifiersFilter.java * /hbase/trunk/hbase-client/src/main/java/org/apache/hadoop/hbase/filter/FuzzyRowFilter.java * /hbase/trunk/hbase-client/src/main/java/org/apache/hadoop/hbase/filter/KeyOnlyFilter.java * /hbase/trunk/hbase-client/src/main/java/org/apache/hadoop/hbase/filter/MultipleColumnPrefixFilter.java * /hbase/trunk/hbase-client/src/main/java/org/apache/hadoop/hbase/filter/NullComparator.java * /hbase/trunk/hbase-client/src/main/java/org/apache/hadoop/hbase/filter/ParseFilter.java * /hbase/trunk/hbase-client/src/main/java/org/apache/hadoop/hbase/filter/QualifierFilter.java * /hbase/trunk/hbase-client/src/main/java/org/apache/hadoop/hbase/filter/RandomRowFilter.java * /hbase/trunk/hbase-client/src/main/java/org/apache/hadoop/hbase/filter/RowFilter.java * /hbase/trunk/hbase-client/src/main/java/org/apache/hadoop/hbase/filter/SingleColumnValueExcludeFilter.java * /hbase/trunk/hbase-client/src/main/java/org/apache/hadoop/hbase/filter/SingleColumnValueFilter.java * /hbase/trunk/hbase-client/src/main/java/org/apache/hadoop/hbase/filter/SkipFilter.java * /hbase/trunk/hbase-client/src/main/java/org/apache/hadoop/hbase/filter/TimestampsFilter.java * /hbase/trunk/hbase-client/src/main/java/org/apache/hadoop/hbase/filter/ValueFilter.java * /hbase/trunk/hbase-client/src/main/java/org/apache/hadoop/hbase/filter/WhileMatchFilter.java * /hbase/trunk/hbase-client/src/test/java/org/apache/hadoop/hbase/ipc/TestPayloadCarryingRpcController.java * /hbase/trunk/hbase-common/src/main/java/org/apache/hadoop/hbase/Cell.java * /hbase/trunk/hbase-common/src/main/java/org/apache/hadoop/hbase/CellUtil.java * /hbase/trunk/hbase-common/src/main/java/org/apache/hadoop/hbase/KeyValue.java * /hbase/trunk/hbase-common/src/main/java/org/apache/hadoop/hbase/KeyValueTestUtil.java * /hbase/trunk/hbase-common/src/main/java/org/apache/hadoop/hbase/io/encoding/EncodedDataBlock.java * /hbase/trunk/hbase-examples/src/main/java/org/apache/hadoop/hbase/coprocessor/example/BulkDeleteEndpoint.java * /hbase/trunk/hbase-examples/src/main/java/org/apache/hadoop/hbase/coprocessor/example/RowCountEndpoint.java * /hbase/trunk/hbase-examples/src/test/java/org/apache/h
[jira] [Commented] (HBASE-9359) Convert KeyValue to Cell in hbase-client module - Result/Put/Delete, ColumnInterpreter
[ https://issues.apache.org/jira/browse/HBASE-9359?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13755230#comment-13755230 ] Hudson commented on HBASE-9359: --- SUCCESS: Integrated in HBase-TRUNK #4452 (See [https://builds.apache.org/job/HBase-TRUNK/4452/]) HBASE-9334 Convert KeyValue to Cell in hbase-client module - Filters HBASE-9359 Convert KeyValue to Cell in hbase-client module - Result/Put/Delete, ColumnInterpreter (jmhsieh: rev 1519077) * /hbase/trunk/hbase-client/src/main/java/org/apache/hadoop/hbase/Coprocessor.java * /hbase/trunk/hbase-client/src/main/java/org/apache/hadoop/hbase/client/ClientScanner.java * /hbase/trunk/hbase-client/src/main/java/org/apache/hadoop/hbase/client/Delete.java * /hbase/trunk/hbase-client/src/main/java/org/apache/hadoop/hbase/client/Get.java * /hbase/trunk/hbase-client/src/main/java/org/apache/hadoop/hbase/client/Put.java * /hbase/trunk/hbase-client/src/main/java/org/apache/hadoop/hbase/client/Result.java * /hbase/trunk/hbase-client/src/main/java/org/apache/hadoop/hbase/client/ScannerCallable.java * /hbase/trunk/hbase-client/src/main/java/org/apache/hadoop/hbase/client/coprocessor/AggregationClient.java * /hbase/trunk/hbase-client/src/main/java/org/apache/hadoop/hbase/client/coprocessor/BigDecimalColumnInterpreter.java * /hbase/trunk/hbase-client/src/main/java/org/apache/hadoop/hbase/client/coprocessor/LongColumnInterpreter.java * /hbase/trunk/hbase-client/src/main/java/org/apache/hadoop/hbase/coprocessor/ColumnInterpreter.java * /hbase/trunk/hbase-client/src/main/java/org/apache/hadoop/hbase/filter/ColumnCountGetFilter.java * /hbase/trunk/hbase-client/src/main/java/org/apache/hadoop/hbase/filter/ColumnPaginationFilter.java * /hbase/trunk/hbase-client/src/main/java/org/apache/hadoop/hbase/filter/ColumnPrefixFilter.java * /hbase/trunk/hbase-client/src/main/java/org/apache/hadoop/hbase/filter/ColumnRangeFilter.java * /hbase/trunk/hbase-client/src/main/java/org/apache/hadoop/hbase/filter/CompareFilter.java * /hbase/trunk/hbase-client/src/main/java/org/apache/hadoop/hbase/filter/DependentColumnFilter.java * /hbase/trunk/hbase-client/src/main/java/org/apache/hadoop/hbase/filter/FamilyFilter.java * /hbase/trunk/hbase-client/src/main/java/org/apache/hadoop/hbase/filter/Filter.java * /hbase/trunk/hbase-client/src/main/java/org/apache/hadoop/hbase/filter/FilterBase.java * /hbase/trunk/hbase-client/src/main/java/org/apache/hadoop/hbase/filter/FilterList.java * /hbase/trunk/hbase-client/src/main/java/org/apache/hadoop/hbase/filter/FilterWrapper.java * /hbase/trunk/hbase-client/src/main/java/org/apache/hadoop/hbase/filter/FirstKeyOnlyFilter.java * /hbase/trunk/hbase-client/src/main/java/org/apache/hadoop/hbase/filter/FirstKeyValueMatchingQualifiersFilter.java * /hbase/trunk/hbase-client/src/main/java/org/apache/hadoop/hbase/filter/FuzzyRowFilter.java * /hbase/trunk/hbase-client/src/main/java/org/apache/hadoop/hbase/filter/KeyOnlyFilter.java * /hbase/trunk/hbase-client/src/main/java/org/apache/hadoop/hbase/filter/MultipleColumnPrefixFilter.java * /hbase/trunk/hbase-client/src/main/java/org/apache/hadoop/hbase/filter/NullComparator.java * /hbase/trunk/hbase-client/src/main/java/org/apache/hadoop/hbase/filter/ParseFilter.java * /hbase/trunk/hbase-client/src/main/java/org/apache/hadoop/hbase/filter/QualifierFilter.java * /hbase/trunk/hbase-client/src/main/java/org/apache/hadoop/hbase/filter/RandomRowFilter.java * /hbase/trunk/hbase-client/src/main/java/org/apache/hadoop/hbase/filter/RowFilter.java * /hbase/trunk/hbase-client/src/main/java/org/apache/hadoop/hbase/filter/SingleColumnValueExcludeFilter.java * /hbase/trunk/hbase-client/src/main/java/org/apache/hadoop/hbase/filter/SingleColumnValueFilter.java * /hbase/trunk/hbase-client/src/main/java/org/apache/hadoop/hbase/filter/SkipFilter.java * /hbase/trunk/hbase-client/src/main/java/org/apache/hadoop/hbase/filter/TimestampsFilter.java * /hbase/trunk/hbase-client/src/main/java/org/apache/hadoop/hbase/filter/ValueFilter.java * /hbase/trunk/hbase-client/src/main/java/org/apache/hadoop/hbase/filter/WhileMatchFilter.java * /hbase/trunk/hbase-client/src/test/java/org/apache/hadoop/hbase/ipc/TestPayloadCarryingRpcController.java * /hbase/trunk/hbase-common/src/main/java/org/apache/hadoop/hbase/Cell.java * /hbase/trunk/hbase-common/src/main/java/org/apache/hadoop/hbase/CellUtil.java * /hbase/trunk/hbase-common/src/main/java/org/apache/hadoop/hbase/KeyValue.java * /hbase/trunk/hbase-common/src/main/java/org/apache/hadoop/hbase/KeyValueTestUtil.java * /hbase/trunk/hbase-common/src/main/java/org/apache/hadoop/hbase/io/encoding/EncodedDataBlock.java * /hbase/trunk/hbase-examples/src/main/java/org/apache/hadoop/hbase/coprocessor/example/BulkDeleteEndpoint.java * /hbase/trunk/hbase-examples/src/main/java/org/apache/hadoop/hbase/coprocessor/example/RowCountEndpoint.java * /hbase/trunk/hbase-examples/src/test/java/org/apache/h
[jira] [Updated] (HBASE-9400) [UI] Catalog tables section isn't aligned
[ https://issues.apache.org/jira/browse/HBASE-9400?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jimmy Xiang updated HBASE-9400: --- Priority: Minor (was: Major) > [UI] Catalog tables section isn't aligned > - > > Key: HBASE-9400 > URL: https://issues.apache.org/jira/browse/HBASE-9400 > Project: HBase > Issue Type: Bug > Components: UI >Affects Versions: 0.95.2 >Reporter: Jimmy Xiang >Priority: Minor > Attachments: catalog-tables.png > > > I attached a picture of what I got. You can see it doesn't look right. > One more thing is that the page doesn't auto-refresh when you switch tabs. > For example, click Catalog tables, create a new table, click User tables, you > don't see the new table. You need to refresh the page to see it. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (HBASE-9400) [UI] Catalog tables section isn't aligned
[ https://issues.apache.org/jira/browse/HBASE-9400?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13755226#comment-13755226 ] Elliott Clark commented on HBASE-9400: -- bq.One more thing is that the page doesn't auto-refresh when you switch tabs. I'm not seeing that at all. Are there js errors on your web ui ? > [UI] Catalog tables section isn't aligned > - > > Key: HBASE-9400 > URL: https://issues.apache.org/jira/browse/HBASE-9400 > Project: HBase > Issue Type: Bug > Components: UI >Affects Versions: 0.95.2 >Reporter: Jimmy Xiang > Attachments: catalog-tables.png > > > I attached a picture of what I got. You can see it doesn't look right. > One more thing is that the page doesn't auto-refresh when you switch tabs. > For example, click Catalog tables, create a new table, click User tables, you > don't see the new table. You need to refresh the page to see it. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (HBASE-9400) [UI] Catalog tables section isn't aligned
[ https://issues.apache.org/jira/browse/HBASE-9400?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jimmy Xiang updated HBASE-9400: --- Attachment: catalog-tables.png > [UI] Catalog tables section isn't aligned > - > > Key: HBASE-9400 > URL: https://issues.apache.org/jira/browse/HBASE-9400 > Project: HBase > Issue Type: Bug > Components: UI >Reporter: Jimmy Xiang > Attachments: catalog-tables.png > > > I attached a picture of what I got. You can see it doesn't look right. > One more thing is that the page doesn't auto-refresh when you switch tabs. > For example, click Catalog tables, create a new table, click User tables, you > don't see the new table. You need to refresh the page to see it. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (HBASE-9400) [UI] Catalog tables section isn't aligned
[ https://issues.apache.org/jira/browse/HBASE-9400?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jimmy Xiang updated HBASE-9400: --- Affects Version/s: 0.95.2 > [UI] Catalog tables section isn't aligned > - > > Key: HBASE-9400 > URL: https://issues.apache.org/jira/browse/HBASE-9400 > Project: HBase > Issue Type: Bug > Components: UI >Affects Versions: 0.95.2 >Reporter: Jimmy Xiang > Attachments: catalog-tables.png > > > I attached a picture of what I got. You can see it doesn't look right. > One more thing is that the page doesn't auto-refresh when you switch tabs. > For example, click Catalog tables, create a new table, click User tables, you > don't see the new table. You need to refresh the page to see it. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Created] (HBASE-9400) [UI] Catalog tables section isn't aligned
Jimmy Xiang created HBASE-9400: -- Summary: [UI] Catalog tables section isn't aligned Key: HBASE-9400 URL: https://issues.apache.org/jira/browse/HBASE-9400 Project: HBase Issue Type: Bug Components: UI Reporter: Jimmy Xiang I attached a picture of what I got. You can see it doesn't look right. One more thing is that the page doesn't auto-refresh when you switch tabs. For example, click Catalog tables, create a new table, click User tables, you don't see the new table. You need to refresh the page to see it. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (HBASE-9399) Up the memstore flush size
[ https://issues.apache.org/jira/browse/HBASE-9399?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13755221#comment-13755221 ] Elliott Clark commented on HBASE-9399: -- My test cluster is pretty slammed right now with testing 0.96. I'll try and get some perf numbers sometime next week. > Up the memstore flush size > -- > > Key: HBASE-9399 > URL: https://issues.apache.org/jira/browse/HBASE-9399 > Project: HBase > Issue Type: Task > Components: regionserver >Affects Versions: 0.98.0, 0.96.0 >Reporter: Elliott Clark >Assignee: Elliott Clark > > As heap sizes get bigger we are still recommending that users keep their > number of regions to a minimum. This leads to lots of un-used memstore > memory. > For example I have a region server with 48 gigs of ram. 30 gigs are there > for the region server. This with current defaults the global memstore size > reserved is 8 gigs. > The per region memstore size is 128mb right now. That means that I need 80 > regions actively taking writes to reach the global memstore size. That > number is way out of line with what our split policies currently give users. > They are given much fewer regions by default. > We should up the hbase.hregion.memstore.flush.size size. Ideally we should > auto tune everything. But until then I think something like 512mb would help > a lot with our write throughput on clusters that don't have several hundred > regions per RS. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (HBASE-9359) Convert KeyValue to Cell in hbase-client module - Result/Put/Delete, ColumnInterpreter
[ https://issues.apache.org/jira/browse/HBASE-9359?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13755206#comment-13755206 ] Hudson commented on HBASE-9359: --- SUCCESS: Integrated in hbase-0.95 #511 (See [https://builds.apache.org/job/hbase-0.95/511/]) HBASE-9334 Convert KeyValue to Cell in hbase-client module - Filters HBASE-9359 Convert KeyValue to Cell in hbase-client module - Result/Put/Delete, ColumnInterpreter (jmhsieh: rev 1519076) * /hbase/branches/0.95/hbase-client/src/main/java/org/apache/hadoop/hbase/Coprocessor.java * /hbase/branches/0.95/hbase-client/src/main/java/org/apache/hadoop/hbase/client/ClientScanner.java * /hbase/branches/0.95/hbase-client/src/main/java/org/apache/hadoop/hbase/client/Delete.java * /hbase/branches/0.95/hbase-client/src/main/java/org/apache/hadoop/hbase/client/Get.java * /hbase/branches/0.95/hbase-client/src/main/java/org/apache/hadoop/hbase/client/Put.java * /hbase/branches/0.95/hbase-client/src/main/java/org/apache/hadoop/hbase/client/Result.java * /hbase/branches/0.95/hbase-client/src/main/java/org/apache/hadoop/hbase/client/ScannerCallable.java * /hbase/branches/0.95/hbase-client/src/main/java/org/apache/hadoop/hbase/client/coprocessor/BigDecimalColumnInterpreter.java * /hbase/branches/0.95/hbase-client/src/main/java/org/apache/hadoop/hbase/client/coprocessor/LongColumnInterpreter.java * /hbase/branches/0.95/hbase-client/src/main/java/org/apache/hadoop/hbase/coprocessor/ColumnInterpreter.java * /hbase/branches/0.95/hbase-client/src/main/java/org/apache/hadoop/hbase/filter/ColumnCountGetFilter.java * /hbase/branches/0.95/hbase-client/src/main/java/org/apache/hadoop/hbase/filter/ColumnPaginationFilter.java * /hbase/branches/0.95/hbase-client/src/main/java/org/apache/hadoop/hbase/filter/ColumnPrefixFilter.java * /hbase/branches/0.95/hbase-client/src/main/java/org/apache/hadoop/hbase/filter/ColumnRangeFilter.java * /hbase/branches/0.95/hbase-client/src/main/java/org/apache/hadoop/hbase/filter/CompareFilter.java * /hbase/branches/0.95/hbase-client/src/main/java/org/apache/hadoop/hbase/filter/DependentColumnFilter.java * /hbase/branches/0.95/hbase-client/src/main/java/org/apache/hadoop/hbase/filter/FamilyFilter.java * /hbase/branches/0.95/hbase-client/src/main/java/org/apache/hadoop/hbase/filter/Filter.java * /hbase/branches/0.95/hbase-client/src/main/java/org/apache/hadoop/hbase/filter/FilterBase.java * /hbase/branches/0.95/hbase-client/src/main/java/org/apache/hadoop/hbase/filter/FilterList.java * /hbase/branches/0.95/hbase-client/src/main/java/org/apache/hadoop/hbase/filter/FilterWrapper.java * /hbase/branches/0.95/hbase-client/src/main/java/org/apache/hadoop/hbase/filter/FirstKeyOnlyFilter.java * /hbase/branches/0.95/hbase-client/src/main/java/org/apache/hadoop/hbase/filter/FirstKeyValueMatchingQualifiersFilter.java * /hbase/branches/0.95/hbase-client/src/main/java/org/apache/hadoop/hbase/filter/FuzzyRowFilter.java * /hbase/branches/0.95/hbase-client/src/main/java/org/apache/hadoop/hbase/filter/KeyOnlyFilter.java * /hbase/branches/0.95/hbase-client/src/main/java/org/apache/hadoop/hbase/filter/MultipleColumnPrefixFilter.java * /hbase/branches/0.95/hbase-client/src/main/java/org/apache/hadoop/hbase/filter/NullComparator.java * /hbase/branches/0.95/hbase-client/src/main/java/org/apache/hadoop/hbase/filter/ParseFilter.java * /hbase/branches/0.95/hbase-client/src/main/java/org/apache/hadoop/hbase/filter/QualifierFilter.java * /hbase/branches/0.95/hbase-client/src/main/java/org/apache/hadoop/hbase/filter/RandomRowFilter.java * /hbase/branches/0.95/hbase-client/src/main/java/org/apache/hadoop/hbase/filter/RowFilter.java * /hbase/branches/0.95/hbase-client/src/main/java/org/apache/hadoop/hbase/filter/SingleColumnValueExcludeFilter.java * /hbase/branches/0.95/hbase-client/src/main/java/org/apache/hadoop/hbase/filter/SingleColumnValueFilter.java * /hbase/branches/0.95/hbase-client/src/main/java/org/apache/hadoop/hbase/filter/SkipFilter.java * /hbase/branches/0.95/hbase-client/src/main/java/org/apache/hadoop/hbase/filter/TimestampsFilter.java * /hbase/branches/0.95/hbase-client/src/main/java/org/apache/hadoop/hbase/filter/ValueFilter.java * /hbase/branches/0.95/hbase-client/src/main/java/org/apache/hadoop/hbase/filter/WhileMatchFilter.java * /hbase/branches/0.95/hbase-client/src/test/java/org/apache/hadoop/hbase/ipc/TestPayloadCarryingRpcController.java * /hbase/branches/0.95/hbase-common/src/main/java/org/apache/hadoop/hbase/Cell.java * /hbase/branches/0.95/hbase-common/src/main/java/org/apache/hadoop/hbase/CellUtil.java * /hbase/branches/0.95/hbase-common/src/main/java/org/apache/hadoop/hbase/KeyValue.java * /hbase/branches/0.95/hbase-common/src/main/java/org/apache/hadoop/hbase/KeyValueTestUtil.java * /hbase/branches/0.95/hbase-common/src/main/java/org/apache/hadoop/hbase/io/encoding/EncodedDataBlock.java * /hbase/branches/0.95/hbase-examples/src/mai
[jira] [Commented] (HBASE-9334) Convert KeyValue to Cell in hbase-client module - Filters
[ https://issues.apache.org/jira/browse/HBASE-9334?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13755207#comment-13755207 ] Hudson commented on HBASE-9334: --- SUCCESS: Integrated in hbase-0.95 #511 (See [https://builds.apache.org/job/hbase-0.95/511/]) HBASE-9334 Convert KeyValue to Cell in hbase-client module - Filters HBASE-9359 Convert KeyValue to Cell in hbase-client module - Result/Put/Delete, ColumnInterpreter (jmhsieh: rev 1519076) * /hbase/branches/0.95/hbase-client/src/main/java/org/apache/hadoop/hbase/Coprocessor.java * /hbase/branches/0.95/hbase-client/src/main/java/org/apache/hadoop/hbase/client/ClientScanner.java * /hbase/branches/0.95/hbase-client/src/main/java/org/apache/hadoop/hbase/client/Delete.java * /hbase/branches/0.95/hbase-client/src/main/java/org/apache/hadoop/hbase/client/Get.java * /hbase/branches/0.95/hbase-client/src/main/java/org/apache/hadoop/hbase/client/Put.java * /hbase/branches/0.95/hbase-client/src/main/java/org/apache/hadoop/hbase/client/Result.java * /hbase/branches/0.95/hbase-client/src/main/java/org/apache/hadoop/hbase/client/ScannerCallable.java * /hbase/branches/0.95/hbase-client/src/main/java/org/apache/hadoop/hbase/client/coprocessor/BigDecimalColumnInterpreter.java * /hbase/branches/0.95/hbase-client/src/main/java/org/apache/hadoop/hbase/client/coprocessor/LongColumnInterpreter.java * /hbase/branches/0.95/hbase-client/src/main/java/org/apache/hadoop/hbase/coprocessor/ColumnInterpreter.java * /hbase/branches/0.95/hbase-client/src/main/java/org/apache/hadoop/hbase/filter/ColumnCountGetFilter.java * /hbase/branches/0.95/hbase-client/src/main/java/org/apache/hadoop/hbase/filter/ColumnPaginationFilter.java * /hbase/branches/0.95/hbase-client/src/main/java/org/apache/hadoop/hbase/filter/ColumnPrefixFilter.java * /hbase/branches/0.95/hbase-client/src/main/java/org/apache/hadoop/hbase/filter/ColumnRangeFilter.java * /hbase/branches/0.95/hbase-client/src/main/java/org/apache/hadoop/hbase/filter/CompareFilter.java * /hbase/branches/0.95/hbase-client/src/main/java/org/apache/hadoop/hbase/filter/DependentColumnFilter.java * /hbase/branches/0.95/hbase-client/src/main/java/org/apache/hadoop/hbase/filter/FamilyFilter.java * /hbase/branches/0.95/hbase-client/src/main/java/org/apache/hadoop/hbase/filter/Filter.java * /hbase/branches/0.95/hbase-client/src/main/java/org/apache/hadoop/hbase/filter/FilterBase.java * /hbase/branches/0.95/hbase-client/src/main/java/org/apache/hadoop/hbase/filter/FilterList.java * /hbase/branches/0.95/hbase-client/src/main/java/org/apache/hadoop/hbase/filter/FilterWrapper.java * /hbase/branches/0.95/hbase-client/src/main/java/org/apache/hadoop/hbase/filter/FirstKeyOnlyFilter.java * /hbase/branches/0.95/hbase-client/src/main/java/org/apache/hadoop/hbase/filter/FirstKeyValueMatchingQualifiersFilter.java * /hbase/branches/0.95/hbase-client/src/main/java/org/apache/hadoop/hbase/filter/FuzzyRowFilter.java * /hbase/branches/0.95/hbase-client/src/main/java/org/apache/hadoop/hbase/filter/KeyOnlyFilter.java * /hbase/branches/0.95/hbase-client/src/main/java/org/apache/hadoop/hbase/filter/MultipleColumnPrefixFilter.java * /hbase/branches/0.95/hbase-client/src/main/java/org/apache/hadoop/hbase/filter/NullComparator.java * /hbase/branches/0.95/hbase-client/src/main/java/org/apache/hadoop/hbase/filter/ParseFilter.java * /hbase/branches/0.95/hbase-client/src/main/java/org/apache/hadoop/hbase/filter/QualifierFilter.java * /hbase/branches/0.95/hbase-client/src/main/java/org/apache/hadoop/hbase/filter/RandomRowFilter.java * /hbase/branches/0.95/hbase-client/src/main/java/org/apache/hadoop/hbase/filter/RowFilter.java * /hbase/branches/0.95/hbase-client/src/main/java/org/apache/hadoop/hbase/filter/SingleColumnValueExcludeFilter.java * /hbase/branches/0.95/hbase-client/src/main/java/org/apache/hadoop/hbase/filter/SingleColumnValueFilter.java * /hbase/branches/0.95/hbase-client/src/main/java/org/apache/hadoop/hbase/filter/SkipFilter.java * /hbase/branches/0.95/hbase-client/src/main/java/org/apache/hadoop/hbase/filter/TimestampsFilter.java * /hbase/branches/0.95/hbase-client/src/main/java/org/apache/hadoop/hbase/filter/ValueFilter.java * /hbase/branches/0.95/hbase-client/src/main/java/org/apache/hadoop/hbase/filter/WhileMatchFilter.java * /hbase/branches/0.95/hbase-client/src/test/java/org/apache/hadoop/hbase/ipc/TestPayloadCarryingRpcController.java * /hbase/branches/0.95/hbase-common/src/main/java/org/apache/hadoop/hbase/Cell.java * /hbase/branches/0.95/hbase-common/src/main/java/org/apache/hadoop/hbase/CellUtil.java * /hbase/branches/0.95/hbase-common/src/main/java/org/apache/hadoop/hbase/KeyValue.java * /hbase/branches/0.95/hbase-common/src/main/java/org/apache/hadoop/hbase/KeyValueTestUtil.java * /hbase/branches/0.95/hbase-common/src/main/java/org/apache/hadoop/hbase/io/encoding/EncodedDataBlock.java * /hbase/branches/0.95/hbase-examples/src/mai
[jira] [Commented] (HBASE-9395) Disable Schema Change on 0.96
[ https://issues.apache.org/jira/browse/HBASE-9395?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13755205#comment-13755205 ] Hudson commented on HBASE-9395: --- SUCCESS: Integrated in hbase-0.95 #511 (See [https://builds.apache.org/job/hbase-0.95/511/]) HBASE-9395 Disable Schema Change on 0.96 (eclark: rev 1519055) * /hbase/branches/0.95/hbase-common/src/main/resources/hbase-default.xml * /hbase/branches/0.95/hbase-it/src/test/java/org/apache/hadoop/hbase/chaos/factories/SlowDeterministicMonkeyFactory.java > Disable Schema Change on 0.96 > - > > Key: HBASE-9395 > URL: https://issues.apache.org/jira/browse/HBASE-9395 > Project: HBase > Issue Type: Bug > Components: master >Affects Versions: 0.98.0 >Reporter: Elliott Clark >Assignee: Elliott Clark >Priority: Blocker > Fix For: 0.96.0 > > Attachments: HBASE-9395-95-0.patch > > > Running LoadTestAndVerify fails when the chaos monkey is slowDeterministic. > When commenting out all of the schema change actions everything passes. We > should disable the schema change until we can be 100% sure of data integrity. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (HBASE-9387) Region could get lost during assignment
[
https://issues.apache.org/jira/browse/HBASE-9387?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13755204#comment-13755204
]
Hadoop QA commented on HBASE-9387:
--
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12600857/9387-v4.3.txt
against trunk revision .
{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 hadoop1.0{color}. The patch compiles against the hadoop
1.0 profile.
{color:green}+1 hadoop2.0{color}. The patch compiles against the hadoop
2.0 profile.
{color:green}+1 javadoc{color}. The javadoc tool did not generate any
warning messages.
{color:green}+1 javac{color}. The applied patch does not increase the
total number of javac compiler warnings.
{color:red}-1 findbugs{color}. The patch appears to introduce 1 new
Findbugs (version 1.3.9) 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/6996//testReport/
Findbugs warnings:
https://builds.apache.org/job/PreCommit-HBASE-Build/6996//artifact/trunk/patchprocess/newPatchFindbugsWarningshbase-protocol.html
Findbugs warnings:
https://builds.apache.org/job/PreCommit-HBASE-Build/6996//artifact/trunk/patchprocess/newPatchFindbugsWarningshbase-client.html
Findbugs warnings:
https://builds.apache.org/job/PreCommit-HBASE-Build/6996//artifact/trunk/patchprocess/newPatchFindbugsWarningshbase-examples.html
Findbugs warnings:
https://builds.apache.org/job/PreCommit-HBASE-Build/6996//artifact/trunk/patchprocess/newPatchFindbugsWarningshbase-hadoop1-compat.html
Findbugs warnings:
https://builds.apache.org/job/PreCommit-HBASE-Build/6996//artifact/trunk/patchprocess/newPatchFindbugsWarningshbase-prefix-tree.html
Findbugs warnings:
https://builds.apache.org/job/PreCommit-HBASE-Build/6996//artifact/trunk/patchprocess/newPatchFindbugsWarningshbase-common.html
Findbugs warnings:
https://builds.apache.org/job/PreCommit-HBASE-Build/6996//artifact/trunk/patchprocess/newPatchFindbugsWarningshbase-server.html
Findbugs warnings:
https://builds.apache.org/job/PreCommit-HBASE-Build/6996//artifact/trunk/patchprocess/newPatchFindbugsWarningshbase-hadoop-compat.html
Console output:
https://builds.apache.org/job/PreCommit-HBASE-Build/6996//console
This message is automatically generated.
> Region could get lost during assignment
> ---
>
> Key: HBASE-9387
> URL: https://issues.apache.org/jira/browse/HBASE-9387
> Project: HBase
> Issue Type: Bug
> Components: Region Assignment
>Affects Versions: 0.95.2
>Reporter: Ted Yu
>Assignee: Ted Yu
>Priority: Critical
> Attachments: 9387-v1.txt, 9387-v3.txt, 9387-v4.2.txt, 9387-v4.3.txt,
> 9387-v4.4.txt, 9387-v4.txt, 9387-v5.txt, hbase-9387.patch,
> org.apache.hadoop.hbase.TestFullLogReconstruction-output.txt
>
>
> I observed test timeout running against hadoop 2.1.0 with distributed log
> replay turned on.
> Looks like region state for 1588230740 became inconsistent between master and
> the surviving region server:
> {code}
> 2013-08-29 22:15:34,180 INFO [AM.ZK.Worker-pool2-t4]
> master.RegionStates(299): Onlined 1588230740 on
> kiyo.gq1.ygridcore.net,57016,1377814510039
> ...
> 2013-08-29 22:15:34,587 DEBUG [Thread-221]
> client.HConnectionManager$HConnectionImplementation(1269): locateRegionInMeta
> parentTable=hbase:meta, metaLocation={region=hbase:meta,,1.1588230740,
> hostname=kiyo.gq1.ygridcore.net,57016,1377814510039, seqNum=0}, attempt=2 of
> 35 failed; retrying after sleep of 302 because:
> org.apache.hadoop.hbase.exceptions.RegionOpeningException: Region is being
> opened: 1588230740
> at
> org.apache.hadoop.hbase.regionserver.HRegionServer.getRegionByEncodedName(HRegionServer.java:2574)
> at
> org.apache.hadoop.hbase.regionserver.HRegionServer.getRegion(HRegionServer.java:3949)
> at
> org.apache.hadoop.hbase.regionserver.HRegionServer.get(HRegionServer.java:2733)
> at
> org.apache.hadoop.hbase.protobuf.generated.ClientProtos$ClientService$2.callBlockingMethod(ClientProtos.java:26965)
> at org.apache.hadoop.hbase.ipc.RpcServer.call(RpcServer.java:2063)
> at
> org.apache.hadoop.hbase.ipc.RpcServer$CallRunner.run(RpcServer.java:1800)
> at
> org.apache.ha
[jira] [Commented] (HBASE-9397) Snapshots with the same name are allowed to proceed concurrently
[
https://issues.apache.org/jira/browse/HBASE-9397?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13755187#comment-13755187
]
Hadoop QA commented on HBASE-9397:
--
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12600852/HBASE-9397-trunk.patch
against trunk revision .
{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 hadoop1.0{color}. The patch compiles against the hadoop
1.0 profile.
{color:green}+1 hadoop2.0{color}. The patch compiles against the hadoop
2.0 profile.
{color:green}+1 javadoc{color}. The javadoc tool did not generate any
warning messages.
{color:green}+1 javac{color}. The applied patch does not increase the
total number of javac compiler warnings.
{color:red}-1 findbugs{color}. The patch appears to introduce 1 new
Findbugs (version 1.3.9) 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/6995//testReport/
Findbugs warnings:
https://builds.apache.org/job/PreCommit-HBASE-Build/6995//artifact/trunk/patchprocess/newPatchFindbugsWarningshbase-prefix-tree.html
Findbugs warnings:
https://builds.apache.org/job/PreCommit-HBASE-Build/6995//artifact/trunk/patchprocess/newPatchFindbugsWarningshbase-client.html
Findbugs warnings:
https://builds.apache.org/job/PreCommit-HBASE-Build/6995//artifact/trunk/patchprocess/newPatchFindbugsWarningshbase-common.html
Findbugs warnings:
https://builds.apache.org/job/PreCommit-HBASE-Build/6995//artifact/trunk/patchprocess/newPatchFindbugsWarningshbase-protocol.html
Findbugs warnings:
https://builds.apache.org/job/PreCommit-HBASE-Build/6995//artifact/trunk/patchprocess/newPatchFindbugsWarningshbase-server.html
Findbugs warnings:
https://builds.apache.org/job/PreCommit-HBASE-Build/6995//artifact/trunk/patchprocess/newPatchFindbugsWarningshbase-hadoop1-compat.html
Findbugs warnings:
https://builds.apache.org/job/PreCommit-HBASE-Build/6995//artifact/trunk/patchprocess/newPatchFindbugsWarningshbase-examples.html
Findbugs warnings:
https://builds.apache.org/job/PreCommit-HBASE-Build/6995//artifact/trunk/patchprocess/newPatchFindbugsWarningshbase-hadoop-compat.html
Console output:
https://builds.apache.org/job/PreCommit-HBASE-Build/6995//console
This message is automatically generated.
> Snapshots with the same name are allowed to proceed concurrently
>
>
> Key: HBASE-9397
> URL: https://issues.apache.org/jira/browse/HBASE-9397
> Project: HBase
> Issue Type: Bug
> Components: snapshots
>Affects Versions: 0.95.2, 0.94.11
>Reporter: Jerry He
>Assignee: Jerry He
> Fix For: 0.94.12, 0.96.0
>
> Attachments: HBASE-9397-0.94.patch, HBASE-9397-trunk.patch
>
>
> Snapshots with the same name (but on different tables) are allowed to proceed
> concurrently.
> This seems to be loop hole created by allowing multiple snapshots (on
> different tables) to run concurrently.
> There are two checks in SnapshotManager, but fail to catch this particular
> case.
> In isSnapshotCompleted(), we only check the completed snapshot directory.
> In isTakingSnapshot(), we only check for the same table name.
> The end result is the concurrently running snapshots with the same name are
> overlapping and messing up each other. For example, cleaning up the other's
> snapshot working directory in .hbase-snapshot/.tmp/snapshot-name.
> {code}
> 2013-08-29 18:25:13,443 ERROR
> org.apache.hadoop.hbase.master.snapshot.TakeSnapshotHandler: Failed taking
> snapshot { ss=mysnapshot table=TestTable type=FLUSH } due to
> exception:Couldn't read snapshot info
> from:hdfs://hdtest009:9000/hbase/.hbase-snapshot/.tmp/mysnapshot/.snapshotinfo
> org.apache.hadoop.hbase.snapshot.CorruptedSnapshotException: Couldn't read
> snapshot info
> from:hdfs://hdtest009:9000/hbase/.hbase-snapshot/.tmp/mysnapshot/.snapshotinfo
> at
> org.apache.hadoop.hbase.snapshot.SnapshotDescriptionUtils.readSnapshotInfo(SnapshotDescriptionUtils.java:321)
> at
> org.apache.hadoop.hbase.master.snaps
[jira] [Updated] (HBASE-9387) Region could get lost during assignment
[
https://issues.apache.org/jira/browse/HBASE-9387?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ted Yu updated HBASE-9387:
--
Attachment: 9387-v4.4.txt
Patch v4.4 removes unnecessary change.
MockRegionServer#abort() calls stop() - HRegionServer#abort() does the same.
Added comment in TestOpenRegionHandler#testYankingRegionFromUnderIt()
explaining why region server abortion is expected.
> Region could get lost during assignment
> ---
>
> Key: HBASE-9387
> URL: https://issues.apache.org/jira/browse/HBASE-9387
> Project: HBase
> Issue Type: Bug
> Components: Region Assignment
>Affects Versions: 0.95.2
>Reporter: Ted Yu
>Assignee: Ted Yu
>Priority: Critical
> Attachments: 9387-v1.txt, 9387-v3.txt, 9387-v4.2.txt, 9387-v4.3.txt,
> 9387-v4.4.txt, 9387-v4.txt, 9387-v5.txt, hbase-9387.patch,
> org.apache.hadoop.hbase.TestFullLogReconstruction-output.txt
>
>
> I observed test timeout running against hadoop 2.1.0 with distributed log
> replay turned on.
> Looks like region state for 1588230740 became inconsistent between master and
> the surviving region server:
> {code}
> 2013-08-29 22:15:34,180 INFO [AM.ZK.Worker-pool2-t4]
> master.RegionStates(299): Onlined 1588230740 on
> kiyo.gq1.ygridcore.net,57016,1377814510039
> ...
> 2013-08-29 22:15:34,587 DEBUG [Thread-221]
> client.HConnectionManager$HConnectionImplementation(1269): locateRegionInMeta
> parentTable=hbase:meta, metaLocation={region=hbase:meta,,1.1588230740,
> hostname=kiyo.gq1.ygridcore.net,57016,1377814510039, seqNum=0}, attempt=2 of
> 35 failed; retrying after sleep of 302 because:
> org.apache.hadoop.hbase.exceptions.RegionOpeningException: Region is being
> opened: 1588230740
> at
> org.apache.hadoop.hbase.regionserver.HRegionServer.getRegionByEncodedName(HRegionServer.java:2574)
> at
> org.apache.hadoop.hbase.regionserver.HRegionServer.getRegion(HRegionServer.java:3949)
> at
> org.apache.hadoop.hbase.regionserver.HRegionServer.get(HRegionServer.java:2733)
> at
> org.apache.hadoop.hbase.protobuf.generated.ClientProtos$ClientService$2.callBlockingMethod(ClientProtos.java:26965)
> at org.apache.hadoop.hbase.ipc.RpcServer.call(RpcServer.java:2063)
> at
> org.apache.hadoop.hbase.ipc.RpcServer$CallRunner.run(RpcServer.java:1800)
> at
> org.apache.hadoop.hbase.ipc.SimpleRpcScheduler.consumerLoop(SimpleRpcScheduler.java:165)
> at
> org.apache.hadoop.hbase.ipc.SimpleRpcScheduler.access$000(SimpleRpcScheduler.java:41)
> {code}
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (HBASE-9399) Up the memstore flush size
[ https://issues.apache.org/jira/browse/HBASE-9399?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Elliott Clark updated HBASE-9399: - Description: As heap sizes get bigger we are still recommending that users keep their number of regions to a minimum. This leads to lots of un-used memstore memory. For example I have a region server with 48 gigs of ram. 30 gigs are there for the region server. This with current defaults the global memstore size reserved is 8 gigs. The per region memstore size is 128mb right now. That means that I need 80 regions actively taking writes to reach the global memstore size. That number is way out of line with what our split policies currently give users. They are given much fewer regions by default. We should up the hbase.hregion.memstore.flush.size size. Ideally we should auto tune everything. But until then I think something like 512mb would help a lot with our write throughput on clusters that don't have several hundred regions per RS. was: As heap sizes get bigger we are still recommending that users keep their number of regions to a minimum. This leads to lots of un-used memstore memory. For example I have a region server with 32+ gigs of ram. 30 gigs are there for the region server. This with current defaults the global memstore size reserved is 8 gigs. The per region memstore size is 128mb right now. That means that I need 80 regions actively taking writes to reach the global memstore size. That number is way out of line with what our split policies currently give users. They are given much fewer regions by default. We should up the hbase.hregion.memstore.flush.size size. Ideally we should auto tune everything. But until then I think something like 512mb would help a lot with our write throughput on clusters that don't have several hundred regions per RS. > Up the memstore flush size > -- > > Key: HBASE-9399 > URL: https://issues.apache.org/jira/browse/HBASE-9399 > Project: HBase > Issue Type: Task > Components: regionserver >Affects Versions: 0.98.0, 0.96.0 >Reporter: Elliott Clark >Assignee: Elliott Clark > > As heap sizes get bigger we are still recommending that users keep their > number of regions to a minimum. This leads to lots of un-used memstore > memory. > For example I have a region server with 48 gigs of ram. 30 gigs are there > for the region server. This with current defaults the global memstore size > reserved is 8 gigs. > The per region memstore size is 128mb right now. That means that I need 80 > regions actively taking writes to reach the global memstore size. That > number is way out of line with what our split policies currently give users. > They are given much fewer regions by default. > We should up the hbase.hregion.memstore.flush.size size. Ideally we should > auto tune everything. But until then I think something like 512mb would help > a lot with our write throughput on clusters that don't have several hundred > regions per RS. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (HBASE-9398) Get HBASE-9190 to branck 0.95
[ https://issues.apache.org/jira/browse/HBASE-9398?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jimmy Xiang updated HBASE-9398: --- Assignee: (was: Jimmy Xiang) > Get HBASE-9190 to branck 0.95 > - > > Key: HBASE-9398 > URL: https://issues.apache.org/jira/browse/HBASE-9398 > Project: HBase > Issue Type: Bug >Reporter: Jimmy Xiang >Priority: Minor > Fix For: 0.96.0 > > > On HBASE-9190, it says it is fixed in 0.95.2. However, the issue is still > there. Found out it is not checked into 0.95 branch. Let me check it into > 0.95. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Resolved] (HBASE-9398) Get HBASE-9190 to branck 0.95
[ https://issues.apache.org/jira/browse/HBASE-9398?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] stack resolved HBASE-9398. -- Resolution: Fixed Fix Version/s: 0.96.0 Hadoop Flags: Reviewed Committed patch from HBASE-9190 on 0.96 branch. Thanks Jimmy. > Get HBASE-9190 to branck 0.95 > - > > Key: HBASE-9398 > URL: https://issues.apache.org/jira/browse/HBASE-9398 > Project: HBase > Issue Type: Bug >Reporter: Jimmy Xiang >Assignee: Jimmy Xiang >Priority: Minor > Fix For: 0.96.0 > > > On HBASE-9190, it says it is fixed in 0.95.2. However, the issue is still > there. Found out it is not checked into 0.95 branch. Let me check it into > 0.95. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (HBASE-9397) Snapshots with the same name are allowed to proceed concurrently
[
https://issues.apache.org/jira/browse/HBASE-9397?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13755113#comment-13755113
]
Jerry He commented on HBASE-9397:
-
Attached a straight fix. Any comment and other suggestion are welcome.
> Snapshots with the same name are allowed to proceed concurrently
>
>
> Key: HBASE-9397
> URL: https://issues.apache.org/jira/browse/HBASE-9397
> Project: HBase
> Issue Type: Bug
> Components: snapshots
>Affects Versions: 0.95.2, 0.94.11
>Reporter: Jerry He
>Assignee: Jerry He
> Fix For: 0.94.12, 0.96.0
>
> Attachments: HBASE-9397-0.94.patch, HBASE-9397-trunk.patch
>
>
> Snapshots with the same name (but on different tables) are allowed to proceed
> concurrently.
> This seems to be loop hole created by allowing multiple snapshots (on
> different tables) to run concurrently.
> There are two checks in SnapshotManager, but fail to catch this particular
> case.
> In isSnapshotCompleted(), we only check the completed snapshot directory.
> In isTakingSnapshot(), we only check for the same table name.
> The end result is the concurrently running snapshots with the same name are
> overlapping and messing up each other. For example, cleaning up the other's
> snapshot working directory in .hbase-snapshot/.tmp/snapshot-name.
> {code}
> 2013-08-29 18:25:13,443 ERROR
> org.apache.hadoop.hbase.master.snapshot.TakeSnapshotHandler: Failed taking
> snapshot { ss=mysnapshot table=TestTable type=FLUSH } due to
> exception:Couldn't read snapshot info
> from:hdfs://hdtest009:9000/hbase/.hbase-snapshot/.tmp/mysnapshot/.snapshotinfo
> org.apache.hadoop.hbase.snapshot.CorruptedSnapshotException: Couldn't read
> snapshot info
> from:hdfs://hdtest009:9000/hbase/.hbase-snapshot/.tmp/mysnapshot/.snapshotinfo
> at
> org.apache.hadoop.hbase.snapshot.SnapshotDescriptionUtils.readSnapshotInfo(SnapshotDescriptionUtils.java:321)
> at
> org.apache.hadoop.hbase.master.snapshot.MasterSnapshotVerifier.verifySnapshotDescription(MasterSnapshotVerifier.java:123)
> {code}
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (HBASE-9397) Snapshots with the same name are allowed to proceed concurrently
[
https://issues.apache.org/jira/browse/HBASE-9397?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jerry He updated HBASE-9397:
Attachment: HBASE-9397-trunk.patch
HBASE-9397-0.94.patch
> Snapshots with the same name are allowed to proceed concurrently
>
>
> Key: HBASE-9397
> URL: https://issues.apache.org/jira/browse/HBASE-9397
> Project: HBase
> Issue Type: Bug
> Components: snapshots
>Affects Versions: 0.95.2, 0.94.11
>Reporter: Jerry He
>Assignee: Jerry He
> Fix For: 0.94.12, 0.96.0
>
> Attachments: HBASE-9397-0.94.patch, HBASE-9397-trunk.patch
>
>
> Snapshots with the same name (but on different tables) are allowed to proceed
> concurrently.
> This seems to be loop hole created by allowing multiple snapshots (on
> different tables) to run concurrently.
> There are two checks in SnapshotManager, but fail to catch this particular
> case.
> In isSnapshotCompleted(), we only check the completed snapshot directory.
> In isTakingSnapshot(), we only check for the same table name.
> The end result is the concurrently running snapshots with the same name are
> overlapping and messing up each other. For example, cleaning up the other's
> snapshot working directory in .hbase-snapshot/.tmp/snapshot-name.
> {code}
> 2013-08-29 18:25:13,443 ERROR
> org.apache.hadoop.hbase.master.snapshot.TakeSnapshotHandler: Failed taking
> snapshot { ss=mysnapshot table=TestTable type=FLUSH } due to
> exception:Couldn't read snapshot info
> from:hdfs://hdtest009:9000/hbase/.hbase-snapshot/.tmp/mysnapshot/.snapshotinfo
> org.apache.hadoop.hbase.snapshot.CorruptedSnapshotException: Couldn't read
> snapshot info
> from:hdfs://hdtest009:9000/hbase/.hbase-snapshot/.tmp/mysnapshot/.snapshotinfo
> at
> org.apache.hadoop.hbase.snapshot.SnapshotDescriptionUtils.readSnapshotInfo(SnapshotDescriptionUtils.java:321)
> at
> org.apache.hadoop.hbase.master.snapshot.MasterSnapshotVerifier.verifySnapshotDescription(MasterSnapshotVerifier.java:123)
> {code}
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (HBASE-9397) Snapshots with the same name are allowed to proceed concurrently
[
https://issues.apache.org/jira/browse/HBASE-9397?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jerry He updated HBASE-9397:
Status: Patch Available (was: Open)
> Snapshots with the same name are allowed to proceed concurrently
>
>
> Key: HBASE-9397
> URL: https://issues.apache.org/jira/browse/HBASE-9397
> Project: HBase
> Issue Type: Bug
> Components: snapshots
>Affects Versions: 0.94.11, 0.95.2
>Reporter: Jerry He
>Assignee: Jerry He
> Fix For: 0.94.12, 0.96.0
>
> Attachments: HBASE-9397-0.94.patch, HBASE-9397-trunk.patch
>
>
> Snapshots with the same name (but on different tables) are allowed to proceed
> concurrently.
> This seems to be loop hole created by allowing multiple snapshots (on
> different tables) to run concurrently.
> There are two checks in SnapshotManager, but fail to catch this particular
> case.
> In isSnapshotCompleted(), we only check the completed snapshot directory.
> In isTakingSnapshot(), we only check for the same table name.
> The end result is the concurrently running snapshots with the same name are
> overlapping and messing up each other. For example, cleaning up the other's
> snapshot working directory in .hbase-snapshot/.tmp/snapshot-name.
> {code}
> 2013-08-29 18:25:13,443 ERROR
> org.apache.hadoop.hbase.master.snapshot.TakeSnapshotHandler: Failed taking
> snapshot { ss=mysnapshot table=TestTable type=FLUSH } due to
> exception:Couldn't read snapshot info
> from:hdfs://hdtest009:9000/hbase/.hbase-snapshot/.tmp/mysnapshot/.snapshotinfo
> org.apache.hadoop.hbase.snapshot.CorruptedSnapshotException: Couldn't read
> snapshot info
> from:hdfs://hdtest009:9000/hbase/.hbase-snapshot/.tmp/mysnapshot/.snapshotinfo
> at
> org.apache.hadoop.hbase.snapshot.SnapshotDescriptionUtils.readSnapshotInfo(SnapshotDescriptionUtils.java:321)
> at
> org.apache.hadoop.hbase.master.snapshot.MasterSnapshotVerifier.verifySnapshotDescription(MasterSnapshotVerifier.java:123)
> {code}
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (HBASE-9388) [replication] ZK Dump prints the raw PBUF for the HLog positions
[ https://issues.apache.org/jira/browse/HBASE-9388?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13755111#comment-13755111 ] Jean-Daniel Cryans commented on HBASE-9388: --- bq. We have to have different deserialization per znode? Basically if it's a leaf under replication/rs/, we print a long. If it's a leaf under replication/peers, we print if it's enabled or disabled. > [replication] ZK Dump prints the raw PBUF for the HLog positions > > > Key: HBASE-9388 > URL: https://issues.apache.org/jira/browse/HBASE-9388 > Project: HBase > Issue Type: Bug >Affects Versions: 0.95.2 >Reporter: Jean-Daniel Cryans >Assignee: Jean-Daniel Cryans > Fix For: 0.98.0, 0.96.0 > > Attachments: HBASE-9388.patch > > > Looking at the ZK dump in the master's web ui, I can see that we're not > trying to parse the positions for the HLogs so it looks like "PBU���" -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Created] (HBASE-9397) Snapshots with the same name are allowed to proceed concurrently
Jerry He created HBASE-9397:
---
Summary: Snapshots with the same name are allowed to proceed
concurrently
Key: HBASE-9397
URL: https://issues.apache.org/jira/browse/HBASE-9397
Project: HBase
Issue Type: Bug
Components: snapshots
Affects Versions: 0.94.11, 0.95.2
Reporter: Jerry He
Assignee: Jerry He
Fix For: 0.94.12, 0.96.0
Snapshots with the same name (but on different tables) are allowed to proceed
concurrently.
This seems to be loop hole created by allowing multiple snapshots (on different
tables) to run concurrently.
There are two checks in SnapshotManager, but fail to catch this particular case.
In isSnapshotCompleted(), we only check the completed snapshot directory.
In isTakingSnapshot(), we only check for the same table name.
The end result is the concurrently running snapshots with the same name are
overlapping and messing up each other. For example, cleaning up the other's
snapshot working directory in .hbase-snapshot/.tmp/snapshot-name.
{code}
2013-08-29 18:25:13,443 ERROR
org.apache.hadoop.hbase.master.snapshot.TakeSnapshotHandler: Failed taking
snapshot { ss=mysnapshot table=TestTable type=FLUSH } due to exception:Couldn't
read snapshot info
from:hdfs://hdtest009:9000/hbase/.hbase-snapshot/.tmp/mysnapshot/.snapshotinfo
org.apache.hadoop.hbase.snapshot.CorruptedSnapshotException: Couldn't read
snapshot info
from:hdfs://hdtest009:9000/hbase/.hbase-snapshot/.tmp/mysnapshot/.snapshotinfo
at
org.apache.hadoop.hbase.snapshot.SnapshotDescriptionUtils.readSnapshotInfo(SnapshotDescriptionUtils.java:321)
at
org.apache.hadoop.hbase.master.snapshot.MasterSnapshotVerifier.verifySnapshotDescription(MasterSnapshotVerifier.java:123)
{code}
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (HBASE-8930) Filter evaluates KVs outside requested columns
[
https://issues.apache.org/jira/browse/HBASE-8930?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13755170#comment-13755170
]
Lars Hofhansl commented on HBASE-8930:
--
After checking back. This *is* just a bug fix after all.
This happens only to columns just after those that the scan actually selects.
+1 on committing, including 0.94.
> Filter evaluates KVs outside requested columns
> --
>
> Key: HBASE-8930
> URL: https://issues.apache.org/jira/browse/HBASE-8930
> Project: HBase
> Issue Type: Bug
> Components: Filters
>Affects Versions: 0.94.7
>Reporter: Federico Gaule
>Assignee: Vasu Mariyala
>Priority: Critical
> Labels: filters, hbase, keyvalue
> Attachments: HBASE-8930.patch, HBASE-8930-rev1.patch,
> HBASE-8930-rev2.patch
>
>
> 1- Fill row with some columns
> 2- Get row with some columns less than universe - Use filter to print kvs
> 3- Filter prints not requested columns
> Filter (AllwaysNextColFilter) always return ReturnCode.INCLUDE_AND_NEXT_COL
> and prints KV's qualifier
> SUFFIX_0 = 0
> SUFFIX_1 = 1
> SUFFIX_4 = 4
> SUFFIX_6 = 6
> P= Persisted
> R= Requested
> E= Evaluated
> X= Returned
> | 5580 | 5581 | 5584 | 5586 | 5590 | 5591 | 5594 | 5596 | 5600 | 5601 | 5604
> | 5606 |...
> | | P | P | | | P | P | | | P | P
> | |...
> | | R | R | R | | R | R | R | | |
> | |...
> | | E | E | | | E | E | | |
> {color:red}E{color} | | |...
> | | X | X | | | X | X | | | |
> | |
> {code:title=ExtraColumnTest.java|borderStyle=solid}
> @Test
> public void testFilter() throws Exception {
> Configuration config = HBaseConfiguration.create();
> config.set("hbase.zookeeper.quorum", "myZK");
> HTable hTable = new HTable(config, "testTable");
> byte[] cf = Bytes.toBytes("cf");
> byte[] row = Bytes.toBytes("row");
> byte[] col1 = new QualifierConverter().objectToByteArray(new
> Qualifier((short) 558, (byte) SUFFIX_1));
> byte[] col2 = new QualifierConverter().objectToByteArray(new
> Qualifier((short) 559, (byte) SUFFIX_1));
> byte[] col3 = new QualifierConverter().objectToByteArray(new
> Qualifier((short) 560, (byte) SUFFIX_1));
> byte[] col4 = new QualifierConverter().objectToByteArray(new
> Qualifier((short) 561, (byte) SUFFIX_1));
> byte[] col5 = new QualifierConverter().objectToByteArray(new
> Qualifier((short) 562, (byte) SUFFIX_1));
> byte[] col6 = new QualifierConverter().objectToByteArray(new
> Qualifier((short) 563, (byte) SUFFIX_1));
> byte[] col1g = new QualifierConverter().objectToByteArray(new
> Qualifier((short) 558, (byte) SUFFIX_6));
> byte[] col2g = new QualifierConverter().objectToByteArray(new
> Qualifier((short) 559, (byte) SUFFIX_6));
> byte[] col1v = new QualifierConverter().objectToByteArray(new
> Qualifier((short) 558, (byte) SUFFIX_4));
> byte[] col2v = new QualifierConverter().objectToByteArray(new
> Qualifier((short) 559, (byte) SUFFIX_4));
> byte[] col3v = new QualifierConverter().objectToByteArray(new
> Qualifier((short) 560, (byte) SUFFIX_4));
> byte[] col4v = new QualifierConverter().objectToByteArray(new
> Qualifier((short) 561, (byte) SUFFIX_4));
> byte[] col5v = new QualifierConverter().objectToByteArray(new
> Qualifier((short) 562, (byte) SUFFIX_4));
> byte[] col6v = new QualifierConverter().objectToByteArray(new
> Qualifier((short) 563, (byte) SUFFIX_4));
> // === INSERTION =//
> Put put = new Put(row);
> put.add(cf, col1, Bytes.toBytes((short) 1));
> put.add(cf, col2, Bytes.toBytes((short) 1));
> put.add(cf, col3, Bytes.toBytes((short) 3));
> put.add(cf, col4, Bytes.toBytes((short) 3));
> put.add(cf, col5, Bytes.toBytes((short) 3));
> put.add(cf, col6, Bytes.toBytes((short) 3));
> hTable.put(put);
> put = new Put(row);
> put.add(cf, col1v, Bytes.toBytes((short) 10));
> put.add(cf, col2v, Bytes.toBytes((short) 10));
> put.add(cf, col3v, Bytes.toBytes((short) 10));
> put.add(cf, col4v, Bytes.toBytes((short) 10));
> put.add(cf, col5v, Bytes.toBytes((short) 10));
> put.add(cf, col6v, Bytes.toBytes((short) 10));
> hTable.put(put);
> hTable.flushCommits();
> //==READING=//
> Filter allwaysNextColFilter = new AllwaysNextColFilter();
> Get get = new Get(row);
> get.addColumn(cf, col1); //5581
> get.addColumn(cf, col1v); //5584
[jira] [Updated] (HBASE-9387) Region could get lost during assignment
[
https://issues.apache.org/jira/browse/HBASE-9387?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ted Yu updated HBASE-9387:
--
Attachment: 9387-v4.3.txt
Reused TestOpenRegionHandler#testYankingRegionFromUnderIt() for verification of
region server abortion.
> Region could get lost during assignment
> ---
>
> Key: HBASE-9387
> URL: https://issues.apache.org/jira/browse/HBASE-9387
> Project: HBase
> Issue Type: Bug
> Components: Region Assignment
>Affects Versions: 0.95.2
>Reporter: Ted Yu
>Assignee: Ted Yu
>Priority: Critical
> Attachments: 9387-v1.txt, 9387-v3.txt, 9387-v4.2.txt, 9387-v4.3.txt,
> 9387-v4.txt, 9387-v5.txt, hbase-9387.patch,
> org.apache.hadoop.hbase.TestFullLogReconstruction-output.txt
>
>
> I observed test timeout running against hadoop 2.1.0 with distributed log
> replay turned on.
> Looks like region state for 1588230740 became inconsistent between master and
> the surviving region server:
> {code}
> 2013-08-29 22:15:34,180 INFO [AM.ZK.Worker-pool2-t4]
> master.RegionStates(299): Onlined 1588230740 on
> kiyo.gq1.ygridcore.net,57016,1377814510039
> ...
> 2013-08-29 22:15:34,587 DEBUG [Thread-221]
> client.HConnectionManager$HConnectionImplementation(1269): locateRegionInMeta
> parentTable=hbase:meta, metaLocation={region=hbase:meta,,1.1588230740,
> hostname=kiyo.gq1.ygridcore.net,57016,1377814510039, seqNum=0}, attempt=2 of
> 35 failed; retrying after sleep of 302 because:
> org.apache.hadoop.hbase.exceptions.RegionOpeningException: Region is being
> opened: 1588230740
> at
> org.apache.hadoop.hbase.regionserver.HRegionServer.getRegionByEncodedName(HRegionServer.java:2574)
> at
> org.apache.hadoop.hbase.regionserver.HRegionServer.getRegion(HRegionServer.java:3949)
> at
> org.apache.hadoop.hbase.regionserver.HRegionServer.get(HRegionServer.java:2733)
> at
> org.apache.hadoop.hbase.protobuf.generated.ClientProtos$ClientService$2.callBlockingMethod(ClientProtos.java:26965)
> at org.apache.hadoop.hbase.ipc.RpcServer.call(RpcServer.java:2063)
> at
> org.apache.hadoop.hbase.ipc.RpcServer$CallRunner.run(RpcServer.java:1800)
> at
> org.apache.hadoop.hbase.ipc.SimpleRpcScheduler.consumerLoop(SimpleRpcScheduler.java:165)
> at
> org.apache.hadoop.hbase.ipc.SimpleRpcScheduler.access$000(SimpleRpcScheduler.java:41)
> {code}
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (HBASE-9387) Region could get lost during assignment
[
https://issues.apache.org/jira/browse/HBASE-9387?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13755153#comment-13755153
]
stack commented on HBASE-9387:
--
You should probably set stopped state too if you call abort in your
MockRegionServer since abort always calls stop.
This change is now gratuitous, right?
@@ -438,9 +439,10 @@
EventType.M_ZK_REGION_OFFLINE,
EventType.RS_ZK_REGION_FAILED_OPEN,
versionOfOfflineNode) == -1) {
-LOG.warn("Unable to mark region " + hri + " as FAILED_OPEN. " +
+String warnMsg = "Unable to mark region " + hri + " as FAILED_OPEN. " +
"It's likely that the master already timed out this open " +
-"attempt, and thus another RS already has the region.");
+"attempt, and thus another RS already has the region.";
+LOG.warn(warnMsg);
} else {
result = true;
}
On the test change, how I know it replicates what we saw here? I started to
dig but it was taking too long. Would expect comment to explain why we expect
RS to abort. Would expect to see explain why the yanking of znode is not same
as master removing it on successful open.
> Region could get lost during assignment
> ---
>
> Key: HBASE-9387
> URL: https://issues.apache.org/jira/browse/HBASE-9387
> Project: HBase
> Issue Type: Bug
> Components: Region Assignment
>Affects Versions: 0.95.2
>Reporter: Ted Yu
>Assignee: Ted Yu
>Priority: Critical
> Attachments: 9387-v1.txt, 9387-v3.txt, 9387-v4.2.txt, 9387-v4.3.txt,
> 9387-v4.txt, 9387-v5.txt, hbase-9387.patch,
> org.apache.hadoop.hbase.TestFullLogReconstruction-output.txt
>
>
> I observed test timeout running against hadoop 2.1.0 with distributed log
> replay turned on.
> Looks like region state for 1588230740 became inconsistent between master and
> the surviving region server:
> {code}
> 2013-08-29 22:15:34,180 INFO [AM.ZK.Worker-pool2-t4]
> master.RegionStates(299): Onlined 1588230740 on
> kiyo.gq1.ygridcore.net,57016,1377814510039
> ...
> 2013-08-29 22:15:34,587 DEBUG [Thread-221]
> client.HConnectionManager$HConnectionImplementation(1269): locateRegionInMeta
> parentTable=hbase:meta, metaLocation={region=hbase:meta,,1.1588230740,
> hostname=kiyo.gq1.ygridcore.net,57016,1377814510039, seqNum=0}, attempt=2 of
> 35 failed; retrying after sleep of 302 because:
> org.apache.hadoop.hbase.exceptions.RegionOpeningException: Region is being
> opened: 1588230740
> at
> org.apache.hadoop.hbase.regionserver.HRegionServer.getRegionByEncodedName(HRegionServer.java:2574)
> at
> org.apache.hadoop.hbase.regionserver.HRegionServer.getRegion(HRegionServer.java:3949)
> at
> org.apache.hadoop.hbase.regionserver.HRegionServer.get(HRegionServer.java:2733)
> at
> org.apache.hadoop.hbase.protobuf.generated.ClientProtos$ClientService$2.callBlockingMethod(ClientProtos.java:26965)
> at org.apache.hadoop.hbase.ipc.RpcServer.call(RpcServer.java:2063)
> at
> org.apache.hadoop.hbase.ipc.RpcServer$CallRunner.run(RpcServer.java:1800)
> at
> org.apache.hadoop.hbase.ipc.SimpleRpcScheduler.consumerLoop(SimpleRpcScheduler.java:165)
> at
> org.apache.hadoop.hbase.ipc.SimpleRpcScheduler.access$000(SimpleRpcScheduler.java:41)
> {code}
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Created] (HBASE-9399) Up the memstore flush size
Elliott Clark created HBASE-9399: Summary: Up the memstore flush size Key: HBASE-9399 URL: https://issues.apache.org/jira/browse/HBASE-9399 Project: HBase Issue Type: Task Components: regionserver Affects Versions: 0.98.0, 0.96.0 Reporter: Elliott Clark Assignee: Elliott Clark As heap sizes get bigger we are still recommending that users keep their number of regions to a minimum. This leads to lots of un-used memstore memory. For example I have a region server with 32+ gigs of ram. 30 gigs are there for the region server. This with current defaults the global memstore size reserved is 8 gigs. The per region memstore size is 128mb right now. That means that I need 80 regions actively taking writes to reach the global memstore size. That number is way out of line with what our split policies currently give users. They are given much fewer regions by default. We should up the hbase.hregion.memstore.flush.size size. Ideally we should auto tune everything. But until then I think something like 512mb would help a lot with our write throughput on clusters that don't have several hundred regions per RS. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (HBASE-9190) Update scan.rb description to match the naming convention of META after namespace change
[
https://issues.apache.org/jira/browse/HBASE-9190?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13755164#comment-13755164
]
Jimmy Xiang commented on HBASE-9190:
Found it is not checked into 0.95, so filed HBASE-9398.
> Update scan.rb description to match the naming convention of META after
> namespace change
>
>
> Key: HBASE-9190
> URL: https://issues.apache.org/jira/browse/HBASE-9190
> Project: HBase
> Issue Type: Bug
>Affects Versions: 0.95.1
>Reporter: ramkrishna.s.vasudevan
>Assignee: ramkrishna.s.vasudevan
>Priority: Minor
> Fix For: 0.98.0
>
> Attachments: HBASE-9190_1.patch, HBASE-9190.patch
>
>
> The example description shows
> hbase> scan '.META.'
> hbase> scan '.META.', {COLUMNS => 'info:regioninfo'}
> But now meta is hbase:meta. The same can be updated in the description for
> easy reference.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Work started] (HBASE-9395) Disable Schema Change on 0.96
[ https://issues.apache.org/jira/browse/HBASE-9395?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Work on HBASE-9395 started by Elliott Clark. > Disable Schema Change on 0.96 > - > > Key: HBASE-9395 > URL: https://issues.apache.org/jira/browse/HBASE-9395 > Project: HBase > Issue Type: Bug > Components: master >Affects Versions: 0.98.0 >Reporter: Elliott Clark >Assignee: Elliott Clark >Priority: Blocker > Fix For: 0.96.0 > > Attachments: HBASE-9395-95-0.patch > > > Running LoadTestAndVerify fails when the chaos monkey is slowDeterministic. > When commenting out all of the schema change actions everything passes. We > should disable the schema change until we can be 100% sure of data integrity. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Created] (HBASE-9398) Get HBASE-9190 to branck 0.95
Jimmy Xiang created HBASE-9398: -- Summary: Get HBASE-9190 to branck 0.95 Key: HBASE-9398 URL: https://issues.apache.org/jira/browse/HBASE-9398 Project: HBase Issue Type: Bug Reporter: Jimmy Xiang Assignee: Jimmy Xiang Priority: Minor On HBASE-9190, it says it is fixed in 0.95.2. However, the issue is still there. Found out it is not checked into 0.95 branch. Let me check it into 0.95. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Resolved] (HBASE-9395) Disable Schema Change on 0.96
[ https://issues.apache.org/jira/browse/HBASE-9395?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Elliott Clark resolved HBASE-9395. -- Resolution: Fixed Release Note: Online Schema Change has been disabled. It's a feature that is not stable on unstable clusters. Committed to 0.95 branch > Disable Schema Change on 0.96 > - > > Key: HBASE-9395 > URL: https://issues.apache.org/jira/browse/HBASE-9395 > Project: HBase > Issue Type: Bug > Components: master >Affects Versions: 0.98.0 >Reporter: Elliott Clark >Assignee: Elliott Clark >Priority: Blocker > Fix For: 0.96.0 > > Attachments: HBASE-9395-95-0.patch > > > Running LoadTestAndVerify fails when the chaos monkey is slowDeterministic. > When commenting out all of the schema change actions everything passes. We > should disable the schema change until we can be 100% sure of data integrity. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (HBASE-9382) replicateWALEntry doesn't use the replication handlers
[ https://issues.apache.org/jira/browse/HBASE-9382?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13754824#comment-13754824 ] Jean-Daniel Cryans commented on HBASE-9382: --- I'll test this one out this morning. > replicateWALEntry doesn't use the replication handlers > -- > > Key: HBASE-9382 > URL: https://issues.apache.org/jira/browse/HBASE-9382 > Project: HBase > Issue Type: Bug >Affects Versions: 0.95.2 >Reporter: Jean-Daniel Cryans >Assignee: stack > Fix For: 0.98.0, 0.96.0 > > Attachments: 9382.trunk.txt, 9382.txt > > > By default we assign 3 handlers for replication, but as far as I can tell the > replication traffic uses the normal handlers in 0.96 -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (HBASE-9190) Update scan.rb description to match the naming convention of META after namespace change
[
https://issues.apache.org/jira/browse/HBASE-9190?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jimmy Xiang updated HBASE-9190:
---
Fix Version/s: (was: 0.95.2)
> Update scan.rb description to match the naming convention of META after
> namespace change
>
>
> Key: HBASE-9190
> URL: https://issues.apache.org/jira/browse/HBASE-9190
> Project: HBase
> Issue Type: Bug
>Affects Versions: 0.95.1
>Reporter: ramkrishna.s.vasudevan
>Assignee: ramkrishna.s.vasudevan
>Priority: Minor
> Fix For: 0.98.0
>
> Attachments: HBASE-9190_1.patch, HBASE-9190.patch
>
>
> The example description shows
> hbase> scan '.META.'
> hbase> scan '.META.', {COLUMNS => 'info:regioninfo'}
> But now meta is hbase:meta. The same can be updated in the description for
> easy reference.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (HBASE-9165) Improvements to addDependencyJars
[
https://issues.apache.org/jira/browse/HBASE-9165?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13755134#comment-13755134
]
Daniel Dai commented on HBASE-9165:
---
+1. Pig need this feature to ship HBase dependent jars correctly. Currently Pig
user have to register HBase dependent jars (such as protobuf.jar) to use
HBaseStorage.
> Improvements to addDependencyJars
> -
>
> Key: HBASE-9165
> URL: https://issues.apache.org/jira/browse/HBASE-9165
> Project: HBase
> Issue Type: Sub-task
> Components: mapreduce
>Affects Versions: 0.95.2
>Reporter: Nick Dimiduk
>Assignee: Nick Dimiduk
> Attachments:
> 0001-HBASE-9165-mapreduce-Modularize-building-dependency-.patch
>
>
> The way we support adding HBase dependencies to a MapReduce job in
> {{TableMapReduceUtils#addDependencyJars(job)}} is a bit monolithic. Advanced
> users need a way to add HBase and its dependencies to their job without us
> snooping around for ouput formats and the like (see PIG-3285). We can also
> benefit from a little more code reuse between our {{mapred}} and
> {{mapreduce}} namespaces.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (HBASE-9373) [replication] data loss because replication doesn't expect partial reads
[
https://issues.apache.org/jira/browse/HBASE-9373?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13755118#comment-13755118
]
Hudson commented on HBASE-9373:
---
SUCCESS: Integrated in HBase-TRUNK #4451 (See
[https://builds.apache.org/job/HBase-TRUNK/4451/])
HBASE-9373 [replication] data loss because replication doesn't expect partial
reads (jdcryans: rev 1519037)
*
/hbase/trunk/hbase-server/src/main/java/org/apache/hadoop/hbase/regionserver/wal/ProtobufLogReader.java
> [replication] data loss because replication doesn't expect partial reads
>
>
> Key: HBASE-9373
> URL: https://issues.apache.org/jira/browse/HBASE-9373
> Project: HBase
> Issue Type: Improvement
>Affects Versions: 0.95.2
>Reporter: Jean-Daniel Cryans
>Assignee: Jean-Daniel Cryans
>Priority: Blocker
> Fix For: 0.98.0, 0.96.0
>
> Attachments: 9373.txt, 9373-v2.txt, 9373-v3.txt, 9373-v4.patch
>
>
> When I see this in the logs it often means we got a partial read and then we
> have the wrong offset when reading the rest of the file
> {noformat}
> 2013-08-28 23:16:07,182 ERROR
> [ReplicationExecutor-0.replicationSource,1-jdec2hbase0403-5,60020,1377730319617]
> org.apache.hadoop.hbase.regionserver.wal.ProtobufLogReader: Invalid PB while
> reading WAL, probably an unexpected EOF, ignoring
> com.google.protobuf.InvalidProtocolBufferException: Protocol message tag had
> invalid wire type.
> at
> com.google.protobuf.InvalidProtocolBufferException.invalidWireType(InvalidProtocolBufferException.java:99)
> at
> com.google.protobuf.UnknownFieldSet$Builder.mergeFieldFrom(UnknownFieldSet.java:498)
> at
> com.google.protobuf.GeneratedMessage.parseUnknownField(GeneratedMessage.java:193)
> at
> org.apache.hadoop.hbase.protobuf.generated.WALProtos$WALKey.(WALProtos.java:686)
> at
> org.apache.hadoop.hbase.protobuf.generated.WALProtos$WALKey.(WALProtos.java:644)
> at
> org.apache.hadoop.hbase.protobuf.generated.WALProtos$WALKey$1.parsePartialFrom(WALProtos.java:771)
> at
> org.apache.hadoop.hbase.protobuf.generated.WALProtos$WALKey$1.parsePartialFrom(WALProtos.java:766)
> at
> org.apache.hadoop.hbase.protobuf.generated.WALProtos$WALKey$Builder.mergeFrom(WALProtos.java:1444)
> at
> org.apache.hadoop.hbase.protobuf.generated.WALProtos$WALKey$Builder.mergeFrom(WALProtos.java:1218)
> at
> com.google.protobuf.AbstractMessageLite$Builder.mergeFrom(AbstractMessageLite.java:220)
> at
> com.google.protobuf.AbstractMessage$Builder.mergeFrom(AbstractMessage.java:912)
> at
> com.google.protobuf.AbstractMessage$Builder.mergeFrom(AbstractMessage.java:267)
> at
> com.google.protobuf.AbstractMessageLite$Builder.mergeDelimitedFrom(AbstractMessageLite.java:290)
> at
> com.google.protobuf.AbstractMessage$Builder.mergeDelimitedFrom(AbstractMessage.java:926)
> at
> com.google.protobuf.AbstractMessageLite$Builder.mergeDelimitedFrom(AbstractMessageLite.java:296)
> at
> com.google.protobuf.AbstractMessage$Builder.mergeDelimitedFrom(AbstractMessage.java:918)
> at
> org.apache.hadoop.hbase.regionserver.wal.ProtobufLogReader.readNext(ProtobufLogReader.java:197)
> at
> org.apache.hadoop.hbase.regionserver.wal.ReaderBase.next(ReaderBase.java:98)
> at
> org.apache.hadoop.hbase.replication.regionserver.ReplicationHLogReaderManager.readNextAndSetPosition(ReplicationHLogReaderManager.java:89)
> at
> org.apache.hadoop.hbase.replication.regionserver.ReplicationSource.readAllEntriesToReplicateOrNextFile(ReplicationSource.java:390)
> at
> org.apache.hadoop.hbase.replication.regionserver.ReplicationSource.run(ReplicationSource.java:298)
> {noformat}
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (HBASE-9359) Convert KeyValue to Cell in hbase-client module - Result/Put/Delete, ColumnInterpreter
[
https://issues.apache.org/jira/browse/HBASE-9359?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jonathan Hsieh updated HBASE-9359:
--
Release Note:
The signature for several methods on Put, Result, ColumnInterpreter, and
BaseRegionObserver have been modified to use the Cell interface instead of
KeyValues. Applications need to convert KeyValue and List to Cell
and List. The changes are summarized here:
Put:
- public List get(byte[] family, byte[] qualifier)
+ public List get(byte[] family, byte[] qualifier)
Result:
- public KeyValue[] raw() {
+ public Cell[] raw() {
- public List list() {
+ public List list() {
- public List getColumn(byte [] family, byte [] qualifier) {
+ public List getColumn(byte [] family, byte [] qualifier) {
- public KeyValue getColumnLatest(byte [] family, byte [] qualifier) {
+ public Cell getColumnLatest(byte [] family, byte [] qualifier) {
- public KeyValue getColumnLatest(byte [] family, int foffset, int flength,
+ public Cell getColumnLatest(byte [] family, int foffset, int flength,
byte [] qualifier, int qoffset, int qlength) {
For extension interfaces BaseRegionObserver and ColumnInterpreter, we have kept
both the old and new signature, including a shim that has the abstract
implementation helper have the new call the old implementation. For the shim to
handle the List -> List conversion, we use an expensive naive
array copy. It is strongly recommended that the new coprocessors are updated
to override the new undeprecated API.
ColumnInterpreter: (abstract class)
- public abstract T getValue(byte[] colFamily, byte[] colQualifier, KeyValue
kv)
+ public abstract T getValue(byte[] colFamily, byte[] colQualifier, Cell kv)
BaseRegionObserver: (abstract class)
RegionObserver: (inteface)
void preGet(final ObserverContext c, final Get
get,
- final List result)
+ final List result)
throws IOException;
void postGet(final ObserverContext c, final
Get get,
- final List result)
+ final List result)
throws IOException;
was:
The signature for several methods on Put, Result, ColumnInterpreter, and
BaseRegionObserver have been modified to use the Cell interface instead of
KeyValues. The changes are summarized here:
Put:
- public List get(byte[] family, byte[] qualifier)
+ public List get(byte[] family, byte[] qualifier)
Result:
- public KeyValue[] raw() {
+ public Cell[] raw() {
- public List list() {
+ public List list() {
- public List getColumn(byte [] family, byte [] qualifier) {
+ public List getColumn(byte [] family, byte [] qualifier) {
- public KeyValue getColumnLatest(byte [] family, byte [] qualifier) {
+ public Cell getColumnLatest(byte [] family, byte [] qualifier) {
- public KeyValue getColumnLatest(byte [] family, int foffset, int flength,
+ public Cell getColumnLatest(byte [] family, int foffset, int flength,
byte [] qualifier, int qoffset, int qlength) {
For extension interfaces BaseRegionObserver and ColumnInterpreter, we have kept
both the old and new signature, including a shim that has the abstract
implementation helper have the new call the old implementation. For the shim to
handle the List -> List conversion, we use an expensive naive
array copy. It is strongly recommended that the new coprocessors are updated
to override the new undeprecated API.
ColumnInterpreter: (abstract class)
- public abstract T getValue(byte[] colFamily, byte[] colQualifier, KeyValue
kv)
+ public abstract T getValue(byte[] colFamily, byte[] colQualifier, Cell kv)
BaseRegionObserver: (abstract class)
RegionObserver: (inteface)
void preGet(final ObserverContext c, final Get
get,
- final List result)
+ final List result)
throws IOException;
void postGet(final ObserverContext c, final
Get get,
- final List result)
+ final List result)
throws IOException;
> Convert KeyValue to Cell in hbase-client module - Result/Put/Delete,
> ColumnInterpreter
> --
>
> Key: HBASE-9359
> URL: https://issues.apache.org/jira/browse/HBASE-9359
> Project: HBase
> Issue Type: Sub-task
> Components: Client
>Affects Versions: 0.95.2
>Reporter: Jonathan Hsieh
>Assignee: Jonathan Hsieh
> Fix For: 0.98.0, 0.96.0
>
> Attachments: hbase-9334-9359.v4.patch, hbase-9359-9334.v5.patch,
> hbase-9359-9334.v6.patch, hbase-9359.patch, hbase-9359.v2.patch,
> hbase-9359.v3.patch, hbase-9359.v5.patch, hbase-9359.v6.patch
>
>
> This path is the second half of eliminating KeyValue from the client
> interfaces. This percolated through quite a bit.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JI
[jira] [Commented] (HBASE-9390) coprocessors observers are not called during a recovery with the new log replay algorithm
[
https://issues.apache.org/jira/browse/HBASE-9390?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13754813#comment-13754813
]
Ted Yu commented on HBASE-9390:
---
{code}
+ public void setThrowOnPostFlush(Boolean val){
{code}
Where is the above method called ?
Can you add some javadoc ?
Thanks
> coprocessors observers are not called during a recovery with the new log
> replay algorithm
> -
>
> Key: HBASE-9390
> URL: https://issues.apache.org/jira/browse/HBASE-9390
> Project: HBase
> Issue Type: Bug
> Components: Coprocessors, MTTR
>Affects Versions: 0.95.2
>Reporter: Nicolas Liochon
> Attachments: copro.patch
>
>
> See the patch to reproduce the issue: If we activate log replay we don't have
> the events on WAL restore.
> Pinging [~jeffreyz], we discussed this offline.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (HBASE-9334) Convert KeyValue to Cell in hbase-client module - Filters
[ https://issues.apache.org/jira/browse/HBASE-9334?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jonathan Hsieh updated HBASE-9334: -- Release Note: The 'KeyValue Filter#getNextKeyHint(KeyValue) throws IOException;' method has been deprecated. Filters should now override 'Cell Filter#getNextCellHint(final Cell) throws IOException' method instead. The 'Filter#getFilterRow(List) method has been deprecated. Filters should now override 'Cell Filter#filterRowCells(List)' method instead. The 'Filter#transform(KeyValue) method has been deprecated. Filters should now override 'Cell Filter#transformCell(Cell)' method instead. Shims have been added to support older filter derived from FilterBase but this incurs a performance penalty. > Convert KeyValue to Cell in hbase-client module - Filters > - > > Key: HBASE-9334 > URL: https://issues.apache.org/jira/browse/HBASE-9334 > Project: HBase > Issue Type: Sub-task > Components: Client >Affects Versions: 0.95.2 >Reporter: Jonathan Hsieh >Assignee: Jonathan Hsieh > Attachments: hbase-9334.patch, hbase-9334.v2.patch, > hbase-9334.v3.patch, hbase-9334.v4.patch, hbase-9334.v6.patch > > > The goal is is to remove KeyValue from the publicly exposed API and require > clients to use the cleaner mroe encapsulated Cell API instead. For filters, > this affects #filterKeyValue, #transform, #filterrow, and #getNextKeyHint. > Since Cell is a base interface for KeyValue, changing these means that 0.94 > apps may need a recompile but probably no modifications. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (HBASE-9359) Convert KeyValue to Cell in hbase-client module - Result/Put/Delete, ColumnInterpreter
[
https://issues.apache.org/jira/browse/HBASE-9359?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jonathan Hsieh updated HBASE-9359:
--
Release Note:
The signature for several methods on Put, Result, ColumnInterpreter, and
BaseRegionObserver have been modified to use the Cell interface instead of
KeyValues. The changes are summarized here:
Put:
- public List get(byte[] family, byte[] qualifier)
+ public List get(byte[] family, byte[] qualifier)
Result:
- public KeyValue[] raw() {
+ public Cell[] raw() {
- public List list() {
+ public List list() {
- public List getColumn(byte [] family, byte [] qualifier) {
+ public List getColumn(byte [] family, byte [] qualifier) {
- public KeyValue getColumnLatest(byte [] family, byte [] qualifier) {
+ public Cell getColumnLatest(byte [] family, byte [] qualifier) {
- public KeyValue getColumnLatest(byte [] family, int foffset, int flength,
+ public Cell getColumnLatest(byte [] family, int foffset, int flength,
byte [] qualifier, int qoffset, int qlength) {
For extension interfaces BaseRegionObserver and ColumnInterpreter, we have kept
both the old and new signature, including a shim that has the abstract
implementation helper have the new call the old implementation. For the shim to
handle the List -> List conversion, we use an expensive naive
array copy. It is strongly recommended that the new coprocessors are updated
to override the new undeprecated API.
ColumnInterpreter: (abstract class)
- public abstract T getValue(byte[] colFamily, byte[] colQualifier, KeyValue
kv)
+ public abstract T getValue(byte[] colFamily, byte[] colQualifier, Cell kv)
BaseRegionObserver: (abstract class)
RegionObserver: (inteface)
void preGet(final ObserverContext c, final Get
get,
- final List result)
+ final List result)
throws IOException;
void postGet(final ObserverContext c, final
Get get,
- final List result)
+ final List result)
throws IOException;
> Convert KeyValue to Cell in hbase-client module - Result/Put/Delete,
> ColumnInterpreter
> --
>
> Key: HBASE-9359
> URL: https://issues.apache.org/jira/browse/HBASE-9359
> Project: HBase
> Issue Type: Sub-task
> Components: Client
>Affects Versions: 0.95.2
>Reporter: Jonathan Hsieh
>Assignee: Jonathan Hsieh
> Fix For: 0.98.0, 0.96.0
>
> Attachments: hbase-9334-9359.v4.patch, hbase-9359-9334.v5.patch,
> hbase-9359-9334.v6.patch, hbase-9359.patch, hbase-9359.v2.patch,
> hbase-9359.v3.patch, hbase-9359.v5.patch, hbase-9359.v6.patch
>
>
> This path is the second half of eliminating KeyValue from the client
> interfaces. This percolated through quite a bit.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (HBASE-9389) Favorednodes command line not verifying assignments correctly
[ https://issues.apache.org/jira/browse/HBASE-9389?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13755119#comment-13755119 ] Hudson commented on HBASE-9389: --- SUCCESS: Integrated in HBase-TRUNK #4451 (See [https://builds.apache.org/job/HBase-TRUNK/4451/]) HBASE-9389. Fixes the verification part of favored node assignments (ddas: rev 1519030) * /hbase/trunk/hbase-server/src/main/java/org/apache/hadoop/hbase/master/AssignmentVerificationReport.java * /hbase/trunk/hbase-server/src/main/java/org/apache/hadoop/hbase/master/RegionPlacementMaintainer.java * /hbase/trunk/hbase-server/src/main/java/org/apache/hadoop/hbase/master/balancer/FavoredNodesPlan.java * /hbase/trunk/hbase-server/src/main/java/org/apache/hadoop/hbase/util/FSRegionScanner.java * /hbase/trunk/hbase-server/src/main/java/org/apache/hadoop/hbase/util/FSUtils.java * /hbase/trunk/hbase-server/src/test/java/org/apache/hadoop/hbase/master/TestRegionPlacement.java > Favorednodes command line not verifying assignments correctly > - > > Key: HBASE-9389 > URL: https://issues.apache.org/jira/browse/HBASE-9389 > Project: HBase > Issue Type: Bug >Affects Versions: 0.96.0 >Reporter: Devaraj Das >Assignee: Devaraj Das >Priority: Critical > Fix For: 0.96.0 > > Attachments: 9389-1.txt, verification-fix.1.txt > > > In manual testing, encountered an issue to do with the command line tool > (HBASE-9116) not verifying the assignments correctly. Although the regions > are assigned to the favored nodes, the verification/print showed otherwise. > The command to reproduce the problem (after having created the tables, and > loading some data): > bin/hbase org.apache.hadoop.hbase.master.RegionPlacementMaintainer -tables > cluster_test1,cluster_test2 -hbase_root /apps/hbase/data -v -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (HBASE-9394) [replication] size accounting is completely off in the source
[
https://issues.apache.org/jira/browse/HBASE-9394?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13755120#comment-13755120
]
Hudson commented on HBASE-9394:
---
SUCCESS: Integrated in HBase-TRUNK #4451 (See
[https://builds.apache.org/job/HBase-TRUNK/4451/])
HBASE-9394 [replication] size accounting is completely off in the source
(jdcryans: rev 1519040)
*
/hbase/trunk/hbase-server/src/main/java/org/apache/hadoop/hbase/replication/regionserver/ReplicationSource.java
> [replication] size accounting is completely off in the source
> -
>
> Key: HBASE-9394
> URL: https://issues.apache.org/jira/browse/HBASE-9394
> Project: HBase
> Issue Type: Bug
>Affects Versions: 0.95.2
>Reporter: Jean-Daniel Cryans
>Assignee: Jean-Daniel Cryans
> Fix For: 0.98.0, 0.96.0
>
> Attachments: HBASE-9394.patch
>
>
> I was under the impression that I was sending way more data than I was
> expecting, so adding some more tracing I can see how much data I read VS how
> I much I think I'm sending:
> {noformat}
> Seeking at position 163771687
> Replicating 2 entries of total size 2790
> Seeking at position 166723643
> {noformat}
> That's about 2MB of data, not 2KB.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (HBASE-9386) [WINDOWS] Small improvements to .cmd scripts
[ https://issues.apache.org/jira/browse/HBASE-9386?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13755117#comment-13755117 ] Hudson commented on HBASE-9386: --- SUCCESS: Integrated in HBase-TRUNK #4451 (See [https://builds.apache.org/job/HBase-TRUNK/4451/]) HBASE-9386 [WINDOWS] Small improvements to .cmd scripts (enis: rev 1519028) * /hbase/trunk/bin/hbase-config.cmd * /hbase/trunk/bin/hbase.cmd * /hbase/trunk/conf/hbase-env.cmd > [WINDOWS] Small improvements to .cmd scripts > > > Key: HBASE-9386 > URL: https://issues.apache.org/jira/browse/HBASE-9386 > Project: HBase > Issue Type: Bug >Reporter: Enis Soztutar >Assignee: Enis Soztutar > Fix For: 0.98.0, 0.96.0 > > Attachments: hbase-9386_v1.patch > > > A collection of small improvements to the .cmd scripts are needed: > - Have hbase.cmd honor --config option > - Fix log4j default appenders for standalone or service mode > - classpath fixes > - Honor JRuby options -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (HBASE-9373) [replication] data loss because replication doesn't expect partial reads
[
https://issues.apache.org/jira/browse/HBASE-9373?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13755106#comment-13755106
]
Hudson commented on HBASE-9373:
---
FAILURE: Integrated in hbase-0.95 #510 (See
[https://builds.apache.org/job/hbase-0.95/510/])
HBASE-9373 [replication] data loss because replication doesn't expect partial
reads (jdcryans: rev 1519038)
*
/hbase/branches/0.95/hbase-server/src/main/java/org/apache/hadoop/hbase/regionserver/wal/ProtobufLogReader.java
> [replication] data loss because replication doesn't expect partial reads
>
>
> Key: HBASE-9373
> URL: https://issues.apache.org/jira/browse/HBASE-9373
> Project: HBase
> Issue Type: Improvement
>Affects Versions: 0.95.2
>Reporter: Jean-Daniel Cryans
>Assignee: Jean-Daniel Cryans
>Priority: Blocker
> Fix For: 0.98.0, 0.96.0
>
> Attachments: 9373.txt, 9373-v2.txt, 9373-v3.txt, 9373-v4.patch
>
>
> When I see this in the logs it often means we got a partial read and then we
> have the wrong offset when reading the rest of the file
> {noformat}
> 2013-08-28 23:16:07,182 ERROR
> [ReplicationExecutor-0.replicationSource,1-jdec2hbase0403-5,60020,1377730319617]
> org.apache.hadoop.hbase.regionserver.wal.ProtobufLogReader: Invalid PB while
> reading WAL, probably an unexpected EOF, ignoring
> com.google.protobuf.InvalidProtocolBufferException: Protocol message tag had
> invalid wire type.
> at
> com.google.protobuf.InvalidProtocolBufferException.invalidWireType(InvalidProtocolBufferException.java:99)
> at
> com.google.protobuf.UnknownFieldSet$Builder.mergeFieldFrom(UnknownFieldSet.java:498)
> at
> com.google.protobuf.GeneratedMessage.parseUnknownField(GeneratedMessage.java:193)
> at
> org.apache.hadoop.hbase.protobuf.generated.WALProtos$WALKey.(WALProtos.java:686)
> at
> org.apache.hadoop.hbase.protobuf.generated.WALProtos$WALKey.(WALProtos.java:644)
> at
> org.apache.hadoop.hbase.protobuf.generated.WALProtos$WALKey$1.parsePartialFrom(WALProtos.java:771)
> at
> org.apache.hadoop.hbase.protobuf.generated.WALProtos$WALKey$1.parsePartialFrom(WALProtos.java:766)
> at
> org.apache.hadoop.hbase.protobuf.generated.WALProtos$WALKey$Builder.mergeFrom(WALProtos.java:1444)
> at
> org.apache.hadoop.hbase.protobuf.generated.WALProtos$WALKey$Builder.mergeFrom(WALProtos.java:1218)
> at
> com.google.protobuf.AbstractMessageLite$Builder.mergeFrom(AbstractMessageLite.java:220)
> at
> com.google.protobuf.AbstractMessage$Builder.mergeFrom(AbstractMessage.java:912)
> at
> com.google.protobuf.AbstractMessage$Builder.mergeFrom(AbstractMessage.java:267)
> at
> com.google.protobuf.AbstractMessageLite$Builder.mergeDelimitedFrom(AbstractMessageLite.java:290)
> at
> com.google.protobuf.AbstractMessage$Builder.mergeDelimitedFrom(AbstractMessage.java:926)
> at
> com.google.protobuf.AbstractMessageLite$Builder.mergeDelimitedFrom(AbstractMessageLite.java:296)
> at
> com.google.protobuf.AbstractMessage$Builder.mergeDelimitedFrom(AbstractMessage.java:918)
> at
> org.apache.hadoop.hbase.regionserver.wal.ProtobufLogReader.readNext(ProtobufLogReader.java:197)
> at
> org.apache.hadoop.hbase.regionserver.wal.ReaderBase.next(ReaderBase.java:98)
> at
> org.apache.hadoop.hbase.replication.regionserver.ReplicationHLogReaderManager.readNextAndSetPosition(ReplicationHLogReaderManager.java:89)
> at
> org.apache.hadoop.hbase.replication.regionserver.ReplicationSource.readAllEntriesToReplicateOrNextFile(ReplicationSource.java:390)
> at
> org.apache.hadoop.hbase.replication.regionserver.ReplicationSource.run(ReplicationSource.java:298)
> {noformat}
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (HBASE-9386) [WINDOWS] Small improvements to .cmd scripts
[ https://issues.apache.org/jira/browse/HBASE-9386?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13755105#comment-13755105 ] Hudson commented on HBASE-9386: --- FAILURE: Integrated in hbase-0.95 #510 (See [https://builds.apache.org/job/hbase-0.95/510/]) HBASE-9386 [WINDOWS] Small improvements to .cmd scripts (enis: rev 1519029) * /hbase/branches/0.95/bin/hbase-config.cmd * /hbase/branches/0.95/bin/hbase.cmd * /hbase/branches/0.95/conf/hbase-env.cmd > [WINDOWS] Small improvements to .cmd scripts > > > Key: HBASE-9386 > URL: https://issues.apache.org/jira/browse/HBASE-9386 > Project: HBase > Issue Type: Bug >Reporter: Enis Soztutar >Assignee: Enis Soztutar > Fix For: 0.98.0, 0.96.0 > > Attachments: hbase-9386_v1.patch > > > A collection of small improvements to the .cmd scripts are needed: > - Have hbase.cmd honor --config option > - Fix log4j default appenders for standalone or service mode > - classpath fixes > - Honor JRuby options -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (HBASE-9389) Favorednodes command line not verifying assignments correctly
[ https://issues.apache.org/jira/browse/HBASE-9389?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13755107#comment-13755107 ] Hudson commented on HBASE-9389: --- FAILURE: Integrated in hbase-0.95 #510 (See [https://builds.apache.org/job/hbase-0.95/510/]) HBASE-9389. Fixes the verification part of favored node assignments (ddas: rev 1519031) * /hbase/branches/0.95/hbase-server/src/main/java/org/apache/hadoop/hbase/master/AssignmentVerificationReport.java * /hbase/branches/0.95/hbase-server/src/main/java/org/apache/hadoop/hbase/master/RegionPlacementMaintainer.java * /hbase/branches/0.95/hbase-server/src/main/java/org/apache/hadoop/hbase/master/balancer/FavoredNodesPlan.java * /hbase/branches/0.95/hbase-server/src/main/java/org/apache/hadoop/hbase/util/FSRegionScanner.java * /hbase/branches/0.95/hbase-server/src/main/java/org/apache/hadoop/hbase/util/FSUtils.java * /hbase/branches/0.95/hbase-server/src/test/java/org/apache/hadoop/hbase/master/TestRegionPlacement.java > Favorednodes command line not verifying assignments correctly > - > > Key: HBASE-9389 > URL: https://issues.apache.org/jira/browse/HBASE-9389 > Project: HBase > Issue Type: Bug >Affects Versions: 0.96.0 >Reporter: Devaraj Das >Assignee: Devaraj Das >Priority: Critical > Fix For: 0.96.0 > > Attachments: 9389-1.txt, verification-fix.1.txt > > > In manual testing, encountered an issue to do with the command line tool > (HBASE-9116) not verifying the assignments correctly. Although the regions > are assigned to the favored nodes, the verification/print showed otherwise. > The command to reproduce the problem (after having created the tables, and > loading some data): > bin/hbase org.apache.hadoop.hbase.master.RegionPlacementMaintainer -tables > cluster_test1,cluster_test2 -hbase_root /apps/hbase/data -v -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (HBASE-9394) [replication] size accounting is completely off in the source
[
https://issues.apache.org/jira/browse/HBASE-9394?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13755108#comment-13755108
]
Hudson commented on HBASE-9394:
---
FAILURE: Integrated in hbase-0.95 #510 (See
[https://builds.apache.org/job/hbase-0.95/510/])
HBASE-9394 [replication] size accounting is completely off in the source
(jdcryans: rev 1519039)
*
/hbase/branches/0.95/hbase-server/src/main/java/org/apache/hadoop/hbase/replication/regionserver/ReplicationSource.java
> [replication] size accounting is completely off in the source
> -
>
> Key: HBASE-9394
> URL: https://issues.apache.org/jira/browse/HBASE-9394
> Project: HBase
> Issue Type: Bug
>Affects Versions: 0.95.2
>Reporter: Jean-Daniel Cryans
>Assignee: Jean-Daniel Cryans
> Fix For: 0.98.0, 0.96.0
>
> Attachments: HBASE-9394.patch
>
>
> I was under the impression that I was sending way more data than I was
> expecting, so adding some more tracing I can see how much data I read VS how
> I much I think I'm sending:
> {noformat}
> Seeking at position 163771687
> Replicating 2 entries of total size 2790
> Seeking at position 166723643
> {noformat}
> That's about 2MB of data, not 2KB.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (HBASE-9359) Convert KeyValue to Cell in hbase-client module - Result/Put/Delete, ColumnInterpreter
[ https://issues.apache.org/jira/browse/HBASE-9359?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jonathan Hsieh updated HBASE-9359: -- Resolution: Fixed Hadoop Flags: Reviewed Status: Resolved (was: Patch Available) Thanks for the reviews, committed simultaneously with HBASE-9334 to 0.96 and trunk. > Convert KeyValue to Cell in hbase-client module - Result/Put/Delete, > ColumnInterpreter > -- > > Key: HBASE-9359 > URL: https://issues.apache.org/jira/browse/HBASE-9359 > Project: HBase > Issue Type: Sub-task > Components: Client >Affects Versions: 0.95.2 >Reporter: Jonathan Hsieh >Assignee: Jonathan Hsieh > Fix For: 0.98.0, 0.96.0 > > Attachments: hbase-9334-9359.v4.patch, hbase-9359-9334.v5.patch, > hbase-9359-9334.v6.patch, hbase-9359.patch, hbase-9359.v2.patch, > hbase-9359.v3.patch, hbase-9359.v5.patch, hbase-9359.v6.patch > > > This path is the second half of eliminating KeyValue from the client > interfaces. This percolated through quite a bit. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (HBASE-9334) Convert KeyValue to Cell in hbase-client module - Filters
[ https://issues.apache.org/jira/browse/HBASE-9334?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jonathan Hsieh updated HBASE-9334: -- Resolution: Fixed Hadoop Flags: Reviewed Status: Resolved (was: Patch Available) Thanks for the reviews. Committed in the same patch as HBASE-9359. > Convert KeyValue to Cell in hbase-client module - Filters > - > > Key: HBASE-9334 > URL: https://issues.apache.org/jira/browse/HBASE-9334 > Project: HBase > Issue Type: Sub-task > Components: Client >Affects Versions: 0.95.2 >Reporter: Jonathan Hsieh >Assignee: Jonathan Hsieh > Attachments: hbase-9334.patch, hbase-9334.v2.patch, > hbase-9334.v3.patch, hbase-9334.v4.patch, hbase-9334.v6.patch > > > The goal is is to remove KeyValue from the publicly exposed API and require > clients to use the cleaner mroe encapsulated Cell API instead. For filters, > this affects #filterKeyValue, #transform, #filterrow, and #getNextKeyHint. > Since Cell is a base interface for KeyValue, changing these means that 0.94 > apps may need a recompile but probably no modifications. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (HBASE-9391) Compilation problem in AccessController with JDK 6
[
https://issues.apache.org/jira/browse/HBASE-9391?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13755097#comment-13755097
]
Gary Helmling commented on HBASE-9391:
--
+1
Patch seems simple enough.
> Compilation problem in AccessController with JDK 6
> --
>
> Key: HBASE-9391
> URL: https://issues.apache.org/jira/browse/HBASE-9391
> Project: HBase
> Issue Type: Bug
>Affects Versions: 0.98.0, 0.95.2
>Reporter: Andrew Purtell
>Assignee: Andrew Purtell
> Attachments: 9391.patch
>
>
> Seeing this with a fresh checkout of trunk and 0.95, only with JDK 6:
> {noformat}
> [ERROR]
> hbase-server/src/main/java/org/apache/hadoop/hbase/security/access/AccessController.java:[541,56]
> incompatible types; no instance(s) of type variable(s) K,V exist so that
> java.util.TreeMap conforms to java.util.Map>
> [ERROR] found : java.util.TreeMap
> [ERROR] required: java.util.Map>
> [ERROR]
> hbase-server/src/main/java/org/apache/hadoop/hbase/security/access/AccessController.java:[1072,56]
> incompatible types; no instance(s) of type variable(s) K,V exist so that
> java.util.TreeMap conforms to java.util.Map>
> [ERROR] found : java.util.TreeMap
> [ERROR] required: java.util.Map>
> [ERROR]
> hbase-server/src/main/java/org/apache/hadoop/hbase/security/access/AccessController.java:[1383,64]
> incompatible types; no instance(s) of type variable(s) K,V exist so that
> java.util.TreeMap conforms to java.util.Map>
> [ERROR] found : java.util.TreeMap
> [ERROR] required: java.util.Map>
> [ERROR]
> hbase-server/src/main/java/org/apache/hadoop/hbase/security/access/AccessController.java:[1473,63]
> incompatible types; no instance(s) of type variable(s) K,V exist so that
> java.util.TreeMap conforms to
> java.util.Map>
> [ERROR] found : java.util.TreeMap
> [ERROR] required: java.util.Map>
> {noformat}
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (HBASE-9387) Region could get lost during assignment
[
https://issues.apache.org/jira/browse/HBASE-9387?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ted Yu updated HBASE-9387:
--
Attachment: 9387-v4.2.txt
The abort() call in tryTransitionFromOfflineToFailedOpen() made
TestRegionServerNoMaster fail.
> Region could get lost during assignment
> ---
>
> Key: HBASE-9387
> URL: https://issues.apache.org/jira/browse/HBASE-9387
> Project: HBase
> Issue Type: Bug
> Components: Region Assignment
>Affects Versions: 0.95.2
>Reporter: Ted Yu
>Assignee: Ted Yu
>Priority: Critical
> Attachments: 9387-v1.txt, 9387-v3.txt, 9387-v4.2.txt, 9387-v4.txt,
> 9387-v5.txt, hbase-9387.patch,
> org.apache.hadoop.hbase.TestFullLogReconstruction-output.txt
>
>
> I observed test timeout running against hadoop 2.1.0 with distributed log
> replay turned on.
> Looks like region state for 1588230740 became inconsistent between master and
> the surviving region server:
> {code}
> 2013-08-29 22:15:34,180 INFO [AM.ZK.Worker-pool2-t4]
> master.RegionStates(299): Onlined 1588230740 on
> kiyo.gq1.ygridcore.net,57016,1377814510039
> ...
> 2013-08-29 22:15:34,587 DEBUG [Thread-221]
> client.HConnectionManager$HConnectionImplementation(1269): locateRegionInMeta
> parentTable=hbase:meta, metaLocation={region=hbase:meta,,1.1588230740,
> hostname=kiyo.gq1.ygridcore.net,57016,1377814510039, seqNum=0}, attempt=2 of
> 35 failed; retrying after sleep of 302 because:
> org.apache.hadoop.hbase.exceptions.RegionOpeningException: Region is being
> opened: 1588230740
> at
> org.apache.hadoop.hbase.regionserver.HRegionServer.getRegionByEncodedName(HRegionServer.java:2574)
> at
> org.apache.hadoop.hbase.regionserver.HRegionServer.getRegion(HRegionServer.java:3949)
> at
> org.apache.hadoop.hbase.regionserver.HRegionServer.get(HRegionServer.java:2733)
> at
> org.apache.hadoop.hbase.protobuf.generated.ClientProtos$ClientService$2.callBlockingMethod(ClientProtos.java:26965)
> at org.apache.hadoop.hbase.ipc.RpcServer.call(RpcServer.java:2063)
> at
> org.apache.hadoop.hbase.ipc.RpcServer$CallRunner.run(RpcServer.java:1800)
> at
> org.apache.hadoop.hbase.ipc.SimpleRpcScheduler.consumerLoop(SimpleRpcScheduler.java:165)
> at
> org.apache.hadoop.hbase.ipc.SimpleRpcScheduler.access$000(SimpleRpcScheduler.java:41)
> {code}
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Created] (HBASE-9396) Remove deprecation and shims from HBASE-9334/HBASE-9359 from 0.98
Jonathan Hsieh created HBASE-9396: - Summary: Remove deprecation and shims from HBASE-9334/HBASE-9359 from 0.98 Key: HBASE-9396 URL: https://issues.apache.org/jira/browse/HBASE-9396 Project: HBase Issue Type: Sub-task Reporter: Jonathan Hsieh Assignee: Jonathan Hsieh The version commited to 0.96 and trunk were essentially identical and included deprecation shims. This follow-on patch will remove deprecated stuff from trunk only. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
