[jira] [Commented] (HBASE-8462) Custom timestamps should not be allowed to be negative
[ https://issues.apache.org/jira/browse/HBASE-8462?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13758836#comment-13758836 ] Jarek Jarcec Cecho commented on HBASE-8462: --- The fixVersion is currently set to 0.98.0 and 0.96.0, however the patch also seems to be available in 0.95. So I'm wondering whether it would make sense to add 0.95.3 to fixVersion as well? > Custom timestamps should not be allowed to be negative > -- > > Key: HBASE-8462 > URL: https://issues.apache.org/jira/browse/HBASE-8462 > Project: HBase > Issue Type: Bug > Components: Client >Reporter: Enis Soztutar >Assignee: Enis Soztutar > Fix For: 0.98.0, 0.96.0 > > Attachments: hbase-8462_v1.patch, hbase-8462_v2.patch, > hbase-8462_v3.patch > > > Client supplied timestamps should not be allowed to be negative, otherwise > unpredictable results will follow. Especially, since we are encoding the ts > using Bytes.Bytes(long), negative timestamps are sorted after positive ones. > Plus, the new PB messages define ts' as uint64. > Credit goes to Huned Lokhandwala for reporting this. -- 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-9430) Memstore heapSize calculation - DEEP_OVERHEAD is incorrect
[
https://issues.apache.org/jira/browse/HBASE-9430?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13758811#comment-13758811
]
Hadoop QA commented on HBASE-9430:
--
{color:green}+1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12601558/HBASE-9430.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: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/7047//testReport/
Findbugs warnings:
https://builds.apache.org/job/PreCommit-HBASE-Build/7047//artifact/trunk/patchprocess/newPatchFindbugsWarningshbase-protocol.html
Findbugs warnings:
https://builds.apache.org/job/PreCommit-HBASE-Build/7047//artifact/trunk/patchprocess/newPatchFindbugsWarningshbase-client.html
Findbugs warnings:
https://builds.apache.org/job/PreCommit-HBASE-Build/7047//artifact/trunk/patchprocess/newPatchFindbugsWarningshbase-examples.html
Findbugs warnings:
https://builds.apache.org/job/PreCommit-HBASE-Build/7047//artifact/trunk/patchprocess/newPatchFindbugsWarningshbase-hadoop1-compat.html
Findbugs warnings:
https://builds.apache.org/job/PreCommit-HBASE-Build/7047//artifact/trunk/patchprocess/newPatchFindbugsWarningshbase-prefix-tree.html
Findbugs warnings:
https://builds.apache.org/job/PreCommit-HBASE-Build/7047//artifact/trunk/patchprocess/newPatchFindbugsWarningshbase-common.html
Findbugs warnings:
https://builds.apache.org/job/PreCommit-HBASE-Build/7047//artifact/trunk/patchprocess/newPatchFindbugsWarningshbase-server.html
Findbugs warnings:
https://builds.apache.org/job/PreCommit-HBASE-Build/7047//artifact/trunk/patchprocess/newPatchFindbugsWarningshbase-hadoop-compat.html
Console output:
https://builds.apache.org/job/PreCommit-HBASE-Build/7047//console
This message is automatically generated.
> Memstore heapSize calculation - DEEP_OVERHEAD is incorrect
> --
>
> Key: HBASE-9430
> URL: https://issues.apache.org/jira/browse/HBASE-9430
> Project: HBase
> Issue Type: Bug
>Reporter: Anoop Sam John
>Assignee: Anoop Sam John
> Attachments: HBASE-9430.patch
>
>
> {code}
> expected += ClassSize.estimateBase(ConcurrentSkipListMap.class, false);
> expected += ClassSize.estimateBase(ConcurrentSkipListMap.class, false);
> expected += ClassSize.estimateBase(CopyOnWriteArraySet.class, false);
> expected += ClassSize.estimateBase(CopyOnWriteArrayList.class, false);
> {code}
> We need to consider the heap requirement for KeyValueSkipListSet.
> From where CopyOnWriteArraySet & CopyOnWriteArrayList is coming into picture?
> I am not able to follow.
> Also we need to consider the heap for TimeRangeTracker
--
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-9443) ReplicationProtbufUtil.toHLogEntries needs to be either removed or deprecated
[ https://issues.apache.org/jira/browse/HBASE-9443?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13758807#comment-13758807 ] Anoop Sam John commented on HBASE-9443: --- Yes this method is useless now. +1 on removing this. You have a patch? > ReplicationProtbufUtil.toHLogEntries needs to be either removed or deprecated > - > > Key: HBASE-9443 > URL: https://issues.apache.org/jira/browse/HBASE-9443 > Project: HBase > Issue Type: Improvement > Components: Replication >Affects Versions: 0.96.0 >Reporter: Roman Shaposhnik > > Currently, due to HBASE-9442 ReplicationProtbufUtil.toHLogEntries is rendered > useless. > Given that it isn't really used by HBase itself, perhaps it needs to be > removed/deprecated? -- 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-9443) ReplicationProtbufUtil.toHLogEntries needs to be either removed or deprecated
Roman Shaposhnik created HBASE-9443: --- Summary: ReplicationProtbufUtil.toHLogEntries needs to be either removed or deprecated Key: HBASE-9443 URL: https://issues.apache.org/jira/browse/HBASE-9443 Project: HBase Issue Type: Improvement Components: Replication Affects Versions: 0.96.0 Reporter: Roman Shaposhnik Currently, due to HBASE-9442 ReplicationProtbufUtil.toHLogEntries is rendered useless. Given that it isn't really used by HBase itself, perhaps it needs to be removed/deprecated? -- 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-9442) HLogKey(walKey) constructor needs to be either removed, deprecated or fixed
Roman Shaposhnik created HBASE-9442: --- Summary: HLogKey(walKey) constructor needs to be either removed, deprecated or fixed Key: HBASE-9442 URL: https://issues.apache.org/jira/browse/HBASE-9442 Project: HBase Issue Type: Bug Affects Versions: 0.96.0 Reporter: Roman Shaposhnik It is currently impossible to use HLogKey(walKey) because of the NPE that occurs due to constructor itself not initializing clusterIds but instead immediately calling readFieldsFromPb which then references it: https://github.com/apache/hbase/blob/trunk/hbase-server/src/main/java/org/apache/hadoop/hbase/regionserver/wal/HLogKey.java#L475 -- 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-8912) [0.94] AssignmentManager throws IllegalStateException from PENDING_OPEN to OFFLINE
[
https://issues.apache.org/jira/browse/HBASE-8912?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13758801#comment-13758801
]
ramkrishna.s.vasudevan commented on HBASE-8912:
---
I can check it next week if you are Okie with it Enis?
> [0.94] AssignmentManager throws IllegalStateException from PENDING_OPEN to
> OFFLINE
> --
>
> Key: HBASE-8912
> URL: https://issues.apache.org/jira/browse/HBASE-8912
> Project: HBase
> Issue Type: Bug
>Reporter: Enis Soztutar
> Fix For: 0.94.12
>
> Attachments: HBase-0.94 #1036 test - testRetrying [Jenkins].html
>
>
> AM throws this exception which subsequently causes the master to abort:
> {code}
> java.lang.IllegalStateException: Unexpected state :
> testRetrying,jjj,1372891751115.9b828792311001062a5ff4b1038fe33b.
> state=PENDING_OPEN, ts=1372891751912,
> server=hemera.apache.org,39064,1372891746132 .. Cannot transit it to OFFLINE.
> at
> org.apache.hadoop.hbase.master.AssignmentManager.setOfflineInZooKeeper(AssignmentManager.java:1879)
> at
> org.apache.hadoop.hbase.master.AssignmentManager.assign(AssignmentManager.java:1688)
> at
> org.apache.hadoop.hbase.master.AssignmentManager.assign(AssignmentManager.java:1424)
> at
> org.apache.hadoop.hbase.master.AssignmentManager.assign(AssignmentManager.java:1399)
> at
> org.apache.hadoop.hbase.master.AssignmentManager.assign(AssignmentManager.java:1394)
> at
> org.apache.hadoop.hbase.master.handler.ClosedRegionHandler.process(ClosedRegionHandler.java:105)
> at
> org.apache.hadoop.hbase.executor.EventHandler.run(EventHandler.java:175)
> at
> java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:895)
> at
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:918)
> at java.lang.Thread.run(Thread.java:662)
> {code}
> This exception trace is from the failing test TestMetaReaderEditor which is
> failing pretty frequently, but looking at the test code, I think this is not
> a test-only issue, but affects the main code path.
> https://builds.apache.org/job/HBase-0.94/1036/testReport/junit/org.apache.hadoop.hbase.catalog/TestMetaReaderEditor/testRetrying/
--
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-8773) Can be setup the COMPRESSION base on HTable in meta or user set in Configuration
[ https://issues.apache.org/jira/browse/HBASE-8773?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Lars Hofhansl updated HBASE-8773: - Fix Version/s: (was: 0.94.12) I'd like to unschedule this for now. > Can be setup the COMPRESSION base on HTable in meta or user set in > Configuration > > > Key: HBASE-8773 > URL: https://issues.apache.org/jira/browse/HBASE-8773 > Project: HBase > Issue Type: New Feature > Components: HFile >Affects Versions: 0.94.8 >Reporter: jay wong >Priority: Minor > Attachments: HBASE-8773.patch > > > when I want create HFile with the ImportTsv. I found that if i set the > compression in the Configuration or not, It's always invalid。 > It because of the method 'configureIncrementalLoad' in HFileOutputFormat will > set the compression with the HTable in meta. So if add a configuration to > switch use set compression with HTable or Not -- 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-9430) Memstore heapSize calculation - DEEP_OVERHEAD is incorrect
[
https://issues.apache.org/jira/browse/HBASE-9430?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Anoop Sam John updated HBASE-9430:
--
Attachment: HBASE-9430.patch
> Memstore heapSize calculation - DEEP_OVERHEAD is incorrect
> --
>
> Key: HBASE-9430
> URL: https://issues.apache.org/jira/browse/HBASE-9430
> Project: HBase
> Issue Type: Bug
>Reporter: Anoop Sam John
>Assignee: Anoop Sam John
> Attachments: HBASE-9430.patch
>
>
> {code}
> expected += ClassSize.estimateBase(ConcurrentSkipListMap.class, false);
> expected += ClassSize.estimateBase(ConcurrentSkipListMap.class, false);
> expected += ClassSize.estimateBase(CopyOnWriteArraySet.class, false);
> expected += ClassSize.estimateBase(CopyOnWriteArrayList.class, false);
> {code}
> We need to consider the heap requirement for KeyValueSkipListSet.
> From where CopyOnWriteArraySet & CopyOnWriteArrayList is coming into picture?
> I am not able to follow.
> Also we need to consider the heap for TimeRangeTracker
--
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-9430) Memstore heapSize calculation - DEEP_OVERHEAD is incorrect
[
https://issues.apache.org/jira/browse/HBASE-9430?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Anoop Sam John updated HBASE-9430:
--
Status: Patch Available (was: Open)
> Memstore heapSize calculation - DEEP_OVERHEAD is incorrect
> --
>
> Key: HBASE-9430
> URL: https://issues.apache.org/jira/browse/HBASE-9430
> Project: HBase
> Issue Type: Bug
>Reporter: Anoop Sam John
>Assignee: Anoop Sam John
> Attachments: HBASE-9430.patch
>
>
> {code}
> expected += ClassSize.estimateBase(ConcurrentSkipListMap.class, false);
> expected += ClassSize.estimateBase(ConcurrentSkipListMap.class, false);
> expected += ClassSize.estimateBase(CopyOnWriteArraySet.class, false);
> expected += ClassSize.estimateBase(CopyOnWriteArrayList.class, false);
> {code}
> We need to consider the heap requirement for KeyValueSkipListSet.
> From where CopyOnWriteArraySet & CopyOnWriteArrayList is coming into picture?
> I am not able to follow.
> Also we need to consider the heap for TimeRangeTracker
--
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-9433) OpenRegionHandler uses different assignment timeout
[ https://issues.apache.org/jira/browse/HBASE-9433?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13758784#comment-13758784 ] Hudson commented on HBASE-9433: --- SUCCESS: Integrated in HBase-TRUNK-on-Hadoop-2.0.0 #711 (See [https://builds.apache.org/job/HBase-TRUNK-on-Hadoop-2.0.0/711/]) HBASE-9433 OpenRegionHandler uses different assignment timeout (jxiang: rev 1520173) * /hbase/trunk/hbase-server/src/main/java/org/apache/hadoop/hbase/master/AssignmentManager.java * /hbase/trunk/hbase-server/src/main/java/org/apache/hadoop/hbase/regionserver/HRegion.java * /hbase/trunk/hbase-server/src/main/java/org/apache/hadoop/hbase/regionserver/handler/OpenRegionHandler.java > OpenRegionHandler uses different assignment timeout > --- > > Key: HBASE-9433 > URL: https://issues.apache.org/jira/browse/HBASE-9433 > Project: HBase > Issue Type: Bug > Components: Region Assignment >Affects Versions: 0.96.0 >Reporter: Jimmy Xiang >Assignee: Jimmy Xiang >Priority: Minor > Fix For: 0.98.0, 0.96.0 > > Attachments: trunk-9433.patch, trunk-9433_rebased.patch, > trunk-9433_v2.patch > > > OpenRegionHandler uses the timeout monitor checking period as the timeout. It > should share the same default as in AssignmentManager. -- 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-9435) Fix jersey serialization/deserialization of json objects
[ https://issues.apache.org/jira/browse/HBASE-9435?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13758782#comment-13758782 ] Hudson commented on HBASE-9435: --- SUCCESS: Integrated in HBase-TRUNK-on-Hadoop-2.0.0 #711 (See [https://builds.apache.org/job/HBase-TRUNK-on-Hadoop-2.0.0/711/]) HBASE-9435 Fix jersey serialization/deserialization of json objects (stack: rev 1520179) * /hbase/trunk/hbase-server/src/main/java/org/apache/hadoop/hbase/rest/client/RemoteHTable.java * /hbase/trunk/hbase-server/src/main/java/org/apache/hadoop/hbase/rest/model/CellModel.java * /hbase/trunk/hbase-server/src/main/java/org/apache/hadoop/hbase/rest/model/CellSetModel.java * /hbase/trunk/hbase-server/src/main/java/org/apache/hadoop/hbase/rest/model/ColumnSchemaModel.java * /hbase/trunk/hbase-server/src/main/java/org/apache/hadoop/hbase/rest/model/RowModel.java * /hbase/trunk/hbase-server/src/main/java/org/apache/hadoop/hbase/rest/model/StorageClusterVersionModel.java * /hbase/trunk/hbase-server/src/main/java/org/apache/hadoop/hbase/rest/model/TableSchemaModel.java * /hbase/trunk/hbase-server/src/main/java/org/apache/hadoop/hbase/rest/provider/JacksonProvider.java * /hbase/trunk/hbase-server/src/test/java/org/apache/hadoop/hbase/rest/TestSchemaResource.java * /hbase/trunk/hbase-server/src/test/java/org/apache/hadoop/hbase/rest/TestStatusResource.java * /hbase/trunk/hbase-server/src/test/java/org/apache/hadoop/hbase/rest/model/TestCellModel.java * /hbase/trunk/hbase-server/src/test/java/org/apache/hadoop/hbase/rest/model/TestCellSetModel.java * /hbase/trunk/hbase-server/src/test/java/org/apache/hadoop/hbase/rest/model/TestColumnSchemaModel.java * /hbase/trunk/hbase-server/src/test/java/org/apache/hadoop/hbase/rest/model/TestModelBase.java * /hbase/trunk/hbase-server/src/test/java/org/apache/hadoop/hbase/rest/model/TestRowModel.java * /hbase/trunk/hbase-server/src/test/java/org/apache/hadoop/hbase/rest/model/TestScannerModel.java * /hbase/trunk/hbase-server/src/test/java/org/apache/hadoop/hbase/rest/model/TestStorageClusterStatusModel.java * /hbase/trunk/hbase-server/src/test/java/org/apache/hadoop/hbase/rest/model/TestStorageClusterVersionModel.java * /hbase/trunk/hbase-server/src/test/java/org/apache/hadoop/hbase/rest/model/TestTableInfoModel.java * /hbase/trunk/hbase-server/src/test/java/org/apache/hadoop/hbase/rest/model/TestTableListModel.java * /hbase/trunk/hbase-server/src/test/java/org/apache/hadoop/hbase/rest/model/TestTableRegionModel.java * /hbase/trunk/hbase-server/src/test/java/org/apache/hadoop/hbase/rest/model/TestTableSchemaModel.java * /hbase/trunk/hbase-server/src/test/java/org/apache/hadoop/hbase/rest/model/TestVersionModel.java > Fix jersey serialization/deserialization of json objects > > > Key: HBASE-9435 > URL: https://issues.apache.org/jira/browse/HBASE-9435 > Project: HBase > Issue Type: Bug > Components: REST >Reporter: Francis Liu >Assignee: Francis Liu > Fix For: 0.98.0, 0.96.1 > > Attachments: HBASE-9435.patch, HBASE-9435.patch > > > Stargate uses the default json marshaller/unmarshaller in natural mode. In > this mode the unmarshaller has trouble unmarshalling json instances. > This patch fixes this issue by using jackson as the marshaller/unmarshaller > instead. > I've also updated all the model unit tests to test json > serialization/deserialization. Backwards compatibilty can be verified by > modify the test base class to use the original marshaller/unmarshaller and > see that model tests pass. > The patch is backward compatible except for StorageClusterStatusModel, which > is broken anyway. It only shows one node in the liveNodes field. -- 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-9439) shell command list shows something not meaningful
[
https://issues.apache.org/jira/browse/HBASE-9439?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13758783#comment-13758783
]
Hudson commented on HBASE-9439:
---
SUCCESS: Integrated in HBase-TRUNK-on-Hadoop-2.0.0 #711 (See
[https://builds.apache.org/job/HBase-TRUNK-on-Hadoop-2.0.0/711/])
HBASE-9439 shell command list shows something not meaningful (jxiang: rev
1520176)
* /hbase/trunk/hbase-server/src/main/ruby/shell/commands/list.rb
> shell command list shows something not meaningful
> -
>
> Key: HBASE-9439
> URL: https://issues.apache.org/jira/browse/HBASE-9439
> Project: HBase
> Issue Type: Bug
> Components: shell
>Reporter: Jimmy Xiang
>Assignee: Jimmy Xiang
>Priority: Minor
> Fix For: 0.98.0, 0.96.0
>
> Attachments: trunk-9439.patch
>
>
> Here is a sample output:
> {noformat}
> hbase(main):004:0> list
> TABLE
>
>
> usertable
>
>
> 1 row(s) in 0.3240 seconds
> => #<#:0x5eb8f6d>
> {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-9259) Update hadoop versions grid in refguide adding hadoop-2.1.x and a note on hadoop-2.0.x versions
[ https://issues.apache.org/jira/browse/HBASE-9259?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13758781#comment-13758781 ] Hudson commented on HBASE-9259: --- SUCCESS: Integrated in HBase-TRUNK-on-Hadoop-2.0.0 #711 (See [https://builds.apache.org/job/HBase-TRUNK-on-Hadoop-2.0.0/711/]) HBASE-9259 Update hadoop versions grid in refguide adding hadoop-2.1.x and a note on hadoop-2.0.x versions (stack: rev 1520185) * /hbase/trunk/src/main/docbkx/configuration.xml * /hbase/trunk/src/main/docbkx/getting_started.xml * /hbase/trunk/src/main/docbkx/preface.xml > Update hadoop versions grid in refguide adding hadoop-2.1.x and a note on > hadoop-2.0.x versions > --- > > Key: HBASE-9259 > URL: https://issues.apache.org/jira/browse/HBASE-9259 > Project: HBase > Issue Type: Sub-task > Components: documentation >Reporter: stack >Assignee: stack > Fix For: 0.98.0, 0.96.0 > > Attachments: 9259.txt > > > Need to update our hadoop versions grid. Add notes on hadoop-2.1 and > hadoop-2.0 (we do the former, not the latter) -- 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=13758780#comment-13758780 ] Hudson commented on HBASE-9388: --- SUCCESS: Integrated in HBase-TRUNK-on-Hadoop-2.0.0 #711 (See [https://builds.apache.org/job/HBase-TRUNK-on-Hadoop-2.0.0/711/]) HBASE-9388 [replication] ZK Dump prints the raw PBUF for the HLog positions (stack: rev 1520184) * /hbase/trunk/hbase-client/src/main/java/org/apache/hadoop/hbase/zookeeper/ZKUtil.java > [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: Himanshu Vashishtha > Fix For: 0.98.0, 0.96.0 > > Attachments: HBase-9388.patch, HBASE-9388.patch, > ReplicationZnodesDump.png > > > 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] [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=13758785#comment-13758785
]
Hudson commented on HBASE-8930:
---
SUCCESS: Integrated in HBase-TRUNK-on-Hadoop-2.0.0 #711 (See
[https://builds.apache.org/job/HBase-TRUNK-on-Hadoop-2.0.0/711/])
HBASE-8930 Add missing file (larsh: rev 1520169)
*
/hbase/trunk/hbase-server/src/test/java/org/apache/hadoop/hbase/filter/TestInvocationRecordFilter.java
> 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
> Fix For: 0.98.0, 0.94.12, 0.96.1
>
> Attachments: 0.94-HBASE-8930.patch, 0.94-HBASE-8930-rev1.patch,
> 0.95-HBASE-8930.patch, 0.95-HBASE-8930-rev1.patch,
> 0.96-HBASE-8930-rev2.patch, 8930-0.94.txt, HBASE-8930.patch,
> HBASE-8930-rev1.patch, HBASE-8930-rev2.patch, HBASE-8930-rev3.patch,
> HBASE-8930-rev4.patch, HBASE-8930-rev5.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.toByte
[jira] [Commented] (HBASE-9259) Update hadoop versions grid in refguide adding hadoop-2.1.x and a note on hadoop-2.0.x versions
[ https://issues.apache.org/jira/browse/HBASE-9259?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13758778#comment-13758778 ] Hudson commented on HBASE-9259: --- SUCCESS: Integrated in hbase-0.96 #12 (See [https://builds.apache.org/job/hbase-0.96/12/]) HBASE-9259 Update hadoop versions grid in refguide adding hadoop-2.1.x and a note on hadoop-2.0.x versions (stack: rev 1520186) * /hbase/branches/0.96/src/main/docbkx/configuration.xml * /hbase/branches/0.96/src/main/docbkx/developer.xml * /hbase/branches/0.96/src/main/docbkx/getting_started.xml * /hbase/branches/0.96/src/main/docbkx/preface.xml * /hbase/branches/0.96/src/main/docbkx/upgrading.xml > Update hadoop versions grid in refguide adding hadoop-2.1.x and a note on > hadoop-2.0.x versions > --- > > Key: HBASE-9259 > URL: https://issues.apache.org/jira/browse/HBASE-9259 > Project: HBase > Issue Type: Sub-task > Components: documentation >Reporter: stack >Assignee: stack > Fix For: 0.98.0, 0.96.0 > > Attachments: 9259.txt > > > Need to update our hadoop versions grid. Add notes on hadoop-2.1 and > hadoop-2.0 (we do the former, not the latter) -- 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=13758777#comment-13758777 ] Hudson commented on HBASE-9388: --- SUCCESS: Integrated in hbase-0.96 #12 (See [https://builds.apache.org/job/hbase-0.96/12/]) HBASE-9388 [replication] ZK Dump prints the raw PBUF for the HLog positions (stack: rev 1520183) * /hbase/branches/0.96/hbase-client/src/main/java/org/apache/hadoop/hbase/zookeeper/ZKUtil.java > [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: Himanshu Vashishtha > Fix For: 0.98.0, 0.96.0 > > Attachments: HBase-9388.patch, HBASE-9388.patch, > ReplicationZnodesDump.png > > > 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] [Commented] (HBASE-9376) TestDistributedLogSplitting creates a MiniCluster rooted at ~/hbase
[
https://issues.apache.org/jira/browse/HBASE-9376?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13758776#comment-13758776
]
Hadoop QA commented on HBASE-9376:
--
{color:green}+1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12601525/hbase-9376.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: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/7046//testReport/
Findbugs warnings:
https://builds.apache.org/job/PreCommit-HBASE-Build/7046//artifact/trunk/patchprocess/newPatchFindbugsWarningshbase-protocol.html
Findbugs warnings:
https://builds.apache.org/job/PreCommit-HBASE-Build/7046//artifact/trunk/patchprocess/newPatchFindbugsWarningshbase-client.html
Findbugs warnings:
https://builds.apache.org/job/PreCommit-HBASE-Build/7046//artifact/trunk/patchprocess/newPatchFindbugsWarningshbase-examples.html
Findbugs warnings:
https://builds.apache.org/job/PreCommit-HBASE-Build/7046//artifact/trunk/patchprocess/newPatchFindbugsWarningshbase-hadoop1-compat.html
Findbugs warnings:
https://builds.apache.org/job/PreCommit-HBASE-Build/7046//artifact/trunk/patchprocess/newPatchFindbugsWarningshbase-prefix-tree.html
Findbugs warnings:
https://builds.apache.org/job/PreCommit-HBASE-Build/7046//artifact/trunk/patchprocess/newPatchFindbugsWarningshbase-common.html
Findbugs warnings:
https://builds.apache.org/job/PreCommit-HBASE-Build/7046//artifact/trunk/patchprocess/newPatchFindbugsWarningshbase-server.html
Findbugs warnings:
https://builds.apache.org/job/PreCommit-HBASE-Build/7046//artifact/trunk/patchprocess/newPatchFindbugsWarningshbase-hadoop-compat.html
Console output:
https://builds.apache.org/job/PreCommit-HBASE-Build/7046//console
This message is automatically generated.
> TestDistributedLogSplitting creates a MiniCluster rooted at ~/hbase
> ---
>
> Key: HBASE-9376
> URL: https://issues.apache.org/jira/browse/HBASE-9376
> Project: HBase
> Issue Type: Test
> Components: test
>Affects Versions: 0.95.2
>Reporter: Nick Dimiduk
>Assignee: Jeffrey Zhong
>Priority: Minor
> Attachments: hbase-9376.patch
>
>
> TestDistributedLogSplitting creates a MiniCluster rooted at ~/hbase. I have a
> machine configured such that my $HOME is NFS mounted, and this combination
> makes for a rather flakey test. Test cluster(s) instantiated by this test
> should instead root out of target (like all the rest).
--
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-9433) OpenRegionHandler uses different assignment timeout
[ https://issues.apache.org/jira/browse/HBASE-9433?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13758753#comment-13758753 ] Hudson commented on HBASE-9433: --- SUCCESS: Integrated in hbase-0.96-hadoop2 #6 (See [https://builds.apache.org/job/hbase-0.96-hadoop2/6/]) HBASE-9433 OpenRegionHandler uses different assignment timeout (jxiang: rev 1520174) * /hbase/branches/0.96/hbase-server/src/main/java/org/apache/hadoop/hbase/master/AssignmentManager.java * /hbase/branches/0.96/hbase-server/src/main/java/org/apache/hadoop/hbase/regionserver/HRegion.java * /hbase/branches/0.96/hbase-server/src/main/java/org/apache/hadoop/hbase/regionserver/handler/OpenRegionHandler.java > OpenRegionHandler uses different assignment timeout > --- > > Key: HBASE-9433 > URL: https://issues.apache.org/jira/browse/HBASE-9433 > Project: HBase > Issue Type: Bug > Components: Region Assignment >Affects Versions: 0.96.0 >Reporter: Jimmy Xiang >Assignee: Jimmy Xiang >Priority: Minor > Fix For: 0.98.0, 0.96.0 > > Attachments: trunk-9433.patch, trunk-9433_rebased.patch, > trunk-9433_v2.patch > > > OpenRegionHandler uses the timeout monitor checking period as the timeout. It > should share the same default as in AssignmentManager. -- 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=13758749#comment-13758749 ] Hudson commented on HBASE-9388: --- SUCCESS: Integrated in hbase-0.96-hadoop2 #6 (See [https://builds.apache.org/job/hbase-0.96-hadoop2/6/]) HBASE-9388 [replication] ZK Dump prints the raw PBUF for the HLog positions (stack: rev 1520183) * /hbase/branches/0.96/hbase-client/src/main/java/org/apache/hadoop/hbase/zookeeper/ZKUtil.java > [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: Himanshu Vashishtha > Fix For: 0.98.0, 0.96.0 > > Attachments: HBase-9388.patch, HBASE-9388.patch, > ReplicationZnodesDump.png > > > 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] [Commented] (HBASE-9439) shell command list shows something not meaningful
[
https://issues.apache.org/jira/browse/HBASE-9439?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13758752#comment-13758752
]
Hudson commented on HBASE-9439:
---
SUCCESS: Integrated in hbase-0.96-hadoop2 #6 (See
[https://builds.apache.org/job/hbase-0.96-hadoop2/6/])
HBASE-9439 shell command list shows something not meaningful (jxiang: rev
1520175)
* /hbase/branches/0.96/hbase-server/src/main/ruby/shell/commands/list.rb
> shell command list shows something not meaningful
> -
>
> Key: HBASE-9439
> URL: https://issues.apache.org/jira/browse/HBASE-9439
> Project: HBase
> Issue Type: Bug
> Components: shell
>Reporter: Jimmy Xiang
>Assignee: Jimmy Xiang
>Priority: Minor
> Fix For: 0.98.0, 0.96.0
>
> Attachments: trunk-9439.patch
>
>
> Here is a sample output:
> {noformat}
> hbase(main):004:0> list
> TABLE
>
>
> usertable
>
>
> 1 row(s) in 0.3240 seconds
> => #<#:0x5eb8f6d>
> {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-9435) Fix jersey serialization/deserialization of json objects
[ https://issues.apache.org/jira/browse/HBASE-9435?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13758751#comment-13758751 ] Hudson commented on HBASE-9435: --- SUCCESS: Integrated in hbase-0.96-hadoop2 #6 (See [https://builds.apache.org/job/hbase-0.96-hadoop2/6/]) HBASE-9435 Fix jersey serialization/deserialization of json objects (stack: rev 1520178) * /hbase/branches/0.96/hbase-server/src/main/java/org/apache/hadoop/hbase/rest/client/RemoteHTable.java * /hbase/branches/0.96/hbase-server/src/main/java/org/apache/hadoop/hbase/rest/model/CellModel.java * /hbase/branches/0.96/hbase-server/src/main/java/org/apache/hadoop/hbase/rest/model/CellSetModel.java * /hbase/branches/0.96/hbase-server/src/main/java/org/apache/hadoop/hbase/rest/model/ColumnSchemaModel.java * /hbase/branches/0.96/hbase-server/src/main/java/org/apache/hadoop/hbase/rest/model/RowModel.java * /hbase/branches/0.96/hbase-server/src/main/java/org/apache/hadoop/hbase/rest/model/StorageClusterVersionModel.java * /hbase/branches/0.96/hbase-server/src/main/java/org/apache/hadoop/hbase/rest/model/TableSchemaModel.java * /hbase/branches/0.96/hbase-server/src/main/java/org/apache/hadoop/hbase/rest/provider/JacksonProvider.java * /hbase/branches/0.96/hbase-server/src/test/java/org/apache/hadoop/hbase/rest/TestSchemaResource.java * /hbase/branches/0.96/hbase-server/src/test/java/org/apache/hadoop/hbase/rest/TestStatusResource.java * /hbase/branches/0.96/hbase-server/src/test/java/org/apache/hadoop/hbase/rest/model/TestCellModel.java * /hbase/branches/0.96/hbase-server/src/test/java/org/apache/hadoop/hbase/rest/model/TestCellSetModel.java * /hbase/branches/0.96/hbase-server/src/test/java/org/apache/hadoop/hbase/rest/model/TestColumnSchemaModel.java * /hbase/branches/0.96/hbase-server/src/test/java/org/apache/hadoop/hbase/rest/model/TestModelBase.java * /hbase/branches/0.96/hbase-server/src/test/java/org/apache/hadoop/hbase/rest/model/TestRowModel.java * /hbase/branches/0.96/hbase-server/src/test/java/org/apache/hadoop/hbase/rest/model/TestScannerModel.java * /hbase/branches/0.96/hbase-server/src/test/java/org/apache/hadoop/hbase/rest/model/TestStorageClusterStatusModel.java * /hbase/branches/0.96/hbase-server/src/test/java/org/apache/hadoop/hbase/rest/model/TestStorageClusterVersionModel.java * /hbase/branches/0.96/hbase-server/src/test/java/org/apache/hadoop/hbase/rest/model/TestTableInfoModel.java * /hbase/branches/0.96/hbase-server/src/test/java/org/apache/hadoop/hbase/rest/model/TestTableListModel.java * /hbase/branches/0.96/hbase-server/src/test/java/org/apache/hadoop/hbase/rest/model/TestTableRegionModel.java * /hbase/branches/0.96/hbase-server/src/test/java/org/apache/hadoop/hbase/rest/model/TestTableSchemaModel.java * /hbase/branches/0.96/hbase-server/src/test/java/org/apache/hadoop/hbase/rest/model/TestVersionModel.java > Fix jersey serialization/deserialization of json objects > > > Key: HBASE-9435 > URL: https://issues.apache.org/jira/browse/HBASE-9435 > Project: HBase > Issue Type: Bug > Components: REST >Reporter: Francis Liu >Assignee: Francis Liu > Fix For: 0.98.0, 0.96.1 > > Attachments: HBASE-9435.patch, HBASE-9435.patch > > > Stargate uses the default json marshaller/unmarshaller in natural mode. In > this mode the unmarshaller has trouble unmarshalling json instances. > This patch fixes this issue by using jackson as the marshaller/unmarshaller > instead. > I've also updated all the model unit tests to test json > serialization/deserialization. Backwards compatibilty can be verified by > modify the test base class to use the original marshaller/unmarshaller and > see that model tests pass. > The patch is backward compatible except for StorageClusterStatusModel, which > is broken anyway. It only shows one node in the liveNodes field. -- 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-9259) Update hadoop versions grid in refguide adding hadoop-2.1.x and a note on hadoop-2.0.x versions
[ https://issues.apache.org/jira/browse/HBASE-9259?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13758750#comment-13758750 ] Hudson commented on HBASE-9259: --- SUCCESS: Integrated in hbase-0.96-hadoop2 #6 (See [https://builds.apache.org/job/hbase-0.96-hadoop2/6/]) HBASE-9259 Update hadoop versions grid in refguide adding hadoop-2.1.x and a note on hadoop-2.0.x versions (stack: rev 1520186) * /hbase/branches/0.96/src/main/docbkx/configuration.xml * /hbase/branches/0.96/src/main/docbkx/developer.xml * /hbase/branches/0.96/src/main/docbkx/getting_started.xml * /hbase/branches/0.96/src/main/docbkx/preface.xml * /hbase/branches/0.96/src/main/docbkx/upgrading.xml > Update hadoop versions grid in refguide adding hadoop-2.1.x and a note on > hadoop-2.0.x versions > --- > > Key: HBASE-9259 > URL: https://issues.apache.org/jira/browse/HBASE-9259 > Project: HBase > Issue Type: Sub-task > Components: documentation >Reporter: stack >Assignee: stack > Fix For: 0.98.0, 0.96.0 > > Attachments: 9259.txt > > > Need to update our hadoop versions grid. Add notes on hadoop-2.1 and > hadoop-2.0 (we do the former, not the latter) -- 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=13758741#comment-13758741 ] Hudson commented on HBASE-9388: --- SUCCESS: Integrated in HBase-TRUNK #4468 (See [https://builds.apache.org/job/HBase-TRUNK/4468/]) HBASE-9388 [replication] ZK Dump prints the raw PBUF for the HLog positions (stack: rev 1520184) * /hbase/trunk/hbase-client/src/main/java/org/apache/hadoop/hbase/zookeeper/ZKUtil.java > [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: Himanshu Vashishtha > Fix For: 0.98.0, 0.96.0 > > Attachments: HBase-9388.patch, HBASE-9388.patch, > ReplicationZnodesDump.png > > > 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] [Commented] (HBASE-9435) Fix jersey serialization/deserialization of json objects
[ https://issues.apache.org/jira/browse/HBASE-9435?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13758743#comment-13758743 ] Hudson commented on HBASE-9435: --- SUCCESS: Integrated in HBase-TRUNK #4468 (See [https://builds.apache.org/job/HBase-TRUNK/4468/]) HBASE-9435 Fix jersey serialization/deserialization of json objects (stack: rev 1520179) * /hbase/trunk/hbase-server/src/main/java/org/apache/hadoop/hbase/rest/client/RemoteHTable.java * /hbase/trunk/hbase-server/src/main/java/org/apache/hadoop/hbase/rest/model/CellModel.java * /hbase/trunk/hbase-server/src/main/java/org/apache/hadoop/hbase/rest/model/CellSetModel.java * /hbase/trunk/hbase-server/src/main/java/org/apache/hadoop/hbase/rest/model/ColumnSchemaModel.java * /hbase/trunk/hbase-server/src/main/java/org/apache/hadoop/hbase/rest/model/RowModel.java * /hbase/trunk/hbase-server/src/main/java/org/apache/hadoop/hbase/rest/model/StorageClusterVersionModel.java * /hbase/trunk/hbase-server/src/main/java/org/apache/hadoop/hbase/rest/model/TableSchemaModel.java * /hbase/trunk/hbase-server/src/main/java/org/apache/hadoop/hbase/rest/provider/JacksonProvider.java * /hbase/trunk/hbase-server/src/test/java/org/apache/hadoop/hbase/rest/TestSchemaResource.java * /hbase/trunk/hbase-server/src/test/java/org/apache/hadoop/hbase/rest/TestStatusResource.java * /hbase/trunk/hbase-server/src/test/java/org/apache/hadoop/hbase/rest/model/TestCellModel.java * /hbase/trunk/hbase-server/src/test/java/org/apache/hadoop/hbase/rest/model/TestCellSetModel.java * /hbase/trunk/hbase-server/src/test/java/org/apache/hadoop/hbase/rest/model/TestColumnSchemaModel.java * /hbase/trunk/hbase-server/src/test/java/org/apache/hadoop/hbase/rest/model/TestModelBase.java * /hbase/trunk/hbase-server/src/test/java/org/apache/hadoop/hbase/rest/model/TestRowModel.java * /hbase/trunk/hbase-server/src/test/java/org/apache/hadoop/hbase/rest/model/TestScannerModel.java * /hbase/trunk/hbase-server/src/test/java/org/apache/hadoop/hbase/rest/model/TestStorageClusterStatusModel.java * /hbase/trunk/hbase-server/src/test/java/org/apache/hadoop/hbase/rest/model/TestStorageClusterVersionModel.java * /hbase/trunk/hbase-server/src/test/java/org/apache/hadoop/hbase/rest/model/TestTableInfoModel.java * /hbase/trunk/hbase-server/src/test/java/org/apache/hadoop/hbase/rest/model/TestTableListModel.java * /hbase/trunk/hbase-server/src/test/java/org/apache/hadoop/hbase/rest/model/TestTableRegionModel.java * /hbase/trunk/hbase-server/src/test/java/org/apache/hadoop/hbase/rest/model/TestTableSchemaModel.java * /hbase/trunk/hbase-server/src/test/java/org/apache/hadoop/hbase/rest/model/TestVersionModel.java > Fix jersey serialization/deserialization of json objects > > > Key: HBASE-9435 > URL: https://issues.apache.org/jira/browse/HBASE-9435 > Project: HBase > Issue Type: Bug > Components: REST >Reporter: Francis Liu >Assignee: Francis Liu > Fix For: 0.98.0, 0.96.1 > > Attachments: HBASE-9435.patch, HBASE-9435.patch > > > Stargate uses the default json marshaller/unmarshaller in natural mode. In > this mode the unmarshaller has trouble unmarshalling json instances. > This patch fixes this issue by using jackson as the marshaller/unmarshaller > instead. > I've also updated all the model unit tests to test json > serialization/deserialization. Backwards compatibilty can be verified by > modify the test base class to use the original marshaller/unmarshaller and > see that model tests pass. > The patch is backward compatible except for StorageClusterStatusModel, which > is broken anyway. It only shows one node in the liveNodes field. -- 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-9259) Update hadoop versions grid in refguide adding hadoop-2.1.x and a note on hadoop-2.0.x versions
[ https://issues.apache.org/jira/browse/HBASE-9259?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13758742#comment-13758742 ] Hudson commented on HBASE-9259: --- SUCCESS: Integrated in HBase-TRUNK #4468 (See [https://builds.apache.org/job/HBase-TRUNK/4468/]) HBASE-9259 Update hadoop versions grid in refguide adding hadoop-2.1.x and a note on hadoop-2.0.x versions (stack: rev 1520185) * /hbase/trunk/src/main/docbkx/configuration.xml * /hbase/trunk/src/main/docbkx/getting_started.xml * /hbase/trunk/src/main/docbkx/preface.xml > Update hadoop versions grid in refguide adding hadoop-2.1.x and a note on > hadoop-2.0.x versions > --- > > Key: HBASE-9259 > URL: https://issues.apache.org/jira/browse/HBASE-9259 > Project: HBase > Issue Type: Sub-task > Components: documentation >Reporter: stack >Assignee: stack > Fix For: 0.98.0, 0.96.0 > > Attachments: 9259.txt > > > Need to update our hadoop versions grid. Add notes on hadoop-2.1 and > hadoop-2.0 (we do the former, not the latter) -- 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-9439) shell command list shows something not meaningful
[
https://issues.apache.org/jira/browse/HBASE-9439?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13758744#comment-13758744
]
Hudson commented on HBASE-9439:
---
SUCCESS: Integrated in HBase-TRUNK #4468 (See
[https://builds.apache.org/job/HBase-TRUNK/4468/])
HBASE-9439 shell command list shows something not meaningful (jxiang: rev
1520176)
* /hbase/trunk/hbase-server/src/main/ruby/shell/commands/list.rb
> shell command list shows something not meaningful
> -
>
> Key: HBASE-9439
> URL: https://issues.apache.org/jira/browse/HBASE-9439
> Project: HBase
> Issue Type: Bug
> Components: shell
>Reporter: Jimmy Xiang
>Assignee: Jimmy Xiang
>Priority: Minor
> Fix For: 0.98.0, 0.96.0
>
> Attachments: trunk-9439.patch
>
>
> Here is a sample output:
> {noformat}
> hbase(main):004:0> list
> TABLE
>
>
> usertable
>
>
> 1 row(s) in 0.3240 seconds
> => #<#:0x5eb8f6d>
> {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-9433) OpenRegionHandler uses different assignment timeout
[ https://issues.apache.org/jira/browse/HBASE-9433?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13758745#comment-13758745 ] Hudson commented on HBASE-9433: --- SUCCESS: Integrated in HBase-TRUNK #4468 (See [https://builds.apache.org/job/HBase-TRUNK/4468/]) HBASE-9433 OpenRegionHandler uses different assignment timeout (jxiang: rev 1520173) * /hbase/trunk/hbase-server/src/main/java/org/apache/hadoop/hbase/master/AssignmentManager.java * /hbase/trunk/hbase-server/src/main/java/org/apache/hadoop/hbase/regionserver/HRegion.java * /hbase/trunk/hbase-server/src/main/java/org/apache/hadoop/hbase/regionserver/handler/OpenRegionHandler.java > OpenRegionHandler uses different assignment timeout > --- > > Key: HBASE-9433 > URL: https://issues.apache.org/jira/browse/HBASE-9433 > Project: HBase > Issue Type: Bug > Components: Region Assignment >Affects Versions: 0.96.0 >Reporter: Jimmy Xiang >Assignee: Jimmy Xiang >Priority: Minor > Fix For: 0.98.0, 0.96.0 > > Attachments: trunk-9433.patch, trunk-9433_rebased.patch, > trunk-9433_v2.patch > > > OpenRegionHandler uses the timeout monitor checking period as the timeout. It > should share the same default as in AssignmentManager. -- 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-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=13758731#comment-13758731
]
Hadoop QA commented on HBASE-9390:
--
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12601532/hbase-9390.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 12 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:red}-1 javadoc{color}. The javadoc tool appears to have generated 1
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/7045//testReport/
Findbugs warnings:
https://builds.apache.org/job/PreCommit-HBASE-Build/7045//artifact/trunk/patchprocess/newPatchFindbugsWarningshbase-prefix-tree.html
Findbugs warnings:
https://builds.apache.org/job/PreCommit-HBASE-Build/7045//artifact/trunk/patchprocess/newPatchFindbugsWarningshbase-client.html
Findbugs warnings:
https://builds.apache.org/job/PreCommit-HBASE-Build/7045//artifact/trunk/patchprocess/newPatchFindbugsWarningshbase-common.html
Findbugs warnings:
https://builds.apache.org/job/PreCommit-HBASE-Build/7045//artifact/trunk/patchprocess/newPatchFindbugsWarningshbase-protocol.html
Findbugs warnings:
https://builds.apache.org/job/PreCommit-HBASE-Build/7045//artifact/trunk/patchprocess/newPatchFindbugsWarningshbase-server.html
Findbugs warnings:
https://builds.apache.org/job/PreCommit-HBASE-Build/7045//artifact/trunk/patchprocess/newPatchFindbugsWarningshbase-hadoop1-compat.html
Findbugs warnings:
https://builds.apache.org/job/PreCommit-HBASE-Build/7045//artifact/trunk/patchprocess/newPatchFindbugsWarningshbase-examples.html
Findbugs warnings:
https://builds.apache.org/job/PreCommit-HBASE-Build/7045//artifact/trunk/patchprocess/newPatchFindbugsWarningshbase-hadoop-compat.html
Console output:
https://builds.apache.org/job/PreCommit-HBASE-Build/7045//console
This message is automatically generated.
> 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
>Assignee: Jeffrey Zhong
> Attachments: copro.patch, hbase-9390.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] [Commented] (HBASE-9153) Create a deprecation policy enforcement check
[
https://issues.apache.org/jira/browse/HBASE-9153?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13758730#comment-13758730
]
Hadoop QA commented on HBASE-9153:
--
{color:green}+1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12601534/HBASE-9153-v3.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 5 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: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/7044//testReport/
Findbugs warnings:
https://builds.apache.org/job/PreCommit-HBASE-Build/7044//artifact/trunk/patchprocess/newPatchFindbugsWarningshbase-protocol.html
Findbugs warnings:
https://builds.apache.org/job/PreCommit-HBASE-Build/7044//artifact/trunk/patchprocess/newPatchFindbugsWarningshbase-client.html
Findbugs warnings:
https://builds.apache.org/job/PreCommit-HBASE-Build/7044//artifact/trunk/patchprocess/newPatchFindbugsWarningshbase-examples.html
Findbugs warnings:
https://builds.apache.org/job/PreCommit-HBASE-Build/7044//artifact/trunk/patchprocess/newPatchFindbugsWarningshbase-hadoop1-compat.html
Findbugs warnings:
https://builds.apache.org/job/PreCommit-HBASE-Build/7044//artifact/trunk/patchprocess/newPatchFindbugsWarningshbase-prefix-tree.html
Findbugs warnings:
https://builds.apache.org/job/PreCommit-HBASE-Build/7044//artifact/trunk/patchprocess/newPatchFindbugsWarningshbase-common.html
Findbugs warnings:
https://builds.apache.org/job/PreCommit-HBASE-Build/7044//artifact/trunk/patchprocess/newPatchFindbugsWarningshbase-server.html
Findbugs warnings:
https://builds.apache.org/job/PreCommit-HBASE-Build/7044//artifact/trunk/patchprocess/newPatchFindbugsWarningshbase-hadoop-compat.html
Console output:
https://builds.apache.org/job/PreCommit-HBASE-Build/7044//console
This message is automatically generated.
> Create a deprecation policy enforcement check
> -
>
> Key: HBASE-9153
> URL: https://issues.apache.org/jira/browse/HBASE-9153
> Project: HBase
> Issue Type: Task
>Reporter: Jonathan Hsieh
> Attachments: HBASE-9153-v1.patch, HBASE-9153-v3.patch
>
>
> We've had a few issues now where we've removed API's without deprecating or
> deprecating in the late release. (HBASE-9142, HBASE-9093) We should just
> have a tool that enforces our api deprecation policy as a release time check
> or as a precommit check.
--
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-9304) [0.92] TestDrainingServer fails occasionally
[
https://issues.apache.org/jira/browse/HBASE-9304?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13758710#comment-13758710
]
Hudson commented on HBASE-9304:
---
FAILURE: Integrated in HBase-0.92-security #150 (See
[https://builds.apache.org/job/HBase-0.92-security/150/])
HBASE-9304. [0.92] TestDrainingServer fails occasionally (apurtell: rev 1517431)
*
/hbase/branches/0.92/src/test/java/org/apache/hadoop/hbase/TestDrainingServer.java
> [0.92] TestDrainingServer fails occasionally
>
>
> Key: HBASE-9304
> URL: https://issues.apache.org/jira/browse/HBASE-9304
> Project: HBase
> Issue Type: Bug
>Affects Versions: 0.92.3
>Reporter: Andrew Purtell
>Assignee: Andrew Purtell
>Priority: Minor
> Fix For: 0.92.3
>
> Attachments: 9304.patch
>
>
> The error is the same in every case:
> {noformat}
> junit.framework.AssertionFailedError
> at junit.framework.Assert.fail(Assert.java:48)
> at junit.framework.Assert.assertTrue(Assert.java:20)
> at junit.framework.Assert.assertFalse(Assert.java:34)
> at junit.framework.Assert.assertFalse(Assert.java:41)
> at
> org.apache.hadoop.hbase.TestDrainingServer.setUpBeforeClass(TestDrainingServer.java:78)
> {noformat}
> This is a check at test startup that every regionserver has an assignment.
> Looks like sometimes it takes a long time for the cluster to come up - there
> are 5 RSes started - and not all get region assignments. Probably a test only
> fix here.
--
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-9216) [0.92] TestReplication.queueFailover fails often
[
https://issues.apache.org/jira/browse/HBASE-9216?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13758708#comment-13758708
]
Hudson commented on HBASE-9216:
---
FAILURE: Integrated in HBase-0.92-security #150 (See
[https://builds.apache.org/job/HBase-0.92-security/150/])
HBASE-9216. [0.92] TestReplication.queueFailover fails often (apurtell: rev
1515971)
*
/hbase/branches/0.92/src/test/java/org/apache/hadoop/hbase/replication/TestReplication.java
> [0.92] TestReplication.queueFailover fails often
>
>
> Key: HBASE-9216
> URL: https://issues.apache.org/jira/browse/HBASE-9216
> Project: HBase
> Issue Type: Bug
>Affects Versions: 0.92.3
>Reporter: Andrew Purtell
>Assignee: Andrew Purtell
>Priority: Minor
> Fix For: 0.92.3
>
> Attachments: 9216.patch
>
>
> Failure trace:
> {noformat}
> java.lang.AssertionError: Waited too much time for queueFailover replication.
> Waited 46463ms.
> at org.junit.Assert.fail(Assert.java:93)
> at
> org.apache.hadoop.hbase.replication.TestReplication.queueFailover(TestReplication.java:666)
> {noformat}
> Logs show the test fails to make progress as the replication source log,
> after an initial few opens/replications/reports/advances, stops increasing in
> size, this sequence until timeout:
> {noformat}
> EventThread.replicationSource,2] regionserver.ReplicationSource(544): Opening
> log for replication
> ip-10-198-0-134.us-west-1.compute.internal%2C54449%2C1376480042448.1376480134578
> at 18587
> 2013-08-14 11:35:39,568 DEBUG
> [RegionServer:0;ip-10-198-0-134.us-west-1.compute.internal,54449,1376480042448-EventThread.replicationSource,2]
> regionserver.ReplicationSource(489): currentNbOperations:16416 and
> seenEntries:0 and size: 0
> 2013-08-14 11:35:39,568 DEBUG
> [RegionServer:0;ip-10-198-0-134.us-west-1.compute.internal,54449,1376480042448-EventThread.replicationSource,2]
> regionserver.ReplicationSource(618): Nothing to replicate, sleeping 100
> times 10
> [...]
> 2013-08-14 11:35:45,205 INFO [Thread-1125] replication.TestReplication(678):
> Only got 16607 rows instead of 17576 current i=-1
> [...]
> {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-8207) Replication could have data loss when machine name contains hyphen "-"
[
https://issues.apache.org/jira/browse/HBASE-8207?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13758704#comment-13758704
]
Hudson commented on HBASE-8207:
---
FAILURE: Integrated in HBase-0.92-security #150 (See
[https://builds.apache.org/job/HBase-0.92-security/150/])
HBASE-9154. [0.92] Backport HBASE-8207 Replication could have data loss when
machine name contains hyphen - (Jeffrey) (apurtell: rev 1511424)
*
/hbase/branches/0.92/src/main/java/org/apache/hadoop/hbase/replication/ReplicationZookeeper.java
*
/hbase/branches/0.92/src/main/java/org/apache/hadoop/hbase/replication/regionserver/ReplicationSource.java
*
/hbase/branches/0.92/src/test/java/org/apache/hadoop/hbase/replication/TestMasterReplication.java
*
/hbase/branches/0.92/src/test/java/org/apache/hadoop/hbase/replication/TestMultiSlaveReplication.java
*
/hbase/branches/0.92/src/test/java/org/apache/hadoop/hbase/replication/TestReplication.java
> Replication could have data loss when machine name contains hyphen "-"
> --
>
> Key: HBASE-8207
> URL: https://issues.apache.org/jira/browse/HBASE-8207
> Project: HBase
> Issue Type: Bug
> Components: Replication
>Affects Versions: 0.94.6, 0.95.0
>Reporter: Jeffrey Zhong
>Assignee: Jeffrey Zhong
>Priority: Critical
> Fix For: 0.98.0, 0.94.7, 0.95.0
>
> Attachments: 8207-trunk-addendum.txt, 8207_v3.patch, failed.txt,
> hbase-8207-0.94-v1.patch, hbase-8207.patch, hbase-8207_v1.patch,
> hbase-8207_v2.patch, hbase-8207_v2.patch, HBASE-8212-94.patch
>
>
> In the recent test case TestReplication* failures, I'm finally able to find
> the cause(or one of causes) for its intermittent failures.
> When a machine name contains "-", it breaks the function
> ReplicationSource.checkIfQueueRecovered. It causes the following issue:
> deadRegionServers list is way off so that replication doesn't wait for log
> splitting finish for a wal file and move on to the next one(data loss)
> You can see that replication use those weird paths constructed from
> deadRegionServers to check a file existence
> {code}
> 2013-03-26 21:26:51,385 INFO
> [ReplicationExecutor-0.replicationSource,2-ip-10-197-0-156.us-west-1.compute.internal,52170,1364333181125]
> regionserver.ReplicationSource(524): Possible location
> hdfs://localhost:52882/user/ec2-user/hbase/.logs/1.compute.internal,52170,1364333181125/ip-10-197-0-156.us-west-1.compute.internal%252C52170%252C1364333181125.1364333199540
> 2013-03-26 21:26:51,386 INFO
> [ReplicationExecutor-0.replicationSource,2-ip-10-197-0-156.us-west-1.compute.internal,52170,1364333181125]
> regionserver.ReplicationSource(524): Possible location
> hdfs://localhost:52882/user/ec2-user/hbase/.logs/1.compute.internal,52170,1364333181125-splitting/ip-10-197-0-156.us-west-1.compute.internal%252C52170%252C1364333181125.1364333199540
> 2013-03-26 21:26:51,387 INFO
> [ReplicationExecutor-0.replicationSource,2-ip-10-197-0-156.us-west-1.compute.internal,52170,1364333181125]
> regionserver.ReplicationSource(524): Possible location
> hdfs://localhost:52882/user/ec2-user/hbase/.logs/west/ip-10-197-0-156.us-west-1.compute.internal%252C52170%252C1364333181125.1364333199540
> 2013-03-26 21:26:51,389 INFO
> [ReplicationExecutor-0.replicationSource,2-ip-10-197-0-156.us-west-1.compute.internal,52170,1364333181125]
> regionserver.ReplicationSource(524): Possible location
> hdfs://localhost:52882/user/ec2-user/hbase/.logs/west-splitting/ip-10-197-0-156.us-west-1.compute.internal%252C52170%252C1364333181125.1364333199540
> 2013-03-26 21:26:51,391 INFO
> [ReplicationExecutor-0.replicationSource,2-ip-10-197-0-156.us-west-1.compute.internal,52170,1364333181125]
> regionserver.ReplicationSource(524): Possible location
> hdfs://localhost:52882/user/ec2-user/hbase/.logs/156.us/ip-10-197-0-156.us-west-1.compute.internal%252C52170%252C1364333181125.1364333199540
> 2013-03-26 21:26:51,394 INFO
> [ReplicationExecutor-0.replicationSource,2-ip-10-197-0-156.us-west-1.compute.internal,52170,1364333181125]
> regionserver.ReplicationSource(524): Possible location
> hdfs://localhost:52882/user/ec2-user/hbase/.logs/156.us-splitting/ip-10-197-0-156.us-west-1.compute.internal%252C52170%252C1364333181125.1364333199540
> 2013-03-26 21:26:51,396 INFO
> [ReplicationExecutor-0.replicationSource,2-ip-10-197-0-156.us-west-1.compute.internal,52170,1364333181125]
> regionserver.ReplicationSource(524): Possible location
> hdfs://localhost:52882/user/ec2-user/hbase/.logs/0/ip-10-197-0-156.us-west-1.compute.internal%252C52170%252C1364333181125.1364333199540
> 2013-03-26 21:26:51,398 INFO
> [ReplicationExecutor-0.replicationSource,2-ip-10-197-0-156.us-west-1.compute.internal,52170,1364333181125]
> regionserver.ReplicationSource(524):
[jira] [Commented] (HBASE-9349) [0.92] NPE in HMaster during shutdown
[
https://issues.apache.org/jira/browse/HBASE-9349?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13758707#comment-13758707
]
Hudson commented on HBASE-9349:
---
FAILURE: Integrated in HBase-0.92-security #150 (See
[https://builds.apache.org/job/HBase-0.92-security/150/])
HBASE-9349. [0.92] NPE in HMaster during shutdown (apurtell: rev 1517752)
* /hbase/branches/0.92/src/main/java/org/apache/hadoop/hbase/master/HMaster.java
> [0.92] NPE in HMaster during shutdown
> -
>
> Key: HBASE-9349
> URL: https://issues.apache.org/jira/browse/HBASE-9349
> Project: HBase
> Issue Type: Bug
>Affects Versions: 0.92.3
>Reporter: Andrew Purtell
>Assignee: Andrew Purtell
>Priority: Minor
> Fix For: 0.92.3
>
> Attachments: 9349.patch
>
>
> Found this in a run of TestWALObserver:
> {noformat}
> java.lang.NullPointerException
> at org.apache.hadoop.hbase.master.HMaster.shutdown(HMaster.java:1510)
> at
> org.apache.hadoop.hbase.util.JVMClusterUtil.shutdown(JVMClusterUtil.java:226)
> at
> org.apache.hadoop.hbase.LocalHBaseCluster.shutdown(LocalHBaseCluster.java:424)
> at
> org.apache.hadoop.hbase.MiniHBaseCluster.shutdown(MiniHBaseCluster.java:417)
> at
> org.apache.hadoop.hbase.HBaseTestingUtility.shutdownMiniHBaseCluster(HBaseTestingUtility.java:607)
> at
> org.apache.hadoop.hbase.HBaseTestingUtility.shutdownMiniCluster(HBaseTestingUtility.java:583)
> at
> org.apache.hadoop.hbase.coprocessor.TestWALObserver.teardownAfterClass(TestWALObserver.java:111)
> {noformat}
> if the active master in the minicluster is terminated before fully
> initialized. Needs null checks in HMaster#shutdown.
--
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-9212) [0.92] TestMasterObserver fails occasionally
[
https://issues.apache.org/jira/browse/HBASE-9212?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13758706#comment-13758706
]
Hudson commented on HBASE-9212:
---
FAILURE: Integrated in HBase-0.92-security #150 (See
[https://builds.apache.org/job/HBase-0.92-security/150/])
HBASE-9212. [0.92] TestMasterObserver fails occasionally (apurtell: rev 1515706)
*
/hbase/branches/0.92/src/main/java/org/apache/hadoop/hbase/util/FSTableDescriptors.java
*
/hbase/branches/0.92/src/test/java/org/apache/hadoop/hbase/coprocessor/TestMasterObserver.java
*
/hbase/branches/0.92/src/test/java/org/apache/hadoop/hbase/util/TestFSTableDescriptors.java
> [0.92] TestMasterObserver fails occasionally
>
>
> Key: HBASE-9212
> URL: https://issues.apache.org/jira/browse/HBASE-9212
> Project: HBase
> Issue Type: Bug
> Components: test
>Affects Versions: 0.92.3
>Reporter: Andrew Purtell
>Assignee: Andrew Purtell
>Priority: Minor
> Fix For: 0.92.3
>
> Attachments: 9212.fix.patch, 9212.patch, detail_1.txt, detail_2.txt
>
>
> Here:
> {noformat}
> org.apache.hadoop.hbase.TableExistsException:
> org.apache.hadoop.hbase.TableExistsException: observed_table
> at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)
> at
> sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:39)
> at
> sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:27)
> at java.lang.reflect.Constructor.newInstance(Constructor.java:513)
> at
> org.apache.hadoop.ipc.RemoteException.instantiateException(RemoteException.java:95)
> at
> org.apache.hadoop.ipc.RemoteException.unwrapRemoteException(RemoteException.java:79)
> at
> org.apache.hadoop.hbase.client.HBaseAdmin.createTableAsync(HBaseAdmin.java:474)
> at
> org.apache.hadoop.hbase.client.HBaseAdmin.createTable(HBaseAdmin.java:365)
> at
> org.apache.hadoop.hbase.client.HBaseAdmin.createTable(HBaseAdmin.java:303)
> at
> org.apache.hadoop.hbase.HBaseTestingUtility.createTable(HBaseTestingUtility.java:700)
> at
> org.apache.hadoop.hbase.HBaseTestingUtility.createTable(HBaseTestingUtility.java:680)
> at
> org.apache.hadoop.hbase.HBaseTestingUtility.createTable(HBaseTestingUtility.java:668)
> at
> org.apache.hadoop.hbase.coprocessor.TestMasterObserver.testRegionTransitionOperations(TestMasterObserver.java:648)
> {noformat}
> and here also:
> {noformat}
> org.apache.hadoop.hbase.InvalidFamilyOperationException:
> org.apache.hadoop.hbase.InvalidFamilyOperationException: Column family 'fam2'
> does not exist
> at
> org.apache.hadoop.hbase.master.handler.TableEventHandler.hasColumnFamily(TableEventHandler.java:182)
> at
> org.apache.hadoop.hbase.master.handler.TableDeleteFamilyHandler.(TableDeleteFamilyHandler.java:42)
> at
> org.apache.hadoop.hbase.master.HMaster.deleteColumn(HMaster.java:1184)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
> at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
> at java.lang.reflect.Method.invoke(Method.java:597)
> at
> org.apache.hadoop.hbase.ipc.WritableRpcEngine$Server.call(WritableRpcEngine.java:364)
> at
> org.apache.hadoop.hbase.ipc.HBaseServer$Handler.run(HBaseServer.java:1344)
> at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)
> at
> sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:39)
> at
> sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:27)
> at java.lang.reflect.Constructor.newInstance(Constructor.java:513)
> at
> org.apache.hadoop.hbase.RemoteExceptionHandler.decodeRemoteException(RemoteExceptionHandler.java:96)
> at
> org.apache.hadoop.hbase.client.HBaseAdmin.deleteColumn(HBaseAdmin.java:984)
> at
> org.apache.hadoop.hbase.coprocessor.TestMasterObserver.testTableOperations(TestMasterObserver.java:621)
> {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-9306) [0.92] TestAdmin.testCreateBadTables fails occasionally
[
https://issues.apache.org/jira/browse/HBASE-9306?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13758709#comment-13758709
]
Hudson commented on HBASE-9306:
---
FAILURE: Integrated in HBase-0.92-security #150 (See
[https://builds.apache.org/job/HBase-0.92-security/150/])
HBASE-9306. [0.92] TestAdmin.testCreateBadTables fails occasionally (apurtell:
rev 1517429)
*
/hbase/branches/0.92/src/test/java/org/apache/hadoop/hbase/client/TestAdmin.java
> [0.92] TestAdmin.testCreateBadTables fails occasionally
> ---
>
> Key: HBASE-9306
> URL: https://issues.apache.org/jira/browse/HBASE-9306
> Project: HBase
> Issue Type: Bug
>Affects Versions: 0.92.3
>Reporter: Andrew Purtell
>Assignee: Andrew Purtell
>Priority: Minor
> Fix For: 0.92.3
>
> Attachments: 9306.patch
>
>
> A typical failure:
> {noformat}
> java.lang.AssertionError: expected:<9> but was:<8>
> at org.junit.Assert.fail(Assert.java:93)
> at org.junit.Assert.failNotEquals(Assert.java:647)
> at org.junit.Assert.assertEquals(Assert.java:128)
> at org.junit.Assert.assertEquals(Assert.java:472)
> at org.junit.Assert.assertEquals(Assert.java:456)
> at
> org.apache.hadoop.hbase.client.TestAdmin.testCreateBadTables(TestAdmin.java:996)
> {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-9209) [0.92] TestSplitTransactionOnCluster occasionally fails
[ https://issues.apache.org/jira/browse/HBASE-9209?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13758711#comment-13758711 ] Hudson commented on HBASE-9209: --- FAILURE: Integrated in HBase-0.92-security #150 (See [https://builds.apache.org/job/HBase-0.92-security/150/]) Amend HBASE-9209. [0.92] TestSplitTransactionOnCluster occasionally fails; Backport additional waits and state checks from 0.94 branch (apurtell: rev 1514160) * /hbase/branches/0.92/src/test/java/org/apache/hadoop/hbase/regionserver/TestSplitTransactionOnCluster.java HBASE-9209. [0.92] TestSplitTransactionOnCluster#testShutdownFixupWhenDaughterHasSplit occasionally fails (apurtell: rev 1513699) * /hbase/branches/0.92/src/test/java/org/apache/hadoop/hbase/regionserver/TestSplitTransactionOnCluster.java > [0.92] TestSplitTransactionOnCluster occasionally fails > --- > > Key: HBASE-9209 > URL: https://issues.apache.org/jira/browse/HBASE-9209 > Project: HBase > Issue Type: Bug >Affects Versions: 0.92.3 >Reporter: Andrew Purtell >Assignee: Andrew Purtell >Priority: Minor > Fix For: 0.92.3 > > Attachments: 9209.patch, 9209.patch, 9209.patch > > > There are some issues with this test fixed in later branches. It doesn't seem > pressing to backport any of that work. Will resolve by disabling the test in > the 0.92 branch. Please indicate if you prefer an alternate approach. -- 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-9154) [0.92] Backport HBASE-8207 to fix replication test failures
[ https://issues.apache.org/jira/browse/HBASE-9154?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13758705#comment-13758705 ] Hudson commented on HBASE-9154: --- FAILURE: Integrated in HBase-0.92-security #150 (See [https://builds.apache.org/job/HBase-0.92-security/150/]) HBASE-9154. [0.92] Backport HBASE-8207 Replication could have data loss when machine name contains hyphen - (Jeffrey) (apurtell: rev 1511424) * /hbase/branches/0.92/src/main/java/org/apache/hadoop/hbase/replication/ReplicationZookeeper.java * /hbase/branches/0.92/src/main/java/org/apache/hadoop/hbase/replication/regionserver/ReplicationSource.java * /hbase/branches/0.92/src/test/java/org/apache/hadoop/hbase/replication/TestMasterReplication.java * /hbase/branches/0.92/src/test/java/org/apache/hadoop/hbase/replication/TestMultiSlaveReplication.java * /hbase/branches/0.92/src/test/java/org/apache/hadoop/hbase/replication/TestReplication.java > [0.92] Backport HBASE-8207 to fix replication test failures > --- > > Key: HBASE-9154 > URL: https://issues.apache.org/jira/browse/HBASE-9154 > Project: HBase > Issue Type: Task >Affects Versions: 0.92.3 >Reporter: Andrew Purtell >Assignee: Andrew Purtell > Fix For: 0.92.3 > > Attachments: 9154.patch > > > HBASE-8207 fixes a hostname parsing problem in replication that can cause > data loss and also manifests as replication test failures in EC2 test > environments, because EC2 hostnames very commonly contain the '-' character. > Backport HBASE-8207 to fix replication test failures observed while prepping > the 0.92.3 RC. After applying this fix no further replication failures are > seen in eight subsequent runs. -- 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-9435) Fix jersey serialization/deserialization of json objects
[ https://issues.apache.org/jira/browse/HBASE-9435?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13758694#comment-13758694 ] Hudson commented on HBASE-9435: --- SUCCESS: Integrated in hbase-0.96 #11 (See [https://builds.apache.org/job/hbase-0.96/11/]) HBASE-9435 Fix jersey serialization/deserialization of json objects (stack: rev 1520178) * /hbase/branches/0.96/hbase-server/src/main/java/org/apache/hadoop/hbase/rest/client/RemoteHTable.java * /hbase/branches/0.96/hbase-server/src/main/java/org/apache/hadoop/hbase/rest/model/CellModel.java * /hbase/branches/0.96/hbase-server/src/main/java/org/apache/hadoop/hbase/rest/model/CellSetModel.java * /hbase/branches/0.96/hbase-server/src/main/java/org/apache/hadoop/hbase/rest/model/ColumnSchemaModel.java * /hbase/branches/0.96/hbase-server/src/main/java/org/apache/hadoop/hbase/rest/model/RowModel.java * /hbase/branches/0.96/hbase-server/src/main/java/org/apache/hadoop/hbase/rest/model/StorageClusterVersionModel.java * /hbase/branches/0.96/hbase-server/src/main/java/org/apache/hadoop/hbase/rest/model/TableSchemaModel.java * /hbase/branches/0.96/hbase-server/src/main/java/org/apache/hadoop/hbase/rest/provider/JacksonProvider.java * /hbase/branches/0.96/hbase-server/src/test/java/org/apache/hadoop/hbase/rest/TestSchemaResource.java * /hbase/branches/0.96/hbase-server/src/test/java/org/apache/hadoop/hbase/rest/TestStatusResource.java * /hbase/branches/0.96/hbase-server/src/test/java/org/apache/hadoop/hbase/rest/model/TestCellModel.java * /hbase/branches/0.96/hbase-server/src/test/java/org/apache/hadoop/hbase/rest/model/TestCellSetModel.java * /hbase/branches/0.96/hbase-server/src/test/java/org/apache/hadoop/hbase/rest/model/TestColumnSchemaModel.java * /hbase/branches/0.96/hbase-server/src/test/java/org/apache/hadoop/hbase/rest/model/TestModelBase.java * /hbase/branches/0.96/hbase-server/src/test/java/org/apache/hadoop/hbase/rest/model/TestRowModel.java * /hbase/branches/0.96/hbase-server/src/test/java/org/apache/hadoop/hbase/rest/model/TestScannerModel.java * /hbase/branches/0.96/hbase-server/src/test/java/org/apache/hadoop/hbase/rest/model/TestStorageClusterStatusModel.java * /hbase/branches/0.96/hbase-server/src/test/java/org/apache/hadoop/hbase/rest/model/TestStorageClusterVersionModel.java * /hbase/branches/0.96/hbase-server/src/test/java/org/apache/hadoop/hbase/rest/model/TestTableInfoModel.java * /hbase/branches/0.96/hbase-server/src/test/java/org/apache/hadoop/hbase/rest/model/TestTableListModel.java * /hbase/branches/0.96/hbase-server/src/test/java/org/apache/hadoop/hbase/rest/model/TestTableRegionModel.java * /hbase/branches/0.96/hbase-server/src/test/java/org/apache/hadoop/hbase/rest/model/TestTableSchemaModel.java * /hbase/branches/0.96/hbase-server/src/test/java/org/apache/hadoop/hbase/rest/model/TestVersionModel.java > Fix jersey serialization/deserialization of json objects > > > Key: HBASE-9435 > URL: https://issues.apache.org/jira/browse/HBASE-9435 > Project: HBase > Issue Type: Bug > Components: REST >Reporter: Francis Liu >Assignee: Francis Liu > Fix For: 0.98.0, 0.96.1 > > Attachments: HBASE-9435.patch, HBASE-9435.patch > > > Stargate uses the default json marshaller/unmarshaller in natural mode. In > this mode the unmarshaller has trouble unmarshalling json instances. > This patch fixes this issue by using jackson as the marshaller/unmarshaller > instead. > I've also updated all the model unit tests to test json > serialization/deserialization. Backwards compatibilty can be verified by > modify the test base class to use the original marshaller/unmarshaller and > see that model tests pass. > The patch is backward compatible except for StorageClusterStatusModel, which > is broken anyway. It only shows one node in the liveNodes field. -- 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-9439) shell command list shows something not meaningful
[
https://issues.apache.org/jira/browse/HBASE-9439?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13758697#comment-13758697
]
Hudson commented on HBASE-9439:
---
SUCCESS: Integrated in hbase-0.96 #11 (See
[https://builds.apache.org/job/hbase-0.96/11/])
HBASE-9439 shell command list shows something not meaningful (jxiang: rev
1520175)
* /hbase/branches/0.96/hbase-server/src/main/ruby/shell/commands/list.rb
> shell command list shows something not meaningful
> -
>
> Key: HBASE-9439
> URL: https://issues.apache.org/jira/browse/HBASE-9439
> Project: HBase
> Issue Type: Bug
> Components: shell
>Reporter: Jimmy Xiang
>Assignee: Jimmy Xiang
>Priority: Minor
> Fix For: 0.98.0, 0.96.0
>
> Attachments: trunk-9439.patch
>
>
> Here is a sample output:
> {noformat}
> hbase(main):004:0> list
> TABLE
>
>
> usertable
>
>
> 1 row(s) in 0.3240 seconds
> => #<#:0x5eb8f6d>
> {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-9412) Startup scripts create 2 .out files.
[
https://issues.apache.org/jira/browse/HBASE-9412?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13758696#comment-13758696
]
Hudson commented on HBASE-9412:
---
SUCCESS: Integrated in hbase-0.96 #11 (See
[https://builds.apache.org/job/hbase-0.96/11/])
HBASE-9412 Startup scripts create 2 .out files (stack: rev 1520164)
* /hbase/branches/0.96/bin/hbase-daemon.sh
> Startup scripts create 2 .out files.
>
>
> Key: HBASE-9412
> URL: https://issues.apache.org/jira/browse/HBASE-9412
> Project: HBase
> Issue Type: Bug
> Components: scripts
>Affects Versions: 0.96.0
>Reporter: Jean-Marc Spaggiari
>Assignee: stack
>Priority: Minor
> Fix For: 0.98.0, 0.96.1
>
> Attachments: 9412.txt
>
>
> When start HBase with bin/start-hbase.sh, script creates 2 out files.
> {code}
> -rw-r--r-- 1 jmspaggiari jmspaggiari 0 Aug 31 15:38
> hbase-jmspaggiari-master-t430s.out
> -rw-r--r-- 1 jmspaggiari jmspaggiari 0 Aug 31 15:38
> hbase-jmspaggiari-master-t430s.out.1
> {code}
> Should create only one.
--
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-9433) OpenRegionHandler uses different assignment timeout
[ https://issues.apache.org/jira/browse/HBASE-9433?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13758698#comment-13758698 ] Hudson commented on HBASE-9433: --- SUCCESS: Integrated in hbase-0.96 #11 (See [https://builds.apache.org/job/hbase-0.96/11/]) HBASE-9433 OpenRegionHandler uses different assignment timeout (jxiang: rev 1520174) * /hbase/branches/0.96/hbase-server/src/main/java/org/apache/hadoop/hbase/master/AssignmentManager.java * /hbase/branches/0.96/hbase-server/src/main/java/org/apache/hadoop/hbase/regionserver/HRegion.java * /hbase/branches/0.96/hbase-server/src/main/java/org/apache/hadoop/hbase/regionserver/handler/OpenRegionHandler.java > OpenRegionHandler uses different assignment timeout > --- > > Key: HBASE-9433 > URL: https://issues.apache.org/jira/browse/HBASE-9433 > Project: HBase > Issue Type: Bug > Components: Region Assignment >Affects Versions: 0.96.0 >Reporter: Jimmy Xiang >Assignee: Jimmy Xiang >Priority: Minor > Fix For: 0.98.0, 0.96.0 > > Attachments: trunk-9433.patch, trunk-9433_rebased.patch, > trunk-9433_v2.patch > > > OpenRegionHandler uses the timeout monitor checking period as the timeout. It > should share the same default as in AssignmentManager. -- 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-9414) start-hbase.cmd doesn't need the execute flag.
[ https://issues.apache.org/jira/browse/HBASE-9414?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13758695#comment-13758695 ] Hudson commented on HBASE-9414: --- SUCCESS: Integrated in hbase-0.96 #11 (See [https://builds.apache.org/job/hbase-0.96/11/]) HBASE-9414 start-hbase.cmd doesn't need the execute flag (stack: rev 1520163) * /hbase/branches/0.96/hbase-assembly/src/main/assembly/components.xml > start-hbase.cmd doesn't need the execute flag. > -- > > Key: HBASE-9414 > URL: https://issues.apache.org/jira/browse/HBASE-9414 > Project: HBase > Issue Type: Bug >Affects Versions: 0.96.0 >Reporter: Jean-Marc Spaggiari >Assignee: stack >Priority: Trivial > Fix For: 0.98.0, 0.96.1 > > Attachments: 9414.txt > > > When you do start- and tabulation, since there start-hbase.cmd has the > execution flag, completion go only up to start-hbase. > We should remove the execution flag for this script. -- 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=13758699#comment-13758699
]
Hudson commented on HBASE-8930:
---
SUCCESS: Integrated in hbase-0.96 #11 (See
[https://builds.apache.org/job/hbase-0.96/11/])
HBASE-8930 Filter evaluates KVs outside requested columns (Vasu Mariyala)
(larsh: rev 1520170)
*
/hbase/branches/0.96/hbase-server/src/main/java/org/apache/hadoop/hbase/regionserver/ColumnTracker.java
*
/hbase/branches/0.96/hbase-server/src/main/java/org/apache/hadoop/hbase/regionserver/ExplicitColumnTracker.java
*
/hbase/branches/0.96/hbase-server/src/main/java/org/apache/hadoop/hbase/regionserver/ScanQueryMatcher.java
*
/hbase/branches/0.96/hbase-server/src/main/java/org/apache/hadoop/hbase/regionserver/ScanWildcardColumnTracker.java
*
/hbase/branches/0.96/hbase-server/src/test/java/org/apache/hadoop/hbase/filter/TestInvocationRecordFilter.java
*
/hbase/branches/0.96/hbase-server/src/test/java/org/apache/hadoop/hbase/regionserver/TestExplicitColumnTracker.java
*
/hbase/branches/0.96/hbase-server/src/test/java/org/apache/hadoop/hbase/regionserver/TestScanWildcardColumnTracker.java
> 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
> Fix For: 0.98.0, 0.94.12, 0.96.1
>
> Attachments: 0.94-HBASE-8930.patch, 0.94-HBASE-8930-rev1.patch,
> 0.95-HBASE-8930.patch, 0.95-HBASE-8930-rev1.patch,
> 0.96-HBASE-8930-rev2.patch, 8930-0.94.txt, HBASE-8930.patch,
> HBASE-8930-rev1.patch, HBASE-8930-rev2.patch, HBASE-8930-rev3.patch,
> HBASE-8930-rev4.patch, HBASE-8930-rev5.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));
> // === INSE
[jira] [Commented] (HBASE-9441) Intermittent TestRegionPlacement#testRegionPlacement failure
[
https://issues.apache.org/jira/browse/HBASE-9441?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13758691#comment-13758691
]
Hadoop QA commented on HBASE-9441:
--
{color:green}+1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12601526/9441-v1.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 3 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: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/7043//testReport/
Findbugs warnings:
https://builds.apache.org/job/PreCommit-HBASE-Build/7043//artifact/trunk/patchprocess/newPatchFindbugsWarningshbase-prefix-tree.html
Findbugs warnings:
https://builds.apache.org/job/PreCommit-HBASE-Build/7043//artifact/trunk/patchprocess/newPatchFindbugsWarningshbase-client.html
Findbugs warnings:
https://builds.apache.org/job/PreCommit-HBASE-Build/7043//artifact/trunk/patchprocess/newPatchFindbugsWarningshbase-common.html
Findbugs warnings:
https://builds.apache.org/job/PreCommit-HBASE-Build/7043//artifact/trunk/patchprocess/newPatchFindbugsWarningshbase-protocol.html
Findbugs warnings:
https://builds.apache.org/job/PreCommit-HBASE-Build/7043//artifact/trunk/patchprocess/newPatchFindbugsWarningshbase-server.html
Findbugs warnings:
https://builds.apache.org/job/PreCommit-HBASE-Build/7043//artifact/trunk/patchprocess/newPatchFindbugsWarningshbase-hadoop1-compat.html
Findbugs warnings:
https://builds.apache.org/job/PreCommit-HBASE-Build/7043//artifact/trunk/patchprocess/newPatchFindbugsWarningshbase-examples.html
Findbugs warnings:
https://builds.apache.org/job/PreCommit-HBASE-Build/7043//artifact/trunk/patchprocess/newPatchFindbugsWarningshbase-hadoop-compat.html
Console output:
https://builds.apache.org/job/PreCommit-HBASE-Build/7043//console
This message is automatically generated.
> Intermittent TestRegionPlacement#testRegionPlacement failure
>
>
> Key: HBASE-9441
> URL: https://issues.apache.org/jira/browse/HBASE-9441
> Project: HBase
> Issue Type: Test
>Reporter: Ted Yu
>Assignee: Ted Yu
>Priority: Minor
> Attachments: 9441-v1.txt,
> org.apache.hadoop.hbase.master.TestRegionPlacement-output.txt
>
>
> Occasionally TestRegionPlacement#testRegionPlacement fails due to no region
> found on secondary / tertiary region server.
> In the following test output, 10359edcfb1a761f94ab6d5b559c2278 was the region
> from the killed region server:
> {code}
> 2013-09-04 23:28:25,127 INFO [pool-1-thread-1] util.FSUtils(1878): Scan DFS
> for locality info takes 38 ms
> Region Assignment Verification for Table: testRegionAssignment
> Total regions : 10
> Total regions on favored nodes 10
> Total regions on PRIMARY region servers: 10
> Total regions on SECONDARY region servers: 0
> Total regions on TERTIARY region servers: 0
> ...
> 2013-09-04 23:28:25,130 DEBUG [pool-1-thread-1-EventThread]
> zookeeper.ZooKeeperWatcher(312): master:37502-0x140eb4dc4ef Received
> ZooKeeper Event, type=NodeDataChanged, state=SyncConnected,
> path=/hbase/region-in-transition/10359edcfb1a761f94ab6d5b559c2278
> 2013-09-04 23:28:25,130 DEBUG [RS_OPEN_REGION-kiyo:49841-1]
> zookeeper.ZKAssign(861): regionserver:49841-0x140eb4dc4ef0007 Transitioned
> node 10359edcfb1a761f94ab6d5b559c2278 from RS_ZK_REGION_OPENING to
> RS_ZK_REGION_OPENED
> 2013-09-04 23:28:25,131 DEBUG [RS_OPEN_REGION-kiyo:49841-1]
> handler.OpenRegionHandler(386): Transitioned 10359edcfb1a761f94ab6d5b559c2278
> to OPENED in zk on kiyo.gq1.ygridcore.net,49841,1378337278470
> 2013-09-04 23:28:25,131 DEBUG [RS_OPEN_REGION-kiyo:49841-1]
> handler.OpenRegionHandler(187): Opened
> hbase:namespace,,1378337284888.10359edcfb1a761f94ab6d5b559c2278. on
> k
[jira] [Commented] (HBASE-9413) WebUI says ".META." table but table got renames to "hbase:meta". Meed to update the UI.
[
https://issues.apache.org/jira/browse/HBASE-9413?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13758689#comment-13758689
]
Hadoop QA commented on HBASE-9413:
--
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12601509/9413v4.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 119
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: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:red}-1 core tests{color}. The patch failed these unit tests:
org.apache.hadoop.hbase.TestInfoServers
Test results:
https://builds.apache.org/job/PreCommit-HBASE-Build/7041//testReport/
Findbugs warnings:
https://builds.apache.org/job/PreCommit-HBASE-Build/7041//artifact/trunk/patchprocess/newPatchFindbugsWarningshbase-protocol.html
Findbugs warnings:
https://builds.apache.org/job/PreCommit-HBASE-Build/7041//artifact/trunk/patchprocess/newPatchFindbugsWarningshbase-client.html
Findbugs warnings:
https://builds.apache.org/job/PreCommit-HBASE-Build/7041//artifact/trunk/patchprocess/newPatchFindbugsWarningshbase-examples.html
Findbugs warnings:
https://builds.apache.org/job/PreCommit-HBASE-Build/7041//artifact/trunk/patchprocess/newPatchFindbugsWarningshbase-hadoop1-compat.html
Findbugs warnings:
https://builds.apache.org/job/PreCommit-HBASE-Build/7041//artifact/trunk/patchprocess/newPatchFindbugsWarningshbase-prefix-tree.html
Findbugs warnings:
https://builds.apache.org/job/PreCommit-HBASE-Build/7041//artifact/trunk/patchprocess/newPatchFindbugsWarningshbase-common.html
Findbugs warnings:
https://builds.apache.org/job/PreCommit-HBASE-Build/7041//artifact/trunk/patchprocess/newPatchFindbugsWarningshbase-server.html
Findbugs warnings:
https://builds.apache.org/job/PreCommit-HBASE-Build/7041//artifact/trunk/patchprocess/newPatchFindbugsWarningshbase-hadoop-compat.html
Console output:
https://builds.apache.org/job/PreCommit-HBASE-Build/7041//console
This message is automatically generated.
> WebUI says ".META." table but table got renames to "hbase:meta". Meed to
> update the UI.
> ---
>
> Key: HBASE-9413
> URL: https://issues.apache.org/jira/browse/HBASE-9413
> Project: HBase
> Issue Type: Bug
> Components: UI
>Affects Versions: 0.98.0, 0.96.0
>Reporter: Jean-Marc Spaggiari
>Assignee: stack
>Priority: Critical
> Attachments: 9413.txt, 9413v2.txt, 9413v3.txt, 9413v4.txt
>
>
> In the UI, we say "The .META. table holds references to all User Table
> regions" but the table name is "hbase:meta" and not ".META." We need to
> update this.
--
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-9317) Define timeout period for TestHBaseFsck#testSplitDaughtersNotInMeta
[ https://issues.apache.org/jira/browse/HBASE-9317?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13758675#comment-13758675 ] Hudson commented on HBASE-9317: --- FAILURE: Integrated in HBase-TRUNK-on-Hadoop-2.0.0 #710 (See [https://builds.apache.org/job/HBase-TRUNK-on-Hadoop-2.0.0/710/]) HBASE-9317 Define timeout period for TestHBaseFsck#testSplitDaughtersNotInMeta (tedyu: rev 1520073) * /hbase/trunk/hbase-server/src/test/java/org/apache/hadoop/hbase/util/TestHBaseFsck.java > Define timeout period for TestHBaseFsck#testSplitDaughtersNotInMeta > --- > > Key: HBASE-9317 > URL: https://issues.apache.org/jira/browse/HBASE-9317 > Project: HBase > Issue Type: Sub-task >Reporter: Ted Yu >Assignee: Ted Yu > Fix For: 0.98.0 > > Attachments: 9317-v1.txt, 9317-v2.txt > > > In hbase-0.95-on-hadoop2 build #247, TestHBaseFsck hung in > testSplitDaughtersNotInMeta. > This sub-task defines timeout period for > TestHBaseFsck#testSplitDaughtersNotInMeta so that long running test would be > timed out instead of hanging. -- 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-9421) Provide better error message when dropping non-existent namespace
[
https://issues.apache.org/jira/browse/HBASE-9421?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13758677#comment-13758677
]
Hudson commented on HBASE-9421:
---
FAILURE: Integrated in HBase-TRUNK-on-Hadoop-2.0.0 #710 (See
[https://builds.apache.org/job/HBase-TRUNK-on-Hadoop-2.0.0/710/])
HBASE-9421 Provide better error message when dropping non-existent namespace
(Ted Yu) (tedyu: rev 1520043)
*
/hbase/trunk/hbase-server/src/main/java/org/apache/hadoop/hbase/master/TableNamespaceManager.java
> Provide better error message when dropping non-existent namespace
> -
>
> Key: HBASE-9421
> URL: https://issues.apache.org/jira/browse/HBASE-9421
> Project: HBase
> Issue Type: Bug
>Reporter: Ted Yu
>Assignee: Ted Yu
>Priority: Minor
> Fix For: 0.98.0, 0.96.0
>
> Attachments: 9421-v1.txt
>
>
> If a non-existent namespace is dropped, FileNotFoundException is thrown.
> There should be better error message like "namespace does not exist"
> {code}
> hbase(main):002:0> drop_namespace 'hi'
> ERROR: java.io.FileNotFoundException: File
> hdfs://h.com:8020/apps/hbase/data/data/hi does not exist.
> at
> org.apache.hadoop.hdfs.DistributedFileSystem.listStatusInternal(DistributedFileSystem.java:656)
> at
> org.apache.hadoop.hdfs.DistributedFileSystem.access$600(DistributedFileSystem.java:92)
> at
> org.apache.hadoop.hdfs.DistributedFileSystem$14.doCall(DistributedFileSystem.java:714)
> at
> org.apache.hadoop.hdfs.DistributedFileSystem$14.doCall(DistributedFileSystem.java:710)
> at
> org.apache.hadoop.fs.FileSystemLinkResolver.resolve(FileSystemLinkResolver.java:78)
> at
> org.apache.hadoop.hdfs.DistributedFileSystem.listStatus(DistributedFileSystem.java:710)
> at org.apache.hadoop.fs.FileSystem.listStatus(FileSystem.java:1478)
> at org.apache.hadoop.fs.FileSystem.listStatus(FileSystem.java:1518)
> at
> org.apache.hadoop.hbase.util.FSUtils.getLocalTableDirs(FSUtils.java:1316)
> at
> org.apache.hadoop.hbase.util.FSTableDescriptors.getByNamespace(FSTableDescriptors.java:222)
> at
> org.apache.hadoop.hbase.master.HMaster.listTableDescriptorsByNamespace(HMaster.java:3121)
> at
> org.apache.hadoop.hbase.master.TableNamespaceManager.remove(TableNamespaceManager.java:158)
> at
> org.apache.hadoop.hbase.master.HMaster.deleteNamespace(HMaster.java:3106)
> at
> org.apache.hadoop.hbase.master.HMaster.deleteNamespace(HMaster.java:3000)
> at
> org.apache.hadoop.hbase.protobuf.generated.MasterAdminProtos$MasterAdminService$2.callBlockingMethod(MasterAdminProtos.java:32902)
> at org.apache.hadoop.hbase.ipc.RpcServer.call(RpcServer.java:2147)
> at
> org.apache.hadoop.hbase.ipc.RpcServer$Handler.run(RpcServer.java:1854)
> Here is some help for this command:
> Drop the named namespace. The namespace must be empty.
> {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-9414) start-hbase.cmd doesn't need the execute flag.
[ https://issues.apache.org/jira/browse/HBASE-9414?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13758672#comment-13758672 ] Hudson commented on HBASE-9414: --- FAILURE: Integrated in HBase-TRUNK-on-Hadoop-2.0.0 #710 (See [https://builds.apache.org/job/HBase-TRUNK-on-Hadoop-2.0.0/710/]) HBASE-9414 start-hbase.cmd doesn't need the execute flag (stack: rev 1520162) * /hbase/trunk/hbase-assembly/src/main/assembly/components.xml > start-hbase.cmd doesn't need the execute flag. > -- > > Key: HBASE-9414 > URL: https://issues.apache.org/jira/browse/HBASE-9414 > Project: HBase > Issue Type: Bug >Affects Versions: 0.96.0 >Reporter: Jean-Marc Spaggiari >Assignee: stack >Priority: Trivial > Fix For: 0.98.0, 0.96.1 > > Attachments: 9414.txt > > > When you do start- and tabulation, since there start-hbase.cmd has the > execution flag, completion go only up to start-hbase. > We should remove the execution flag for this script. -- 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-9412) Startup scripts create 2 .out files.
[
https://issues.apache.org/jira/browse/HBASE-9412?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13758674#comment-13758674
]
Hudson commented on HBASE-9412:
---
FAILURE: Integrated in HBase-TRUNK-on-Hadoop-2.0.0 #710 (See
[https://builds.apache.org/job/HBase-TRUNK-on-Hadoop-2.0.0/710/])
HBASE-9412 Startup scripts create 2 .out files (stack: rev 1520165)
* /hbase/trunk/bin/hbase-daemon.sh
> Startup scripts create 2 .out files.
>
>
> Key: HBASE-9412
> URL: https://issues.apache.org/jira/browse/HBASE-9412
> Project: HBase
> Issue Type: Bug
> Components: scripts
>Affects Versions: 0.96.0
>Reporter: Jean-Marc Spaggiari
>Assignee: stack
>Priority: Minor
> Fix For: 0.98.0, 0.96.1
>
> Attachments: 9412.txt
>
>
> When start HBase with bin/start-hbase.sh, script creates 2 out files.
> {code}
> -rw-r--r-- 1 jmspaggiari jmspaggiari 0 Aug 31 15:38
> hbase-jmspaggiari-master-t430s.out
> -rw-r--r-- 1 jmspaggiari jmspaggiari 0 Aug 31 15:38
> hbase-jmspaggiari-master-t430s.out.1
> {code}
> Should create only one.
--
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-9428) Regex filters are at least an order of magnitude slower since 0.94.3
[
https://issues.apache.org/jira/browse/HBASE-9428?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13758673#comment-13758673
]
Hudson commented on HBASE-9428:
---
FAILURE: Integrated in HBase-TRUNK-on-Hadoop-2.0.0 #710 (See
[https://builds.apache.org/job/HBase-TRUNK-on-Hadoop-2.0.0/710/])
HBASE-9428 Regex filters are at least an order of magnitude slower since 0.94.3
(larsh: rev 1520095)
*
/hbase/trunk/hbase-client/src/main/java/org/apache/hadoop/hbase/filter/RegexStringComparator.java
> Regex filters are at least an order of magnitude slower since 0.94.3
>
>
> Key: HBASE-9428
> URL: https://issues.apache.org/jira/browse/HBASE-9428
> Project: HBase
> Issue Type: Bug
>Reporter: Jean-Daniel Cryans
>Assignee: Lars Hofhansl
> Fix For: 0.98.0, 0.94.12, 0.96.1
>
> Attachments: 9428-0.94.txt, 9428-trunk.txt
>
>
> I found this issue after debugging a performance problem on an OpenTSDB
> cluster, it was basically unusable after an upgrade from 0.94.2 to 0.94.6. It
> was caused by HBASE-7279 (ping [~lhofhansl]).
> The easiest way to see it is to run a simple 1 client PE:
> {noformat}
> $ ./bin/hbase org.apache.hadoop.hbase.PerformanceEvaluation sequentialWrite 1
> {noformat}
> Then in the shell do a filter scan (flush the table first and make sure if
> fits in your blockcache if you want stable numbers).
> Pre HBASE-7279:
> {noformat}
> hbase(main):028:0> scan 'TestTable', {FILTER => "(RowFilter (=,
> 'regexstring:055872') )"}
> ROW COLUMN+CELL
>
>
> 055872 column=info:data,
> timestamp=1378248850191, value=(blanked)
>
>
> 1 row(s) in 1.2780 seconds
> {noformat}
> Post HBASE-7279
> {noformat}
> hbase(main):037:0* scan 'TestTable', {FILTER => "(RowFilter (=,
> 'regexstring:055872') )"}
> ROW COLUMN+CELL
>
>
> 055872 column=info:data,
> timestamp=1378248850191, value=(blanked)
>
>
> 1 row(s) in 24.2940 seconds
> {noformat}
> I tried a bunch of 0.94, up to 0.94.11, and the tip of 0.96. They are all
> slow like this.
> It seems that since that jira went in we do a lot more row matching, and
> running the regex gets super expensive.
--
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=13758671#comment-13758671
]
Hudson commented on HBASE-9387:
---
FAILURE: Integrated in HBase-TRUNK-on-Hadoop-2.0.0 #710 (See
[https://builds.apache.org/job/HBase-TRUNK-on-Hadoop-2.0.0/710/])
HBASE-9387 Region could get lost during assignment (Ted Yu) (tedyu: rev 1520058)
*
/hbase/trunk/hbase-server/src/main/java/org/apache/hadoop/hbase/regionserver/handler/OpenRegionHandler.java
*
/hbase/trunk/hbase-server/src/test/java/org/apache/hadoop/hbase/MockRegionServerServices.java
*
/hbase/trunk/hbase-server/src/test/java/org/apache/hadoop/hbase/TestFullLogReconstruction.java
*
/hbase/trunk/hbase-server/src/test/java/org/apache/hadoop/hbase/regionserver/handler/TestOpenRegionHandler.java
> 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
> Fix For: 0.98.0, 0.96.0
>
> 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,
> 9387-v8.txt, 9387-v9.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-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=13758676#comment-13758676
]
Hudson commented on HBASE-8930:
---
FAILURE: Integrated in HBase-TRUNK-on-Hadoop-2.0.0 #710 (See
[https://builds.apache.org/job/HBase-TRUNK-on-Hadoop-2.0.0/710/])
HBASE-8930 Filter evaluates KVs outside requested columns (Vasu Mariyala)
(larsh: rev 1520168)
*
/hbase/trunk/hbase-server/src/main/java/org/apache/hadoop/hbase/regionserver/ColumnTracker.java
*
/hbase/trunk/hbase-server/src/main/java/org/apache/hadoop/hbase/regionserver/ExplicitColumnTracker.java
*
/hbase/trunk/hbase-server/src/main/java/org/apache/hadoop/hbase/regionserver/ScanQueryMatcher.java
*
/hbase/trunk/hbase-server/src/main/java/org/apache/hadoop/hbase/regionserver/ScanWildcardColumnTracker.java
*
/hbase/trunk/hbase-server/src/test/java/org/apache/hadoop/hbase/regionserver/TestExplicitColumnTracker.java
*
/hbase/trunk/hbase-server/src/test/java/org/apache/hadoop/hbase/regionserver/TestScanWildcardColumnTracker.java
> 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
> Fix For: 0.98.0, 0.94.12, 0.96.1
>
> Attachments: 0.94-HBASE-8930.patch, 0.94-HBASE-8930-rev1.patch,
> 0.95-HBASE-8930.patch, 0.95-HBASE-8930-rev1.patch,
> 0.96-HBASE-8930-rev2.patch, 8930-0.94.txt, HBASE-8930.patch,
> HBASE-8930-rev1.patch, HBASE-8930-rev2.patch, HBASE-8930-rev3.patch,
> HBASE-8930-rev4.patch, HBASE-8930-rev5.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.a
[jira] [Comment Edited] (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=13758669#comment-13758669 ] Gary Helmling edited comment on HBASE-9390 at 9/5/13 2:01 AM: -- bq. we should not allow external clients to control if to recover edits. Otherwise, HBase data integrity is nondeterministic. Is this true? If a coprocessor inserts it's own WAL edits to handle state, wouldn't we want it to also be able to bypass "normal" processing of them on restore? Either way, changing the semantics of the RegionObserver API and semantics seems outside the scope of this issue. Can you open another JIRA if you think that's really necessary? was (Author: ghelmling): .bq we should not allow external clients to control if to recover edits. Otherwise, HBase data integrity is nondeterministic. Is this true? If a coprocessor inserts it's own WAL edits to handle state, wouldn't we want it to also be able to bypass "normal" processing of them on restore? Either way, changing the semantics of the RegionObserver API and semantics seems outside the scope of this issue. Can you open another JIRA if you think that's really necessary? > 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 >Assignee: Jeffrey Zhong > Attachments: copro.patch, hbase-9390.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] [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=13758669#comment-13758669 ] Gary Helmling commented on HBASE-9390: -- .bq we should not allow external clients to control if to recover edits. Otherwise, HBase data integrity is nondeterministic. Is this true? If a coprocessor inserts it's own WAL edits to handle state, wouldn't we want it to also be able to bypass "normal" processing of them on restore? Either way, changing the semantics of the RegionObserver API and semantics seems outside the scope of this issue. Can you open another JIRA if you think that's really necessary? > 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 >Assignee: Jeffrey Zhong > Attachments: copro.patch, hbase-9390.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-9441) Intermittent TestRegionPlacement#testRegionPlacement failure
[
https://issues.apache.org/jira/browse/HBASE-9441?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ted Yu updated HBASE-9441:
--
Attachment: org.apache.hadoop.hbase.master.TestRegionPlacement-output.txt
Here it is.
> Intermittent TestRegionPlacement#testRegionPlacement failure
>
>
> Key: HBASE-9441
> URL: https://issues.apache.org/jira/browse/HBASE-9441
> Project: HBase
> Issue Type: Test
>Reporter: Ted Yu
>Assignee: Ted Yu
>Priority: Minor
> Attachments: 9441-v1.txt,
> org.apache.hadoop.hbase.master.TestRegionPlacement-output.txt
>
>
> Occasionally TestRegionPlacement#testRegionPlacement fails due to no region
> found on secondary / tertiary region server.
> In the following test output, 10359edcfb1a761f94ab6d5b559c2278 was the region
> from the killed region server:
> {code}
> 2013-09-04 23:28:25,127 INFO [pool-1-thread-1] util.FSUtils(1878): Scan DFS
> for locality info takes 38 ms
> Region Assignment Verification for Table: testRegionAssignment
> Total regions : 10
> Total regions on favored nodes 10
> Total regions on PRIMARY region servers: 10
> Total regions on SECONDARY region servers: 0
> Total regions on TERTIARY region servers: 0
> ...
> 2013-09-04 23:28:25,130 DEBUG [pool-1-thread-1-EventThread]
> zookeeper.ZooKeeperWatcher(312): master:37502-0x140eb4dc4ef Received
> ZooKeeper Event, type=NodeDataChanged, state=SyncConnected,
> path=/hbase/region-in-transition/10359edcfb1a761f94ab6d5b559c2278
> 2013-09-04 23:28:25,130 DEBUG [RS_OPEN_REGION-kiyo:49841-1]
> zookeeper.ZKAssign(861): regionserver:49841-0x140eb4dc4ef0007 Transitioned
> node 10359edcfb1a761f94ab6d5b559c2278 from RS_ZK_REGION_OPENING to
> RS_ZK_REGION_OPENED
> 2013-09-04 23:28:25,131 DEBUG [RS_OPEN_REGION-kiyo:49841-1]
> handler.OpenRegionHandler(386): Transitioned 10359edcfb1a761f94ab6d5b559c2278
> to OPENED in zk on kiyo.gq1.ygridcore.net,49841,1378337278470
> 2013-09-04 23:28:25,131 DEBUG [RS_OPEN_REGION-kiyo:49841-1]
> handler.OpenRegionHandler(187): Opened
> hbase:namespace,,1378337284888.10359edcfb1a761f94ab6d5b559c2278. on
> kiyo.gq1.ygridcore.net,49841,1378337278470
> 2013-09-04 23:28:25,132 DEBUG [AM.ZK.Worker-pool2-t6]
> master.AssignmentManager(801): Handling transition=RS_ZK_REGION_OPENED,
> server=kiyo.gq1.ygridcore.net,49841,1378337278470,
> region=10359edcfb1a761f94ab6d5b559c2278, current state from region state map
> ={10359edcfb1a761f94ab6d5b559c2278 state=OPENING, ts=1378337305025,
> server=kiyo.gq1.ygridcore.net,49841,1378337278470}
> 2013-09-04 23:28:25,132 INFO [AM.ZK.Worker-pool2-t6]
> master.RegionStates(263): Transitioned from {10359edcfb1a761f94ab6d5b559c2278
> state=OPENING, ts=1378337305025,
> server=kiyo.gq1.ygridcore.net,49841,1378337278470} to
> {10359edcfb1a761f94ab6d5b559c2278 state=OPEN, ts=1378337305132,
> server=kiyo.gq1.ygridcore.net,49841,1378337278470}
> 2013-09-04 23:28:25,132 DEBUG [AM.ZK.Worker-pool2-t6]
> handler.OpenedRegionHandler(150): Handling OPENED event for
> 10359edcfb1a761f94ab6d5b559c2278 from
> kiyo.gq1.ygridcore.net,49841,1378337278470; deleting unassigned node
> 2013-09-04 23:28:25,132 DEBUG [AM.ZK.Worker-pool2-t6]
> zookeeper.ZKAssign(405): master:37502-0x140eb4dc4ef Deleting existing
> unassigned node 10359edcfb1a761f94ab6d5b559c2278 in expected state
> RS_ZK_REGION_OPENED
> 2013-09-04 23:28:25,188 INFO [pool-1-thread-1] hbase.ResourceChecker(171):
> after: master.TestRegionPlacement#testRegionPlacement Thread=873 (was 814)
> Potentially hanging thread: RS_OPEN_REGION-kiyo:53373-2
> ...
> - Thread LEAK? -, OpenFileDescriptor=1061 (was 1033) - OpenFileDescriptor
> LEAK? -, MaxFileDescriptor=32768 (was 32768), SystemLoadAverage=549 (was
> 609), ProcessCount=489 (was 489), AvailableMemoryMB=9288 (was 9107) -
> AvailableMemoryMB LEAK? -, ConnectionCount=23 (was 22) - ConnectionCount
> LEAK? -
> 2013-09-04 23:28:25,189 WARN [pool-1-thread-1] hbase.ResourceChecker(134):
> Thread=873 is superior to 500
> 2013-09-04 23:28:25,190 WARN [pool-1-thread-1] hbase.ResourceChecker(134):
> OpenFileDescriptor=1061 is superior to 1024
> 2013-09-04 23:28:25,223 DEBUG [pool-1-thread-1-EventThread]
> zookeeper.ZooKeeperWatcher(312): master:37502-0x140eb4dc4ef Received
> ZooKeeper Event, type=NodeDeleted, state=SyncConnected,
> path=/hbase/region-in-transition/10359edcfb1a761f94ab6d5b559c2278
> 2013-09-04 23:28:25,224 DEBUG [pool-1-thread-1-EventThread]
> zookeeper.ZooKeeperWatcher(312): master:37502-0x140eb4dc4ef Received
> ZooKeeper Event, type=NodeChildrenChanged, state=SyncConnected,
> path=/hbase/region-in-transition
> 2013-09-04 23:28:25,224 DEBUG [AM.ZK.Worker-pool2-t6]
> zookeeper.ZKAssign(434): master:37502-0x140eb4dc4ef Deleted u
[jira] [Updated] (HBASE-9441) Intermittent TestRegionPlacement#testRegionPlacement failure
[
https://issues.apache.org/jira/browse/HBASE-9441?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ted Yu updated HBASE-9441:
--
Status: Open (was: Patch Available)
> Intermittent TestRegionPlacement#testRegionPlacement failure
>
>
> Key: HBASE-9441
> URL: https://issues.apache.org/jira/browse/HBASE-9441
> Project: HBase
> Issue Type: Test
>Reporter: Ted Yu
>Assignee: Ted Yu
>Priority: Minor
> Attachments: 9441-v1.txt,
> org.apache.hadoop.hbase.master.TestRegionPlacement-output.txt
>
>
> Occasionally TestRegionPlacement#testRegionPlacement fails due to no region
> found on secondary / tertiary region server.
> In the following test output, 10359edcfb1a761f94ab6d5b559c2278 was the region
> from the killed region server:
> {code}
> 2013-09-04 23:28:25,127 INFO [pool-1-thread-1] util.FSUtils(1878): Scan DFS
> for locality info takes 38 ms
> Region Assignment Verification for Table: testRegionAssignment
> Total regions : 10
> Total regions on favored nodes 10
> Total regions on PRIMARY region servers: 10
> Total regions on SECONDARY region servers: 0
> Total regions on TERTIARY region servers: 0
> ...
> 2013-09-04 23:28:25,130 DEBUG [pool-1-thread-1-EventThread]
> zookeeper.ZooKeeperWatcher(312): master:37502-0x140eb4dc4ef Received
> ZooKeeper Event, type=NodeDataChanged, state=SyncConnected,
> path=/hbase/region-in-transition/10359edcfb1a761f94ab6d5b559c2278
> 2013-09-04 23:28:25,130 DEBUG [RS_OPEN_REGION-kiyo:49841-1]
> zookeeper.ZKAssign(861): regionserver:49841-0x140eb4dc4ef0007 Transitioned
> node 10359edcfb1a761f94ab6d5b559c2278 from RS_ZK_REGION_OPENING to
> RS_ZK_REGION_OPENED
> 2013-09-04 23:28:25,131 DEBUG [RS_OPEN_REGION-kiyo:49841-1]
> handler.OpenRegionHandler(386): Transitioned 10359edcfb1a761f94ab6d5b559c2278
> to OPENED in zk on kiyo.gq1.ygridcore.net,49841,1378337278470
> 2013-09-04 23:28:25,131 DEBUG [RS_OPEN_REGION-kiyo:49841-1]
> handler.OpenRegionHandler(187): Opened
> hbase:namespace,,1378337284888.10359edcfb1a761f94ab6d5b559c2278. on
> kiyo.gq1.ygridcore.net,49841,1378337278470
> 2013-09-04 23:28:25,132 DEBUG [AM.ZK.Worker-pool2-t6]
> master.AssignmentManager(801): Handling transition=RS_ZK_REGION_OPENED,
> server=kiyo.gq1.ygridcore.net,49841,1378337278470,
> region=10359edcfb1a761f94ab6d5b559c2278, current state from region state map
> ={10359edcfb1a761f94ab6d5b559c2278 state=OPENING, ts=1378337305025,
> server=kiyo.gq1.ygridcore.net,49841,1378337278470}
> 2013-09-04 23:28:25,132 INFO [AM.ZK.Worker-pool2-t6]
> master.RegionStates(263): Transitioned from {10359edcfb1a761f94ab6d5b559c2278
> state=OPENING, ts=1378337305025,
> server=kiyo.gq1.ygridcore.net,49841,1378337278470} to
> {10359edcfb1a761f94ab6d5b559c2278 state=OPEN, ts=1378337305132,
> server=kiyo.gq1.ygridcore.net,49841,1378337278470}
> 2013-09-04 23:28:25,132 DEBUG [AM.ZK.Worker-pool2-t6]
> handler.OpenedRegionHandler(150): Handling OPENED event for
> 10359edcfb1a761f94ab6d5b559c2278 from
> kiyo.gq1.ygridcore.net,49841,1378337278470; deleting unassigned node
> 2013-09-04 23:28:25,132 DEBUG [AM.ZK.Worker-pool2-t6]
> zookeeper.ZKAssign(405): master:37502-0x140eb4dc4ef Deleting existing
> unassigned node 10359edcfb1a761f94ab6d5b559c2278 in expected state
> RS_ZK_REGION_OPENED
> 2013-09-04 23:28:25,188 INFO [pool-1-thread-1] hbase.ResourceChecker(171):
> after: master.TestRegionPlacement#testRegionPlacement Thread=873 (was 814)
> Potentially hanging thread: RS_OPEN_REGION-kiyo:53373-2
> ...
> - Thread LEAK? -, OpenFileDescriptor=1061 (was 1033) - OpenFileDescriptor
> LEAK? -, MaxFileDescriptor=32768 (was 32768), SystemLoadAverage=549 (was
> 609), ProcessCount=489 (was 489), AvailableMemoryMB=9288 (was 9107) -
> AvailableMemoryMB LEAK? -, ConnectionCount=23 (was 22) - ConnectionCount
> LEAK? -
> 2013-09-04 23:28:25,189 WARN [pool-1-thread-1] hbase.ResourceChecker(134):
> Thread=873 is superior to 500
> 2013-09-04 23:28:25,190 WARN [pool-1-thread-1] hbase.ResourceChecker(134):
> OpenFileDescriptor=1061 is superior to 1024
> 2013-09-04 23:28:25,223 DEBUG [pool-1-thread-1-EventThread]
> zookeeper.ZooKeeperWatcher(312): master:37502-0x140eb4dc4ef Received
> ZooKeeper Event, type=NodeDeleted, state=SyncConnected,
> path=/hbase/region-in-transition/10359edcfb1a761f94ab6d5b559c2278
> 2013-09-04 23:28:25,224 DEBUG [pool-1-thread-1-EventThread]
> zookeeper.ZooKeeperWatcher(312): master:37502-0x140eb4dc4ef Received
> ZooKeeper Event, type=NodeChildrenChanged, state=SyncConnected,
> path=/hbase/region-in-transition
> 2013-09-04 23:28:25,224 DEBUG [AM.ZK.Worker-pool2-t6]
> zookeeper.ZKAssign(434): master:37502-0x140eb4dc4ef Deleted unassigned
> node 10359edcfb1a761f94ab6d5b559c2278 in expected
[jira] [Commented] (HBASE-9054) HBaseAdmin#isTableDisabled() should check table existence before checking zk state.
[ https://issues.apache.org/jira/browse/HBASE-9054?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13758657#comment-13758657 ] rajeshbabu commented on HBASE-9054: --- For trunk, can we check for table state znode is present or not, if not present we can throw TableNotFoundException? > HBaseAdmin#isTableDisabled() should check table existence before checking zk > state. > > > Key: HBASE-9054 > URL: https://issues.apache.org/jira/browse/HBASE-9054 > Project: HBase > Issue Type: Bug > Components: Admin >Affects Versions: 0.94.10 >Reporter: Bene Guo > Fix For: 0.94.12 > > Attachments: HBASE-9054-94.patch > > > To avoid compatibility issues with older versions HBaseAdmin#isTableDisabled > and HBaseAdmin#isTableEnabled()(The HBASE-8538 fix isTableEnabled.) returning > true even if the table state is null. Its also returning true even a table is > not present. We should confirm table existence from .META. before checking in > zk. If table not present or deleted, then It will throw > TableNotFoundException. -- 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-9441) Intermittent TestRegionPlacement#testRegionPlacement failure
[
https://issues.apache.org/jira/browse/HBASE-9441?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13758646#comment-13758646
]
Devaraj Das commented on HBASE-9441:
[~yuzhih...@gmail.com], can you please upload the full test log if available.
Thanks.
> Intermittent TestRegionPlacement#testRegionPlacement failure
>
>
> Key: HBASE-9441
> URL: https://issues.apache.org/jira/browse/HBASE-9441
> Project: HBase
> Issue Type: Test
>Reporter: Ted Yu
>Assignee: Ted Yu
>Priority: Minor
> Attachments: 9441-v1.txt
>
>
> Occasionally TestRegionPlacement#testRegionPlacement fails due to no region
> found on secondary / tertiary region server.
> In the following test output, 10359edcfb1a761f94ab6d5b559c2278 was the region
> from the killed region server:
> {code}
> 2013-09-04 23:28:25,127 INFO [pool-1-thread-1] util.FSUtils(1878): Scan DFS
> for locality info takes 38 ms
> Region Assignment Verification for Table: testRegionAssignment
> Total regions : 10
> Total regions on favored nodes 10
> Total regions on PRIMARY region servers: 10
> Total regions on SECONDARY region servers: 0
> Total regions on TERTIARY region servers: 0
> ...
> 2013-09-04 23:28:25,130 DEBUG [pool-1-thread-1-EventThread]
> zookeeper.ZooKeeperWatcher(312): master:37502-0x140eb4dc4ef Received
> ZooKeeper Event, type=NodeDataChanged, state=SyncConnected,
> path=/hbase/region-in-transition/10359edcfb1a761f94ab6d5b559c2278
> 2013-09-04 23:28:25,130 DEBUG [RS_OPEN_REGION-kiyo:49841-1]
> zookeeper.ZKAssign(861): regionserver:49841-0x140eb4dc4ef0007 Transitioned
> node 10359edcfb1a761f94ab6d5b559c2278 from RS_ZK_REGION_OPENING to
> RS_ZK_REGION_OPENED
> 2013-09-04 23:28:25,131 DEBUG [RS_OPEN_REGION-kiyo:49841-1]
> handler.OpenRegionHandler(386): Transitioned 10359edcfb1a761f94ab6d5b559c2278
> to OPENED in zk on kiyo.gq1.ygridcore.net,49841,1378337278470
> 2013-09-04 23:28:25,131 DEBUG [RS_OPEN_REGION-kiyo:49841-1]
> handler.OpenRegionHandler(187): Opened
> hbase:namespace,,1378337284888.10359edcfb1a761f94ab6d5b559c2278. on
> kiyo.gq1.ygridcore.net,49841,1378337278470
> 2013-09-04 23:28:25,132 DEBUG [AM.ZK.Worker-pool2-t6]
> master.AssignmentManager(801): Handling transition=RS_ZK_REGION_OPENED,
> server=kiyo.gq1.ygridcore.net,49841,1378337278470,
> region=10359edcfb1a761f94ab6d5b559c2278, current state from region state map
> ={10359edcfb1a761f94ab6d5b559c2278 state=OPENING, ts=1378337305025,
> server=kiyo.gq1.ygridcore.net,49841,1378337278470}
> 2013-09-04 23:28:25,132 INFO [AM.ZK.Worker-pool2-t6]
> master.RegionStates(263): Transitioned from {10359edcfb1a761f94ab6d5b559c2278
> state=OPENING, ts=1378337305025,
> server=kiyo.gq1.ygridcore.net,49841,1378337278470} to
> {10359edcfb1a761f94ab6d5b559c2278 state=OPEN, ts=1378337305132,
> server=kiyo.gq1.ygridcore.net,49841,1378337278470}
> 2013-09-04 23:28:25,132 DEBUG [AM.ZK.Worker-pool2-t6]
> handler.OpenedRegionHandler(150): Handling OPENED event for
> 10359edcfb1a761f94ab6d5b559c2278 from
> kiyo.gq1.ygridcore.net,49841,1378337278470; deleting unassigned node
> 2013-09-04 23:28:25,132 DEBUG [AM.ZK.Worker-pool2-t6]
> zookeeper.ZKAssign(405): master:37502-0x140eb4dc4ef Deleting existing
> unassigned node 10359edcfb1a761f94ab6d5b559c2278 in expected state
> RS_ZK_REGION_OPENED
> 2013-09-04 23:28:25,188 INFO [pool-1-thread-1] hbase.ResourceChecker(171):
> after: master.TestRegionPlacement#testRegionPlacement Thread=873 (was 814)
> Potentially hanging thread: RS_OPEN_REGION-kiyo:53373-2
> ...
> - Thread LEAK? -, OpenFileDescriptor=1061 (was 1033) - OpenFileDescriptor
> LEAK? -, MaxFileDescriptor=32768 (was 32768), SystemLoadAverage=549 (was
> 609), ProcessCount=489 (was 489), AvailableMemoryMB=9288 (was 9107) -
> AvailableMemoryMB LEAK? -, ConnectionCount=23 (was 22) - ConnectionCount
> LEAK? -
> 2013-09-04 23:28:25,189 WARN [pool-1-thread-1] hbase.ResourceChecker(134):
> Thread=873 is superior to 500
> 2013-09-04 23:28:25,190 WARN [pool-1-thread-1] hbase.ResourceChecker(134):
> OpenFileDescriptor=1061 is superior to 1024
> 2013-09-04 23:28:25,223 DEBUG [pool-1-thread-1-EventThread]
> zookeeper.ZooKeeperWatcher(312): master:37502-0x140eb4dc4ef Received
> ZooKeeper Event, type=NodeDeleted, state=SyncConnected,
> path=/hbase/region-in-transition/10359edcfb1a761f94ab6d5b559c2278
> 2013-09-04 23:28:25,224 DEBUG [pool-1-thread-1-EventThread]
> zookeeper.ZooKeeperWatcher(312): master:37502-0x140eb4dc4ef Received
> ZooKeeper Event, type=NodeChildrenChanged, state=SyncConnected,
> path=/hbase/region-in-transition
> 2013-09-04 23:28:25,224 DEBUG [AM.ZK.Worker-pool2-t6]
> zookeeper.ZKAssign(434): master:37502-0x140eb4dc4ef Deleted unas
[jira] [Updated] (HBASE-9153) Create a deprecation policy enforcement check
[ https://issues.apache.org/jira/browse/HBASE-9153?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aleksandr Shulman updated HBASE-9153: - Attachment: HBASE-9153-v3.patch > Create a deprecation policy enforcement check > - > > Key: HBASE-9153 > URL: https://issues.apache.org/jira/browse/HBASE-9153 > Project: HBase > Issue Type: Task >Reporter: Jonathan Hsieh > Attachments: HBASE-9153-v1.patch, HBASE-9153-v3.patch > > > We've had a few issues now where we've removed API's without deprecating or > deprecating in the late release. (HBASE-9142, HBASE-9093) We should just > have a tool that enforces our api deprecation policy as a release time check > or as a precommit check. -- 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-6127) TestAtomicOperation#testMultiRowMutationMultiThreads occasionally fails
[ https://issues.apache.org/jira/browse/HBASE-6127?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] stack updated HBASE-6127: - Fix Version/s: (was: 0.96.0) > TestAtomicOperation#testMultiRowMutationMultiThreads occasionally fails > --- > > Key: HBASE-6127 > URL: https://issues.apache.org/jira/browse/HBASE-6127 > Project: HBase > Issue Type: Bug > Components: test >Reporter: Ted Yu > > TestAtomicOperation occasionally fails. > Here is one instance: > https://builds.apache.org/job/HBase-TRUNK/2944/testReport/junit/org.apache.hadoop.hbase.regionserver/TestAtomicOperation/testMultiRowMutationMultiThreads/ -- 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-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:all-tabpanel
]
Jeffrey Zhong updated HBASE-9390:
-
Attachment: hbase-9390.patch
I combined the Nicolas patch into the hbase-9390.patch.
I modified preWALRestore interface as following because we should not allow
external clients to control if to recover edits. Otherwise, HBase data
integrity is nondeterministic.
{code}
- public boolean preWALRestore(HRegionInfo info, HLogKey logKey, WALEdit
logEdit) throws IOException
+ public void preWALRestore(HRegionInfo info, HLogKey logKey, WALEdit logEdit)
throws IOException
{code}
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
>Assignee: Jeffrey Zhong
> Attachments: copro.patch, hbase-9390.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-7141) Cleanup Increment and Append issues
[ https://issues.apache.org/jira/browse/HBASE-7141?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] stack updated HBASE-7141: - Fix Version/s: (was: 0.96.0) 0.98.0 > Cleanup Increment and Append issues > --- > > Key: HBASE-7141 > URL: https://issues.apache.org/jira/browse/HBASE-7141 > Project: HBase > Issue Type: Bug >Reporter: Lars Hofhansl > Fix For: 0.98.0 > > > * Append and Increment should take a TS for their update phase > * Append should access a timerange for the read phase > * Increment should no longer implement Writable (in trunk) > * Increment and Append makes changes visible through the memstore before the > WAL is sync'ed > This depends on HBASE-4583 -- 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-7679) implement store file management for stripe compactions
[ https://issues.apache.org/jira/browse/HBASE-7679?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] stack updated HBASE-7679: - Description: Needs loving. Moving out for now. Can pull in on point release after goes into trunk. Fix Version/s: (was: 0.96.0) 0.98.0 > implement store file management for stripe compactions > -- > > Key: HBASE-7679 > URL: https://issues.apache.org/jira/browse/HBASE-7679 > Project: HBase > Issue Type: Sub-task >Reporter: Sergey Shelukhin >Assignee: Sergey Shelukhin > Fix For: 0.98.0 > > Attachments: HBASE-7667-and-7603-v0-incomplete.patch, > HBASE-7667-and-7603-v0-incomplete.patch, HBASE-7667-and-7603-v1.patch, > HBASE-7667-and-7603-v1.patch, HBASE-7667-v1.patch, HBASE-7667-v1.patch, > HBASE-7667-v2.patch, HBASE-7667-v2.patch, HBASE-7667-v3.patch, > HBASE-7679-v10.patch, HBASE-7679-v11.patch, HBASE-7679-v12.patch, > HBASE-7679-v12.patch, HBASE-7679-v13.patch, HBASE-7679-v13.patch, > HBASE-7679-v14.patch, HBASE-7679-v15.patch, HBASE-7679-v16.patch, > HBASE-7679-v17.patch, HBASE-7679-v17.patch, HBASE-7679-v4.patch, > HBASE-7679-v5.patch, HBASE-7679-v6.patch, HBASE-7679-v7-.patch, > HBASE-7679-v7.patch, HBASE-7679-v8.patch, HBASE-7679-v9.patch > > > Needs loving. Moving out for now. Can pull in on point release after goes > into trunk. -- 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-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:all-tabpanel ] Jeffrey Zhong updated HBASE-9390: - Status: Patch Available (was: Open) > 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 >Assignee: Jeffrey Zhong > Attachments: copro.patch, hbase-9390.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] [Commented] (HBASE-9153) Create a deprecation policy enforcement check
[ https://issues.apache.org/jira/browse/HBASE-9153?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13758631#comment-13758631 ] Aleksandr Shulman commented on HBASE-9153: -- >From the feedback of the previous review, I made some pretty sweeping changes. >I'll go ahead and put it up on ReviewBoard shortly. At a high level: - Report can be run anywhere - User does not need to specify whether the versions are before, across, or after singularity. This is autodetected. - Bits can be sourced from either git or from local branch https://reviews.apache.org/r/13788/ > Create a deprecation policy enforcement check > - > > Key: HBASE-9153 > URL: https://issues.apache.org/jira/browse/HBASE-9153 > Project: HBase > Issue Type: Task >Reporter: Jonathan Hsieh > Attachments: HBASE-9153-v1.patch, HBASE-9153-v3.patch > > > We've had a few issues now where we've removed API's without deprecating or > deprecating in the late release. (HBASE-9142, HBASE-9093) We should just > have a tool that enforces our api deprecation policy as a release time check > or as a precommit check. -- 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-8369) MapReduce over snapshot files
[ https://issues.apache.org/jira/browse/HBASE-8369?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] stack updated HBASE-8369: - Fix Version/s: (was: 0.96.0) > MapReduce over snapshot files > - > > Key: HBASE-8369 > URL: https://issues.apache.org/jira/browse/HBASE-8369 > Project: HBase > Issue Type: New Feature > Components: mapreduce, snapshots >Reporter: Enis Soztutar >Assignee: Enis Soztutar > Fix For: 0.98.0 > > Attachments: HBASE-8369-0.94.patch, HBASE-8369-0.94_v2.patch, > HBASE-8369-0.94_v3.patch, HBASE-8369-0.94_v4.patch, HBASE-8369-0.94_v5.patch, > HBASE-8369-trunk_v1.patch, HBASE-8369-trunk_v2.patch, > HBASE-8369-trunk_v3.patch, hbase-8369_v0.patch > > > The idea is to add an InputFormat, which can run the mapreduce job over > snapshot files directly bypassing hbase server layer. The IF is similar in > usage to TableInputFormat, taking a Scan object from the user, but instead of > running from an online table, it runs from a table snapshot. We do one split > per region in the snapshot, and open an HRegion inside the RecordReader. A > RegionScanner is used internally for doing the scan without any HRegionServer > bits. > Users have been asking and searching for ways to run MR jobs by reading > directly from hfiles, so this allows new use cases if reading from stale data > is ok: > - Take snapshots periodically, and run MR jobs only on snapshots. > - Export snapshots to remote hdfs cluster, run the MR jobs at that cluster > without HBase cluster. > - (Future use case) Combine snapshot data with online hbase data: Scan from > yesterday's snapshot, but read today's data from online hbase cluster. -- 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-7680) implement compaction policy for stripe compactions
[ https://issues.apache.org/jira/browse/HBASE-7680?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] stack updated HBASE-7680: - Fix Version/s: (was: 0.96.0) 0.98.0 Needs loving. Moving out for now. Can pull in on point release after goes into trunk. > implement compaction policy for stripe compactions > -- > > Key: HBASE-7680 > URL: https://issues.apache.org/jira/browse/HBASE-7680 > Project: HBase > Issue Type: Sub-task >Reporter: Sergey Shelukhin >Assignee: Sergey Shelukhin > Fix For: 0.98.0 > > Attachments: HBASE-7680-latest-with-dependencies.patch, > HBASE-7680-latest-with-dependencies.patch, > HBASE-7680-latest-with-dependencies.patch, > HBASE-7680-latest-with-dependencies.patch, > HBASE-7680-latest-with-dependencies.patch, > HBASE-7680-latest-with-dependencies.patch, > HBASE-7680-latest-with-dependencies.patch, HBASE-7680-v0.patch, > HBASE-7680-v10.patch, HBASE-7680-v10.patch, HBASE-7680-v11.patch, > HBASE-7680-v12.patch, HBASE-7680-v13.patch, HBASE-7680-v13.patch, > HBASE-7680-v14.patch, HBASE-7680-v1.patch, HBASE-7680-v2.patch, > HBASE-7680-v3.patch, HBASE-7680-v4.patch, HBASE-7680-v5.patch, > HBASE-7680-v6.patch, HBASE-7680-v7.patch, HBASE-7680-v8.patch, > HBASE-7680-v9.patch > > > Bringing into 0.95.2 so gets some consideration -- 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-9376) TestDistributedLogSplitting creates a MiniCluster rooted at ~/hbase
[ https://issues.apache.org/jira/browse/HBASE-9376?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jeffrey Zhong updated HBASE-9376: - Status: Patch Available (was: Open) > TestDistributedLogSplitting creates a MiniCluster rooted at ~/hbase > --- > > Key: HBASE-9376 > URL: https://issues.apache.org/jira/browse/HBASE-9376 > Project: HBase > Issue Type: Test > Components: test >Affects Versions: 0.95.2 >Reporter: Nick Dimiduk >Assignee: Jeffrey Zhong >Priority: Minor > Attachments: hbase-9376.patch > > > TestDistributedLogSplitting creates a MiniCluster rooted at ~/hbase. I have a > machine configured such that my $HOME is NFS mounted, and this combination > makes for a rather flakey test. Test cluster(s) instantiated by this test > should instead root out of target (like all the rest). -- 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-8741) Scope sequenceid to the region rather than regionserver (WAS: Mutations on Regions in recovery mode might have same sequenceIDs)
[ https://issues.apache.org/jira/browse/HBASE-8741?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] stack updated HBASE-8741: - Fix Version/s: (was: 0.96.0) > Scope sequenceid to the region rather than regionserver (WAS: Mutations on > Regions in recovery mode might have same sequenceIDs) > > > Key: HBASE-8741 > URL: https://issues.apache.org/jira/browse/HBASE-8741 > Project: HBase > Issue Type: Bug > Components: MTTR >Affects Versions: 0.95.1 >Reporter: Himanshu Vashishtha >Assignee: Himanshu Vashishtha > Fix For: 0.98.0 > > Attachments: HBASE-8741-v0.patch, HBASE-8741-v2.patch, > HBASE-8741-v3.patch, HBASE-8741-v4-again.patch, HBASE-8741-v4-again.patch, > HBASE-8741-v4.patch, HBASE-8741-v5-again.patch, HBASE-8741-v5.patch > > > Currently, when opening a region, we find the maximum sequence ID from all > its HFiles and then set the LogSequenceId of the log (in case the later is at > a small value). This works good in recovered.edits case as we are not writing > to the region until we have replayed all of its previous edits. > With distributed log replay, if we want to enable writes while a region is > under recovery, we need to make sure that the logSequenceId > maximum > logSequenceId of the old regionserver. Otherwise, we might have a situation > where new edits have same (or smaller) sequenceIds. > We can store region level information in the WALTrailer, than this scenario > could be avoided by: > a) reading the trailer of the "last completed" file, i.e., last wal file > which has a trailer and, > b) completely reading the last wal file (this file would not have the > trailer, so it needs to be read completely). > In future, if we switch to multi wal file, we could read the trailer for all > completed WAL files, and reading the remaining incomplete files. -- 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-9259) Update hadoop versions grid in refguide adding hadoop-2.1.x and a note on hadoop-2.0.x versions
[ https://issues.apache.org/jira/browse/HBASE-9259?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] stack resolved HBASE-9259. -- Resolution: Fixed Fix Version/s: 0.98.0 Assignee: stack Committed to trunk and to branch so 0.96 has the updated grid too. > Update hadoop versions grid in refguide adding hadoop-2.1.x and a note on > hadoop-2.0.x versions > --- > > Key: HBASE-9259 > URL: https://issues.apache.org/jira/browse/HBASE-9259 > Project: HBase > Issue Type: Sub-task > Components: documentation >Reporter: stack >Assignee: stack > Fix For: 0.98.0, 0.96.0 > > Attachments: 9259.txt > > > Need to update our hadoop versions grid. Add notes on hadoop-2.1 and > hadoop-2.0 (we do the former, not the latter) -- 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-9259) Update hadoop versions grid in refguide adding hadoop-2.1.x and a note on hadoop-2.0.x versions
[ https://issues.apache.org/jira/browse/HBASE-9259?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] stack updated HBASE-9259: - Attachment: 9259.txt This will do for now. Makes mention of 2.0.x-alpha, 2.1.0-beta, and 2.x > Update hadoop versions grid in refguide adding hadoop-2.1.x and a note on > hadoop-2.0.x versions > --- > > Key: HBASE-9259 > URL: https://issues.apache.org/jira/browse/HBASE-9259 > Project: HBase > Issue Type: Sub-task > Components: documentation >Reporter: stack > Fix For: 0.96.0 > > Attachments: 9259.txt > > > Need to update our hadoop versions grid. Add notes on hadoop-2.1 and > hadoop-2.0 (we do the former, not the latter) -- 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-9441) Intermittent TestRegionPlacement#testRegionPlacement failure
[
https://issues.apache.org/jira/browse/HBASE-9441?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ted Yu updated HBASE-9441:
--
Status: Patch Available (was: Open)
> Intermittent TestRegionPlacement#testRegionPlacement failure
>
>
> Key: HBASE-9441
> URL: https://issues.apache.org/jira/browse/HBASE-9441
> Project: HBase
> Issue Type: Test
>Reporter: Ted Yu
>Assignee: Ted Yu
>Priority: Minor
> Attachments: 9441-v1.txt
>
>
> Occasionally TestRegionPlacement#testRegionPlacement fails due to no region
> found on secondary / tertiary region server.
> In the following test output, 10359edcfb1a761f94ab6d5b559c2278 was the region
> from the killed region server:
> {code}
> 2013-09-04 23:28:25,127 INFO [pool-1-thread-1] util.FSUtils(1878): Scan DFS
> for locality info takes 38 ms
> Region Assignment Verification for Table: testRegionAssignment
> Total regions : 10
> Total regions on favored nodes 10
> Total regions on PRIMARY region servers: 10
> Total regions on SECONDARY region servers: 0
> Total regions on TERTIARY region servers: 0
> ...
> 2013-09-04 23:28:25,130 DEBUG [pool-1-thread-1-EventThread]
> zookeeper.ZooKeeperWatcher(312): master:37502-0x140eb4dc4ef Received
> ZooKeeper Event, type=NodeDataChanged, state=SyncConnected,
> path=/hbase/region-in-transition/10359edcfb1a761f94ab6d5b559c2278
> 2013-09-04 23:28:25,130 DEBUG [RS_OPEN_REGION-kiyo:49841-1]
> zookeeper.ZKAssign(861): regionserver:49841-0x140eb4dc4ef0007 Transitioned
> node 10359edcfb1a761f94ab6d5b559c2278 from RS_ZK_REGION_OPENING to
> RS_ZK_REGION_OPENED
> 2013-09-04 23:28:25,131 DEBUG [RS_OPEN_REGION-kiyo:49841-1]
> handler.OpenRegionHandler(386): Transitioned 10359edcfb1a761f94ab6d5b559c2278
> to OPENED in zk on kiyo.gq1.ygridcore.net,49841,1378337278470
> 2013-09-04 23:28:25,131 DEBUG [RS_OPEN_REGION-kiyo:49841-1]
> handler.OpenRegionHandler(187): Opened
> hbase:namespace,,1378337284888.10359edcfb1a761f94ab6d5b559c2278. on
> kiyo.gq1.ygridcore.net,49841,1378337278470
> 2013-09-04 23:28:25,132 DEBUG [AM.ZK.Worker-pool2-t6]
> master.AssignmentManager(801): Handling transition=RS_ZK_REGION_OPENED,
> server=kiyo.gq1.ygridcore.net,49841,1378337278470,
> region=10359edcfb1a761f94ab6d5b559c2278, current state from region state map
> ={10359edcfb1a761f94ab6d5b559c2278 state=OPENING, ts=1378337305025,
> server=kiyo.gq1.ygridcore.net,49841,1378337278470}
> 2013-09-04 23:28:25,132 INFO [AM.ZK.Worker-pool2-t6]
> master.RegionStates(263): Transitioned from {10359edcfb1a761f94ab6d5b559c2278
> state=OPENING, ts=1378337305025,
> server=kiyo.gq1.ygridcore.net,49841,1378337278470} to
> {10359edcfb1a761f94ab6d5b559c2278 state=OPEN, ts=1378337305132,
> server=kiyo.gq1.ygridcore.net,49841,1378337278470}
> 2013-09-04 23:28:25,132 DEBUG [AM.ZK.Worker-pool2-t6]
> handler.OpenedRegionHandler(150): Handling OPENED event for
> 10359edcfb1a761f94ab6d5b559c2278 from
> kiyo.gq1.ygridcore.net,49841,1378337278470; deleting unassigned node
> 2013-09-04 23:28:25,132 DEBUG [AM.ZK.Worker-pool2-t6]
> zookeeper.ZKAssign(405): master:37502-0x140eb4dc4ef Deleting existing
> unassigned node 10359edcfb1a761f94ab6d5b559c2278 in expected state
> RS_ZK_REGION_OPENED
> 2013-09-04 23:28:25,188 INFO [pool-1-thread-1] hbase.ResourceChecker(171):
> after: master.TestRegionPlacement#testRegionPlacement Thread=873 (was 814)
> Potentially hanging thread: RS_OPEN_REGION-kiyo:53373-2
> ...
> - Thread LEAK? -, OpenFileDescriptor=1061 (was 1033) - OpenFileDescriptor
> LEAK? -, MaxFileDescriptor=32768 (was 32768), SystemLoadAverage=549 (was
> 609), ProcessCount=489 (was 489), AvailableMemoryMB=9288 (was 9107) -
> AvailableMemoryMB LEAK? -, ConnectionCount=23 (was 22) - ConnectionCount
> LEAK? -
> 2013-09-04 23:28:25,189 WARN [pool-1-thread-1] hbase.ResourceChecker(134):
> Thread=873 is superior to 500
> 2013-09-04 23:28:25,190 WARN [pool-1-thread-1] hbase.ResourceChecker(134):
> OpenFileDescriptor=1061 is superior to 1024
> 2013-09-04 23:28:25,223 DEBUG [pool-1-thread-1-EventThread]
> zookeeper.ZooKeeperWatcher(312): master:37502-0x140eb4dc4ef Received
> ZooKeeper Event, type=NodeDeleted, state=SyncConnected,
> path=/hbase/region-in-transition/10359edcfb1a761f94ab6d5b559c2278
> 2013-09-04 23:28:25,224 DEBUG [pool-1-thread-1-EventThread]
> zookeeper.ZooKeeperWatcher(312): master:37502-0x140eb4dc4ef Received
> ZooKeeper Event, type=NodeChildrenChanged, state=SyncConnected,
> path=/hbase/region-in-transition
> 2013-09-04 23:28:25,224 DEBUG [AM.ZK.Worker-pool2-t6]
> zookeeper.ZKAssign(434): master:37502-0x140eb4dc4ef Deleted unassigned
> node 10359edcfb1a761f94ab6d5b559c2278 in expected state RS_ZK_REGION_OPENED
> 2013-09-04 23:28:25,225 DEBUG [AM.ZK.
[jira] [Updated] (HBASE-9376) TestDistributedLogSplitting creates a MiniCluster rooted at ~/hbase
[ https://issues.apache.org/jira/browse/HBASE-9376?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jeffrey Zhong updated HBASE-9376: - Attachment: hbase-9376.patch This issue is caused by an early optimization where we only restart MiniHBaseCluster while still keep around MiniDFSCluster and MiniZKCluster to cut off the start up & tear down overhead. But during the optimization, we don't reuse original conf which start minidfscluster, so the tests inside the suite use local file system not MiniDFSCluster. > TestDistributedLogSplitting creates a MiniCluster rooted at ~/hbase > --- > > Key: HBASE-9376 > URL: https://issues.apache.org/jira/browse/HBASE-9376 > Project: HBase > Issue Type: Test > Components: test >Affects Versions: 0.95.2 >Reporter: Nick Dimiduk >Priority: Minor > Attachments: hbase-9376.patch > > > TestDistributedLogSplitting creates a MiniCluster rooted at ~/hbase. I have a > machine configured such that my $HOME is NFS mounted, and this combination > makes for a rather flakey test. Test cluster(s) instantiated by this test > should instead root out of target (like all the rest). -- 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-9441) Intermittent TestRegionPlacement#testRegionPlacement failure
[
https://issues.apache.org/jira/browse/HBASE-9441?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ted Yu updated HBASE-9441:
--
Attachment: 9441-v1.txt
Patch v1 waits for region transition to complete before obtaining region
placement report.
> Intermittent TestRegionPlacement#testRegionPlacement failure
>
>
> Key: HBASE-9441
> URL: https://issues.apache.org/jira/browse/HBASE-9441
> Project: HBase
> Issue Type: Test
>Reporter: Ted Yu
>Assignee: Ted Yu
>Priority: Minor
> Attachments: 9441-v1.txt
>
>
> Occasionally TestRegionPlacement#testRegionPlacement fails due to no region
> found on secondary / tertiary region server.
> In the following test output, 10359edcfb1a761f94ab6d5b559c2278 was the region
> from the killed region server:
> {code}
> 2013-09-04 23:28:25,127 INFO [pool-1-thread-1] util.FSUtils(1878): Scan DFS
> for locality info takes 38 ms
> Region Assignment Verification for Table: testRegionAssignment
> Total regions : 10
> Total regions on favored nodes 10
> Total regions on PRIMARY region servers: 10
> Total regions on SECONDARY region servers: 0
> Total regions on TERTIARY region servers: 0
> ...
> 2013-09-04 23:28:25,130 DEBUG [pool-1-thread-1-EventThread]
> zookeeper.ZooKeeperWatcher(312): master:37502-0x140eb4dc4ef Received
> ZooKeeper Event, type=NodeDataChanged, state=SyncConnected,
> path=/hbase/region-in-transition/10359edcfb1a761f94ab6d5b559c2278
> 2013-09-04 23:28:25,130 DEBUG [RS_OPEN_REGION-kiyo:49841-1]
> zookeeper.ZKAssign(861): regionserver:49841-0x140eb4dc4ef0007 Transitioned
> node 10359edcfb1a761f94ab6d5b559c2278 from RS_ZK_REGION_OPENING to
> RS_ZK_REGION_OPENED
> 2013-09-04 23:28:25,131 DEBUG [RS_OPEN_REGION-kiyo:49841-1]
> handler.OpenRegionHandler(386): Transitioned 10359edcfb1a761f94ab6d5b559c2278
> to OPENED in zk on kiyo.gq1.ygridcore.net,49841,1378337278470
> 2013-09-04 23:28:25,131 DEBUG [RS_OPEN_REGION-kiyo:49841-1]
> handler.OpenRegionHandler(187): Opened
> hbase:namespace,,1378337284888.10359edcfb1a761f94ab6d5b559c2278. on
> kiyo.gq1.ygridcore.net,49841,1378337278470
> 2013-09-04 23:28:25,132 DEBUG [AM.ZK.Worker-pool2-t6]
> master.AssignmentManager(801): Handling transition=RS_ZK_REGION_OPENED,
> server=kiyo.gq1.ygridcore.net,49841,1378337278470,
> region=10359edcfb1a761f94ab6d5b559c2278, current state from region state map
> ={10359edcfb1a761f94ab6d5b559c2278 state=OPENING, ts=1378337305025,
> server=kiyo.gq1.ygridcore.net,49841,1378337278470}
> 2013-09-04 23:28:25,132 INFO [AM.ZK.Worker-pool2-t6]
> master.RegionStates(263): Transitioned from {10359edcfb1a761f94ab6d5b559c2278
> state=OPENING, ts=1378337305025,
> server=kiyo.gq1.ygridcore.net,49841,1378337278470} to
> {10359edcfb1a761f94ab6d5b559c2278 state=OPEN, ts=1378337305132,
> server=kiyo.gq1.ygridcore.net,49841,1378337278470}
> 2013-09-04 23:28:25,132 DEBUG [AM.ZK.Worker-pool2-t6]
> handler.OpenedRegionHandler(150): Handling OPENED event for
> 10359edcfb1a761f94ab6d5b559c2278 from
> kiyo.gq1.ygridcore.net,49841,1378337278470; deleting unassigned node
> 2013-09-04 23:28:25,132 DEBUG [AM.ZK.Worker-pool2-t6]
> zookeeper.ZKAssign(405): master:37502-0x140eb4dc4ef Deleting existing
> unassigned node 10359edcfb1a761f94ab6d5b559c2278 in expected state
> RS_ZK_REGION_OPENED
> 2013-09-04 23:28:25,188 INFO [pool-1-thread-1] hbase.ResourceChecker(171):
> after: master.TestRegionPlacement#testRegionPlacement Thread=873 (was 814)
> Potentially hanging thread: RS_OPEN_REGION-kiyo:53373-2
> ...
> - Thread LEAK? -, OpenFileDescriptor=1061 (was 1033) - OpenFileDescriptor
> LEAK? -, MaxFileDescriptor=32768 (was 32768), SystemLoadAverage=549 (was
> 609), ProcessCount=489 (was 489), AvailableMemoryMB=9288 (was 9107) -
> AvailableMemoryMB LEAK? -, ConnectionCount=23 (was 22) - ConnectionCount
> LEAK? -
> 2013-09-04 23:28:25,189 WARN [pool-1-thread-1] hbase.ResourceChecker(134):
> Thread=873 is superior to 500
> 2013-09-04 23:28:25,190 WARN [pool-1-thread-1] hbase.ResourceChecker(134):
> OpenFileDescriptor=1061 is superior to 1024
> 2013-09-04 23:28:25,223 DEBUG [pool-1-thread-1-EventThread]
> zookeeper.ZooKeeperWatcher(312): master:37502-0x140eb4dc4ef Received
> ZooKeeper Event, type=NodeDeleted, state=SyncConnected,
> path=/hbase/region-in-transition/10359edcfb1a761f94ab6d5b559c2278
> 2013-09-04 23:28:25,224 DEBUG [pool-1-thread-1-EventThread]
> zookeeper.ZooKeeperWatcher(312): master:37502-0x140eb4dc4ef Received
> ZooKeeper Event, type=NodeChildrenChanged, state=SyncConnected,
> path=/hbase/region-in-transition
> 2013-09-04 23:28:25,224 DEBUG [AM.ZK.Worker-pool2-t6]
> zookeeper.ZKAssign(434): master:37502-0x140eb4dc4ef Deleted unassigned
> node 10359edcfb1a761f94
[jira] [Assigned] (HBASE-9376) TestDistributedLogSplitting creates a MiniCluster rooted at ~/hbase
[ https://issues.apache.org/jira/browse/HBASE-9376?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jeffrey Zhong reassigned HBASE-9376: Assignee: Jeffrey Zhong > TestDistributedLogSplitting creates a MiniCluster rooted at ~/hbase > --- > > Key: HBASE-9376 > URL: https://issues.apache.org/jira/browse/HBASE-9376 > Project: HBase > Issue Type: Test > Components: test >Affects Versions: 0.95.2 >Reporter: Nick Dimiduk >Assignee: Jeffrey Zhong >Priority: Minor > Attachments: hbase-9376.patch > > > TestDistributedLogSplitting creates a MiniCluster rooted at ~/hbase. I have a > machine configured such that my $HOME is NFS mounted, and this combination > makes for a rather flakey test. Test cluster(s) instantiated by this test > should instead root out of target (like all the rest). -- 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-9414) start-hbase.cmd doesn't need the execute flag.
[ https://issues.apache.org/jira/browse/HBASE-9414?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13758606#comment-13758606 ] Hudson commented on HBASE-9414: --- FAILURE: Integrated in HBase-TRUNK #4467 (See [https://builds.apache.org/job/HBase-TRUNK/4467/]) HBASE-9414 start-hbase.cmd doesn't need the execute flag (stack: rev 1520162) * /hbase/trunk/hbase-assembly/src/main/assembly/components.xml > start-hbase.cmd doesn't need the execute flag. > -- > > Key: HBASE-9414 > URL: https://issues.apache.org/jira/browse/HBASE-9414 > Project: HBase > Issue Type: Bug >Affects Versions: 0.96.0 >Reporter: Jean-Marc Spaggiari >Assignee: stack >Priority: Trivial > Fix For: 0.98.0, 0.96.1 > > Attachments: 9414.txt > > > When you do start- and tabulation, since there start-hbase.cmd has the > execution flag, completion go only up to start-hbase. > We should remove the execution flag for this script. -- 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=13758609#comment-13758609
]
Hudson commented on HBASE-8930:
---
FAILURE: Integrated in HBase-TRUNK #4467 (See
[https://builds.apache.org/job/HBase-TRUNK/4467/])
HBASE-8930 Add missing file (larsh: rev 1520169)
*
/hbase/trunk/hbase-server/src/test/java/org/apache/hadoop/hbase/filter/TestInvocationRecordFilter.java
HBASE-8930 Filter evaluates KVs outside requested columns (Vasu Mariyala)
(larsh: rev 1520168)
*
/hbase/trunk/hbase-server/src/main/java/org/apache/hadoop/hbase/regionserver/ColumnTracker.java
*
/hbase/trunk/hbase-server/src/main/java/org/apache/hadoop/hbase/regionserver/ExplicitColumnTracker.java
*
/hbase/trunk/hbase-server/src/main/java/org/apache/hadoop/hbase/regionserver/ScanQueryMatcher.java
*
/hbase/trunk/hbase-server/src/main/java/org/apache/hadoop/hbase/regionserver/ScanWildcardColumnTracker.java
*
/hbase/trunk/hbase-server/src/test/java/org/apache/hadoop/hbase/regionserver/TestExplicitColumnTracker.java
*
/hbase/trunk/hbase-server/src/test/java/org/apache/hadoop/hbase/regionserver/TestScanWildcardColumnTracker.java
> 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
> Fix For: 0.98.0, 0.94.12, 0.96.1
>
> Attachments: 0.94-HBASE-8930.patch, 0.94-HBASE-8930-rev1.patch,
> 0.95-HBASE-8930.patch, 0.95-HBASE-8930-rev1.patch,
> 0.96-HBASE-8930-rev2.patch, 8930-0.94.txt, HBASE-8930.patch,
> HBASE-8930-rev1.patch, HBASE-8930-rev2.patch, HBASE-8930-rev3.patch,
> HBASE-8930-rev4.patch, HBASE-8930-rev5.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));
> // === INSER
[jira] [Created] (HBASE-9441) Intermittent TestRegionPlacement#testRegionPlacement failure
Ted Yu created HBASE-9441:
-
Summary: Intermittent TestRegionPlacement#testRegionPlacement
failure
Key: HBASE-9441
URL: https://issues.apache.org/jira/browse/HBASE-9441
Project: HBase
Issue Type: Test
Reporter: Ted Yu
Assignee: Ted Yu
Priority: Minor
Occasionally TestRegionPlacement#testRegionPlacement fails due to no region
found on secondary / tertiary region server.
In the following test output, 10359edcfb1a761f94ab6d5b559c2278 was the region
from the killed region server:
{code}
2013-09-04 23:28:25,127 INFO [pool-1-thread-1] util.FSUtils(1878): Scan DFS
for locality info takes 38 ms
Region Assignment Verification for Table: testRegionAssignment
Total regions : 10
Total regions on favored nodes 10
Total regions on PRIMARY region servers: 10
Total regions on SECONDARY region servers: 0
Total regions on TERTIARY region servers: 0
...
2013-09-04 23:28:25,130 DEBUG [pool-1-thread-1-EventThread]
zookeeper.ZooKeeperWatcher(312): master:37502-0x140eb4dc4ef Received
ZooKeeper Event, type=NodeDataChanged, state=SyncConnected,
path=/hbase/region-in-transition/10359edcfb1a761f94ab6d5b559c2278
2013-09-04 23:28:25,130 DEBUG [RS_OPEN_REGION-kiyo:49841-1]
zookeeper.ZKAssign(861): regionserver:49841-0x140eb4dc4ef0007 Transitioned node
10359edcfb1a761f94ab6d5b559c2278 from RS_ZK_REGION_OPENING to
RS_ZK_REGION_OPENED
2013-09-04 23:28:25,131 DEBUG [RS_OPEN_REGION-kiyo:49841-1]
handler.OpenRegionHandler(386): Transitioned 10359edcfb1a761f94ab6d5b559c2278
to OPENED in zk on kiyo.gq1.ygridcore.net,49841,1378337278470
2013-09-04 23:28:25,131 DEBUG [RS_OPEN_REGION-kiyo:49841-1]
handler.OpenRegionHandler(187): Opened
hbase:namespace,,1378337284888.10359edcfb1a761f94ab6d5b559c2278. on
kiyo.gq1.ygridcore.net,49841,1378337278470
2013-09-04 23:28:25,132 DEBUG [AM.ZK.Worker-pool2-t6]
master.AssignmentManager(801): Handling transition=RS_ZK_REGION_OPENED,
server=kiyo.gq1.ygridcore.net,49841,1378337278470,
region=10359edcfb1a761f94ab6d5b559c2278, current state from region state map
={10359edcfb1a761f94ab6d5b559c2278 state=OPENING, ts=1378337305025,
server=kiyo.gq1.ygridcore.net,49841,1378337278470}
2013-09-04 23:28:25,132 INFO [AM.ZK.Worker-pool2-t6] master.RegionStates(263):
Transitioned from {10359edcfb1a761f94ab6d5b559c2278 state=OPENING,
ts=1378337305025, server=kiyo.gq1.ygridcore.net,49841,1378337278470} to
{10359edcfb1a761f94ab6d5b559c2278 state=OPEN, ts=1378337305132,
server=kiyo.gq1.ygridcore.net,49841,1378337278470}
2013-09-04 23:28:25,132 DEBUG [AM.ZK.Worker-pool2-t6]
handler.OpenedRegionHandler(150): Handling OPENED event for
10359edcfb1a761f94ab6d5b559c2278 from
kiyo.gq1.ygridcore.net,49841,1378337278470; deleting unassigned node
2013-09-04 23:28:25,132 DEBUG [AM.ZK.Worker-pool2-t6] zookeeper.ZKAssign(405):
master:37502-0x140eb4dc4ef Deleting existing unassigned node
10359edcfb1a761f94ab6d5b559c2278 in expected state RS_ZK_REGION_OPENED
2013-09-04 23:28:25,188 INFO [pool-1-thread-1] hbase.ResourceChecker(171):
after: master.TestRegionPlacement#testRegionPlacement Thread=873 (was 814)
Potentially hanging thread: RS_OPEN_REGION-kiyo:53373-2
...
- Thread LEAK? -, OpenFileDescriptor=1061 (was 1033) - OpenFileDescriptor
LEAK? -, MaxFileDescriptor=32768 (was 32768), SystemLoadAverage=549 (was 609),
ProcessCount=489 (was 489), AvailableMemoryMB=9288 (was 9107) -
AvailableMemoryMB LEAK? -, ConnectionCount=23 (was 22) - ConnectionCount LEAK? -
2013-09-04 23:28:25,189 WARN [pool-1-thread-1] hbase.ResourceChecker(134):
Thread=873 is superior to 500
2013-09-04 23:28:25,190 WARN [pool-1-thread-1] hbase.ResourceChecker(134):
OpenFileDescriptor=1061 is superior to 1024
2013-09-04 23:28:25,223 DEBUG [pool-1-thread-1-EventThread]
zookeeper.ZooKeeperWatcher(312): master:37502-0x140eb4dc4ef Received
ZooKeeper Event, type=NodeDeleted, state=SyncConnected,
path=/hbase/region-in-transition/10359edcfb1a761f94ab6d5b559c2278
2013-09-04 23:28:25,224 DEBUG [pool-1-thread-1-EventThread]
zookeeper.ZooKeeperWatcher(312): master:37502-0x140eb4dc4ef Received
ZooKeeper Event, type=NodeChildrenChanged, state=SyncConnected,
path=/hbase/region-in-transition
2013-09-04 23:28:25,224 DEBUG [AM.ZK.Worker-pool2-t6] zookeeper.ZKAssign(434):
master:37502-0x140eb4dc4ef Deleted unassigned node
10359edcfb1a761f94ab6d5b559c2278 in expected state RS_ZK_REGION_OPENED
2013-09-04 23:28:25,225 DEBUG [AM.ZK.Worker-pool2-t6]
master.AssignmentManager$4(1276): Znode
hbase:namespace,,1378337284888.10359edcfb1a761f94ab6d5b559c2278. deleted,
state: {10359edcfb1a761f94ab6d5b559c2278 state=OPEN, ts=1378337305132,
server=kiyo.gq1.ygridcore.net,49841,1378337278470}
2013-09-04 23:28:25,225 INFO [AM.ZK.Worker-pool2-t6] master.RegionStates(299):
Onlined 10359edcfb1a761f94ab6d5b559c2278 on
kiyo.gq1.ygridcore.net,4984
[jira] [Commented] (HBASE-9429) Add back MetaScanner.allTableRegions(Configuration conf,byte[] tablename,boolean offlined) method
[ https://issues.apache.org/jira/browse/HBASE-9429?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13758605#comment-13758605 ] Hudson commented on HBASE-9429: --- FAILURE: Integrated in HBase-0.94 #1135 (See [https://builds.apache.org/job/HBase-0.94/1135/]) HBASE-9429 Add back MetaScanner.allTableRegions(Configuration conf,byte[] tablename,boolean offlined) method (larsh: rev 1520155) * /hbase/branches/0.94/src/main/java/org/apache/hadoop/hbase/client/MetaScanner.java > Add back MetaScanner.allTableRegions(Configuration conf,byte[] > tablename,boolean offlined) method > - > > Key: HBASE-9429 > URL: https://issues.apache.org/jira/browse/HBASE-9429 > Project: HBase > Issue Type: Bug > Components: Client >Affects Versions: 0.94.11 >Reporter: James Taylor >Assignee: Lars Hofhansl > Fix For: 0.94.12 > > > The MetaScanner.allTableRegions(Configuration conf,byte[] tablename,boolean > offlined) method was removed in 0.94.11. Please add it back for backward > compatibility. -- 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=13758607#comment-13758607
]
Hudson commented on HBASE-8930:
---
FAILURE: Integrated in HBase-0.94 #1135 (See
[https://builds.apache.org/job/HBase-0.94/1135/])
HBASE-8930 Filter evaluates KVs outside requested columns (Vasu Mariyala)
(larsh: rev 1520171)
*
/hbase/branches/0.94/src/main/java/org/apache/hadoop/hbase/regionserver/ColumnTracker.java
*
/hbase/branches/0.94/src/main/java/org/apache/hadoop/hbase/regionserver/ExplicitColumnTracker.java
*
/hbase/branches/0.94/src/main/java/org/apache/hadoop/hbase/regionserver/ScanQueryMatcher.java
*
/hbase/branches/0.94/src/main/java/org/apache/hadoop/hbase/regionserver/ScanWildcardColumnTracker.java
*
/hbase/branches/0.94/src/test/java/org/apache/hadoop/hbase/filter/TestInvocationRecordFilter.java
*
/hbase/branches/0.94/src/test/java/org/apache/hadoop/hbase/regionserver/TestExplicitColumnTracker.java
*
/hbase/branches/0.94/src/test/java/org/apache/hadoop/hbase/regionserver/TestScanWildcardColumnTracker.java
> 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
> Fix For: 0.98.0, 0.94.12, 0.96.1
>
> Attachments: 0.94-HBASE-8930.patch, 0.94-HBASE-8930-rev1.patch,
> 0.95-HBASE-8930.patch, 0.95-HBASE-8930-rev1.patch,
> 0.96-HBASE-8930-rev2.patch, 8930-0.94.txt, HBASE-8930.patch,
> HBASE-8930-rev1.patch, HBASE-8930-rev2.patch, HBASE-8930-rev3.patch,
> HBASE-8930-rev4.patch, HBASE-8930-rev5.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, Byt
[jira] [Commented] (HBASE-9412) Startup scripts create 2 .out files.
[
https://issues.apache.org/jira/browse/HBASE-9412?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13758608#comment-13758608
]
Hudson commented on HBASE-9412:
---
FAILURE: Integrated in HBase-TRUNK #4467 (See
[https://builds.apache.org/job/HBase-TRUNK/4467/])
HBASE-9412 Startup scripts create 2 .out files (stack: rev 1520165)
* /hbase/trunk/bin/hbase-daemon.sh
> Startup scripts create 2 .out files.
>
>
> Key: HBASE-9412
> URL: https://issues.apache.org/jira/browse/HBASE-9412
> Project: HBase
> Issue Type: Bug
> Components: scripts
>Affects Versions: 0.96.0
>Reporter: Jean-Marc Spaggiari
>Assignee: stack
>Priority: Minor
> Fix For: 0.98.0, 0.96.1
>
> Attachments: 9412.txt
>
>
> When start HBase with bin/start-hbase.sh, script creates 2 out files.
> {code}
> -rw-r--r-- 1 jmspaggiari jmspaggiari 0 Aug 31 15:38
> hbase-jmspaggiari-master-t430s.out
> -rw-r--r-- 1 jmspaggiari jmspaggiari 0 Aug 31 15:38
> hbase-jmspaggiari-master-t430s.out.1
> {code}
> Should create only one.
--
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-9421) Provide better error message when dropping non-existent namespace
[
https://issues.apache.org/jira/browse/HBASE-9421?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13758602#comment-13758602
]
Hudson commented on HBASE-9421:
---
FAILURE: Integrated in hbase-0.96-hadoop2 #5 (See
[https://builds.apache.org/job/hbase-0.96-hadoop2/5/])
HBASE-9421 Provide better error message when dropping non-existent namespace
(tedyu: rev 1520136)
*
/hbase/branches/0.96/hbase-server/src/main/java/org/apache/hadoop/hbase/master/TableNamespaceManager.java
> Provide better error message when dropping non-existent namespace
> -
>
> Key: HBASE-9421
> URL: https://issues.apache.org/jira/browse/HBASE-9421
> Project: HBase
> Issue Type: Bug
>Reporter: Ted Yu
>Assignee: Ted Yu
>Priority: Minor
> Fix For: 0.98.0, 0.96.0
>
> Attachments: 9421-v1.txt
>
>
> If a non-existent namespace is dropped, FileNotFoundException is thrown.
> There should be better error message like "namespace does not exist"
> {code}
> hbase(main):002:0> drop_namespace 'hi'
> ERROR: java.io.FileNotFoundException: File
> hdfs://h.com:8020/apps/hbase/data/data/hi does not exist.
> at
> org.apache.hadoop.hdfs.DistributedFileSystem.listStatusInternal(DistributedFileSystem.java:656)
> at
> org.apache.hadoop.hdfs.DistributedFileSystem.access$600(DistributedFileSystem.java:92)
> at
> org.apache.hadoop.hdfs.DistributedFileSystem$14.doCall(DistributedFileSystem.java:714)
> at
> org.apache.hadoop.hdfs.DistributedFileSystem$14.doCall(DistributedFileSystem.java:710)
> at
> org.apache.hadoop.fs.FileSystemLinkResolver.resolve(FileSystemLinkResolver.java:78)
> at
> org.apache.hadoop.hdfs.DistributedFileSystem.listStatus(DistributedFileSystem.java:710)
> at org.apache.hadoop.fs.FileSystem.listStatus(FileSystem.java:1478)
> at org.apache.hadoop.fs.FileSystem.listStatus(FileSystem.java:1518)
> at
> org.apache.hadoop.hbase.util.FSUtils.getLocalTableDirs(FSUtils.java:1316)
> at
> org.apache.hadoop.hbase.util.FSTableDescriptors.getByNamespace(FSTableDescriptors.java:222)
> at
> org.apache.hadoop.hbase.master.HMaster.listTableDescriptorsByNamespace(HMaster.java:3121)
> at
> org.apache.hadoop.hbase.master.TableNamespaceManager.remove(TableNamespaceManager.java:158)
> at
> org.apache.hadoop.hbase.master.HMaster.deleteNamespace(HMaster.java:3106)
> at
> org.apache.hadoop.hbase.master.HMaster.deleteNamespace(HMaster.java:3000)
> at
> org.apache.hadoop.hbase.protobuf.generated.MasterAdminProtos$MasterAdminService$2.callBlockingMethod(MasterAdminProtos.java:32902)
> at org.apache.hadoop.hbase.ipc.RpcServer.call(RpcServer.java:2147)
> at
> org.apache.hadoop.hbase.ipc.RpcServer$Handler.run(RpcServer.java:1854)
> Here is some help for this command:
> Drop the named namespace. The namespace must be empty.
> {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-9428) Regex filters are at least an order of magnitude slower since 0.94.3
[
https://issues.apache.org/jira/browse/HBASE-9428?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13758599#comment-13758599
]
Hudson commented on HBASE-9428:
---
FAILURE: Integrated in hbase-0.96-hadoop2 #5 (See
[https://builds.apache.org/job/hbase-0.96-hadoop2/5/])
HBASE-9428 Regex filters are at least an order of magnitude slower since 0.94.3
(larsh: rev 1520100)
*
/hbase/branches/0.96/hbase-client/src/main/java/org/apache/hadoop/hbase/filter/RegexStringComparator.java
> Regex filters are at least an order of magnitude slower since 0.94.3
>
>
> Key: HBASE-9428
> URL: https://issues.apache.org/jira/browse/HBASE-9428
> Project: HBase
> Issue Type: Bug
>Reporter: Jean-Daniel Cryans
>Assignee: Lars Hofhansl
> Fix For: 0.98.0, 0.94.12, 0.96.1
>
> Attachments: 9428-0.94.txt, 9428-trunk.txt
>
>
> I found this issue after debugging a performance problem on an OpenTSDB
> cluster, it was basically unusable after an upgrade from 0.94.2 to 0.94.6. It
> was caused by HBASE-7279 (ping [~lhofhansl]).
> The easiest way to see it is to run a simple 1 client PE:
> {noformat}
> $ ./bin/hbase org.apache.hadoop.hbase.PerformanceEvaluation sequentialWrite 1
> {noformat}
> Then in the shell do a filter scan (flush the table first and make sure if
> fits in your blockcache if you want stable numbers).
> Pre HBASE-7279:
> {noformat}
> hbase(main):028:0> scan 'TestTable', {FILTER => "(RowFilter (=,
> 'regexstring:055872') )"}
> ROW COLUMN+CELL
>
>
> 055872 column=info:data,
> timestamp=1378248850191, value=(blanked)
>
>
> 1 row(s) in 1.2780 seconds
> {noformat}
> Post HBASE-7279
> {noformat}
> hbase(main):037:0* scan 'TestTable', {FILTER => "(RowFilter (=,
> 'regexstring:055872') )"}
> ROW COLUMN+CELL
>
>
> 055872 column=info:data,
> timestamp=1378248850191, value=(blanked)
>
>
> 1 row(s) in 24.2940 seconds
> {noformat}
> I tried a bunch of 0.94, up to 0.94.11, and the tip of 0.96. They are all
> slow like this.
> It seems that since that jira went in we do a lot more row matching, and
> running the regex gets super expensive.
--
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-9414) start-hbase.cmd doesn't need the execute flag.
[ https://issues.apache.org/jira/browse/HBASE-9414?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13758598#comment-13758598 ] Hudson commented on HBASE-9414: --- FAILURE: Integrated in hbase-0.96-hadoop2 #5 (See [https://builds.apache.org/job/hbase-0.96-hadoop2/5/]) HBASE-9414 start-hbase.cmd doesn't need the execute flag (stack: rev 1520163) * /hbase/branches/0.96/hbase-assembly/src/main/assembly/components.xml > start-hbase.cmd doesn't need the execute flag. > -- > > Key: HBASE-9414 > URL: https://issues.apache.org/jira/browse/HBASE-9414 > Project: HBase > Issue Type: Bug >Affects Versions: 0.96.0 >Reporter: Jean-Marc Spaggiari >Assignee: stack >Priority: Trivial > Fix For: 0.98.0, 0.96.1 > > Attachments: 9414.txt > > > When you do start- and tabulation, since there start-hbase.cmd has the > execution flag, completion go only up to start-hbase. > We should remove the execution flag for this script. -- 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=13758601#comment-13758601
]
Hudson commented on HBASE-8930:
---
FAILURE: Integrated in hbase-0.96-hadoop2 #5 (See
[https://builds.apache.org/job/hbase-0.96-hadoop2/5/])
HBASE-8930 Filter evaluates KVs outside requested columns (Vasu Mariyala)
(larsh: rev 1520170)
*
/hbase/branches/0.96/hbase-server/src/main/java/org/apache/hadoop/hbase/regionserver/ColumnTracker.java
*
/hbase/branches/0.96/hbase-server/src/main/java/org/apache/hadoop/hbase/regionserver/ExplicitColumnTracker.java
*
/hbase/branches/0.96/hbase-server/src/main/java/org/apache/hadoop/hbase/regionserver/ScanQueryMatcher.java
*
/hbase/branches/0.96/hbase-server/src/main/java/org/apache/hadoop/hbase/regionserver/ScanWildcardColumnTracker.java
*
/hbase/branches/0.96/hbase-server/src/test/java/org/apache/hadoop/hbase/filter/TestInvocationRecordFilter.java
*
/hbase/branches/0.96/hbase-server/src/test/java/org/apache/hadoop/hbase/regionserver/TestExplicitColumnTracker.java
*
/hbase/branches/0.96/hbase-server/src/test/java/org/apache/hadoop/hbase/regionserver/TestScanWildcardColumnTracker.java
> 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
> Fix For: 0.98.0, 0.94.12, 0.96.1
>
> Attachments: 0.94-HBASE-8930.patch, 0.94-HBASE-8930-rev1.patch,
> 0.95-HBASE-8930.patch, 0.95-HBASE-8930-rev1.patch,
> 0.96-HBASE-8930-rev2.patch, 8930-0.94.txt, HBASE-8930.patch,
> HBASE-8930-rev1.patch, HBASE-8930-rev2.patch, HBASE-8930-rev3.patch,
> HBASE-8930-rev4.patch, HBASE-8930-rev5.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));
> // ==
[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=13758597#comment-13758597
]
Hudson commented on HBASE-9387:
---
FAILURE: Integrated in hbase-0.96-hadoop2 #5 (See
[https://builds.apache.org/job/hbase-0.96-hadoop2/5/])
HBASE-9387 Region could get lost during assignment (tedyu: rev 1520092)
*
/hbase/branches/0.96/hbase-server/src/main/java/org/apache/hadoop/hbase/regionserver/handler/OpenRegionHandler.java
*
/hbase/branches/0.96/hbase-server/src/test/java/org/apache/hadoop/hbase/MockRegionServerServices.java
*
/hbase/branches/0.96/hbase-server/src/test/java/org/apache/hadoop/hbase/TestFullLogReconstruction.java
*
/hbase/branches/0.96/hbase-server/src/test/java/org/apache/hadoop/hbase/regionserver/handler/TestOpenRegionHandler.java
> 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
> Fix For: 0.98.0, 0.96.0
>
> 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,
> 9387-v8.txt, 9387-v9.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-9412) Startup scripts create 2 .out files.
[
https://issues.apache.org/jira/browse/HBASE-9412?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13758600#comment-13758600
]
Hudson commented on HBASE-9412:
---
FAILURE: Integrated in hbase-0.96-hadoop2 #5 (See
[https://builds.apache.org/job/hbase-0.96-hadoop2/5/])
HBASE-9412 Startup scripts create 2 .out files (stack: rev 1520164)
* /hbase/branches/0.96/bin/hbase-daemon.sh
> Startup scripts create 2 .out files.
>
>
> Key: HBASE-9412
> URL: https://issues.apache.org/jira/browse/HBASE-9412
> Project: HBase
> Issue Type: Bug
> Components: scripts
>Affects Versions: 0.96.0
>Reporter: Jean-Marc Spaggiari
>Assignee: stack
>Priority: Minor
> Fix For: 0.98.0, 0.96.1
>
> Attachments: 9412.txt
>
>
> When start HBase with bin/start-hbase.sh, script creates 2 out files.
> {code}
> -rw-r--r-- 1 jmspaggiari jmspaggiari 0 Aug 31 15:38
> hbase-jmspaggiari-master-t430s.out
> -rw-r--r-- 1 jmspaggiari jmspaggiari 0 Aug 31 15:38
> hbase-jmspaggiari-master-t430s.out.1
> {code}
> Should create only one.
--
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-9438) Enhance hbase shell un/assign to take encoded region name
[ https://issues.apache.org/jira/browse/HBASE-9438?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13758583#comment-13758583 ] stack commented on HBASE-9438: -- ok +1 on commit to 0.96 and to trunk after fixing dup. > Enhance hbase shell un/assign to take encoded region name > - > > Key: HBASE-9438 > URL: https://issues.apache.org/jira/browse/HBASE-9438 > Project: HBase > Issue Type: Improvement > Components: shell >Reporter: Jimmy Xiang >Assignee: Jimmy Xiang >Priority: Minor > Fix For: 0.96.0 > > Attachments: trunk-9438.patch > > > Currently assign/unassign in hbase shell takes only region name. It is hard > to type the region name especially when there is some non-printable character. -- 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
]
stack updated HBASE-9387:
-
Resolution: Fixed
Status: Resolved (was: Patch Available)
Committed to 0.96 and trunk so resolving.
> 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
> Fix For: 0.98.0, 0.96.0
>
> 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,
> 9387-v8.txt, 9387-v9.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-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:all-tabpanel ] stack updated HBASE-9388: - Resolution: Fixed Assignee: Himanshu Vashishtha (was: Jean-Daniel Cryans) Hadoop Flags: Reviewed Status: Resolved (was: Patch Available) Makes sense [~himan...@cloudera.com] (that this state is not of your making -- that you are just continuing the pattern enforce upon you by the layers above). Committed to 0.96 and to trunk. > [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: Himanshu Vashishtha > Fix For: 0.98.0, 0.96.0 > > Attachments: HBase-9388.patch, HBASE-9388.patch, > ReplicationZnodesDump.png > > > 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] [Commented] (HBASE-8803) region_mover.rb should move multiple regions at a time
[ https://issues.apache.org/jira/browse/HBASE-8803?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13758580#comment-13758580 ] stack commented on HBASE-8803: -- This is an excellent improvement. There is the issue above that needs looking into where we seemingly do not restore node to its former state. Should also redo these scripts as pure java since they are critical functionality now but that could be done in another issue. Reading elsewhere [~jmspaggi] is resource constrained which probably explains why no progress here. > region_mover.rb should move multiple regions at a time > -- > > Key: HBASE-8803 > URL: https://issues.apache.org/jira/browse/HBASE-8803 > Project: HBase > Issue Type: Bug > Components: Usability >Affects Versions: 0.98.0, 0.94.8, 0.95.1 >Reporter: Jean-Marc Spaggiari >Assignee: Jean-Marc Spaggiari > Fix For: 0.98.0, 0.94.12, 0.96.0 > > Attachments: 8803v5.txt, HBASE-8803-v0-trunk.patch, > HBASE-8803-v1-0.94.patch, HBASE-8803-v1-trunk.patch, > HBASE-8803-v2-0.94.patch, HBASE-8803-v2-0.94.patch, HBASE-8803-v3-0.94.patch, > HBASE-8803-v4-0.94.patch, HBASE-8803-v4-trunk.patch > > Original Estimate: 48h > Remaining Estimate: 48h > > When there is many regions in a cluster, rolling_restart can take hours > because region_mover is moving the regions one by one. -- 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=13758578#comment-13758578 ] stack commented on HBASE-9401: -- +1 > 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-8912) [0.94] AssignmentManager throws IllegalStateException from PENDING_OPEN to OFFLINE
[
https://issues.apache.org/jira/browse/HBASE-8912?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13758564#comment-13758564
]
Enis Soztutar commented on HBASE-8912:
--
I think this is still very important to fix. I can take a look at it next week
or so, unless some AM expert wants to chime in and relieve me from the burden.
> [0.94] AssignmentManager throws IllegalStateException from PENDING_OPEN to
> OFFLINE
> --
>
> Key: HBASE-8912
> URL: https://issues.apache.org/jira/browse/HBASE-8912
> Project: HBase
> Issue Type: Bug
>Reporter: Enis Soztutar
> Fix For: 0.94.12
>
> Attachments: HBase-0.94 #1036 test - testRetrying [Jenkins].html
>
>
> AM throws this exception which subsequently causes the master to abort:
> {code}
> java.lang.IllegalStateException: Unexpected state :
> testRetrying,jjj,1372891751115.9b828792311001062a5ff4b1038fe33b.
> state=PENDING_OPEN, ts=1372891751912,
> server=hemera.apache.org,39064,1372891746132 .. Cannot transit it to OFFLINE.
> at
> org.apache.hadoop.hbase.master.AssignmentManager.setOfflineInZooKeeper(AssignmentManager.java:1879)
> at
> org.apache.hadoop.hbase.master.AssignmentManager.assign(AssignmentManager.java:1688)
> at
> org.apache.hadoop.hbase.master.AssignmentManager.assign(AssignmentManager.java:1424)
> at
> org.apache.hadoop.hbase.master.AssignmentManager.assign(AssignmentManager.java:1399)
> at
> org.apache.hadoop.hbase.master.AssignmentManager.assign(AssignmentManager.java:1394)
> at
> org.apache.hadoop.hbase.master.handler.ClosedRegionHandler.process(ClosedRegionHandler.java:105)
> at
> org.apache.hadoop.hbase.executor.EventHandler.run(EventHandler.java:175)
> at
> java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:895)
> at
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:918)
> at java.lang.Thread.run(Thread.java:662)
> {code}
> This exception trace is from the failing test TestMetaReaderEditor which is
> failing pretty frequently, but looking at the test code, I think this is not
> a test-only issue, but affects the main code path.
> https://builds.apache.org/job/HBase-0.94/1036/testReport/junit/org.apache.hadoop.hbase.catalog/TestMetaReaderEditor/testRetrying/
--
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-8803) region_mover.rb should move multiple regions at a time
[ https://issues.apache.org/jira/browse/HBASE-8803?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13758558#comment-13758558 ] Lars Hofhansl commented on HBASE-8803: -- > region_mover.rb should move multiple regions at a time > -- > > Key: HBASE-8803 > URL: https://issues.apache.org/jira/browse/HBASE-8803 > Project: HBase > Issue Type: Bug > Components: Usability >Affects Versions: 0.98.0, 0.94.8, 0.95.1 >Reporter: Jean-Marc Spaggiari >Assignee: Jean-Marc Spaggiari > Fix For: 0.98.0, 0.94.12, 0.96.0 > > Attachments: 8803v5.txt, HBASE-8803-v0-trunk.patch, > HBASE-8803-v1-0.94.patch, HBASE-8803-v1-trunk.patch, > HBASE-8803-v2-0.94.patch, HBASE-8803-v2-0.94.patch, HBASE-8803-v3-0.94.patch, > HBASE-8803-v4-0.94.patch, HBASE-8803-v4-trunk.patch > > Original Estimate: 48h > Remaining Estimate: 48h > > When there is many regions in a cluster, rolling_restart can take hours > because region_mover is moving the regions one by one. -- 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=13758557#comment-13758557 ] Himanshu Vashishtha commented on HBASE-9388: I was thinking of the same while redoing it... have methods to give list of znodes for these. But then, this binding of presentation and composition starts from the parent dump() API itself. If we need to make it functional programming oriented (which would be neat), I'd start from there. But then, we would be refactoring it, rather than fixing the current issue at hand. Please let me know if that's okay (refactoring a bit). Thanks. > [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, HBASE-9388.patch, > ReplicationZnodesDump.png > > > 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] [Updated] (HBASE-9438) Enhance hbase shell un/assign to take encoded region name
[ https://issues.apache.org/jira/browse/HBASE-9438?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jimmy Xiang updated HBASE-9438: --- Status: Open (was: Patch Available) > Enhance hbase shell un/assign to take encoded region name > - > > Key: HBASE-9438 > URL: https://issues.apache.org/jira/browse/HBASE-9438 > Project: HBase > Issue Type: Improvement > Components: shell >Reporter: Jimmy Xiang >Assignee: Jimmy Xiang >Priority: Minor > Fix For: 0.96.0 > > Attachments: trunk-9438.patch > > > Currently assign/unassign in hbase shell takes only region name. It is hard > to type the region name especially when there is some non-printable character. -- 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-9438) Enhance hbase shell un/assign to take encoded region name
[ https://issues.apache.org/jira/browse/HBASE-9438?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13758553#comment-13758553 ] Jimmy Xiang commented on HBASE-9438: We don't pass the encoded name to the master. If an encoded name is specified, we find the corresponding region in the client side at first, then pass its region name to the master. Sure, will fix the duplicated code. > Enhance hbase shell un/assign to take encoded region name > - > > Key: HBASE-9438 > URL: https://issues.apache.org/jira/browse/HBASE-9438 > Project: HBase > Issue Type: Improvement > Components: shell >Reporter: Jimmy Xiang >Assignee: Jimmy Xiang >Priority: Minor > Fix For: 0.96.0 > > Attachments: trunk-9438.patch > > > Currently assign/unassign in hbase shell takes only region name. It is hard > to type the region name especially when there is some non-printable character. -- 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-9438) Enhance hbase shell un/assign to take encoded region name
[ https://issues.apache.org/jira/browse/HBASE-9438?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13758550#comment-13758550 ] stack commented on HBASE-9438: -- Looks good except for the duplicated code in HBaseAdmin; fix? So, it is ok passing an encoded name only to the master? It will just use it? Does the assign/unassign in the master then figure whether it has been handed a regionname or an encoded name? > Enhance hbase shell un/assign to take encoded region name > - > > Key: HBASE-9438 > URL: https://issues.apache.org/jira/browse/HBASE-9438 > Project: HBase > Issue Type: Improvement > Components: shell >Reporter: Jimmy Xiang >Assignee: Jimmy Xiang >Priority: Minor > Fix For: 0.96.0 > > Attachments: trunk-9438.patch > > > Currently assign/unassign in hbase shell takes only region name. It is hard > to type the region name especially when there is some non-printable character. -- 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-9421) Provide better error message when dropping non-existent namespace
[
https://issues.apache.org/jira/browse/HBASE-9421?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13758545#comment-13758545
]
Hudson commented on HBASE-9421:
---
SUCCESS: Integrated in hbase-0.96 #10 (See
[https://builds.apache.org/job/hbase-0.96/10/])
HBASE-9421 Provide better error message when dropping non-existent namespace
(tedyu: rev 1520136)
*
/hbase/branches/0.96/hbase-server/src/main/java/org/apache/hadoop/hbase/master/TableNamespaceManager.java
> Provide better error message when dropping non-existent namespace
> -
>
> Key: HBASE-9421
> URL: https://issues.apache.org/jira/browse/HBASE-9421
> Project: HBase
> Issue Type: Bug
>Reporter: Ted Yu
>Assignee: Ted Yu
>Priority: Minor
> Fix For: 0.98.0, 0.96.0
>
> Attachments: 9421-v1.txt
>
>
> If a non-existent namespace is dropped, FileNotFoundException is thrown.
> There should be better error message like "namespace does not exist"
> {code}
> hbase(main):002:0> drop_namespace 'hi'
> ERROR: java.io.FileNotFoundException: File
> hdfs://h.com:8020/apps/hbase/data/data/hi does not exist.
> at
> org.apache.hadoop.hdfs.DistributedFileSystem.listStatusInternal(DistributedFileSystem.java:656)
> at
> org.apache.hadoop.hdfs.DistributedFileSystem.access$600(DistributedFileSystem.java:92)
> at
> org.apache.hadoop.hdfs.DistributedFileSystem$14.doCall(DistributedFileSystem.java:714)
> at
> org.apache.hadoop.hdfs.DistributedFileSystem$14.doCall(DistributedFileSystem.java:710)
> at
> org.apache.hadoop.fs.FileSystemLinkResolver.resolve(FileSystemLinkResolver.java:78)
> at
> org.apache.hadoop.hdfs.DistributedFileSystem.listStatus(DistributedFileSystem.java:710)
> at org.apache.hadoop.fs.FileSystem.listStatus(FileSystem.java:1478)
> at org.apache.hadoop.fs.FileSystem.listStatus(FileSystem.java:1518)
> at
> org.apache.hadoop.hbase.util.FSUtils.getLocalTableDirs(FSUtils.java:1316)
> at
> org.apache.hadoop.hbase.util.FSTableDescriptors.getByNamespace(FSTableDescriptors.java:222)
> at
> org.apache.hadoop.hbase.master.HMaster.listTableDescriptorsByNamespace(HMaster.java:3121)
> at
> org.apache.hadoop.hbase.master.TableNamespaceManager.remove(TableNamespaceManager.java:158)
> at
> org.apache.hadoop.hbase.master.HMaster.deleteNamespace(HMaster.java:3106)
> at
> org.apache.hadoop.hbase.master.HMaster.deleteNamespace(HMaster.java:3000)
> at
> org.apache.hadoop.hbase.protobuf.generated.MasterAdminProtos$MasterAdminService$2.callBlockingMethod(MasterAdminProtos.java:32902)
> at org.apache.hadoop.hbase.ipc.RpcServer.call(RpcServer.java:2147)
> at
> org.apache.hadoop.hbase.ipc.RpcServer$Handler.run(RpcServer.java:1854)
> Here is some help for this command:
> Drop the named namespace. The namespace must be empty.
> {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
