[jira] [Commented] (HBASE-14188) Read path optimizations after HBASE-11425 profiling
[
https://issues.apache.org/jira/browse/HBASE-14188?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14659579#comment-14659579
]
Hadoop QA commented on HBASE-14188:
---
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12748997/HBASE-14188.patch
against master branch at commit 5d2708f628d4718f6267e9da6c8cbafeda66f4fb.
ATTACHMENT ID: 12748997
{color:green}+1 @author{color}. The patch does not contain any @author
tags.
{color:green}+1 tests included{color}. The patch appears to include 4 new
or modified tests.
{color:green}+1 hadoop versions{color}. The patch compiles with all
supported hadoop versions (2.4.0 2.4.1 2.5.0 2.5.1 2.5.2 2.6.0 2.7.0)
{color:green}+1 javac{color}. The applied patch does not increase the
total number of javac compiler warnings.
{color:green}+1 protoc{color}. The applied patch does not increase the
total number of protoc compiler warnings.
{color:green}+1 javadoc{color}. The javadoc tool did not generate any
warning messages.
{color:green}+1 checkstyle{color}. The applied patch does not increase the
total number of checkstyle errors
{color:green}+1 findbugs{color}. The patch does not introduce any new
Findbugs (version 2.0.3) warnings.
{color:green}+1 release audit{color}. The applied patch does not increase
the total number of release audit warnings.
{color:green}+1 lineLengths{color}. The patch does not introduce lines
longer than 100
{color:green}+1 site{color}. The mvn post-site goal succeeds with this patch.
{color:red}-1 core tests{color}. The patch failed these unit tests:
org.apache.hadoop.hbase.io.hfile.bucket.TestBucketCache
Test results:
https://builds.apache.org/job/PreCommit-HBASE-Build/14988//testReport/
Release Findbugs (version 2.0.3)warnings:
https://builds.apache.org/job/PreCommit-HBASE-Build/14988//artifact/patchprocess/newFindbugsWarnings.html
Checkstyle Errors:
https://builds.apache.org/job/PreCommit-HBASE-Build/14988//artifact/patchprocess/checkstyle-aggregate.html
Console output:
https://builds.apache.org/job/PreCommit-HBASE-Build/14988//console
This message is automatically generated.
> Read path optimizations after HBASE-11425 profiling
> ---
>
> Key: HBASE-14188
> URL: https://issues.apache.org/jira/browse/HBASE-14188
> Project: HBase
> Issue Type: Sub-task
> Components: Scanners
>Reporter: ramkrishna.s.vasudevan
>Assignee: ramkrishna.s.vasudevan
> Attachments: HBASE-14188.patch, setSeqId.png
>
>
> This subtask deals with some improvments that can be done in the read path
> (scans) after the changes for HBASE-11425 went in.
> -> Avoid CellUtil.setSequenceId in hot path.
> -> Use BBUtils in the MultibyteBuff.
> -> Use ByteBuff.skip() API in HFileReader rather than
> MultiByteBuff.position().
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (HBASE-14178) regionserver blocks because of waiting for offsetLock
[
https://issues.apache.org/jira/browse/HBASE-14178?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14659576#comment-14659576
]
ramkrishna.s.vasudevan commented on HBASE-14178:
Okie. Agree for a TODO. +1 for adding a comment regarding this. +1.
> regionserver blocks because of waiting for offsetLock
> -
>
> Key: HBASE-14178
> URL: https://issues.apache.org/jira/browse/HBASE-14178
> Project: HBase
> Issue Type: Bug
> Components: regionserver
>Affects Versions: 0.98.6
>Reporter: Heng Chen
>Priority: Critical
> Fix For: 0.98.6
>
> Attachments: HBASE-14178-0.98.patch, HBASE-14178.patch,
> HBASE-14178_v1.patch, HBASE-14178_v2.patch, HBASE-14178_v3.patch,
> HBASE-14178_v4.patch, HBASE-14178_v5.patch, HBASE-14178_v6.patch, jstack
>
>
> My regionserver blocks, and all client rpc timeout.
> I print the regionserver's jstack, it seems a lot of threads were blocked
> for waiting offsetLock, detail infomation belows:
> PS: my table's block cache is off
> {code}
> "B.DefaultRpcServer.handler=2,queue=2,port=60020" #82 daemon prio=5 os_prio=0
> tid=0x01827000 nid=0x2cdc in Object.wait() [0x7f3831b72000]
>java.lang.Thread.State: WAITING (on object monitor)
> at java.lang.Object.wait(Native Method)
> at java.lang.Object.wait(Object.java:502)
> at org.apache.hadoop.hbase.util.IdLock.getLockEntry(IdLock.java:79)
> - locked <0x000773af7c18> (a
> org.apache.hadoop.hbase.util.IdLock$Entry)
> at
> org.apache.hadoop.hbase.io.hfile.HFileReaderV2.readBlock(HFileReaderV2.java:352)
> at
> org.apache.hadoop.hbase.io.hfile.HFileBlockIndex$BlockIndexReader.loadDataBlockWithScanInfo(HFileBlockIndex.java:253)
> at
> org.apache.hadoop.hbase.io.hfile.HFileReaderV2$AbstractScannerV2.seekTo(HFileReaderV2.java:524)
> at
> org.apache.hadoop.hbase.io.hfile.HFileReaderV2$AbstractScannerV2.reseekTo(HFileReaderV2.java:572)
> at
> org.apache.hadoop.hbase.regionserver.StoreFileScanner.reseekAtOrAfter(StoreFileScanner.java:257)
> at
> org.apache.hadoop.hbase.regionserver.StoreFileScanner.reseek(StoreFileScanner.java:173)
> at
> org.apache.hadoop.hbase.regionserver.NonLazyKeyValueScanner.doRealSeek(NonLazyKeyValueScanner.java:55)
> at
> org.apache.hadoop.hbase.regionserver.KeyValueHeap.generalizedSeek(KeyValueHeap.java:313)
> at
> org.apache.hadoop.hbase.regionserver.KeyValueHeap.requestSeek(KeyValueHeap.java:269)
> at
> org.apache.hadoop.hbase.regionserver.StoreScanner.reseek(StoreScanner.java:695)
> at
> org.apache.hadoop.hbase.regionserver.StoreScanner.seekAsDirection(StoreScanner.java:683)
> at
> org.apache.hadoop.hbase.regionserver.StoreScanner.next(StoreScanner.java:533)
> at
> org.apache.hadoop.hbase.regionserver.KeyValueHeap.next(KeyValueHeap.java:140)
> at
> org.apache.hadoop.hbase.regionserver.HRegion$RegionScannerImpl.populateResult(HRegion.java:3889)
> at
> org.apache.hadoop.hbase.regionserver.HRegion$RegionScannerImpl.nextInternal(HRegion.java:3969)
> at
> org.apache.hadoop.hbase.regionserver.HRegion$RegionScannerImpl.nextRaw(HRegion.java:3847)
> at
> org.apache.hadoop.hbase.regionserver.HRegion$RegionScannerImpl.next(HRegion.java:3820)
> - locked <0x0005e5c55ad0> (a
> org.apache.hadoop.hbase.regionserver.HRegion$RegionScannerImpl)
> at
> org.apache.hadoop.hbase.regionserver.HRegion$RegionScannerImpl.next(HRegion.java:3807)
> at org.apache.hadoop.hbase.regionserver.HRegion.get(HRegion.java:4779)
> at org.apache.hadoop.hbase.regionserver.HRegion.get(HRegion.java:4753)
> at
> org.apache.hadoop.hbase.regionserver.HRegionServer.get(HRegionServer.java:2916)
> at
> org.apache.hadoop.hbase.protobuf.generated.ClientProtos$ClientService$2.callBlockingMethod(ClientProtos.java:29583)
> at org.apache.hadoop.hbase.ipc.RpcServer.call(RpcServer.java:2027)
> at org.apache.hadoop.hbase.ipc.CallRunner.run(CallRunner.java:108)
> at
> org.apache.hadoop.hbase.ipc.RpcExecutor.consumerLoop(RpcExecutor.java:114)
> at org.apache.hadoop.hbase.ipc.RpcExecutor$1.run(RpcExecutor.java:94)
> at java.lang.Thread.run(Thread.java:745)
>Locked ownable synchronizers:
> - <0x0005e5c55c08> (a
> java.util.concurrent.locks.ReentrantLock$NonfairSync)
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Comment Edited] (HBASE-14178) regionserver blocks because of waiting for offsetLock
[
https://issues.apache.org/jira/browse/HBASE-14178?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14659574#comment-14659574
]
Duo Zhang edited comment on HBASE-14178 at 8/6/15 6:46 AM:
---
[~ram_krish] A bit strange but now, {{family.isBlockCacheEnabled}} only means
{{cacheDataOnRead}} ... {{cacheDataOnWrite}} and some other configurations such
as {{prefetchOnOpen}} are separated which means you can set them to {{true}}
and will take effect even if you explicitly call
{{family.setBlockCacheEnabled(false)}}. So theoretically even if you disable BC
at family level, it is still possible that we could find the block in BC...
was (Author: apache9):
[~ram_krish] A bit strange but now, {{family.isBlockCacheEnabled}} only means
{{cacheDataOnRead }}... {{cacheDataOnWrite}} and some other configurations such
as {{prefetchOnOpen}} are separated which means you can set them to {{true}}
and will take effect even if you explicitly call
{{family.setBlockCacheEnabled(false)}}. So theoretically even if you disable BC
at family level, it is still possible that we could find the block in BC...
> regionserver blocks because of waiting for offsetLock
> -
>
> Key: HBASE-14178
> URL: https://issues.apache.org/jira/browse/HBASE-14178
> Project: HBase
> Issue Type: Bug
> Components: regionserver
>Affects Versions: 0.98.6
>Reporter: Heng Chen
>Priority: Critical
> Fix For: 0.98.6
>
> Attachments: HBASE-14178-0.98.patch, HBASE-14178.patch,
> HBASE-14178_v1.patch, HBASE-14178_v2.patch, HBASE-14178_v3.patch,
> HBASE-14178_v4.patch, HBASE-14178_v5.patch, HBASE-14178_v6.patch, jstack
>
>
> My regionserver blocks, and all client rpc timeout.
> I print the regionserver's jstack, it seems a lot of threads were blocked
> for waiting offsetLock, detail infomation belows:
> PS: my table's block cache is off
> {code}
> "B.DefaultRpcServer.handler=2,queue=2,port=60020" #82 daemon prio=5 os_prio=0
> tid=0x01827000 nid=0x2cdc in Object.wait() [0x7f3831b72000]
>java.lang.Thread.State: WAITING (on object monitor)
> at java.lang.Object.wait(Native Method)
> at java.lang.Object.wait(Object.java:502)
> at org.apache.hadoop.hbase.util.IdLock.getLockEntry(IdLock.java:79)
> - locked <0x000773af7c18> (a
> org.apache.hadoop.hbase.util.IdLock$Entry)
> at
> org.apache.hadoop.hbase.io.hfile.HFileReaderV2.readBlock(HFileReaderV2.java:352)
> at
> org.apache.hadoop.hbase.io.hfile.HFileBlockIndex$BlockIndexReader.loadDataBlockWithScanInfo(HFileBlockIndex.java:253)
> at
> org.apache.hadoop.hbase.io.hfile.HFileReaderV2$AbstractScannerV2.seekTo(HFileReaderV2.java:524)
> at
> org.apache.hadoop.hbase.io.hfile.HFileReaderV2$AbstractScannerV2.reseekTo(HFileReaderV2.java:572)
> at
> org.apache.hadoop.hbase.regionserver.StoreFileScanner.reseekAtOrAfter(StoreFileScanner.java:257)
> at
> org.apache.hadoop.hbase.regionserver.StoreFileScanner.reseek(StoreFileScanner.java:173)
> at
> org.apache.hadoop.hbase.regionserver.NonLazyKeyValueScanner.doRealSeek(NonLazyKeyValueScanner.java:55)
> at
> org.apache.hadoop.hbase.regionserver.KeyValueHeap.generalizedSeek(KeyValueHeap.java:313)
> at
> org.apache.hadoop.hbase.regionserver.KeyValueHeap.requestSeek(KeyValueHeap.java:269)
> at
> org.apache.hadoop.hbase.regionserver.StoreScanner.reseek(StoreScanner.java:695)
> at
> org.apache.hadoop.hbase.regionserver.StoreScanner.seekAsDirection(StoreScanner.java:683)
> at
> org.apache.hadoop.hbase.regionserver.StoreScanner.next(StoreScanner.java:533)
> at
> org.apache.hadoop.hbase.regionserver.KeyValueHeap.next(KeyValueHeap.java:140)
> at
> org.apache.hadoop.hbase.regionserver.HRegion$RegionScannerImpl.populateResult(HRegion.java:3889)
> at
> org.apache.hadoop.hbase.regionserver.HRegion$RegionScannerImpl.nextInternal(HRegion.java:3969)
> at
> org.apache.hadoop.hbase.regionserver.HRegion$RegionScannerImpl.nextRaw(HRegion.java:3847)
> at
> org.apache.hadoop.hbase.regionserver.HRegion$RegionScannerImpl.next(HRegion.java:3820)
> - locked <0x0005e5c55ad0> (a
> org.apache.hadoop.hbase.regionserver.HRegion$RegionScannerImpl)
> at
> org.apache.hadoop.hbase.regionserver.HRegion$RegionScannerImpl.next(HRegion.java:3807)
> at org.apache.hadoop.hbase.regionserver.HRegion.get(HRegion.java:4779)
> at org.apache.hadoop.hbase.regionserver.HRegion.get(HRegion.java:4753)
> at
> org.apache.hadoop.hbase.regionserver.HRegionServer.get(HRegionServer.java:2916)
> at
> org.apache.hadoop.hbase.protobuf.generated.ClientProtos$ClientService$2.callBlockingMethod(ClientProtos.java:29
[jira] [Commented] (HBASE-14178) regionserver blocks because of waiting for offsetLock
[
https://issues.apache.org/jira/browse/HBASE-14178?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14659574#comment-14659574
]
Duo Zhang commented on HBASE-14178:
---
[~ram_krish] A bit strange but now, {{family.isBlockCacheEnabled}} only means
{{cacheDataOnRead }}... {{cacheDataOnWrite}} and some other configurations such
as {{prefetchOnOpen}} are separated which means you can set them to {{true}}
and will take effect even if you explicitly call
{{family.setBlockCacheEnabled(false)}}. So theoretically even if you disable BC
at family level, it is still possible that we could find the block in BC...
> regionserver blocks because of waiting for offsetLock
> -
>
> Key: HBASE-14178
> URL: https://issues.apache.org/jira/browse/HBASE-14178
> Project: HBase
> Issue Type: Bug
> Components: regionserver
>Affects Versions: 0.98.6
>Reporter: Heng Chen
>Priority: Critical
> Fix For: 0.98.6
>
> Attachments: HBASE-14178-0.98.patch, HBASE-14178.patch,
> HBASE-14178_v1.patch, HBASE-14178_v2.patch, HBASE-14178_v3.patch,
> HBASE-14178_v4.patch, HBASE-14178_v5.patch, HBASE-14178_v6.patch, jstack
>
>
> My regionserver blocks, and all client rpc timeout.
> I print the regionserver's jstack, it seems a lot of threads were blocked
> for waiting offsetLock, detail infomation belows:
> PS: my table's block cache is off
> {code}
> "B.DefaultRpcServer.handler=2,queue=2,port=60020" #82 daemon prio=5 os_prio=0
> tid=0x01827000 nid=0x2cdc in Object.wait() [0x7f3831b72000]
>java.lang.Thread.State: WAITING (on object monitor)
> at java.lang.Object.wait(Native Method)
> at java.lang.Object.wait(Object.java:502)
> at org.apache.hadoop.hbase.util.IdLock.getLockEntry(IdLock.java:79)
> - locked <0x000773af7c18> (a
> org.apache.hadoop.hbase.util.IdLock$Entry)
> at
> org.apache.hadoop.hbase.io.hfile.HFileReaderV2.readBlock(HFileReaderV2.java:352)
> at
> org.apache.hadoop.hbase.io.hfile.HFileBlockIndex$BlockIndexReader.loadDataBlockWithScanInfo(HFileBlockIndex.java:253)
> at
> org.apache.hadoop.hbase.io.hfile.HFileReaderV2$AbstractScannerV2.seekTo(HFileReaderV2.java:524)
> at
> org.apache.hadoop.hbase.io.hfile.HFileReaderV2$AbstractScannerV2.reseekTo(HFileReaderV2.java:572)
> at
> org.apache.hadoop.hbase.regionserver.StoreFileScanner.reseekAtOrAfter(StoreFileScanner.java:257)
> at
> org.apache.hadoop.hbase.regionserver.StoreFileScanner.reseek(StoreFileScanner.java:173)
> at
> org.apache.hadoop.hbase.regionserver.NonLazyKeyValueScanner.doRealSeek(NonLazyKeyValueScanner.java:55)
> at
> org.apache.hadoop.hbase.regionserver.KeyValueHeap.generalizedSeek(KeyValueHeap.java:313)
> at
> org.apache.hadoop.hbase.regionserver.KeyValueHeap.requestSeek(KeyValueHeap.java:269)
> at
> org.apache.hadoop.hbase.regionserver.StoreScanner.reseek(StoreScanner.java:695)
> at
> org.apache.hadoop.hbase.regionserver.StoreScanner.seekAsDirection(StoreScanner.java:683)
> at
> org.apache.hadoop.hbase.regionserver.StoreScanner.next(StoreScanner.java:533)
> at
> org.apache.hadoop.hbase.regionserver.KeyValueHeap.next(KeyValueHeap.java:140)
> at
> org.apache.hadoop.hbase.regionserver.HRegion$RegionScannerImpl.populateResult(HRegion.java:3889)
> at
> org.apache.hadoop.hbase.regionserver.HRegion$RegionScannerImpl.nextInternal(HRegion.java:3969)
> at
> org.apache.hadoop.hbase.regionserver.HRegion$RegionScannerImpl.nextRaw(HRegion.java:3847)
> at
> org.apache.hadoop.hbase.regionserver.HRegion$RegionScannerImpl.next(HRegion.java:3820)
> - locked <0x0005e5c55ad0> (a
> org.apache.hadoop.hbase.regionserver.HRegion$RegionScannerImpl)
> at
> org.apache.hadoop.hbase.regionserver.HRegion$RegionScannerImpl.next(HRegion.java:3807)
> at org.apache.hadoop.hbase.regionserver.HRegion.get(HRegion.java:4779)
> at org.apache.hadoop.hbase.regionserver.HRegion.get(HRegion.java:4753)
> at
> org.apache.hadoop.hbase.regionserver.HRegionServer.get(HRegionServer.java:2916)
> at
> org.apache.hadoop.hbase.protobuf.generated.ClientProtos$ClientService$2.callBlockingMethod(ClientProtos.java:29583)
> at org.apache.hadoop.hbase.ipc.RpcServer.call(RpcServer.java:2027)
> at org.apache.hadoop.hbase.ipc.CallRunner.run(CallRunner.java:108)
> at
> org.apache.hadoop.hbase.ipc.RpcExecutor.consumerLoop(RpcExecutor.java:114)
> at org.apache.hadoop.hbase.ipc.RpcExecutor$1.run(RpcExecutor.java:94)
> at java.lang.Thread.run(Thread.java:745)
>Locked ownable synchronizers:
> - <0x0005e5c55c08> (a
> java.util.concurrent.locks.ReentrantLock$NonfairSync)
> {code}
[jira] [Commented] (HBASE-6721) RegionServer Group based Assignment
[ https://issues.apache.org/jira/browse/HBASE-6721?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14659561#comment-14659561 ] Francis Liu commented on HBASE-6721: Thanks [~apurtell], that'd be great let me work on one. > RegionServer Group based Assignment > --- > > Key: HBASE-6721 > URL: https://issues.apache.org/jira/browse/HBASE-6721 > Project: HBase > Issue Type: New Feature >Reporter: Francis Liu >Assignee: Francis Liu > Attachments: 6721-master-webUI.patch, HBASE-6721-DesigDoc.pdf, > HBASE-6721-DesigDoc.pdf, HBASE-6721-DesigDoc.pdf, HBASE-6721-DesigDoc.pdf, > HBASE-6721_10.patch, HBASE-6721_11.patch, HBASE-6721_8.patch, > HBASE-6721_9.patch, HBASE-6721_9.patch, HBASE-6721_94.patch, > HBASE-6721_94.patch, HBASE-6721_94_2.patch, HBASE-6721_94_3.patch, > HBASE-6721_94_3.patch, HBASE-6721_94_4.patch, HBASE-6721_94_5.patch, > HBASE-6721_94_6.patch, HBASE-6721_94_7.patch, HBASE-6721_trunk.patch, > HBASE-6721_trunk.patch, HBASE-6721_trunk.patch, HBASE-6721_trunk1.patch, > HBASE-6721_trunk2.patch > > > In multi-tenant deployments of HBase, it is likely that a RegionServer will > be serving out regions from a number of different tables owned by various > client applications. Being able to group a subset of running RegionServers > and assign specific tables to it, provides a client application a level of > isolation and resource allocation. > The proposal essentially is to have an AssignmentManager which is aware of > RegionServer groups and assigns tables to region servers based on groupings. > Load balancing will occur on a per group basis as well. > This is essentially a simplification of the approach taken in HBASE-4120. See > attached document. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (HBASE-14178) regionserver blocks because of waiting for offsetLock
[
https://issues.apache.org/jira/browse/HBASE-14178?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14659560#comment-14659560
]
Anoop Sam John commented on HBASE-14178:
I see.. I get you now.. Basically we need it as 2 new methods in CacheConfig
so as to accommodate some of the issues in today's impl. Like we discussed,
when the CF level BC usage is explicitly disabled, we should honour that. In
such a case whatever be the value of cache on write or prefetch option, we
should not cache those data blocks.. Here in this patch, we try to stick with
the current behaviour. FIne.. We can correct them as part of another jira.
+1
Just add a TODO with some comments as we discussed here in these new methods
and well as old methods in CacheConfig. Which we need change as part of the
above fix.
> regionserver blocks because of waiting for offsetLock
> -
>
> Key: HBASE-14178
> URL: https://issues.apache.org/jira/browse/HBASE-14178
> Project: HBase
> Issue Type: Bug
> Components: regionserver
>Affects Versions: 0.98.6
>Reporter: Heng Chen
>Priority: Critical
> Fix For: 0.98.6
>
> Attachments: HBASE-14178-0.98.patch, HBASE-14178.patch,
> HBASE-14178_v1.patch, HBASE-14178_v2.patch, HBASE-14178_v3.patch,
> HBASE-14178_v4.patch, HBASE-14178_v5.patch, HBASE-14178_v6.patch, jstack
>
>
> My regionserver blocks, and all client rpc timeout.
> I print the regionserver's jstack, it seems a lot of threads were blocked
> for waiting offsetLock, detail infomation belows:
> PS: my table's block cache is off
> {code}
> "B.DefaultRpcServer.handler=2,queue=2,port=60020" #82 daemon prio=5 os_prio=0
> tid=0x01827000 nid=0x2cdc in Object.wait() [0x7f3831b72000]
>java.lang.Thread.State: WAITING (on object monitor)
> at java.lang.Object.wait(Native Method)
> at java.lang.Object.wait(Object.java:502)
> at org.apache.hadoop.hbase.util.IdLock.getLockEntry(IdLock.java:79)
> - locked <0x000773af7c18> (a
> org.apache.hadoop.hbase.util.IdLock$Entry)
> at
> org.apache.hadoop.hbase.io.hfile.HFileReaderV2.readBlock(HFileReaderV2.java:352)
> at
> org.apache.hadoop.hbase.io.hfile.HFileBlockIndex$BlockIndexReader.loadDataBlockWithScanInfo(HFileBlockIndex.java:253)
> at
> org.apache.hadoop.hbase.io.hfile.HFileReaderV2$AbstractScannerV2.seekTo(HFileReaderV2.java:524)
> at
> org.apache.hadoop.hbase.io.hfile.HFileReaderV2$AbstractScannerV2.reseekTo(HFileReaderV2.java:572)
> at
> org.apache.hadoop.hbase.regionserver.StoreFileScanner.reseekAtOrAfter(StoreFileScanner.java:257)
> at
> org.apache.hadoop.hbase.regionserver.StoreFileScanner.reseek(StoreFileScanner.java:173)
> at
> org.apache.hadoop.hbase.regionserver.NonLazyKeyValueScanner.doRealSeek(NonLazyKeyValueScanner.java:55)
> at
> org.apache.hadoop.hbase.regionserver.KeyValueHeap.generalizedSeek(KeyValueHeap.java:313)
> at
> org.apache.hadoop.hbase.regionserver.KeyValueHeap.requestSeek(KeyValueHeap.java:269)
> at
> org.apache.hadoop.hbase.regionserver.StoreScanner.reseek(StoreScanner.java:695)
> at
> org.apache.hadoop.hbase.regionserver.StoreScanner.seekAsDirection(StoreScanner.java:683)
> at
> org.apache.hadoop.hbase.regionserver.StoreScanner.next(StoreScanner.java:533)
> at
> org.apache.hadoop.hbase.regionserver.KeyValueHeap.next(KeyValueHeap.java:140)
> at
> org.apache.hadoop.hbase.regionserver.HRegion$RegionScannerImpl.populateResult(HRegion.java:3889)
> at
> org.apache.hadoop.hbase.regionserver.HRegion$RegionScannerImpl.nextInternal(HRegion.java:3969)
> at
> org.apache.hadoop.hbase.regionserver.HRegion$RegionScannerImpl.nextRaw(HRegion.java:3847)
> at
> org.apache.hadoop.hbase.regionserver.HRegion$RegionScannerImpl.next(HRegion.java:3820)
> - locked <0x0005e5c55ad0> (a
> org.apache.hadoop.hbase.regionserver.HRegion$RegionScannerImpl)
> at
> org.apache.hadoop.hbase.regionserver.HRegion$RegionScannerImpl.next(HRegion.java:3807)
> at org.apache.hadoop.hbase.regionserver.HRegion.get(HRegion.java:4779)
> at org.apache.hadoop.hbase.regionserver.HRegion.get(HRegion.java:4753)
> at
> org.apache.hadoop.hbase.regionserver.HRegionServer.get(HRegionServer.java:2916)
> at
> org.apache.hadoop.hbase.protobuf.generated.ClientProtos$ClientService$2.callBlockingMethod(ClientProtos.java:29583)
> at org.apache.hadoop.hbase.ipc.RpcServer.call(RpcServer.java:2027)
> at org.apache.hadoop.hbase.ipc.CallRunner.run(CallRunner.java:108)
> at
> org.apache.hadoop.hbase.ipc.RpcExecutor.consumerLoop(RpcExecutor.java:114)
> at org.apache.hadoop.hbase.ipc.RpcExecutor$1.run(RpcEx
[jira] [Commented] (HBASE-14178) regionserver blocks because of waiting for offsetLock
[
https://issues.apache.org/jira/browse/HBASE-14178?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14659558#comment-14659558
]
ramkrishna.s.vasudevan commented on HBASE-14178:
Reading thro the comments and the current code in CacheConfig, I think
{code}
if (cacheDataOnWrite) {
448 return true;
449 }
{code}
These conditions may really be not needed. As you are saying
isBlockCacheEnabled() wouild mean cacheDataOnRead is also true. (I think this
setting is going to be implemented per family only).
> regionserver blocks because of waiting for offsetLock
> -
>
> Key: HBASE-14178
> URL: https://issues.apache.org/jira/browse/HBASE-14178
> Project: HBase
> Issue Type: Bug
> Components: regionserver
>Affects Versions: 0.98.6
>Reporter: Heng Chen
>Priority: Critical
> Fix For: 0.98.6
>
> Attachments: HBASE-14178-0.98.patch, HBASE-14178.patch,
> HBASE-14178_v1.patch, HBASE-14178_v2.patch, HBASE-14178_v3.patch,
> HBASE-14178_v4.patch, HBASE-14178_v5.patch, HBASE-14178_v6.patch, jstack
>
>
> My regionserver blocks, and all client rpc timeout.
> I print the regionserver's jstack, it seems a lot of threads were blocked
> for waiting offsetLock, detail infomation belows:
> PS: my table's block cache is off
> {code}
> "B.DefaultRpcServer.handler=2,queue=2,port=60020" #82 daemon prio=5 os_prio=0
> tid=0x01827000 nid=0x2cdc in Object.wait() [0x7f3831b72000]
>java.lang.Thread.State: WAITING (on object monitor)
> at java.lang.Object.wait(Native Method)
> at java.lang.Object.wait(Object.java:502)
> at org.apache.hadoop.hbase.util.IdLock.getLockEntry(IdLock.java:79)
> - locked <0x000773af7c18> (a
> org.apache.hadoop.hbase.util.IdLock$Entry)
> at
> org.apache.hadoop.hbase.io.hfile.HFileReaderV2.readBlock(HFileReaderV2.java:352)
> at
> org.apache.hadoop.hbase.io.hfile.HFileBlockIndex$BlockIndexReader.loadDataBlockWithScanInfo(HFileBlockIndex.java:253)
> at
> org.apache.hadoop.hbase.io.hfile.HFileReaderV2$AbstractScannerV2.seekTo(HFileReaderV2.java:524)
> at
> org.apache.hadoop.hbase.io.hfile.HFileReaderV2$AbstractScannerV2.reseekTo(HFileReaderV2.java:572)
> at
> org.apache.hadoop.hbase.regionserver.StoreFileScanner.reseekAtOrAfter(StoreFileScanner.java:257)
> at
> org.apache.hadoop.hbase.regionserver.StoreFileScanner.reseek(StoreFileScanner.java:173)
> at
> org.apache.hadoop.hbase.regionserver.NonLazyKeyValueScanner.doRealSeek(NonLazyKeyValueScanner.java:55)
> at
> org.apache.hadoop.hbase.regionserver.KeyValueHeap.generalizedSeek(KeyValueHeap.java:313)
> at
> org.apache.hadoop.hbase.regionserver.KeyValueHeap.requestSeek(KeyValueHeap.java:269)
> at
> org.apache.hadoop.hbase.regionserver.StoreScanner.reseek(StoreScanner.java:695)
> at
> org.apache.hadoop.hbase.regionserver.StoreScanner.seekAsDirection(StoreScanner.java:683)
> at
> org.apache.hadoop.hbase.regionserver.StoreScanner.next(StoreScanner.java:533)
> at
> org.apache.hadoop.hbase.regionserver.KeyValueHeap.next(KeyValueHeap.java:140)
> at
> org.apache.hadoop.hbase.regionserver.HRegion$RegionScannerImpl.populateResult(HRegion.java:3889)
> at
> org.apache.hadoop.hbase.regionserver.HRegion$RegionScannerImpl.nextInternal(HRegion.java:3969)
> at
> org.apache.hadoop.hbase.regionserver.HRegion$RegionScannerImpl.nextRaw(HRegion.java:3847)
> at
> org.apache.hadoop.hbase.regionserver.HRegion$RegionScannerImpl.next(HRegion.java:3820)
> - locked <0x0005e5c55ad0> (a
> org.apache.hadoop.hbase.regionserver.HRegion$RegionScannerImpl)
> at
> org.apache.hadoop.hbase.regionserver.HRegion$RegionScannerImpl.next(HRegion.java:3807)
> at org.apache.hadoop.hbase.regionserver.HRegion.get(HRegion.java:4779)
> at org.apache.hadoop.hbase.regionserver.HRegion.get(HRegion.java:4753)
> at
> org.apache.hadoop.hbase.regionserver.HRegionServer.get(HRegionServer.java:2916)
> at
> org.apache.hadoop.hbase.protobuf.generated.ClientProtos$ClientService$2.callBlockingMethod(ClientProtos.java:29583)
> at org.apache.hadoop.hbase.ipc.RpcServer.call(RpcServer.java:2027)
> at org.apache.hadoop.hbase.ipc.CallRunner.run(CallRunner.java:108)
> at
> org.apache.hadoop.hbase.ipc.RpcExecutor.consumerLoop(RpcExecutor.java:114)
> at org.apache.hadoop.hbase.ipc.RpcExecutor$1.run(RpcExecutor.java:94)
> at java.lang.Thread.run(Thread.java:745)
>Locked ownable synchronizers:
> - <0x0005e5c55c08> (a
> java.util.concurrent.locks.ReentrantLock$NonfairSync)
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (HBASE-14169) API to refreshSuperUserGroupsConfiguration
[ https://issues.apache.org/jira/browse/HBASE-14169?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14659557#comment-14659557 ] Francis Liu commented on HBASE-14169: - Sounds good. I've updated the patch to check for system user. Also [~apurtell] and [~mbertozzi], Should I follow the same semantics to as acl table to propagate requests (ie use zk as a message bus), seemed a bit clunky and overly complicated to me for this particular case? I've uploaded a draft which sends the rpc request to the master and the master propagates it to the RSes, since the master has the list of online servers on-hand. I haven't read how ProcedureV2 plans to propagate messages. So let me know what would work best. > API to refreshSuperUserGroupsConfiguration > -- > > Key: HBASE-14169 > URL: https://issues.apache.org/jira/browse/HBASE-14169 > Project: HBase > Issue Type: New Feature >Reporter: Francis Liu >Assignee: Francis Liu > Attachments: HBASE-14169.patch, HBASE-14169_2.patch > > > For deployments that use security. User impersonation (AKA doAs()) is needed > for some services (ie Stargate, thriftserver, Oozie, etc). Impersonation > definitions are defined in a xml config file and read and cached by the > ProxyUsers class. Calling this api will refresh cached information, > eliminating the need to restart the master/regionserver whenever the > configuration is changed. > Implementation just adds another method to AccessControlService. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (HBASE-14085) Correct LICENSE and NOTICE files in artifacts
[
https://issues.apache.org/jira/browse/HBASE-14085?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14659556#comment-14659556
]
Hudson commented on HBASE-14085:
FAILURE: Integrated in HBase-0.98 #1067 (See
[https://builds.apache.org/job/HBase-0.98/1067/])
HBASE-14085 Update LICENSE and NOTICE files. (apurtell: rev
edc48c10f2fba231c146aeb26a37adc3540e9d60)
* hbase-thrift/pom.xml
* hbase-thrift/src/main/appended-resources/META-INF/LICENSE
* LICENSE.txt
* hbase-thrift/src/test/resources/META-INF/NOTICE
* hbase-common/src/test/resources/META-INF/NOTICE
* hbase-common/pom.xml
* hbase-assembly/pom.xml
* pom.xml
* hbase-thrift/src/main/appended-resources/META-INF/NOTICE
* hbase-annotations/pom.xml
* hbase-common/src/main/appended-resources/META-INF/NOTICE
* hbase-examples/pom.xml
* hbase-shell/pom.xml
* hbase-server/pom.xml
* hbase-testing-util/pom.xml
* hbase-resource-bundle/src/main/resources/supplemental-models.xml
* hbase-it/pom.xml
* hbase-rest/pom.xml
* hbase-assembly/src/main/resources/META-INF/LEGAL
* hbase-assembly/src/main/assembly/components.xml
* hbase-resource-bundle/src/main/resources/META-INF/LICENSE.vm
* hbase-assembly/src/main/assembly/hadoop-two-compat.xml
* hbase-resource-bundle/pom.xml
* hbase-checkstyle/pom.xml
* hbase-hadoop-compat/pom.xml
* hbase-client/pom.xml
* hbase-resource-bundle/src/main/resources/META-INF/NOTICE.vm
* hbase-thrift/src/test/resources/META-INF/LICENSE
* hbase-server/src/test/resources/META-INF/LICENSE
* hbase-server/src/test/resources/META-INF/NOTICE
* hbase-hadoop2-compat/pom.xml
* hbase-protocol/pom.xml
* NOTICE.txt
* hbase-prefix-tree/pom.xml
> Correct LICENSE and NOTICE files in artifacts
> -
>
> Key: HBASE-14085
> URL: https://issues.apache.org/jira/browse/HBASE-14085
> Project: HBase
> Issue Type: Task
> Components: build
>Affects Versions: 2.0.0, 0.94.28, 0.98.14, 1.0.2, 1.2.0, 1.1.2, 1.3.0
>Reporter: Sean Busbey
>Assignee: Sean Busbey
>Priority: Blocker
> Fix For: 2.0.0, 0.94.28, 0.98.14, 1.0.2, 1.2.0, 1.1.2
>
> Attachments: HBASE-14085.1.patch, HBASE-14085.2.patch,
> HBASE-14085.3.patch
>
>
> +Problems:
> * checked LICENSE/NOTICE on binary
> ** binary artifact LICENSE file has not been updated to include the
> additional license terms for contained third party dependencies
> ** binary artifact NOTICE file does not include a copyright line
> ** binary artifact NOTICE file does not appear to propagate appropriate info
> from the NOTICE files from bundled dependencies
> * checked NOTICE on source
> ** source artifact NOTICE file does not include a copyright line
> ** source NOTICE file includes notices for third party dependencies not
> included in the artifact
> * checked NOTICE files shipped in maven jars
> ** copyright line only says 2015 when it's very likely the contents are under
> copyright prior to this year
> * nit: NOTICE file on jars in maven say "HBase - ${module}" rather than
> "Apache HBase - ${module}" as required
> refs:
> http://www.apache.org/dev/licensing-howto.html#bundled-vs-non-bundled
> http://www.apache.org/dev/licensing-howto.html#binary
> http://www.apache.org/dev/licensing-howto.html#simple
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (HBASE-14178) regionserver blocks because of waiting for offsetLock
[
https://issues.apache.org/jira/browse/HBASE-14178?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14659553#comment-14659553
]
Heng Chen commented on HBASE-14178:
---
{quote}
Why we need different condition for reading from the cache with and with out
lock? with out lock we do at first , as an optimistic approach. If block is not
there by then, we are doing one more round of check for a possible another
concurrent thread doing the caching of this block. So we use lock then. So am
not sure whether to read from cache why it has to have different condition.
Looks like the patch tend to make an impression that we will read from cache
with lock in order to cache that block into the BC. But it is not the case.
Sorry if I missed some other discussion parts in above comments
{quote}
Thanks for your reply!
The lock purpose is to improve the perf when other thread read same block. If
we make sure the block is not in BC, there is no need to lock. So in
{{shouldLockOnCacheMiss}} , we will check if the block will be cached after
read from hdfs.
> regionserver blocks because of waiting for offsetLock
> -
>
> Key: HBASE-14178
> URL: https://issues.apache.org/jira/browse/HBASE-14178
> Project: HBase
> Issue Type: Bug
> Components: regionserver
>Affects Versions: 0.98.6
>Reporter: Heng Chen
>Priority: Critical
> Fix For: 0.98.6
>
> Attachments: HBASE-14178-0.98.patch, HBASE-14178.patch,
> HBASE-14178_v1.patch, HBASE-14178_v2.patch, HBASE-14178_v3.patch,
> HBASE-14178_v4.patch, HBASE-14178_v5.patch, HBASE-14178_v6.patch, jstack
>
>
> My regionserver blocks, and all client rpc timeout.
> I print the regionserver's jstack, it seems a lot of threads were blocked
> for waiting offsetLock, detail infomation belows:
> PS: my table's block cache is off
> {code}
> "B.DefaultRpcServer.handler=2,queue=2,port=60020" #82 daemon prio=5 os_prio=0
> tid=0x01827000 nid=0x2cdc in Object.wait() [0x7f3831b72000]
>java.lang.Thread.State: WAITING (on object monitor)
> at java.lang.Object.wait(Native Method)
> at java.lang.Object.wait(Object.java:502)
> at org.apache.hadoop.hbase.util.IdLock.getLockEntry(IdLock.java:79)
> - locked <0x000773af7c18> (a
> org.apache.hadoop.hbase.util.IdLock$Entry)
> at
> org.apache.hadoop.hbase.io.hfile.HFileReaderV2.readBlock(HFileReaderV2.java:352)
> at
> org.apache.hadoop.hbase.io.hfile.HFileBlockIndex$BlockIndexReader.loadDataBlockWithScanInfo(HFileBlockIndex.java:253)
> at
> org.apache.hadoop.hbase.io.hfile.HFileReaderV2$AbstractScannerV2.seekTo(HFileReaderV2.java:524)
> at
> org.apache.hadoop.hbase.io.hfile.HFileReaderV2$AbstractScannerV2.reseekTo(HFileReaderV2.java:572)
> at
> org.apache.hadoop.hbase.regionserver.StoreFileScanner.reseekAtOrAfter(StoreFileScanner.java:257)
> at
> org.apache.hadoop.hbase.regionserver.StoreFileScanner.reseek(StoreFileScanner.java:173)
> at
> org.apache.hadoop.hbase.regionserver.NonLazyKeyValueScanner.doRealSeek(NonLazyKeyValueScanner.java:55)
> at
> org.apache.hadoop.hbase.regionserver.KeyValueHeap.generalizedSeek(KeyValueHeap.java:313)
> at
> org.apache.hadoop.hbase.regionserver.KeyValueHeap.requestSeek(KeyValueHeap.java:269)
> at
> org.apache.hadoop.hbase.regionserver.StoreScanner.reseek(StoreScanner.java:695)
> at
> org.apache.hadoop.hbase.regionserver.StoreScanner.seekAsDirection(StoreScanner.java:683)
> at
> org.apache.hadoop.hbase.regionserver.StoreScanner.next(StoreScanner.java:533)
> at
> org.apache.hadoop.hbase.regionserver.KeyValueHeap.next(KeyValueHeap.java:140)
> at
> org.apache.hadoop.hbase.regionserver.HRegion$RegionScannerImpl.populateResult(HRegion.java:3889)
> at
> org.apache.hadoop.hbase.regionserver.HRegion$RegionScannerImpl.nextInternal(HRegion.java:3969)
> at
> org.apache.hadoop.hbase.regionserver.HRegion$RegionScannerImpl.nextRaw(HRegion.java:3847)
> at
> org.apache.hadoop.hbase.regionserver.HRegion$RegionScannerImpl.next(HRegion.java:3820)
> - locked <0x0005e5c55ad0> (a
> org.apache.hadoop.hbase.regionserver.HRegion$RegionScannerImpl)
> at
> org.apache.hadoop.hbase.regionserver.HRegion$RegionScannerImpl.next(HRegion.java:3807)
> at org.apache.hadoop.hbase.regionserver.HRegion.get(HRegion.java:4779)
> at org.apache.hadoop.hbase.regionserver.HRegion.get(HRegion.java:4753)
> at
> org.apache.hadoop.hbase.regionserver.HRegionServer.get(HRegionServer.java:2916)
> at
> org.apache.hadoop.hbase.protobuf.generated.ClientProtos$ClientService$2.callBlockingMethod(ClientProtos.java:29583)
> at org.apache.hadoop.hbase.ipc.RpcServer.call(RpcS
[jira] [Updated] (HBASE-14169) API to refreshSuperUserGroupsConfiguration
[ https://issues.apache.org/jira/browse/HBASE-14169?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Francis Liu updated HBASE-14169: Attachment: HBASE-14169_2.patch > API to refreshSuperUserGroupsConfiguration > -- > > Key: HBASE-14169 > URL: https://issues.apache.org/jira/browse/HBASE-14169 > Project: HBase > Issue Type: New Feature >Reporter: Francis Liu >Assignee: Francis Liu > Attachments: HBASE-14169.patch, HBASE-14169_2.patch > > > For deployments that use security. User impersonation (AKA doAs()) is needed > for some services (ie Stargate, thriftserver, Oozie, etc). Impersonation > definitions are defined in a xml config file and read and cached by the > ProxyUsers class. Calling this api will refresh cached information, > eliminating the need to restart the master/regionserver whenever the > configuration is changed. > Implementation just adds another method to AccessControlService. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (HBASE-14188) Read path optimizations after HBASE-11425 profiling
[ https://issues.apache.org/jira/browse/HBASE-14188?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14659535#comment-14659535 ] Anoop Sam John commented on HBASE-14188: Patch LGTM getNextCellStartPosition -> Now it is not returning the next cell's start pos. It is returning cur cell serialization size in the HFile.. Pls change the method name accordingly. Can fix on commit. > Read path optimizations after HBASE-11425 profiling > --- > > Key: HBASE-14188 > URL: https://issues.apache.org/jira/browse/HBASE-14188 > Project: HBase > Issue Type: Sub-task > Components: Scanners >Reporter: ramkrishna.s.vasudevan >Assignee: ramkrishna.s.vasudevan > Attachments: HBASE-14188.patch, setSeqId.png > > > This subtask deals with some improvments that can be done in the read path > (scans) after the changes for HBASE-11425 went in. > -> Avoid CellUtil.setSequenceId in hot path. > -> Use BBUtils in the MultibyteBuff. > -> Use ByteBuff.skip() API in HFileReader rather than > MultiByteBuff.position(). -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (HBASE-14178) regionserver blocks because of waiting for offsetLock
[
https://issues.apache.org/jira/browse/HBASE-14178?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14659524#comment-14659524
]
Duo Zhang commented on HBASE-14178:
---
Yes, we doing more round of check with lock because maybe another thread has
already cache the block for us. Things happen here is we disable BC for the
given family, so it is impossible that another thread will do the work for us,
so we just read from HDFS and bypass the second checking BC round.
And as I mentioned above, there are lots of configurations for BC, and
{{family.isBlockCacheEnabled()}} is treated as {{cacheDataOnRead}} (You can see
the code pasted by [~chenheng], maybe it is a mistake but it is not important
for this issue I think, we could open another issue for it). So the safe way to
determine if we need the second 'read BC with lock' round is to check if we
will put the block back to BC after we read it from HDFS. This is why we
introduce a {{shouldLockOnCacheMiss}} method here. Maybe we cound change the
name to {{shouldReadAgainWithLockOnCacheMiss}}?
Thanks.
> regionserver blocks because of waiting for offsetLock
> -
>
> Key: HBASE-14178
> URL: https://issues.apache.org/jira/browse/HBASE-14178
> Project: HBase
> Issue Type: Bug
> Components: regionserver
>Affects Versions: 0.98.6
>Reporter: Heng Chen
>Priority: Critical
> Fix For: 0.98.6
>
> Attachments: HBASE-14178-0.98.patch, HBASE-14178.patch,
> HBASE-14178_v1.patch, HBASE-14178_v2.patch, HBASE-14178_v3.patch,
> HBASE-14178_v4.patch, HBASE-14178_v5.patch, HBASE-14178_v6.patch, jstack
>
>
> My regionserver blocks, and all client rpc timeout.
> I print the regionserver's jstack, it seems a lot of threads were blocked
> for waiting offsetLock, detail infomation belows:
> PS: my table's block cache is off
> {code}
> "B.DefaultRpcServer.handler=2,queue=2,port=60020" #82 daemon prio=5 os_prio=0
> tid=0x01827000 nid=0x2cdc in Object.wait() [0x7f3831b72000]
>java.lang.Thread.State: WAITING (on object monitor)
> at java.lang.Object.wait(Native Method)
> at java.lang.Object.wait(Object.java:502)
> at org.apache.hadoop.hbase.util.IdLock.getLockEntry(IdLock.java:79)
> - locked <0x000773af7c18> (a
> org.apache.hadoop.hbase.util.IdLock$Entry)
> at
> org.apache.hadoop.hbase.io.hfile.HFileReaderV2.readBlock(HFileReaderV2.java:352)
> at
> org.apache.hadoop.hbase.io.hfile.HFileBlockIndex$BlockIndexReader.loadDataBlockWithScanInfo(HFileBlockIndex.java:253)
> at
> org.apache.hadoop.hbase.io.hfile.HFileReaderV2$AbstractScannerV2.seekTo(HFileReaderV2.java:524)
> at
> org.apache.hadoop.hbase.io.hfile.HFileReaderV2$AbstractScannerV2.reseekTo(HFileReaderV2.java:572)
> at
> org.apache.hadoop.hbase.regionserver.StoreFileScanner.reseekAtOrAfter(StoreFileScanner.java:257)
> at
> org.apache.hadoop.hbase.regionserver.StoreFileScanner.reseek(StoreFileScanner.java:173)
> at
> org.apache.hadoop.hbase.regionserver.NonLazyKeyValueScanner.doRealSeek(NonLazyKeyValueScanner.java:55)
> at
> org.apache.hadoop.hbase.regionserver.KeyValueHeap.generalizedSeek(KeyValueHeap.java:313)
> at
> org.apache.hadoop.hbase.regionserver.KeyValueHeap.requestSeek(KeyValueHeap.java:269)
> at
> org.apache.hadoop.hbase.regionserver.StoreScanner.reseek(StoreScanner.java:695)
> at
> org.apache.hadoop.hbase.regionserver.StoreScanner.seekAsDirection(StoreScanner.java:683)
> at
> org.apache.hadoop.hbase.regionserver.StoreScanner.next(StoreScanner.java:533)
> at
> org.apache.hadoop.hbase.regionserver.KeyValueHeap.next(KeyValueHeap.java:140)
> at
> org.apache.hadoop.hbase.regionserver.HRegion$RegionScannerImpl.populateResult(HRegion.java:3889)
> at
> org.apache.hadoop.hbase.regionserver.HRegion$RegionScannerImpl.nextInternal(HRegion.java:3969)
> at
> org.apache.hadoop.hbase.regionserver.HRegion$RegionScannerImpl.nextRaw(HRegion.java:3847)
> at
> org.apache.hadoop.hbase.regionserver.HRegion$RegionScannerImpl.next(HRegion.java:3820)
> - locked <0x0005e5c55ad0> (a
> org.apache.hadoop.hbase.regionserver.HRegion$RegionScannerImpl)
> at
> org.apache.hadoop.hbase.regionserver.HRegion$RegionScannerImpl.next(HRegion.java:3807)
> at org.apache.hadoop.hbase.regionserver.HRegion.get(HRegion.java:4779)
> at org.apache.hadoop.hbase.regionserver.HRegion.get(HRegion.java:4753)
> at
> org.apache.hadoop.hbase.regionserver.HRegionServer.get(HRegionServer.java:2916)
> at
> org.apache.hadoop.hbase.protobuf.generated.ClientProtos$ClientService$2.callBlockingMethod(ClientProtos.java:29583)
> at org.apache.hadoop.hbase.ipc.RpcServer.call
[jira] [Commented] (HBASE-13965) Stochastic Load Balancer JMX Metrics
[ https://issues.apache.org/jira/browse/HBASE-13965?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14659522#comment-14659522 ] Hudson commented on HBASE-13965: FAILURE: Integrated in HBase-1.3 #90 (See [https://builds.apache.org/job/HBase-1.3/90/]) HBASE-13965 Stochastic Load Balancer JMX Metrics (Lei Chen) (tedyu: rev 6a2b618d97c13320bb91a5f555827437099e3a26) * hbase-common/src/main/java/org/apache/hadoop/hbase/HConstants.java * hbase-server/src/main/java/org/apache/hadoop/hbase/master/balancer/MetricsStochasticBalancer.java * hbase-server/src/main/java/org/apache/hadoop/hbase/master/RegionStates.java * hbase-server/src/main/java/org/apache/hadoop/hbase/master/balancer/BaseLoadBalancer.java * hbase-server/src/test/java/org/apache/hadoop/hbase/TestStochasticBalancerJmxMetrics.java * hbase-hadoop2-compat/src/main/resources/META-INF/services/org.apache.hadoop.hbase.master.balancer.MetricsStochasticBalancerSource * hbase-server/src/main/java/org/apache/hadoop/hbase/master/balancer/SimpleLoadBalancer.java * hbase-server/src/main/java/org/apache/hadoop/hbase/master/balancer/StochasticLoadBalancer.java * hbase-server/src/test/java/org/apache/hadoop/hbase/master/TestAssignmentManager.java * hbase-server/src/main/java/org/apache/hadoop/hbase/master/HMaster.java * hbase-server/src/main/java/org/apache/hadoop/hbase/master/balancer/MetricsBalancer.java * hbase-hadoop2-compat/src/main/java/org/apache/hadoop/hbase/master/balancer/MetricsStochasticBalancerSourceImpl.java * hbase-server/src/main/java/org/apache/hadoop/hbase/master/LoadBalancer.java * hbase-hadoop-compat/src/main/java/org/apache/hadoop/hbase/master/balancer/MetricsStochasticBalancerSource.java * hbase-server/src/test/java/org/apache/hadoop/hbase/master/balancer/TestBaseLoadBalancer.java * hbase-server/src/main/java/org/apache/hadoop/hbase/master/balancer/FavoredNodeLoadBalancer.java > Stochastic Load Balancer JMX Metrics > > > Key: HBASE-13965 > URL: https://issues.apache.org/jira/browse/HBASE-13965 > Project: HBase > Issue Type: Improvement > Components: Balancer, metrics >Reporter: Lei Chen >Assignee: Lei Chen > Fix For: 2.0.0 > > Attachments: 13965-addendum.txt, HBASE-13965-branch-1-v2.patch, > HBASE-13965-branch-1.patch, HBASE-13965-v10.patch, HBASE-13965-v11.patch, > HBASE-13965-v3.patch, HBASE-13965-v4.patch, HBASE-13965-v5.patch, > HBASE-13965-v6.patch, HBASE-13965-v7.patch, HBASE-13965-v8.patch, > HBASE-13965-v9.patch, HBASE-13965_v2.patch, HBase-13965-JConsole.png, > HBase-13965-v1.patch, stochasticloadbalancerclasses_v2.png > > > Today’s default HBase load balancer (the Stochastic load balancer) is cost > function based. The cost function weights are tunable but no visibility into > those cost function results is directly provided. > A driving example is a cluster we have been tuning which has skewed rack size > (one rack has half the nodes of the other few racks). We are tuning the > cluster for uniform response time from all region servers with the ability to > tolerate a rack failure. Balancing LocalityCost, RegionReplicaRack Cost and > RegionCountSkew Cost is difficult without a way to attribute each cost > function’s contribution to overall cost. > What this jira proposes is to provide visibility via JMX into each cost > function of the stochastic load balancer, as well as the overall cost of the > balancing plan. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (HBASE-14021) Quota table has a wrong description on the UI
[ https://issues.apache.org/jira/browse/HBASE-14021?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ashish Singhi updated HBASE-14021: -- Attachment: HBASE-14021branch-1.1.patch Patch for branch-1.1 > Quota table has a wrong description on the UI > - > > Key: HBASE-14021 > URL: https://issues.apache.org/jira/browse/HBASE-14021 > Project: HBase > Issue Type: Bug > Components: UI >Affects Versions: 1.1.0 >Reporter: Ashish Singhi >Assignee: Ashish Singhi >Priority: Minor > Fix For: 2.0.0, 1.3.0, 1.2.1 > > Attachments: HBASE-14021.patch, HBASE-14021.patch, > HBASE-14021branch-1.1.patch, error.png, fix.png > > > !error.png! -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (HBASE-14188) Read path optimizations after HBASE-11425 profiling
[ https://issues.apache.org/jira/browse/HBASE-14188?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] ramkrishna.s.vasudevan updated HBASE-14188: --- Attachment: HBASE-14188.patch Patch that avoids setSequenceId() and other minor improvements. After this patch the setSequenceId() no longer appears in the profiler. Previously before the HBASE-11425 changes we were calling this setSequenceId directly on the Keyvalue object. > Read path optimizations after HBASE-11425 profiling > --- > > Key: HBASE-14188 > URL: https://issues.apache.org/jira/browse/HBASE-14188 > Project: HBase > Issue Type: Sub-task > Components: Scanners >Reporter: ramkrishna.s.vasudevan >Assignee: ramkrishna.s.vasudevan > Attachments: HBASE-14188.patch, setSeqId.png > > > This subtask deals with some improvments that can be done in the read path > (scans) after the changes for HBASE-11425 went in. > -> Avoid CellUtil.setSequenceId in hot path. > -> Use BBUtils in the MultibyteBuff. > -> Use ByteBuff.skip() API in HFileReader rather than > MultiByteBuff.position(). -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (HBASE-14188) Read path optimizations after HBASE-11425 profiling
[ https://issues.apache.org/jira/browse/HBASE-14188?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] ramkrishna.s.vasudevan updated HBASE-14188: --- Status: Patch Available (was: Open) > Read path optimizations after HBASE-11425 profiling > --- > > Key: HBASE-14188 > URL: https://issues.apache.org/jira/browse/HBASE-14188 > Project: HBase > Issue Type: Sub-task > Components: Scanners >Reporter: ramkrishna.s.vasudevan >Assignee: ramkrishna.s.vasudevan > Attachments: HBASE-14188.patch, setSeqId.png > > > This subtask deals with some improvments that can be done in the read path > (scans) after the changes for HBASE-11425 went in. > -> Avoid CellUtil.setSequenceId in hot path. > -> Use BBUtils in the MultibyteBuff. > -> Use ByteBuff.skip() API in HFileReader rather than > MultiByteBuff.position(). -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (HBASE-14188) Read path optimizations after HBASE-11425 profiling
[ https://issues.apache.org/jira/browse/HBASE-14188?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] ramkrishna.s.vasudevan updated HBASE-14188: --- Attachment: setSeqId.png A profiler snapshot when using CellUtil.setSequenceId() in the hot path. > Read path optimizations after HBASE-11425 profiling > --- > > Key: HBASE-14188 > URL: https://issues.apache.org/jira/browse/HBASE-14188 > Project: HBase > Issue Type: Sub-task > Components: Scanners >Reporter: ramkrishna.s.vasudevan >Assignee: ramkrishna.s.vasudevan > Attachments: setSeqId.png > > > This subtask deals with some improvments that can be done in the read path > (scans) after the changes for HBASE-11425 went in. > -> Avoid CellUtil.setSequenceId in hot path. > -> Use BBUtils in the MultibyteBuff. > -> Use ByteBuff.skip() API in HFileReader rather than > MultiByteBuff.position(). -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (HBASE-14188) Read path optimizations after HBASE-11425 profiling
ramkrishna.s.vasudevan created HBASE-14188: -- Summary: Read path optimizations after HBASE-11425 profiling Key: HBASE-14188 URL: https://issues.apache.org/jira/browse/HBASE-14188 Project: HBase Issue Type: Sub-task Reporter: ramkrishna.s.vasudevan Assignee: ramkrishna.s.vasudevan This subtask deals with some improvments that can be done in the read path (scans) after the changes for HBASE-11425 went in. -> Avoid CellUtil.setSequenceId in hot path. -> Use BBUtils in the MultibyteBuff. -> Use ByteBuff.skip() API in HFileReader rather than MultiByteBuff.position(). -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (HBASE-13965) Stochastic Load Balancer JMX Metrics
[ https://issues.apache.org/jira/browse/HBASE-13965?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14659508#comment-14659508 ] Hudson commented on HBASE-13965: FAILURE: Integrated in HBase-1.3-IT #72 (See [https://builds.apache.org/job/HBase-1.3-IT/72/]) HBASE-13965 Stochastic Load Balancer JMX Metrics (Lei Chen) (tedyu: rev 6a2b618d97c13320bb91a5f555827437099e3a26) * hbase-server/src/main/java/org/apache/hadoop/hbase/master/balancer/SimpleLoadBalancer.java * hbase-server/src/main/java/org/apache/hadoop/hbase/master/balancer/FavoredNodeLoadBalancer.java * hbase-server/src/main/java/org/apache/hadoop/hbase/master/HMaster.java * hbase-server/src/main/java/org/apache/hadoop/hbase/master/LoadBalancer.java * hbase-hadoop-compat/src/main/java/org/apache/hadoop/hbase/master/balancer/MetricsStochasticBalancerSource.java * hbase-hadoop2-compat/src/main/java/org/apache/hadoop/hbase/master/balancer/MetricsStochasticBalancerSourceImpl.java * hbase-server/src/main/java/org/apache/hadoop/hbase/master/RegionStates.java * hbase-server/src/main/java/org/apache/hadoop/hbase/master/balancer/MetricsBalancer.java * hbase-server/src/test/java/org/apache/hadoop/hbase/TestStochasticBalancerJmxMetrics.java * hbase-common/src/main/java/org/apache/hadoop/hbase/HConstants.java * hbase-server/src/test/java/org/apache/hadoop/hbase/master/TestAssignmentManager.java * hbase-server/src/main/java/org/apache/hadoop/hbase/master/balancer/MetricsStochasticBalancer.java * hbase-server/src/test/java/org/apache/hadoop/hbase/master/balancer/TestBaseLoadBalancer.java * hbase-hadoop2-compat/src/main/resources/META-INF/services/org.apache.hadoop.hbase.master.balancer.MetricsStochasticBalancerSource * hbase-server/src/main/java/org/apache/hadoop/hbase/master/balancer/StochasticLoadBalancer.java * hbase-server/src/main/java/org/apache/hadoop/hbase/master/balancer/BaseLoadBalancer.java > Stochastic Load Balancer JMX Metrics > > > Key: HBASE-13965 > URL: https://issues.apache.org/jira/browse/HBASE-13965 > Project: HBase > Issue Type: Improvement > Components: Balancer, metrics >Reporter: Lei Chen >Assignee: Lei Chen > Fix For: 2.0.0 > > Attachments: 13965-addendum.txt, HBASE-13965-branch-1-v2.patch, > HBASE-13965-branch-1.patch, HBASE-13965-v10.patch, HBASE-13965-v11.patch, > HBASE-13965-v3.patch, HBASE-13965-v4.patch, HBASE-13965-v5.patch, > HBASE-13965-v6.patch, HBASE-13965-v7.patch, HBASE-13965-v8.patch, > HBASE-13965-v9.patch, HBASE-13965_v2.patch, HBase-13965-JConsole.png, > HBase-13965-v1.patch, stochasticloadbalancerclasses_v2.png > > > Today’s default HBase load balancer (the Stochastic load balancer) is cost > function based. The cost function weights are tunable but no visibility into > those cost function results is directly provided. > A driving example is a cluster we have been tuning which has skewed rack size > (one rack has half the nodes of the other few racks). We are tuning the > cluster for uniform response time from all region servers with the ability to > tolerate a rack failure. Balancing LocalityCost, RegionReplicaRack Cost and > RegionCountSkew Cost is difficult without a way to attribute each cost > function’s contribution to overall cost. > What this jira proposes is to provide visibility via JMX into each cost > function of the stochastic load balancer, as well as the overall cost of the > balancing plan. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (HBASE-5878) Use getVisibleLength public api from HdfsDataInputStream from Hadoop-2.
[
https://issues.apache.org/jira/browse/HBASE-5878?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14659496#comment-14659496
]
Ashish Singhi commented on HBASE-5878:
--
Done.
> Use getVisibleLength public api from HdfsDataInputStream from Hadoop-2.
> ---
>
> Key: HBASE-5878
> URL: https://issues.apache.org/jira/browse/HBASE-5878
> Project: HBase
> Issue Type: Bug
> Components: wal
>Reporter: Uma Maheswara Rao G
>Assignee: Ashish Singhi
> Fix For: 2.0.0, 1.1.2, 1.3.0, 1.2.1, 1.0.3
>
> Attachments: HBASE-5878-v2.patch, HBASE-5878-v3.patch,
> HBASE-5878-v4.patch, HBASE-5878-v5.patch, HBASE-5878-v5.patch,
> HBASE-5878.patch
>
>
> SequencFileLogReader:
> Currently Hbase using getFileLength api from DFSInputStream class by
> reflection. DFSInputStream is not exposed as public. So, this may change in
> future. Now HDFS exposed HdfsDataInputStream as public API.
> We can make use of it, when we are not able to find the getFileLength api
> from DFSInputStream as a else condition. So, that we will not have any sudden
> surprise like we are facing today.
> Also, it is just logging one warn message and proceeding if it throws any
> exception while getting the length. I think we can re-throw the exception
> because there is no point in continuing with dataloss.
> {code}
> long adjust = 0;
> try {
> Field fIn = FilterInputStream.class.getDeclaredField("in");
> fIn.setAccessible(true);
> Object realIn = fIn.get(this.in);
> // In hadoop 0.22, DFSInputStream is a standalone class. Before
> this,
> // it was an inner class of DFSClient.
> if (realIn.getClass().getName().endsWith("DFSInputStream")) {
> Method getFileLength = realIn.getClass().
> getDeclaredMethod("getFileLength", new Class []{});
> getFileLength.setAccessible(true);
> long realLength = ((Long)getFileLength.
> invoke(realIn, new Object []{})).longValue();
> assert(realLength >= this.length);
> adjust = realLength - this.length;
> } else {
> LOG.info("Input stream class: " + realIn.getClass().getName() +
> ", not adjusting length");
> }
> } catch(Exception e) {
> SequenceFileLogReader.LOG.warn(
> "Error while trying to get accurate file length. " +
> "Truncation / data loss may occur if RegionServers die.", e);
> }
> return adjust + super.getPos();
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (HBASE-14178) regionserver blocks because of waiting for offsetLock
[
https://issues.apache.org/jira/browse/HBASE-14178?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14659494#comment-14659494
]
Anoop Sam John commented on HBASE-14178:
Why we need different condition for reading from the cache with and with out
lock? with out lock we do at first , as an optimistic approach. If block is
not there by then, we are doing one more round of check for a possible another
concurrent thread doing the caching of this block. So we use lock then. So am
not sure whether to read from cache why it has to have different condition.
Looks like the patch tend to make an impression that we will read from cache
*with lock* in order to cache that block into the BC. But it is not the case.
Sorry if I missed some other discussion parts in above comments
> regionserver blocks because of waiting for offsetLock
> -
>
> Key: HBASE-14178
> URL: https://issues.apache.org/jira/browse/HBASE-14178
> Project: HBase
> Issue Type: Bug
> Components: regionserver
>Affects Versions: 0.98.6
>Reporter: Heng Chen
>Priority: Critical
> Fix For: 0.98.6
>
> Attachments: HBASE-14178-0.98.patch, HBASE-14178.patch,
> HBASE-14178_v1.patch, HBASE-14178_v2.patch, HBASE-14178_v3.patch,
> HBASE-14178_v4.patch, HBASE-14178_v5.patch, HBASE-14178_v6.patch, jstack
>
>
> My regionserver blocks, and all client rpc timeout.
> I print the regionserver's jstack, it seems a lot of threads were blocked
> for waiting offsetLock, detail infomation belows:
> PS: my table's block cache is off
> {code}
> "B.DefaultRpcServer.handler=2,queue=2,port=60020" #82 daemon prio=5 os_prio=0
> tid=0x01827000 nid=0x2cdc in Object.wait() [0x7f3831b72000]
>java.lang.Thread.State: WAITING (on object monitor)
> at java.lang.Object.wait(Native Method)
> at java.lang.Object.wait(Object.java:502)
> at org.apache.hadoop.hbase.util.IdLock.getLockEntry(IdLock.java:79)
> - locked <0x000773af7c18> (a
> org.apache.hadoop.hbase.util.IdLock$Entry)
> at
> org.apache.hadoop.hbase.io.hfile.HFileReaderV2.readBlock(HFileReaderV2.java:352)
> at
> org.apache.hadoop.hbase.io.hfile.HFileBlockIndex$BlockIndexReader.loadDataBlockWithScanInfo(HFileBlockIndex.java:253)
> at
> org.apache.hadoop.hbase.io.hfile.HFileReaderV2$AbstractScannerV2.seekTo(HFileReaderV2.java:524)
> at
> org.apache.hadoop.hbase.io.hfile.HFileReaderV2$AbstractScannerV2.reseekTo(HFileReaderV2.java:572)
> at
> org.apache.hadoop.hbase.regionserver.StoreFileScanner.reseekAtOrAfter(StoreFileScanner.java:257)
> at
> org.apache.hadoop.hbase.regionserver.StoreFileScanner.reseek(StoreFileScanner.java:173)
> at
> org.apache.hadoop.hbase.regionserver.NonLazyKeyValueScanner.doRealSeek(NonLazyKeyValueScanner.java:55)
> at
> org.apache.hadoop.hbase.regionserver.KeyValueHeap.generalizedSeek(KeyValueHeap.java:313)
> at
> org.apache.hadoop.hbase.regionserver.KeyValueHeap.requestSeek(KeyValueHeap.java:269)
> at
> org.apache.hadoop.hbase.regionserver.StoreScanner.reseek(StoreScanner.java:695)
> at
> org.apache.hadoop.hbase.regionserver.StoreScanner.seekAsDirection(StoreScanner.java:683)
> at
> org.apache.hadoop.hbase.regionserver.StoreScanner.next(StoreScanner.java:533)
> at
> org.apache.hadoop.hbase.regionserver.KeyValueHeap.next(KeyValueHeap.java:140)
> at
> org.apache.hadoop.hbase.regionserver.HRegion$RegionScannerImpl.populateResult(HRegion.java:3889)
> at
> org.apache.hadoop.hbase.regionserver.HRegion$RegionScannerImpl.nextInternal(HRegion.java:3969)
> at
> org.apache.hadoop.hbase.regionserver.HRegion$RegionScannerImpl.nextRaw(HRegion.java:3847)
> at
> org.apache.hadoop.hbase.regionserver.HRegion$RegionScannerImpl.next(HRegion.java:3820)
> - locked <0x0005e5c55ad0> (a
> org.apache.hadoop.hbase.regionserver.HRegion$RegionScannerImpl)
> at
> org.apache.hadoop.hbase.regionserver.HRegion$RegionScannerImpl.next(HRegion.java:3807)
> at org.apache.hadoop.hbase.regionserver.HRegion.get(HRegion.java:4779)
> at org.apache.hadoop.hbase.regionserver.HRegion.get(HRegion.java:4753)
> at
> org.apache.hadoop.hbase.regionserver.HRegionServer.get(HRegionServer.java:2916)
> at
> org.apache.hadoop.hbase.protobuf.generated.ClientProtos$ClientService$2.callBlockingMethod(ClientProtos.java:29583)
> at org.apache.hadoop.hbase.ipc.RpcServer.call(RpcServer.java:2027)
> at org.apache.hadoop.hbase.ipc.CallRunner.run(CallRunner.java:108)
> at
> org.apache.hadoop.hbase.ipc.RpcExecutor.consumerLoop(RpcExecutor.java:114)
> at org.apache.hadoop.hbase.ipc.RpcExecutor$1.run(RpcExecutor.java:94)
>
[jira] [Updated] (HBASE-14186) Read mvcc vlong optimization
[
https://issues.apache.org/jira/browse/HBASE-14186?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Anoop Sam John updated HBASE-14186:
---
Component/s: Performance
> Read mvcc vlong optimization
>
>
> Key: HBASE-14186
> URL: https://issues.apache.org/jira/browse/HBASE-14186
> Project: HBase
> Issue Type: Sub-task
> Components: Performance, Scanners
>Reporter: Anoop Sam John
>Assignee: Anoop Sam John
> Fix For: 2.0.0
>
> Attachments: HBASE-14186.patch
>
>
> {code}
> for (int idx = 0; idx < remaining; idx++) {
> byte b = blockBuffer.getByteAfterPosition(offsetFromPos + idx);
> i = i << 8;
> i = i | (b & 0xFF);
> }
> {code}
> Doing the read as in case of BIG_ENDIAN.
> After HBASE-12600, we tend to keep the mvcc and so byte by byte read looks
> eating up lot of CPU time. (In my test HFileReaderImpl#_readMvccVersion comes
> on top in terms of hot methods). We can optimize here by reading 4 or 2 bytes
> in one shot when the length of the vlong is more than 4 bytes. We will in
> turn use UnsafeAccess methods which handles ENDIAN.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (HBASE-14186) Read mvcc vlong optimization
[
https://issues.apache.org/jira/browse/HBASE-14186?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14659487#comment-14659487
]
Anoop Sam John commented on HBASE-14186:
Thanks for the review Stack. Pushed to master.
Do we need this in branch-1 as well? Seems HBASE-12600 is in all 1.x branches.
> Read mvcc vlong optimization
>
>
> Key: HBASE-14186
> URL: https://issues.apache.org/jira/browse/HBASE-14186
> Project: HBase
> Issue Type: Sub-task
> Components: Performance, Scanners
>Reporter: Anoop Sam John
>Assignee: Anoop Sam John
> Fix For: 2.0.0
>
> Attachments: HBASE-14186.patch
>
>
> {code}
> for (int idx = 0; idx < remaining; idx++) {
> byte b = blockBuffer.getByteAfterPosition(offsetFromPos + idx);
> i = i << 8;
> i = i | (b & 0xFF);
> }
> {code}
> Doing the read as in case of BIG_ENDIAN.
> After HBASE-12600, we tend to keep the mvcc and so byte by byte read looks
> eating up lot of CPU time. (In my test HFileReaderImpl#_readMvccVersion comes
> on top in terms of hot methods). We can optimize here by reading 4 or 2 bytes
> in one shot when the length of the vlong is more than 4 bytes. We will in
> turn use UnsafeAccess methods which handles ENDIAN.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (HBASE-13965) Stochastic Load Balancer JMX Metrics
[
https://issues.apache.org/jira/browse/HBASE-13965?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14659463#comment-14659463
]
Hadoop QA commented on HBASE-13965:
---
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12748968/HBASE-13965-branch-1-v2.patch
against branch-1 branch at commit 18c9bb8b54a5bb101f793e555272cbc74b8288cb.
ATTACHMENT ID: 12748968
{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 hadoop versions{color}. The patch compiles with all
supported hadoop versions (2.4.0 2.4.1 2.5.0 2.5.1 2.5.2 2.6.0 2.7.0)
{color:green}+1 javac{color}. The applied patch does not increase the
total number of javac compiler warnings.
{color:green}+1 protoc{color}. The applied patch does not increase the
total number of protoc compiler warnings.
{color:green}+1 javadoc{color}. The javadoc tool did not generate any
warning messages.
{color:green}+1 checkstyle{color}. The applied patch does not increase the
total number of checkstyle errors
{color:green}+1 findbugs{color}. The patch does not introduce any new
Findbugs (version 2.0.3) warnings.
{color:green}+1 release audit{color}. The applied patch does not increase
the total number of release audit warnings.
{color:green}+1 lineLengths{color}. The patch does not introduce lines
longer than 100
{color:green}+1 site{color}. The mvn post-site goal succeeds with this patch.
{color:red}-1 core tests{color}. The patch failed these unit tests:
org.apache.hadoop.hbase.util.TestProcessBasedCluster
org.apache.hadoop.hbase.mapreduce.TestImportExport
Test results:
https://builds.apache.org/job/PreCommit-HBASE-Build/14987//testReport/
Release Findbugs (version 2.0.3)warnings:
https://builds.apache.org/job/PreCommit-HBASE-Build/14987//artifact/patchprocess/newFindbugsWarnings.html
Checkstyle Errors:
https://builds.apache.org/job/PreCommit-HBASE-Build/14987//artifact/patchprocess/checkstyle-aggregate.html
Console output:
https://builds.apache.org/job/PreCommit-HBASE-Build/14987//console
This message is automatically generated.
> Stochastic Load Balancer JMX Metrics
>
>
> Key: HBASE-13965
> URL: https://issues.apache.org/jira/browse/HBASE-13965
> Project: HBase
> Issue Type: Improvement
> Components: Balancer, metrics
>Reporter: Lei Chen
>Assignee: Lei Chen
> Fix For: 2.0.0
>
> Attachments: 13965-addendum.txt, HBASE-13965-branch-1-v2.patch,
> HBASE-13965-branch-1.patch, HBASE-13965-v10.patch, HBASE-13965-v11.patch,
> HBASE-13965-v3.patch, HBASE-13965-v4.patch, HBASE-13965-v5.patch,
> HBASE-13965-v6.patch, HBASE-13965-v7.patch, HBASE-13965-v8.patch,
> HBASE-13965-v9.patch, HBASE-13965_v2.patch, HBase-13965-JConsole.png,
> HBase-13965-v1.patch, stochasticloadbalancerclasses_v2.png
>
>
> Today’s default HBase load balancer (the Stochastic load balancer) is cost
> function based. The cost function weights are tunable but no visibility into
> those cost function results is directly provided.
> A driving example is a cluster we have been tuning which has skewed rack size
> (one rack has half the nodes of the other few racks). We are tuning the
> cluster for uniform response time from all region servers with the ability to
> tolerate a rack failure. Balancing LocalityCost, RegionReplicaRack Cost and
> RegionCountSkew Cost is difficult without a way to attribute each cost
> function’s contribution to overall cost.
> What this jira proposes is to provide visibility via JMX into each cost
> function of the stochastic load balancer, as well as the overall cost of the
> balancing plan.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (HBASE-14085) Correct LICENSE and NOTICE files in artifacts
[
https://issues.apache.org/jira/browse/HBASE-14085?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14659391#comment-14659391
]
Sean Busbey commented on HBASE-14085:
-
If [~lhofhansl] is going to do another 0.94 release, I'll do a reworking of
this for that branch. here or another jira is fine, though having it here makes
it easier to refer generally to our licensing correction.
> Correct LICENSE and NOTICE files in artifacts
> -
>
> Key: HBASE-14085
> URL: https://issues.apache.org/jira/browse/HBASE-14085
> Project: HBase
> Issue Type: Task
> Components: build
>Affects Versions: 2.0.0, 0.94.28, 0.98.14, 1.0.2, 1.2.0, 1.1.2, 1.3.0
>Reporter: Sean Busbey
>Assignee: Sean Busbey
>Priority: Blocker
> Fix For: 2.0.0, 0.94.28, 0.98.14, 1.0.2, 1.2.0, 1.1.2
>
> Attachments: HBASE-14085.1.patch, HBASE-14085.2.patch,
> HBASE-14085.3.patch
>
>
> +Problems:
> * checked LICENSE/NOTICE on binary
> ** binary artifact LICENSE file has not been updated to include the
> additional license terms for contained third party dependencies
> ** binary artifact NOTICE file does not include a copyright line
> ** binary artifact NOTICE file does not appear to propagate appropriate info
> from the NOTICE files from bundled dependencies
> * checked NOTICE on source
> ** source artifact NOTICE file does not include a copyright line
> ** source NOTICE file includes notices for third party dependencies not
> included in the artifact
> * checked NOTICE files shipped in maven jars
> ** copyright line only says 2015 when it's very likely the contents are under
> copyright prior to this year
> * nit: NOTICE file on jars in maven say "HBase - ${module}" rather than
> "Apache HBase - ${module}" as required
> refs:
> http://www.apache.org/dev/licensing-howto.html#bundled-vs-non-bundled
> http://www.apache.org/dev/licensing-howto.html#binary
> http://www.apache.org/dev/licensing-howto.html#simple
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (HBASE-14085) Correct LICENSE and NOTICE files in artifacts
[
https://issues.apache.org/jira/browse/HBASE-14085?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14659390#comment-14659390
]
Hudson commented on HBASE-14085:
FAILURE: Integrated in HBase-1.1 #598 (See
[https://builds.apache.org/job/HBase-1.1/598/])
HBASE-14085 Update LICENSE and NOTICE files. (apurtell: rev
c6504fa825052a5947e03b3f5bc09147ebc7779f)
* hbase-common/src/main/appended-resources/META-INF/NOTICE
* hbase-checkstyle/pom.xml
* hbase-prefix-tree/pom.xml
* hbase-assembly/src/main/resources/META-INF/LEGAL
* hbase-shaded/hbase-shaded-server/pom.xml
* hbase-rest/pom.xml
* hbase-thrift/pom.xml
* hbase-assembly/src/main/assembly/components.xml
* hbase-assembly/pom.xml
* hbase-shell/pom.xml
* hbase-hadoop2-compat/pom.xml
* hbase-shaded/hbase-shaded-client/pom.xml
* hbase-thrift/src/main/appended-resources/META-INF/NOTICE
* hbase-resource-bundle/pom.xml
* hbase-assembly/src/main/assembly/hadoop-two-compat.xml
* pom.xml
* hbase-server/src/test/resources/META-INF/NOTICE
* hbase-resource-bundle/src/main/resources/META-INF/LICENSE.vm
* hbase-common/src/test/resources/META-INF/NOTICE
* hbase-resource-bundle/src/main/resources/META-INF/NOTICE.vm
* hbase-testing-util/pom.xml
* NOTICE.txt
* LICENSE.txt
* hbase-protocol/pom.xml
* hbase-thrift/src/test/resources/META-INF/LICENSE
* hbase-client/pom.xml
* hbase-annotations/pom.xml
* hbase-thrift/src/test/resources/META-INF/NOTICE
* hbase-thrift/src/main/appended-resources/META-INF/LICENSE
* hbase-server/pom.xml
* hbase-examples/pom.xml
* hbase-common/pom.xml
* hbase-hadoop-compat/pom.xml
* hbase-it/pom.xml
* hbase-shaded/pom.xml
* hbase-server/src/test/resources/META-INF/LICENSE
* hbase-procedure/pom.xml
* hbase-resource-bundle/src/main/resources/supplemental-models.xml
> Correct LICENSE and NOTICE files in artifacts
> -
>
> Key: HBASE-14085
> URL: https://issues.apache.org/jira/browse/HBASE-14085
> Project: HBase
> Issue Type: Task
> Components: build
>Affects Versions: 2.0.0, 0.94.28, 0.98.14, 1.0.2, 1.2.0, 1.1.2, 1.3.0
>Reporter: Sean Busbey
>Assignee: Sean Busbey
>Priority: Blocker
> Fix For: 2.0.0, 0.94.28, 0.98.14, 1.0.2, 1.2.0, 1.1.2
>
> Attachments: HBASE-14085.1.patch, HBASE-14085.2.patch,
> HBASE-14085.3.patch
>
>
> +Problems:
> * checked LICENSE/NOTICE on binary
> ** binary artifact LICENSE file has not been updated to include the
> additional license terms for contained third party dependencies
> ** binary artifact NOTICE file does not include a copyright line
> ** binary artifact NOTICE file does not appear to propagate appropriate info
> from the NOTICE files from bundled dependencies
> * checked NOTICE on source
> ** source artifact NOTICE file does not include a copyright line
> ** source NOTICE file includes notices for third party dependencies not
> included in the artifact
> * checked NOTICE files shipped in maven jars
> ** copyright line only says 2015 when it's very likely the contents are under
> copyright prior to this year
> * nit: NOTICE file on jars in maven say "HBase - ${module}" rather than
> "Apache HBase - ${module}" as required
> refs:
> http://www.apache.org/dev/licensing-howto.html#bundled-vs-non-bundled
> http://www.apache.org/dev/licensing-howto.html#binary
> http://www.apache.org/dev/licensing-howto.html#simple
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (HBASE-14085) Correct LICENSE and NOTICE files in artifacts
[
https://issues.apache.org/jira/browse/HBASE-14085?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14659389#comment-14659389
]
Hudson commented on HBASE-14085:
FAILURE: Integrated in HBase-1.0 #1001 (See
[https://builds.apache.org/job/HBase-1.0/1001/])
HBASE-14085 Update LICENSE and NOTICE files. (apurtell: rev
7141d8f0bb2896061ca2d1d57f02c9853e8a34af)
* hbase-server/src/test/resources/META-INF/NOTICE
* hbase-testing-util/pom.xml
* hbase-resource-bundle/src/main/resources/META-INF/LICENSE.vm
* hbase-thrift/src/test/resources/META-INF/NOTICE
* hbase-assembly/src/main/assembly/components.xml
* hbase-it/pom.xml
* hbase-thrift/pom.xml
* hbase-hadoop-compat/pom.xml
* hbase-hadoop2-compat/pom.xml
* hbase-annotations/pom.xml
* hbase-resource-bundle/pom.xml
* hbase-common/src/test/resources/META-INF/NOTICE
* pom.xml
* hbase-resource-bundle/src/main/resources/META-INF/NOTICE.vm
* hbase-server/src/test/resources/META-INF/LICENSE
* LICENSE.txt
* hbase-server/pom.xml
* NOTICE.txt
* hbase-examples/pom.xml
* hbase-thrift/src/test/resources/META-INF/LICENSE
* hbase-common/pom.xml
* hbase-prefix-tree/pom.xml
* hbase-shell/pom.xml
* hbase-resource-bundle/src/main/resources/supplemental-models.xml
* hbase-checkstyle/pom.xml
* hbase-thrift/src/main/appended-resources/META-INF/LICENSE
* hbase-assembly/src/main/assembly/hadoop-two-compat.xml
* hbase-protocol/pom.xml
* hbase-thrift/src/main/appended-resources/META-INF/NOTICE
* hbase-rest/pom.xml
* hbase-client/pom.xml
* hbase-assembly/pom.xml
* hbase-assembly/src/main/resources/META-INF/LEGAL
* hbase-common/src/main/appended-resources/META-INF/NOTICE
> Correct LICENSE and NOTICE files in artifacts
> -
>
> Key: HBASE-14085
> URL: https://issues.apache.org/jira/browse/HBASE-14085
> Project: HBase
> Issue Type: Task
> Components: build
>Affects Versions: 2.0.0, 0.94.28, 0.98.14, 1.0.2, 1.2.0, 1.1.2, 1.3.0
>Reporter: Sean Busbey
>Assignee: Sean Busbey
>Priority: Blocker
> Fix For: 2.0.0, 0.94.28, 0.98.14, 1.0.2, 1.2.0, 1.1.2
>
> Attachments: HBASE-14085.1.patch, HBASE-14085.2.patch,
> HBASE-14085.3.patch
>
>
> +Problems:
> * checked LICENSE/NOTICE on binary
> ** binary artifact LICENSE file has not been updated to include the
> additional license terms for contained third party dependencies
> ** binary artifact NOTICE file does not include a copyright line
> ** binary artifact NOTICE file does not appear to propagate appropriate info
> from the NOTICE files from bundled dependencies
> * checked NOTICE on source
> ** source artifact NOTICE file does not include a copyright line
> ** source NOTICE file includes notices for third party dependencies not
> included in the artifact
> * checked NOTICE files shipped in maven jars
> ** copyright line only says 2015 when it's very likely the contents are under
> copyright prior to this year
> * nit: NOTICE file on jars in maven say "HBase - ${module}" rather than
> "Apache HBase - ${module}" as required
> refs:
> http://www.apache.org/dev/licensing-howto.html#bundled-vs-non-bundled
> http://www.apache.org/dev/licensing-howto.html#binary
> http://www.apache.org/dev/licensing-howto.html#simple
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (HBASE-14085) Correct LICENSE and NOTICE files in artifacts
[
https://issues.apache.org/jira/browse/HBASE-14085?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14659386#comment-14659386
]
Andrew Purtell commented on HBASE-14085:
This has been committed to 0.98 and up.
What do we want to do about 0.94? Picking back the changes aren't possible, it
will have to be redone for a pre modular build. I suggest we file another issue
to follow up with 0.94, if we're going to make another release of it, and
resolve this one as Fixed.
/cc [~lhofhansl]
> Correct LICENSE and NOTICE files in artifacts
> -
>
> Key: HBASE-14085
> URL: https://issues.apache.org/jira/browse/HBASE-14085
> Project: HBase
> Issue Type: Task
> Components: build
>Affects Versions: 2.0.0, 0.94.28, 0.98.14, 1.0.2, 1.2.0, 1.1.2, 1.3.0
>Reporter: Sean Busbey
>Assignee: Sean Busbey
>Priority: Blocker
> Fix For: 2.0.0, 0.94.28, 0.98.14, 1.0.2, 1.2.0, 1.1.2
>
> Attachments: HBASE-14085.1.patch, HBASE-14085.2.patch,
> HBASE-14085.3.patch
>
>
> +Problems:
> * checked LICENSE/NOTICE on binary
> ** binary artifact LICENSE file has not been updated to include the
> additional license terms for contained third party dependencies
> ** binary artifact NOTICE file does not include a copyright line
> ** binary artifact NOTICE file does not appear to propagate appropriate info
> from the NOTICE files from bundled dependencies
> * checked NOTICE on source
> ** source artifact NOTICE file does not include a copyright line
> ** source NOTICE file includes notices for third party dependencies not
> included in the artifact
> * checked NOTICE files shipped in maven jars
> ** copyright line only says 2015 when it's very likely the contents are under
> copyright prior to this year
> * nit: NOTICE file on jars in maven say "HBase - ${module}" rather than
> "Apache HBase - ${module}" as required
> refs:
> http://www.apache.org/dev/licensing-howto.html#bundled-vs-non-bundled
> http://www.apache.org/dev/licensing-howto.html#binary
> http://www.apache.org/dev/licensing-howto.html#simple
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (HBASE-14085) Correct LICENSE and NOTICE files in artifacts
[
https://issues.apache.org/jira/browse/HBASE-14085?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14659384#comment-14659384
]
Andrew Purtell commented on HBASE-14085:
||0.98||
|cherry pick change back|x|
|verify no other third party works in source (grep for 'copyright', 'copied
from')|x|
|verify hbase-server, hbase-common, hbase-thrift all still incorporate third
party works they did in master (the logo files, jquery, and bootstrap), checked
by looking at running UI|x|
|for shaded jars, check dependency:list against the one in master and check any
difference for LICENSE.vm or NOTICE.vm in hbase-resource-bundle not covering
things|n/a|
|in the assembly artifact check dependency:list against the one in master
similar to the shaded jars
* Added com.github.stephenc.high-scale-lib:high-scale-lib (Public Domain)
* Removed com.jamesmurty.utils:java-xmlbuilder
* Added org.jboss.netty:netty (ASLv2)
* Modified org.netty:netty (ASLv2), renamed from org.netty:netty-all
* Added org.cloudera.htrace:htrace-core (ASLv2)|x|
|build release bin and source artifacts, RAT check enabled|x|
|spot check the LICENSE and NOTICE files in a few jars (common, server,
server-test) and in the bin and source artifacts|x|
There are some formatting nits that can be improved as follow on work.
> Correct LICENSE and NOTICE files in artifacts
> -
>
> Key: HBASE-14085
> URL: https://issues.apache.org/jira/browse/HBASE-14085
> Project: HBase
> Issue Type: Task
> Components: build
>Affects Versions: 2.0.0, 0.94.28, 0.98.14, 1.0.2, 1.2.0, 1.1.2, 1.3.0
>Reporter: Sean Busbey
>Assignee: Sean Busbey
>Priority: Blocker
> Fix For: 2.0.0, 0.94.28, 0.98.14, 1.0.2, 1.2.0, 1.1.2
>
> Attachments: HBASE-14085.1.patch, HBASE-14085.2.patch,
> HBASE-14085.3.patch
>
>
> +Problems:
> * checked LICENSE/NOTICE on binary
> ** binary artifact LICENSE file has not been updated to include the
> additional license terms for contained third party dependencies
> ** binary artifact NOTICE file does not include a copyright line
> ** binary artifact NOTICE file does not appear to propagate appropriate info
> from the NOTICE files from bundled dependencies
> * checked NOTICE on source
> ** source artifact NOTICE file does not include a copyright line
> ** source NOTICE file includes notices for third party dependencies not
> included in the artifact
> * checked NOTICE files shipped in maven jars
> ** copyright line only says 2015 when it's very likely the contents are under
> copyright prior to this year
> * nit: NOTICE file on jars in maven say "HBase - ${module}" rather than
> "Apache HBase - ${module}" as required
> refs:
> http://www.apache.org/dev/licensing-howto.html#bundled-vs-non-bundled
> http://www.apache.org/dev/licensing-howto.html#binary
> http://www.apache.org/dev/licensing-howto.html#simple
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (HBASE-13706) CoprocessorClassLoader should not exempt Hive classes
[
https://issues.apache.org/jira/browse/HBASE-13706?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14659345#comment-14659345
]
Hadoop QA commented on HBASE-13706:
---
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12748951/HBASE-13706-master-v2.patch
against master branch at commit 18c9bb8b54a5bb101f793e555272cbc74b8288cb.
ATTACHMENT ID: 12748951
{color:green}+1 @author{color}. The patch does not contain any @author
tags.
{color:red}-1 tests included{color}. The patch doesn't appear to include
any new or modified tests.
Please justify why no new tests are needed for this
patch.
Also please list what manual steps were performed to
verify this patch.
{color:green}+1 hadoop versions{color}. The patch compiles with all
supported hadoop versions (2.4.0 2.4.1 2.5.0 2.5.1 2.5.2 2.6.0 2.7.0)
{color:green}+1 javac{color}. The applied patch does not increase the
total number of javac compiler warnings.
{color:green}+1 protoc{color}. The applied patch does not increase the
total number of protoc compiler warnings.
{color:green}+1 javadoc{color}. The javadoc tool did not generate any
warning messages.
{color:green}+1 checkstyle{color}. The applied patch does not increase the
total number of checkstyle errors
{color:green}+1 findbugs{color}. The patch does not introduce any new
Findbugs (version 2.0.3) warnings.
{color:green}+1 release audit{color}. The applied patch does not increase
the total number of release audit warnings.
{color:green}+1 lineLengths{color}. The patch does not introduce lines
longer than 100
{color:green}+1 site{color}. The mvn post-site goal succeeds with this patch.
{color:red}-1 core tests{color}. The patch failed these unit tests:
Test results:
https://builds.apache.org/job/PreCommit-HBASE-Build/14986//testReport/
Release Findbugs (version 2.0.3)warnings:
https://builds.apache.org/job/PreCommit-HBASE-Build/14986//artifact/patchprocess/newFindbugsWarnings.html
Checkstyle Errors:
https://builds.apache.org/job/PreCommit-HBASE-Build/14986//artifact/patchprocess/checkstyle-aggregate.html
Console output:
https://builds.apache.org/job/PreCommit-HBASE-Build/14986//console
This message is automatically generated.
> CoprocessorClassLoader should not exempt Hive classes
> -
>
> Key: HBASE-13706
> URL: https://issues.apache.org/jira/browse/HBASE-13706
> Project: HBase
> Issue Type: Bug
> Components: Coprocessors
>Affects Versions: 2.0.0, 1.0.1, 1.1.0, 0.98.12
>Reporter: Jerry He
>Assignee: Jerry He
>Priority: Minor
> Fix For: 2.0.0, 0.98.14, 1.0.2, 1.1.3
>
> Attachments: HBASE-13706-master-v2.patch, HBASE-13706.patch
>
>
> CoprocessorClassLoader is used to load classes from the coprocessor jar.
> Certain classes are exempt from being loaded by this ClassLoader, which means
> they will be ignored in the coprocessor jar, but loaded from parent classpath
> instead.
> One problem is that we categorically exempt "org.apache.hadoop".
> But it happens that Hive packages start with "org.apache.hadoop".
> There is no reason to exclude hive classes from theCoprocessorClassLoader.
> HBase does not even include Hive jars.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (HBASE-14085) Correct LICENSE and NOTICE files in artifacts
[
https://issues.apache.org/jira/browse/HBASE-14085?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14659331#comment-14659331
]
Hudson commented on HBASE-14085:
FAILURE: Integrated in HBase-1.2 #92 (See
[https://builds.apache.org/job/HBase-1.2/92/])
HBASE-14085 Update LICENSE and NOTICE files. (apurtell: rev
52352c835418c005cd945ff903b8ae71ac283901)
* hbase-checkstyle/pom.xml
* hbase-common/src/test/resources/META-INF/NOTICE
* hbase-thrift/src/main/appended-resources/META-INF/LICENSE
* hbase-common/src/main/appended-resources/META-INF/NOTICE
* hbase-it/pom.xml
* hbase-resource-bundle/src/main/resources/META-INF/LICENSE.vm
* hbase-thrift/src/test/resources/META-INF/NOTICE
* hbase-hadoop-compat/pom.xml
* hbase-prefix-tree/pom.xml
* hbase-resource-bundle/src/main/resources/supplemental-models.xml
* hbase-thrift/src/test/resources/META-INF/LICENSE
* hbase-testing-util/pom.xml
* hbase-shaded/hbase-shaded-server/pom.xml
* hbase-server/pom.xml
* hbase-client/pom.xml
* hbase-thrift/pom.xml
* hbase-annotations/pom.xml
* hbase-assembly/src/main/assembly/hadoop-two-compat.xml
* hbase-resource-bundle/pom.xml
* hbase-shell/pom.xml
* hbase-server/src/test/resources/META-INF/NOTICE
* hbase-assembly/src/main/assembly/components.xml
* pom.xml
* hbase-assembly/src/main/resources/META-INF/LEGAL
* hbase-shaded/hbase-shaded-client/pom.xml
* NOTICE.txt
* hbase-hadoop2-compat/pom.xml
* hbase-resource-bundle/src/main/resources/META-INF/NOTICE.vm
* hbase-rest/pom.xml
* hbase-protocol/pom.xml
* hbase-common/pom.xml
* hbase-assembly/pom.xml
* hbase-thrift/src/main/appended-resources/META-INF/NOTICE
* hbase-shaded/pom.xml
* hbase-server/src/test/resources/META-INF/LICENSE
* LICENSE.txt
* hbase-examples/pom.xml
* hbase-procedure/pom.xml
> Correct LICENSE and NOTICE files in artifacts
> -
>
> Key: HBASE-14085
> URL: https://issues.apache.org/jira/browse/HBASE-14085
> Project: HBase
> Issue Type: Task
> Components: build
>Affects Versions: 2.0.0, 0.94.28, 0.98.14, 1.0.2, 1.2.0, 1.1.2, 1.3.0
>Reporter: Sean Busbey
>Assignee: Sean Busbey
>Priority: Blocker
> Fix For: 2.0.0, 0.94.28, 0.98.14, 1.0.2, 1.2.0, 1.1.2
>
> Attachments: HBASE-14085.1.patch, HBASE-14085.2.patch,
> HBASE-14085.3.patch
>
>
> +Problems:
> * checked LICENSE/NOTICE on binary
> ** binary artifact LICENSE file has not been updated to include the
> additional license terms for contained third party dependencies
> ** binary artifact NOTICE file does not include a copyright line
> ** binary artifact NOTICE file does not appear to propagate appropriate info
> from the NOTICE files from bundled dependencies
> * checked NOTICE on source
> ** source artifact NOTICE file does not include a copyright line
> ** source NOTICE file includes notices for third party dependencies not
> included in the artifact
> * checked NOTICE files shipped in maven jars
> ** copyright line only says 2015 when it's very likely the contents are under
> copyright prior to this year
> * nit: NOTICE file on jars in maven say "HBase - ${module}" rather than
> "Apache HBase - ${module}" as required
> refs:
> http://www.apache.org/dev/licensing-howto.html#bundled-vs-non-bundled
> http://www.apache.org/dev/licensing-howto.html#binary
> http://www.apache.org/dev/licensing-howto.html#simple
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (HBASE-14085) Correct LICENSE and NOTICE files in artifacts
[
https://issues.apache.org/jira/browse/HBASE-14085?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14659327#comment-14659327
]
Hudson commented on HBASE-14085:
SUCCESS: Integrated in HBase-1.3-IT #71 (See
[https://builds.apache.org/job/HBase-1.3-IT/71/])
HBASE-14085 Update LICENSE and NOTICE files. (apurtell: rev
a45651c2cfe22f7c56fff4544279fd340b8c99ea)
* hbase-assembly/pom.xml
* hbase-assembly/src/main/resources/META-INF/LEGAL
* hbase-resource-bundle/src/main/resources/META-INF/LICENSE.vm
* hbase-resource-bundle/src/main/resources/supplemental-models.xml
* hbase-common/src/test/resources/META-INF/NOTICE
* hbase-resource-bundle/pom.xml
* LICENSE.txt
* hbase-prefix-tree/pom.xml
* hbase-annotations/pom.xml
* hbase-examples/pom.xml
* hbase-rest/pom.xml
* hbase-hadoop2-compat/pom.xml
* hbase-thrift/src/main/appended-resources/META-INF/LICENSE
* hbase-thrift/pom.xml
* hbase-thrift/src/main/appended-resources/META-INF/NOTICE
* hbase-server/src/test/resources/META-INF/NOTICE
* hbase-shaded/hbase-shaded-server/pom.xml
* hbase-hadoop-compat/pom.xml
* hbase-server/src/test/resources/META-INF/LICENSE
* NOTICE.txt
* hbase-it/pom.xml
* hbase-protocol/pom.xml
* hbase-shaded/hbase-shaded-client/pom.xml
* hbase-assembly/src/main/assembly/components.xml
* hbase-procedure/pom.xml
* hbase-thrift/src/test/resources/META-INF/NOTICE
* hbase-resource-bundle/src/main/resources/META-INF/NOTICE.vm
* hbase-testing-util/pom.xml
* hbase-shell/pom.xml
* hbase-client/pom.xml
* hbase-shaded/pom.xml
* pom.xml
* hbase-server/pom.xml
* hbase-assembly/src/main/assembly/hadoop-two-compat.xml
* hbase-thrift/src/test/resources/META-INF/LICENSE
* hbase-checkstyle/pom.xml
* hbase-common/pom.xml
* hbase-common/src/main/appended-resources/META-INF/NOTICE
> Correct LICENSE and NOTICE files in artifacts
> -
>
> Key: HBASE-14085
> URL: https://issues.apache.org/jira/browse/HBASE-14085
> Project: HBase
> Issue Type: Task
> Components: build
>Affects Versions: 2.0.0, 0.94.28, 0.98.14, 1.0.2, 1.2.0, 1.1.2, 1.3.0
>Reporter: Sean Busbey
>Assignee: Sean Busbey
>Priority: Blocker
> Fix For: 2.0.0, 0.94.28, 0.98.14, 1.0.2, 1.2.0, 1.1.2
>
> Attachments: HBASE-14085.1.patch, HBASE-14085.2.patch,
> HBASE-14085.3.patch
>
>
> +Problems:
> * checked LICENSE/NOTICE on binary
> ** binary artifact LICENSE file has not been updated to include the
> additional license terms for contained third party dependencies
> ** binary artifact NOTICE file does not include a copyright line
> ** binary artifact NOTICE file does not appear to propagate appropriate info
> from the NOTICE files from bundled dependencies
> * checked NOTICE on source
> ** source artifact NOTICE file does not include a copyright line
> ** source NOTICE file includes notices for third party dependencies not
> included in the artifact
> * checked NOTICE files shipped in maven jars
> ** copyright line only says 2015 when it's very likely the contents are under
> copyright prior to this year
> * nit: NOTICE file on jars in maven say "HBase - ${module}" rather than
> "Apache HBase - ${module}" as required
> refs:
> http://www.apache.org/dev/licensing-howto.html#bundled-vs-non-bundled
> http://www.apache.org/dev/licensing-howto.html#binary
> http://www.apache.org/dev/licensing-howto.html#simple
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (HBASE-14085) Correct LICENSE and NOTICE files in artifacts
[
https://issues.apache.org/jira/browse/HBASE-14085?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14659315#comment-14659315
]
Hudson commented on HBASE-14085:
SUCCESS: Integrated in HBase-1.3 #89 (See
[https://builds.apache.org/job/HBase-1.3/89/])
HBASE-14085 Update LICENSE and NOTICE files. (apurtell: rev
a45651c2cfe22f7c56fff4544279fd340b8c99ea)
* hbase-assembly/src/main/resources/META-INF/LEGAL
* hbase-client/pom.xml
* hbase-resource-bundle/pom.xml
* hbase-testing-util/pom.xml
* hbase-checkstyle/pom.xml
* hbase-rest/pom.xml
* hbase-thrift/src/test/resources/META-INF/LICENSE
* hbase-resource-bundle/src/main/resources/META-INF/LICENSE.vm
* hbase-hadoop2-compat/pom.xml
* hbase-resource-bundle/src/main/resources/META-INF/NOTICE.vm
* hbase-common/src/test/resources/META-INF/NOTICE
* hbase-assembly/pom.xml
* hbase-server/pom.xml
* hbase-annotations/pom.xml
* hbase-hadoop-compat/pom.xml
* hbase-examples/pom.xml
* hbase-procedure/pom.xml
* hbase-it/pom.xml
* LICENSE.txt
* hbase-thrift/src/main/appended-resources/META-INF/NOTICE
* hbase-assembly/src/main/assembly/hadoop-two-compat.xml
* NOTICE.txt
* hbase-server/src/test/resources/META-INF/NOTICE
* hbase-shaded/hbase-shaded-server/pom.xml
* hbase-common/src/main/appended-resources/META-INF/NOTICE
* hbase-shaded/pom.xml
* pom.xml
* hbase-common/pom.xml
* hbase-thrift/src/test/resources/META-INF/NOTICE
* hbase-server/src/test/resources/META-INF/LICENSE
* hbase-protocol/pom.xml
* hbase-resource-bundle/src/main/resources/supplemental-models.xml
* hbase-thrift/src/main/appended-resources/META-INF/LICENSE
* hbase-prefix-tree/pom.xml
* hbase-shell/pom.xml
* hbase-shaded/hbase-shaded-client/pom.xml
* hbase-thrift/pom.xml
* hbase-assembly/src/main/assembly/components.xml
> Correct LICENSE and NOTICE files in artifacts
> -
>
> Key: HBASE-14085
> URL: https://issues.apache.org/jira/browse/HBASE-14085
> Project: HBase
> Issue Type: Task
> Components: build
>Affects Versions: 2.0.0, 0.94.28, 0.98.14, 1.0.2, 1.2.0, 1.1.2, 1.3.0
>Reporter: Sean Busbey
>Assignee: Sean Busbey
>Priority: Blocker
> Fix For: 2.0.0, 0.94.28, 0.98.14, 1.0.2, 1.2.0, 1.1.2
>
> Attachments: HBASE-14085.1.patch, HBASE-14085.2.patch,
> HBASE-14085.3.patch
>
>
> +Problems:
> * checked LICENSE/NOTICE on binary
> ** binary artifact LICENSE file has not been updated to include the
> additional license terms for contained third party dependencies
> ** binary artifact NOTICE file does not include a copyright line
> ** binary artifact NOTICE file does not appear to propagate appropriate info
> from the NOTICE files from bundled dependencies
> * checked NOTICE on source
> ** source artifact NOTICE file does not include a copyright line
> ** source NOTICE file includes notices for third party dependencies not
> included in the artifact
> * checked NOTICE files shipped in maven jars
> ** copyright line only says 2015 when it's very likely the contents are under
> copyright prior to this year
> * nit: NOTICE file on jars in maven say "HBase - ${module}" rather than
> "Apache HBase - ${module}" as required
> refs:
> http://www.apache.org/dev/licensing-howto.html#bundled-vs-non-bundled
> http://www.apache.org/dev/licensing-howto.html#binary
> http://www.apache.org/dev/licensing-howto.html#simple
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (HBASE-14085) Correct LICENSE and NOTICE files in artifacts
[
https://issues.apache.org/jira/browse/HBASE-14085?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14659313#comment-14659313
]
Hudson commented on HBASE-14085:
SUCCESS: Integrated in HBase-1.2-IT #75 (See
[https://builds.apache.org/job/HBase-1.2-IT/75/])
HBASE-14085 Update LICENSE and NOTICE files. (apurtell: rev
52352c835418c005cd945ff903b8ae71ac283901)
* hbase-prefix-tree/pom.xml
* hbase-thrift/src/main/appended-resources/META-INF/NOTICE
* hbase-shaded/hbase-shaded-server/pom.xml
* hbase-server/src/test/resources/META-INF/NOTICE
* hbase-resource-bundle/src/main/resources/supplemental-models.xml
* hbase-procedure/pom.xml
* hbase-protocol/pom.xml
* hbase-resource-bundle/pom.xml
* hbase-shaded/hbase-shaded-client/pom.xml
* hbase-resource-bundle/src/main/resources/META-INF/LICENSE.vm
* hbase-checkstyle/pom.xml
* hbase-client/pom.xml
* hbase-thrift/src/test/resources/META-INF/LICENSE
* hbase-assembly/src/main/assembly/hadoop-two-compat.xml
* hbase-shaded/pom.xml
* hbase-assembly/src/main/assembly/components.xml
* hbase-examples/pom.xml
* hbase-common/src/test/resources/META-INF/NOTICE
* hbase-thrift/src/test/resources/META-INF/NOTICE
* hbase-assembly/src/main/resources/META-INF/LEGAL
* NOTICE.txt
* hbase-server/src/test/resources/META-INF/LICENSE
* hbase-rest/pom.xml
* hbase-common/src/main/appended-resources/META-INF/NOTICE
* hbase-annotations/pom.xml
* hbase-thrift/pom.xml
* hbase-shell/pom.xml
* hbase-hadoop-compat/pom.xml
* hbase-resource-bundle/src/main/resources/META-INF/NOTICE.vm
* hbase-it/pom.xml
* hbase-testing-util/pom.xml
* hbase-common/pom.xml
* hbase-assembly/pom.xml
* hbase-thrift/src/main/appended-resources/META-INF/LICENSE
* hbase-hadoop2-compat/pom.xml
* pom.xml
* hbase-server/pom.xml
* LICENSE.txt
> Correct LICENSE and NOTICE files in artifacts
> -
>
> Key: HBASE-14085
> URL: https://issues.apache.org/jira/browse/HBASE-14085
> Project: HBase
> Issue Type: Task
> Components: build
>Affects Versions: 2.0.0, 0.94.28, 0.98.14, 1.0.2, 1.2.0, 1.1.2, 1.3.0
>Reporter: Sean Busbey
>Assignee: Sean Busbey
>Priority: Blocker
> Fix For: 2.0.0, 0.94.28, 0.98.14, 1.0.2, 1.2.0, 1.1.2
>
> Attachments: HBASE-14085.1.patch, HBASE-14085.2.patch,
> HBASE-14085.3.patch
>
>
> +Problems:
> * checked LICENSE/NOTICE on binary
> ** binary artifact LICENSE file has not been updated to include the
> additional license terms for contained third party dependencies
> ** binary artifact NOTICE file does not include a copyright line
> ** binary artifact NOTICE file does not appear to propagate appropriate info
> from the NOTICE files from bundled dependencies
> * checked NOTICE on source
> ** source artifact NOTICE file does not include a copyright line
> ** source NOTICE file includes notices for third party dependencies not
> included in the artifact
> * checked NOTICE files shipped in maven jars
> ** copyright line only says 2015 when it's very likely the contents are under
> copyright prior to this year
> * nit: NOTICE file on jars in maven say "HBase - ${module}" rather than
> "Apache HBase - ${module}" as required
> refs:
> http://www.apache.org/dev/licensing-howto.html#bundled-vs-non-bundled
> http://www.apache.org/dev/licensing-howto.html#binary
> http://www.apache.org/dev/licensing-howto.html#simple
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (HBASE-14081) (outdated) references to SVN/trunk in documentation
[ https://issues.apache.org/jira/browse/HBASE-14081?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14659304#comment-14659304 ] Gabor Liptak commented on HBASE-14081: -- [~ndimiduk] Would you have the SVN repository URL used to build http://hbase.apache.org/ ? > (outdated) references to SVN/trunk in documentation > --- > > Key: HBASE-14081 > URL: https://issues.apache.org/jira/browse/HBASE-14081 > Project: HBase > Issue Type: Bug >Reporter: Gabor Liptak >Priority: Minor > > Looking at > https://svn.apache.org/repos/asf/hbase/tags/ > SVN is no longer seems to be updated. > Is http://hbase.apache.org/ being built from Git? > https://issues.apache.org/jira/browse/INFRA-7768 is also being discussed. > Can those updated to master (or removed)? > Thanks -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (HBASE-13965) Stochastic Load Balancer JMX Metrics
[ https://issues.apache.org/jira/browse/HBASE-13965?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Lei Chen updated HBASE-13965: - Attachment: HBASE-13965-branch-1-v2.patch Updates: 1. wrapped a long line (> 100) The failed test from last patch seems not related. Here is the log: testWalRollOnLowReplication(org.apache.hadoop.hbase.master.procedure.TestWALProcedureStoreOnHDFS) Time elapsed: 3.804 sec <<< ERROR! java.lang.RuntimeException: sync aborted at org.apache.hadoop.hbase.procedure2.store.wal.WALProcedureStore.pushData(WALProcedureStore.java:491) at org.apache.hadoop.hbase.procedure2.store.wal.WALProcedureStore.insert(WALProcedureStore.java:334) at org.apache.hadoop.hbase.master.procedure.TestWALProcedureStoreOnHDFS.testWalRollOnLowReplication(TestWALProcedureStoreOnHDFS.java:189) Caused by: org.apache.hadoop.ipc.RemoteException: File /test-logs/state-0006.log could only be replicated to 2 nodes instead of minReplication (=3). There are 3 datanode(s) running and 3 node(s) are excluded in this operation. at org.apache.hadoop.hdfs.server.blockmanagement.BlockManager.chooseTarget(BlockManager.java:1471) at org.apache.hadoop.hdfs.server.namenode.FSNamesystem.getAdditionalBlock(FSNamesystem.java:2791) at org.apache.hadoop.hdfs.server.namenode.NameNodeRpcServer.addBlock(NameNodeRpcServer.java:606) at org.apache.hadoop.hdfs.protocolPB.ClientNamenodeProtocolServerSideTranslatorPB.addBlock(ClientNamenodeProtocolServerSideTranslatorPB.java:455) at org.apache.hadoop.hdfs.protocol.proto.ClientNamenodeProtocolProtos$ClientNamenodeProtocol$2.callBlockingMethod(ClientNamenodeProtocolProtos.java) at org.apache.hadoop.ipc.ProtobufRpcEngine$Server$ProtoBufRpcInvoker.call(ProtobufRpcEngine.java:585) at org.apache.hadoop.ipc.RPC$Server.call(RPC.java:928) at org.apache.hadoop.ipc.Server$Handler$1.run(Server.java:2013) at org.apache.hadoop.ipc.Server$Handler$1.run(Server.java:2009) at java.security.AccessController.doPrivileged(Native Method) at javax.security.auth.Subject.doAs(Subject.java:415) at org.apache.hadoop.security.UserGroupInformation.doAs(UserGroupInformation.java:1614) at org.apache.hadoop.ipc.Server$Handler.run(Server.java:2007) at org.apache.hadoop.ipc.Client.call(Client.java:1411) at org.apache.hadoop.ipc.Client.call(Client.java:1364) at org.apache.hadoop.ipc.ProtobufRpcEngine$Invoker.invoke(ProtobufRpcEngine.java:206) at com.sun.proxy.$Proxy20.addBlock(Unknown Source) at sun.reflect.GeneratedMethodAccessor8.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:606) at org.apache.hadoop.io.retry.RetryInvocationHandler.invokeMethod(RetryInvocationHandler.java:187) at org.apache.hadoop.io.retry.RetryInvocationHandler.invoke(RetryInvocationHandler.java:102) at com.sun.proxy.$Proxy20.addBlock(Unknown Source) at org.apache.hadoop.hdfs.protocolPB.ClientNamenodeProtocolTranslatorPB.addBlock(ClientNamenodeProtocolTranslatorPB.java:368) at org.apache.hadoop.hdfs.DFSOutputStream$DataStreamer.locateFollowingBlock(DFSOutputStream.java:1449) at org.apache.hadoop.hdfs.DFSOutputStream$DataStreamer.nextBlockOutputStream(DFSOutputStream.java:1270) at org.apache.hadoop.hdfs.DFSOutputStream$DataStreamer.run(DFSOutputStream.java:526) > Stochastic Load Balancer JMX Metrics > > > Key: HBASE-13965 > URL: https://issues.apache.org/jira/browse/HBASE-13965 > Project: HBase > Issue Type: Improvement > Components: Balancer, metrics >Reporter: Lei Chen >Assignee: Lei Chen > Fix For: 2.0.0 > > Attachments: 13965-addendum.txt, HBASE-13965-branch-1-v2.patch, > HBASE-13965-branch-1.patch, HBASE-13965-v10.patch, HBASE-13965-v11.patch, > HBASE-13965-v3.patch, HBASE-13965-v4.patch, HBASE-13965-v5.patch, > HBASE-13965-v6.patch, HBASE-13965-v7.patch, HBASE-13965-v8.patch, > HBASE-13965-v9.patch, HBASE-13965_v2.patch, HBase-13965-JConsole.png, > HBase-13965-v1.patch, stochasticloadbalancerclasses_v2.png > > > Today’s default HBase load balancer (the Stochastic load balancer) is cost > function based. The cost function weights are tunable but no visibility into > those cost function results is directly provided. > A driving example is a cluster we have been tuning which has skewed rack size > (one rack has half the nodes of the other few racks). We are tuning the > cluster for uniform response time from all region servers with the ability to > tolerate a rack failure. Balancing LocalityCost, RegionReplicaRack Cost and > RegionCountSkew Cost is difficu
[jira] [Commented] (HBASE-14085) Correct LICENSE and NOTICE files in artifacts
[
https://issues.apache.org/jira/browse/HBASE-14085?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14659276#comment-14659276
]
Andrew Purtell commented on HBASE-14085:
||branch-1.0||
|cherry pick change back|x|
|verify no other third party works in source (grep for 'copyright', 'copied
from')|x|
|verify hbase-server, hbase-common, hbase-thrift all still incorporate third
party works they did in master (the logo files, jquery, and bootstrap), checked
by looking at running UI|x|
|for shaded jars, check dependency:list against the one in master and check any
difference for LICENSE.vm or NOTICE.vm in hbase-resource-bundle not covering
things|n/a|
|in the assembly artifact check dependency:list against the one in master
similar to the shaded jars|x|
|build release bin and source artifacts, RAT check enabled|x|
|spot check the LICENSE and NOTICE files in a few jars (common, server,
server-test) and in the bin and source artifacts|x|
> Correct LICENSE and NOTICE files in artifacts
> -
>
> Key: HBASE-14085
> URL: https://issues.apache.org/jira/browse/HBASE-14085
> Project: HBase
> Issue Type: Task
> Components: build
>Affects Versions: 2.0.0, 0.94.28, 0.98.14, 1.0.2, 1.2.0, 1.1.2, 1.3.0
>Reporter: Sean Busbey
>Assignee: Sean Busbey
>Priority: Blocker
> Fix For: 2.0.0, 0.94.28, 0.98.14, 1.0.2, 1.2.0, 1.1.2
>
> Attachments: HBASE-14085.1.patch, HBASE-14085.2.patch,
> HBASE-14085.3.patch
>
>
> +Problems:
> * checked LICENSE/NOTICE on binary
> ** binary artifact LICENSE file has not been updated to include the
> additional license terms for contained third party dependencies
> ** binary artifact NOTICE file does not include a copyright line
> ** binary artifact NOTICE file does not appear to propagate appropriate info
> from the NOTICE files from bundled dependencies
> * checked NOTICE on source
> ** source artifact NOTICE file does not include a copyright line
> ** source NOTICE file includes notices for third party dependencies not
> included in the artifact
> * checked NOTICE files shipped in maven jars
> ** copyright line only says 2015 when it's very likely the contents are under
> copyright prior to this year
> * nit: NOTICE file on jars in maven say "HBase - ${module}" rather than
> "Apache HBase - ${module}" as required
> refs:
> http://www.apache.org/dev/licensing-howto.html#bundled-vs-non-bundled
> http://www.apache.org/dev/licensing-howto.html#binary
> http://www.apache.org/dev/licensing-howto.html#simple
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (HBASE-14178) regionserver blocks because of waiting for offsetLock
[
https://issues.apache.org/jira/browse/HBASE-14178?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14659274#comment-14659274
]
Duo Zhang commented on HBASE-14178:
---
[~anoopsamjohn] Any concerns of patch v6? Thanks.
> regionserver blocks because of waiting for offsetLock
> -
>
> Key: HBASE-14178
> URL: https://issues.apache.org/jira/browse/HBASE-14178
> Project: HBase
> Issue Type: Bug
> Components: regionserver
>Affects Versions: 0.98.6
>Reporter: Heng Chen
>Priority: Critical
> Fix For: 0.98.6
>
> Attachments: HBASE-14178-0.98.patch, HBASE-14178.patch,
> HBASE-14178_v1.patch, HBASE-14178_v2.patch, HBASE-14178_v3.patch,
> HBASE-14178_v4.patch, HBASE-14178_v5.patch, HBASE-14178_v6.patch, jstack
>
>
> My regionserver blocks, and all client rpc timeout.
> I print the regionserver's jstack, it seems a lot of threads were blocked
> for waiting offsetLock, detail infomation belows:
> PS: my table's block cache is off
> {code}
> "B.DefaultRpcServer.handler=2,queue=2,port=60020" #82 daemon prio=5 os_prio=0
> tid=0x01827000 nid=0x2cdc in Object.wait() [0x7f3831b72000]
>java.lang.Thread.State: WAITING (on object monitor)
> at java.lang.Object.wait(Native Method)
> at java.lang.Object.wait(Object.java:502)
> at org.apache.hadoop.hbase.util.IdLock.getLockEntry(IdLock.java:79)
> - locked <0x000773af7c18> (a
> org.apache.hadoop.hbase.util.IdLock$Entry)
> at
> org.apache.hadoop.hbase.io.hfile.HFileReaderV2.readBlock(HFileReaderV2.java:352)
> at
> org.apache.hadoop.hbase.io.hfile.HFileBlockIndex$BlockIndexReader.loadDataBlockWithScanInfo(HFileBlockIndex.java:253)
> at
> org.apache.hadoop.hbase.io.hfile.HFileReaderV2$AbstractScannerV2.seekTo(HFileReaderV2.java:524)
> at
> org.apache.hadoop.hbase.io.hfile.HFileReaderV2$AbstractScannerV2.reseekTo(HFileReaderV2.java:572)
> at
> org.apache.hadoop.hbase.regionserver.StoreFileScanner.reseekAtOrAfter(StoreFileScanner.java:257)
> at
> org.apache.hadoop.hbase.regionserver.StoreFileScanner.reseek(StoreFileScanner.java:173)
> at
> org.apache.hadoop.hbase.regionserver.NonLazyKeyValueScanner.doRealSeek(NonLazyKeyValueScanner.java:55)
> at
> org.apache.hadoop.hbase.regionserver.KeyValueHeap.generalizedSeek(KeyValueHeap.java:313)
> at
> org.apache.hadoop.hbase.regionserver.KeyValueHeap.requestSeek(KeyValueHeap.java:269)
> at
> org.apache.hadoop.hbase.regionserver.StoreScanner.reseek(StoreScanner.java:695)
> at
> org.apache.hadoop.hbase.regionserver.StoreScanner.seekAsDirection(StoreScanner.java:683)
> at
> org.apache.hadoop.hbase.regionserver.StoreScanner.next(StoreScanner.java:533)
> at
> org.apache.hadoop.hbase.regionserver.KeyValueHeap.next(KeyValueHeap.java:140)
> at
> org.apache.hadoop.hbase.regionserver.HRegion$RegionScannerImpl.populateResult(HRegion.java:3889)
> at
> org.apache.hadoop.hbase.regionserver.HRegion$RegionScannerImpl.nextInternal(HRegion.java:3969)
> at
> org.apache.hadoop.hbase.regionserver.HRegion$RegionScannerImpl.nextRaw(HRegion.java:3847)
> at
> org.apache.hadoop.hbase.regionserver.HRegion$RegionScannerImpl.next(HRegion.java:3820)
> - locked <0x0005e5c55ad0> (a
> org.apache.hadoop.hbase.regionserver.HRegion$RegionScannerImpl)
> at
> org.apache.hadoop.hbase.regionserver.HRegion$RegionScannerImpl.next(HRegion.java:3807)
> at org.apache.hadoop.hbase.regionserver.HRegion.get(HRegion.java:4779)
> at org.apache.hadoop.hbase.regionserver.HRegion.get(HRegion.java:4753)
> at
> org.apache.hadoop.hbase.regionserver.HRegionServer.get(HRegionServer.java:2916)
> at
> org.apache.hadoop.hbase.protobuf.generated.ClientProtos$ClientService$2.callBlockingMethod(ClientProtos.java:29583)
> at org.apache.hadoop.hbase.ipc.RpcServer.call(RpcServer.java:2027)
> at org.apache.hadoop.hbase.ipc.CallRunner.run(CallRunner.java:108)
> at
> org.apache.hadoop.hbase.ipc.RpcExecutor.consumerLoop(RpcExecutor.java:114)
> at org.apache.hadoop.hbase.ipc.RpcExecutor$1.run(RpcExecutor.java:94)
> at java.lang.Thread.run(Thread.java:745)
>Locked ownable synchronizers:
> - <0x0005e5c55c08> (a
> java.util.concurrent.locks.ReentrantLock$NonfairSync)
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (HBASE-14186) Read mvcc vlong optimization
[
https://issues.apache.org/jira/browse/HBASE-14186?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14659249#comment-14659249
]
stack commented on HBASE-14186:
---
ok. +1
> Read mvcc vlong optimization
>
>
> Key: HBASE-14186
> URL: https://issues.apache.org/jira/browse/HBASE-14186
> Project: HBase
> Issue Type: Sub-task
> Components: Scanners
>Reporter: Anoop Sam John
>Assignee: Anoop Sam John
> Fix For: 2.0.0
>
> Attachments: HBASE-14186.patch
>
>
> {code}
> for (int idx = 0; idx < remaining; idx++) {
> byte b = blockBuffer.getByteAfterPosition(offsetFromPos + idx);
> i = i << 8;
> i = i | (b & 0xFF);
> }
> {code}
> Doing the read as in case of BIG_ENDIAN.
> After HBASE-12600, we tend to keep the mvcc and so byte by byte read looks
> eating up lot of CPU time. (In my test HFileReaderImpl#_readMvccVersion comes
> on top in terms of hot methods). We can optimize here by reading 4 or 2 bytes
> in one shot when the length of the vlong is more than 4 bytes. We will in
> turn use UnsafeAccess methods which handles ENDIAN.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (HBASE-13867) Add endpoint coprocessor guide to HBase book
[ https://issues.apache.org/jira/browse/HBASE-13867?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14659238#comment-14659238 ] Gaurav Bhardwaj commented on HBASE-13867: - [~ndimiduk], there is restriction that line length cannot be greater than 100 and there were several problems reported in earlier patch (see [commnet|https://issues.apache.org/jira/browse/HBASE-13867?focusedCommentId=14617215&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-14617215]), so to avoid any such error I deliberately break the line wherever the line exceeds 100 characters. Let me know if there is a way to handle this 100 character limitations, i will resubmit the patch after modifying it with the suggested changes. As a general opinion I think, this limitation should be be relaxed to 300 characters for documents (HBase book) for handling special cases like URL addresses etc. > Add endpoint coprocessor guide to HBase book > > > Key: HBASE-13867 > URL: https://issues.apache.org/jira/browse/HBASE-13867 > Project: HBase > Issue Type: Task > Components: Coprocessors, documentation >Reporter: Vladimir Rodionov >Assignee: Gaurav Bhardwaj > Fix For: 2.0.0 > > Attachments: HBASE-13867.1.patch, HBASE-13867.2.patch, > HBASE-13867.2.patch > > > Endpoint coprocessors are very poorly documented. > Coprocessor section of HBase book must be updated either with its own > endpoint coprocessors HOW-TO guide or, at least, with the link(s) to some > other guides. There is good description here: > http://www.3pillarglobal.com/insights/hbase-coprocessors -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (HBASE-14085) Correct LICENSE and NOTICE files in artifacts
[
https://issues.apache.org/jira/browse/HBASE-14085?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14659234#comment-14659234
]
Andrew Purtell commented on HBASE-14085:
||branch-1.1||
|cherry pick change back|x|
|verify no other third party works in source (grep for 'copyright', 'copied
from')|x|
|verify hbase-server, hbase-common, hbase-thrift all still incorporate third
party works they did in master (the logo files, jquery, and bootstrap), checked
by looking at running UI|x|
|for shaded jars, check dependency:list against the one in master and check any
difference for LICENSE.vm or NOTICE.vm in hbase-resource-bundle not covering
things|x|
|in the assembly artifact check dependency:list against the one in master
similar to the shaded jars|x|
|build release bin and source artifacts, RAT check enabled|x|
|spot check the LICENSE and NOTICE files in a few jars (common, server,
server-test) and in the bin and source artifacts|x|
> Correct LICENSE and NOTICE files in artifacts
> -
>
> Key: HBASE-14085
> URL: https://issues.apache.org/jira/browse/HBASE-14085
> Project: HBase
> Issue Type: Task
> Components: build
>Affects Versions: 2.0.0, 0.94.28, 0.98.14, 1.0.2, 1.2.0, 1.1.2, 1.3.0
>Reporter: Sean Busbey
>Assignee: Sean Busbey
>Priority: Blocker
> Fix For: 2.0.0, 0.94.28, 0.98.14, 1.0.2, 1.2.0, 1.1.2
>
> Attachments: HBASE-14085.1.patch, HBASE-14085.2.patch,
> HBASE-14085.3.patch
>
>
> +Problems:
> * checked LICENSE/NOTICE on binary
> ** binary artifact LICENSE file has not been updated to include the
> additional license terms for contained third party dependencies
> ** binary artifact NOTICE file does not include a copyright line
> ** binary artifact NOTICE file does not appear to propagate appropriate info
> from the NOTICE files from bundled dependencies
> * checked NOTICE on source
> ** source artifact NOTICE file does not include a copyright line
> ** source NOTICE file includes notices for third party dependencies not
> included in the artifact
> * checked NOTICE files shipped in maven jars
> ** copyright line only says 2015 when it's very likely the contents are under
> copyright prior to this year
> * nit: NOTICE file on jars in maven say "HBase - ${module}" rather than
> "Apache HBase - ${module}" as required
> refs:
> http://www.apache.org/dev/licensing-howto.html#bundled-vs-non-bundled
> http://www.apache.org/dev/licensing-howto.html#binary
> http://www.apache.org/dev/licensing-howto.html#simple
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (HBASE-13706) CoprocessorClassLoader should not exempt Hive classes
[
https://issues.apache.org/jira/browse/HBASE-13706?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14659159#comment-14659159
]
Jerry He commented on HBASE-13706:
--
Attached a master-v2 patch.
Are you ok with this one for master branch, [~apurtell]?
What about for the other branches? Explicit listing of the hadoop packages?
{noformat}
org.apache.hadoop.security
org.apache.hadoop.HadoopIllegalArgumentException
org.apache.hadoop.conf
org.apache.hadoop.fs
org.apache.hadoop.http
org.apache.hadoop.io
org.apache.hadoop.ipc
org.apache.hadoop.metrics
org.apache.hadoop.metrics2
org.apache.hadoop.net
org.apache.hadoop.util
org.apache.hadoop.hdfs
{noformat}
> CoprocessorClassLoader should not exempt Hive classes
> -
>
> Key: HBASE-13706
> URL: https://issues.apache.org/jira/browse/HBASE-13706
> Project: HBase
> Issue Type: Bug
> Components: Coprocessors
>Affects Versions: 2.0.0, 1.0.1, 1.1.0, 0.98.12
>Reporter: Jerry He
>Assignee: Jerry He
>Priority: Minor
> Fix For: 2.0.0, 0.98.14, 1.0.2, 1.1.3
>
> Attachments: HBASE-13706-master-v2.patch, HBASE-13706.patch
>
>
> CoprocessorClassLoader is used to load classes from the coprocessor jar.
> Certain classes are exempt from being loaded by this ClassLoader, which means
> they will be ignored in the coprocessor jar, but loaded from parent classpath
> instead.
> One problem is that we categorically exempt "org.apache.hadoop".
> But it happens that Hive packages start with "org.apache.hadoop".
> There is no reason to exclude hive classes from theCoprocessorClassLoader.
> HBase does not even include Hive jars.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (HBASE-13706) CoprocessorClassLoader should not exempt Hive classes
[ https://issues.apache.org/jira/browse/HBASE-13706?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jerry He updated HBASE-13706: - Attachment: HBASE-13706-master-v2.patch > CoprocessorClassLoader should not exempt Hive classes > - > > Key: HBASE-13706 > URL: https://issues.apache.org/jira/browse/HBASE-13706 > Project: HBase > Issue Type: Bug > Components: Coprocessors >Affects Versions: 2.0.0, 1.0.1, 1.1.0, 0.98.12 >Reporter: Jerry He >Assignee: Jerry He >Priority: Minor > Fix For: 2.0.0, 0.98.14, 1.0.2, 1.1.3 > > Attachments: HBASE-13706-master-v2.patch, HBASE-13706.patch > > > CoprocessorClassLoader is used to load classes from the coprocessor jar. > Certain classes are exempt from being loaded by this ClassLoader, which means > they will be ignored in the coprocessor jar, but loaded from parent classpath > instead. > One problem is that we categorically exempt "org.apache.hadoop". > But it happens that Hive packages start with "org.apache.hadoop". > There is no reason to exclude hive classes from theCoprocessorClassLoader. > HBase does not even include Hive jars. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (HBASE-14085) Correct LICENSE and NOTICE files in artifacts
[
https://issues.apache.org/jira/browse/HBASE-14085?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14659148#comment-14659148
]
Andrew Purtell commented on HBASE-14085:
||branch-1.2||
|cherry pick change back|x|
|verify no other third party works in source (grep for 'copyright', 'copied
from')|x|
|verify hbase-server, hbase-common, hbase-thrift all still incorporate third
party works they did in master (the logo files, jquery, and bootstrap), checked
by looking at running UI|x|
|for shaded jars, check dependency:list against the one in master and check any
difference for LICENSE.vm or NOTICE.vm in hbase-resource-bundle not covering
things|x|
|in the assembly artifact check dependency:list against the one in master
similar to the shaded jars|x|
|build release bin and source artifacts, RAT check enabled|x|
|spot check the LICENSE and NOTICE files in a few jars (common, server,
server-test) and in the bin and source artifacts|x|
> Correct LICENSE and NOTICE files in artifacts
> -
>
> Key: HBASE-14085
> URL: https://issues.apache.org/jira/browse/HBASE-14085
> Project: HBase
> Issue Type: Task
> Components: build
>Affects Versions: 2.0.0, 0.94.28, 0.98.14, 1.0.2, 1.2.0, 1.1.2, 1.3.0
>Reporter: Sean Busbey
>Assignee: Sean Busbey
>Priority: Blocker
> Fix For: 2.0.0, 0.94.28, 0.98.14, 1.0.2, 1.2.0, 1.1.2
>
> Attachments: HBASE-14085.1.patch, HBASE-14085.2.patch,
> HBASE-14085.3.patch
>
>
> +Problems:
> * checked LICENSE/NOTICE on binary
> ** binary artifact LICENSE file has not been updated to include the
> additional license terms for contained third party dependencies
> ** binary artifact NOTICE file does not include a copyright line
> ** binary artifact NOTICE file does not appear to propagate appropriate info
> from the NOTICE files from bundled dependencies
> * checked NOTICE on source
> ** source artifact NOTICE file does not include a copyright line
> ** source NOTICE file includes notices for third party dependencies not
> included in the artifact
> * checked NOTICE files shipped in maven jars
> ** copyright line only says 2015 when it's very likely the contents are under
> copyright prior to this year
> * nit: NOTICE file on jars in maven say "HBase - ${module}" rather than
> "Apache HBase - ${module}" as required
> refs:
> http://www.apache.org/dev/licensing-howto.html#bundled-vs-non-bundled
> http://www.apache.org/dev/licensing-howto.html#binary
> http://www.apache.org/dev/licensing-howto.html#simple
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (HBASE-13965) Stochastic Load Balancer JMX Metrics
[
https://issues.apache.org/jira/browse/HBASE-13965?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14659136#comment-14659136
]
Hadoop QA commented on HBASE-13965:
---
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12748903/HBASE-13965-branch-1.patch
against branch-1 branch at commit 18c9bb8b54a5bb101f793e555272cbc74b8288cb.
ATTACHMENT ID: 12748903
{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 hadoop versions{color}. The patch compiles with all
supported hadoop versions (2.4.0 2.4.1 2.5.0 2.5.1 2.5.2 2.6.0 2.7.0)
{color:green}+1 javac{color}. The applied patch does not increase the
total number of javac compiler warnings.
{color:green}+1 protoc{color}. The applied patch does not increase the
total number of protoc compiler warnings.
{color:green}+1 javadoc{color}. The javadoc tool did not generate any
warning messages.
{color:green}+1 checkstyle{color}. The applied patch does not increase the
total number of checkstyle errors
{color:green}+1 findbugs{color}. The patch does not introduce any new
Findbugs (version 2.0.3) warnings.
{color:green}+1 release audit{color}. The applied patch does not increase
the total number of release audit warnings.
{color:red}-1 lineLengths{color}. The patch introduces the following lines
longer than 100:
+ for (Entry>> e :
assignmentsByTable.entrySet()) {
+
JMXConnectorFactory.connect(JMXListener.buildJMXServiceURL(connectorPort,
connectorPort));
{color:green}+1 site{color}. The mvn post-site goal succeeds with this patch.
{color:red}-1 core tests{color}. The patch failed these unit tests:
Test results:
https://builds.apache.org/job/PreCommit-HBASE-Build/14984//testReport/
Release Findbugs (version 2.0.3)warnings:
https://builds.apache.org/job/PreCommit-HBASE-Build/14984//artifact/patchprocess/newFindbugsWarnings.html
Checkstyle Errors:
https://builds.apache.org/job/PreCommit-HBASE-Build/14984//artifact/patchprocess/checkstyle-aggregate.html
Console output:
https://builds.apache.org/job/PreCommit-HBASE-Build/14984//console
This message is automatically generated.
> Stochastic Load Balancer JMX Metrics
>
>
> Key: HBASE-13965
> URL: https://issues.apache.org/jira/browse/HBASE-13965
> Project: HBase
> Issue Type: Improvement
> Components: Balancer, metrics
>Reporter: Lei Chen
>Assignee: Lei Chen
> Fix For: 2.0.0
>
> Attachments: 13965-addendum.txt, HBASE-13965-branch-1.patch,
> HBASE-13965-v10.patch, HBASE-13965-v11.patch, HBASE-13965-v3.patch,
> HBASE-13965-v4.patch, HBASE-13965-v5.patch, HBASE-13965-v6.patch,
> HBASE-13965-v7.patch, HBASE-13965-v8.patch, HBASE-13965-v9.patch,
> HBASE-13965_v2.patch, HBase-13965-JConsole.png, HBase-13965-v1.patch,
> stochasticloadbalancerclasses_v2.png
>
>
> Today’s default HBase load balancer (the Stochastic load balancer) is cost
> function based. The cost function weights are tunable but no visibility into
> those cost function results is directly provided.
> A driving example is a cluster we have been tuning which has skewed rack size
> (one rack has half the nodes of the other few racks). We are tuning the
> cluster for uniform response time from all region servers with the ability to
> tolerate a rack failure. Balancing LocalityCost, RegionReplicaRack Cost and
> RegionCountSkew Cost is difficult without a way to attribute each cost
> function’s contribution to overall cost.
> What this jira proposes is to provide visibility via JMX into each cost
> function of the stochastic load balancer, as well as the overall cost of the
> balancing plan.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (HBASE-14085) Correct LICENSE and NOTICE files in artifacts
[
https://issues.apache.org/jira/browse/HBASE-14085?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14659077#comment-14659077
]
Andrew Purtell commented on HBASE-14085:
||branch-1||
|cherry pick change back|x|
|verify no other third party works in source (grep for 'copyright', 'copied
from')|x|
|verify hbase-server, hbase-common, hbase-thrift all still incorporate third
party works they did in master (the logo files, jquery, and bootstrap), checked
by looking at running UI|x|
|for shaded jars, check dependency:list against the one in master and check any
difference for LICENSE.vm or NOTICE.vm in hbase-resource-bundle not covering
things|x|
|in the assembly artifact check dependency:list against the one in master
similar to the shaded jars|x|
|build release bin and source artifacts, RAT check enabled|x|
|spot check the LICENSE and NOTICE files in a few jars (common, server,
server-test) and in the bin and source artifacts|x|
> Correct LICENSE and NOTICE files in artifacts
> -
>
> Key: HBASE-14085
> URL: https://issues.apache.org/jira/browse/HBASE-14085
> Project: HBase
> Issue Type: Task
> Components: build
>Affects Versions: 2.0.0, 0.94.28, 0.98.14, 1.0.2, 1.2.0, 1.1.2, 1.3.0
>Reporter: Sean Busbey
>Assignee: Sean Busbey
>Priority: Blocker
> Fix For: 2.0.0, 0.94.28, 0.98.14, 1.0.2, 1.2.0, 1.1.2
>
> Attachments: HBASE-14085.1.patch, HBASE-14085.2.patch,
> HBASE-14085.3.patch
>
>
> +Problems:
> * checked LICENSE/NOTICE on binary
> ** binary artifact LICENSE file has not been updated to include the
> additional license terms for contained third party dependencies
> ** binary artifact NOTICE file does not include a copyright line
> ** binary artifact NOTICE file does not appear to propagate appropriate info
> from the NOTICE files from bundled dependencies
> * checked NOTICE on source
> ** source artifact NOTICE file does not include a copyright line
> ** source NOTICE file includes notices for third party dependencies not
> included in the artifact
> * checked NOTICE files shipped in maven jars
> ** copyright line only says 2015 when it's very likely the contents are under
> copyright prior to this year
> * nit: NOTICE file on jars in maven say "HBase - ${module}" rather than
> "Apache HBase - ${module}" as required
> refs:
> http://www.apache.org/dev/licensing-howto.html#bundled-vs-non-bundled
> http://www.apache.org/dev/licensing-howto.html#binary
> http://www.apache.org/dev/licensing-howto.html#simple
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (HBASE-12269) Add support for Scan.setRowPrefixFilter to thrift
[ https://issues.apache.org/jira/browse/HBASE-12269?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sean Busbey updated HBASE-12269: Fix Version/s: 1.3.0 2.0.0 > Add support for Scan.setRowPrefixFilter to thrift > - > > Key: HBASE-12269 > URL: https://issues.apache.org/jira/browse/HBASE-12269 > Project: HBase > Issue Type: New Feature > Components: Thrift >Reporter: Niels Basjes >Assignee: Niels Basjes > Fix For: 2.0.0, 1.3.0 > > Attachments: HBASE-12269-2014-10-15-v1.patch, > HBASE-12269-2014-10-16-v2-INCOMPLETE.patch, HBASE-12269-2014-12-05-v2.patch > > > I think having the feature introduced in HBASE-11990 in the hbase thrift > interface would be very useful. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (HBASE-14085) Correct LICENSE and NOTICE files in artifacts
[
https://issues.apache.org/jira/browse/HBASE-14085?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14659008#comment-14659008
]
Andrew Purtell commented on HBASE-14085:
Got sidetracked, working on this now. Tests pass locally so the precommit build
above had something else going on
> Correct LICENSE and NOTICE files in artifacts
> -
>
> Key: HBASE-14085
> URL: https://issues.apache.org/jira/browse/HBASE-14085
> Project: HBase
> Issue Type: Task
> Components: build
>Affects Versions: 2.0.0, 0.94.28, 0.98.14, 1.0.2, 1.2.0, 1.1.2, 1.3.0
>Reporter: Sean Busbey
>Assignee: Sean Busbey
>Priority: Blocker
> Fix For: 2.0.0, 0.94.28, 0.98.14, 1.0.2, 1.2.0, 1.1.2
>
> Attachments: HBASE-14085.1.patch, HBASE-14085.2.patch,
> HBASE-14085.3.patch
>
>
> +Problems:
> * checked LICENSE/NOTICE on binary
> ** binary artifact LICENSE file has not been updated to include the
> additional license terms for contained third party dependencies
> ** binary artifact NOTICE file does not include a copyright line
> ** binary artifact NOTICE file does not appear to propagate appropriate info
> from the NOTICE files from bundled dependencies
> * checked NOTICE on source
> ** source artifact NOTICE file does not include a copyright line
> ** source NOTICE file includes notices for third party dependencies not
> included in the artifact
> * checked NOTICE files shipped in maven jars
> ** copyright line only says 2015 when it's very likely the contents are under
> copyright prior to this year
> * nit: NOTICE file on jars in maven say "HBase - ${module}" rather than
> "Apache HBase - ${module}" as required
> refs:
> http://www.apache.org/dev/licensing-howto.html#bundled-vs-non-bundled
> http://www.apache.org/dev/licensing-howto.html#binary
> http://www.apache.org/dev/licensing-howto.html#simple
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (HBASE-5878) Use getVisibleLength public api from HdfsDataInputStream from Hadoop-2.
[
https://issues.apache.org/jira/browse/HBASE-5878?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14658921#comment-14658921
]
Nick Dimiduk commented on HBASE-5878:
-
It would be good to update the dependency to the specific JIRA so as to avoid
confusion for lookers-on.
> Use getVisibleLength public api from HdfsDataInputStream from Hadoop-2.
> ---
>
> Key: HBASE-5878
> URL: https://issues.apache.org/jira/browse/HBASE-5878
> Project: HBase
> Issue Type: Bug
> Components: wal
>Reporter: Uma Maheswara Rao G
>Assignee: Ashish Singhi
> Fix For: 2.0.0, 1.1.2, 1.3.0, 1.2.1, 1.0.3
>
> Attachments: HBASE-5878-v2.patch, HBASE-5878-v3.patch,
> HBASE-5878-v4.patch, HBASE-5878-v5.patch, HBASE-5878-v5.patch,
> HBASE-5878.patch
>
>
> SequencFileLogReader:
> Currently Hbase using getFileLength api from DFSInputStream class by
> reflection. DFSInputStream is not exposed as public. So, this may change in
> future. Now HDFS exposed HdfsDataInputStream as public API.
> We can make use of it, when we are not able to find the getFileLength api
> from DFSInputStream as a else condition. So, that we will not have any sudden
> surprise like we are facing today.
> Also, it is just logging one warn message and proceeding if it throws any
> exception while getting the length. I think we can re-throw the exception
> because there is no point in continuing with dataloss.
> {code}
> long adjust = 0;
> try {
> Field fIn = FilterInputStream.class.getDeclaredField("in");
> fIn.setAccessible(true);
> Object realIn = fIn.get(this.in);
> // In hadoop 0.22, DFSInputStream is a standalone class. Before
> this,
> // it was an inner class of DFSClient.
> if (realIn.getClass().getName().endsWith("DFSInputStream")) {
> Method getFileLength = realIn.getClass().
> getDeclaredMethod("getFileLength", new Class []{});
> getFileLength.setAccessible(true);
> long realLength = ((Long)getFileLength.
> invoke(realIn, new Object []{})).longValue();
> assert(realLength >= this.length);
> adjust = realLength - this.length;
> } else {
> LOG.info("Input stream class: " + realIn.getClass().getName() +
> ", not adjusting length");
> }
> } catch(Exception e) {
> SequenceFileLogReader.LOG.warn(
> "Error while trying to get accurate file length. " +
> "Truncation / data loss may occur if RegionServers die.", e);
> }
> return adjust + super.getPos();
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (HBASE-14021) Quota table has a wrong description on the UI
[ https://issues.apache.org/jira/browse/HBASE-14021?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14658918#comment-14658918 ] Ted Yu commented on HBASE-14021: The patch didn't apply cleanly to branch-1.1 If Ashish prepares backported patch, I would be happy to apply. > Quota table has a wrong description on the UI > - > > Key: HBASE-14021 > URL: https://issues.apache.org/jira/browse/HBASE-14021 > Project: HBase > Issue Type: Bug > Components: UI >Affects Versions: 1.1.0 >Reporter: Ashish Singhi >Assignee: Ashish Singhi >Priority: Minor > Fix For: 2.0.0, 1.3.0, 1.2.1 > > Attachments: HBASE-14021.patch, HBASE-14021.patch, error.png, fix.png > > > !error.png! -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (HBASE-14021) Quota table has a wrong description on the UI
[ https://issues.apache.org/jira/browse/HBASE-14021?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14658914#comment-14658914 ] Nick Dimiduk commented on HBASE-14021: -- [~tedyu] excuse my ignorance, but does branch-1.1 or branch-1.0 not have a quota table? > Quota table has a wrong description on the UI > - > > Key: HBASE-14021 > URL: https://issues.apache.org/jira/browse/HBASE-14021 > Project: HBase > Issue Type: Bug > Components: UI >Affects Versions: 1.1.0 >Reporter: Ashish Singhi >Assignee: Ashish Singhi >Priority: Minor > Fix For: 2.0.0, 1.3.0, 1.2.1 > > Attachments: HBASE-14021.patch, HBASE-14021.patch, error.png, fix.png > > > !error.png! -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (HBASE-13867) Add endpoint coprocessor guide to HBase book
[ https://issues.apache.org/jira/browse/HBASE-13867?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nick Dimiduk updated HBASE-13867: - Fix Version/s: (was: 1.1.2) (was: 1.2.0) (was: 1.0.2) Dropping other release versions because book patches are explicitly committed only to master. RM's manage bringing back book content on release. > Add endpoint coprocessor guide to HBase book > > > Key: HBASE-13867 > URL: https://issues.apache.org/jira/browse/HBASE-13867 > Project: HBase > Issue Type: Task > Components: Coprocessors, documentation >Reporter: Vladimir Rodionov >Assignee: Gaurav Bhardwaj > Fix For: 2.0.0 > > Attachments: HBASE-13867.1.patch, HBASE-13867.2.patch, > HBASE-13867.2.patch > > > Endpoint coprocessors are very poorly documented. > Coprocessor section of HBase book must be updated either with its own > endpoint coprocessors HOW-TO guide or, at least, with the link(s) to some > other guides. There is good description here: > http://www.3pillarglobal.com/insights/hbase-coprocessors -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (HBASE-13865) Increase the default value for hbase.hregion.memstore.block.multipler from 2 to 4 (part 2)
[ https://issues.apache.org/jira/browse/HBASE-13865?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=1465#comment-1465 ] Nick Dimiduk commented on HBASE-13865: -- Invoking here the spirit of [~nkeywal] for review. > Increase the default value for hbase.hregion.memstore.block.multipler from 2 > to 4 (part 2) > -- > > Key: HBASE-13865 > URL: https://issues.apache.org/jira/browse/HBASE-13865 > Project: HBase > Issue Type: Bug > Components: documentation >Affects Versions: 2.0.0 >Reporter: Vladimir Rodionov >Assignee: Gabor Liptak >Priority: Trivial > Fix For: 2.0.0, 0.98.14, 1.3.0, 1.2.1, 1.0.3, 1.1.3 > > Attachments: HBASE-13865.1.patch, HBASE-13865.2.patch, > HBASE-13865.2.patch > > > Its 4 in the book and 2 in a current master. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (HBASE-13865) Increase the default value for hbase.hregion.memstore.block.multipler from 2 to 4 (part 2)
[ https://issues.apache.org/jira/browse/HBASE-13865?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nick Dimiduk updated HBASE-13865: - Fix Version/s: 1.1.3 1.0.3 1.2.1 1.3.0 0.98.14 2.0.0 > Increase the default value for hbase.hregion.memstore.block.multipler from 2 > to 4 (part 2) > -- > > Key: HBASE-13865 > URL: https://issues.apache.org/jira/browse/HBASE-13865 > Project: HBase > Issue Type: Bug > Components: documentation >Affects Versions: 2.0.0 >Reporter: Vladimir Rodionov >Assignee: Gabor Liptak >Priority: Trivial > Fix For: 2.0.0, 0.98.14, 1.3.0, 1.2.1, 1.0.3, 1.1.3 > > Attachments: HBASE-13865.1.patch, HBASE-13865.2.patch, > HBASE-13865.2.patch > > > Its 4 in the book and 2 in a current master. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (HBASE-13865) Increase the default value for hbase.hregion.memstore.block.multipler from 2 to 4 (part 2)
[ https://issues.apache.org/jira/browse/HBASE-13865?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nick Dimiduk updated HBASE-13865: - Summary: Increase the default value for hbase.hregion.memstore.block.multipler from 2 to 4 (part 2) (was: Increased hbase.hregion.memstore.block.multiplier from 2 to 4) > Increase the default value for hbase.hregion.memstore.block.multipler from 2 > to 4 (part 2) > -- > > Key: HBASE-13865 > URL: https://issues.apache.org/jira/browse/HBASE-13865 > Project: HBase > Issue Type: Bug > Components: documentation >Affects Versions: 2.0.0 >Reporter: Vladimir Rodionov >Assignee: Gabor Liptak >Priority: Trivial > Attachments: HBASE-13865.1.patch, HBASE-13865.2.patch, > HBASE-13865.2.patch > > > Its 4 in the book and 2 in a current master. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (HBASE-13865) Increased hbase.hregion.memstore.block.multiplier from 2 to 4
[ https://issues.apache.org/jira/browse/HBASE-13865?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nick Dimiduk updated HBASE-13865: - Summary: Increased hbase.hregion.memstore.block.multiplier from 2 to 4 (was: Default value of hbase.hregion.memstore.block.multiplier in HBase book is wrong) > Increased hbase.hregion.memstore.block.multiplier from 2 to 4 > - > > Key: HBASE-13865 > URL: https://issues.apache.org/jira/browse/HBASE-13865 > Project: HBase > Issue Type: Bug > Components: documentation >Affects Versions: 2.0.0 >Reporter: Vladimir Rodionov >Assignee: Gabor Liptak >Priority: Trivial > Attachments: HBASE-13865.1.patch, HBASE-13865.2.patch, > HBASE-13865.2.patch > > > Its 4 in the book and 2 in a current master. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Assigned] (HBASE-12269) Add support for Scan.setRowPrefixFilter to thrift
[ https://issues.apache.org/jira/browse/HBASE-12269?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Niels Basjes reassigned HBASE-12269: Assignee: Niels Basjes > Add support for Scan.setRowPrefixFilter to thrift > - > > Key: HBASE-12269 > URL: https://issues.apache.org/jira/browse/HBASE-12269 > Project: HBase > Issue Type: New Feature > Components: Thrift >Reporter: Niels Basjes >Assignee: Niels Basjes > Attachments: HBASE-12269-2014-10-15-v1.patch, > HBASE-12269-2014-10-16-v2-INCOMPLETE.patch, HBASE-12269-2014-12-05-v2.patch > > > I think having the feature introduced in HBASE-11990 in the hbase thrift > interface would be very useful. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (HBASE-7972) Add a configuration for the TCP backlog in the Thrift server
[ https://issues.apache.org/jira/browse/HBASE-7972?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14658806#comment-14658806 ] Sean Busbey commented on HBASE-7972: still have time to work this [~esteban]? if not, mind if I grab it? > Add a configuration for the TCP backlog in the Thrift server > > > Key: HBASE-7972 > URL: https://issues.apache.org/jira/browse/HBASE-7972 > Project: HBase > Issue Type: Improvement > Components: Thrift >Affects Versions: 2.0.0, 1.3.0 >Reporter: Jean-Daniel Cryans >Assignee: Esteban Gutierrez > Labels: thrift, thrift2 > Fix For: 2.0.0, 1.3.0 > > > Once THRIFT-1868 goes in, we can start letting our users configure the TCP > backlog. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (HBASE-13965) Stochastic Load Balancer JMX Metrics
[ https://issues.apache.org/jira/browse/HBASE-13965?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Anonymous updated HBASE-13965: -- Status: Patch Available (was: Reopened) > Stochastic Load Balancer JMX Metrics > > > Key: HBASE-13965 > URL: https://issues.apache.org/jira/browse/HBASE-13965 > Project: HBase > Issue Type: Improvement > Components: Balancer, metrics >Reporter: Lei Chen >Assignee: Lei Chen > Fix For: 2.0.0 > > Attachments: 13965-addendum.txt, HBASE-13965-branch-1.patch, > HBASE-13965-v10.patch, HBASE-13965-v11.patch, HBASE-13965-v3.patch, > HBASE-13965-v4.patch, HBASE-13965-v5.patch, HBASE-13965-v6.patch, > HBASE-13965-v7.patch, HBASE-13965-v8.patch, HBASE-13965-v9.patch, > HBASE-13965_v2.patch, HBase-13965-JConsole.png, HBase-13965-v1.patch, > stochasticloadbalancerclasses_v2.png > > > Today’s default HBase load balancer (the Stochastic load balancer) is cost > function based. The cost function weights are tunable but no visibility into > those cost function results is directly provided. > A driving example is a cluster we have been tuning which has skewed rack size > (one rack has half the nodes of the other few racks). We are tuning the > cluster for uniform response time from all region servers with the ability to > tolerate a rack failure. Balancing LocalityCost, RegionReplicaRack Cost and > RegionCountSkew Cost is difficult without a way to attribute each cost > function’s contribution to overall cost. > What this jira proposes is to provide visibility via JMX into each cost > function of the stochastic load balancer, as well as the overall cost of the > balancing plan. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (HBASE-13965) Stochastic Load Balancer JMX Metrics
[ https://issues.apache.org/jira/browse/HBASE-13965?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Lei Chen updated HBASE-13965: - Attachment: HBASE-13965-branch-1.patch Updates: 1. Included 13965-addendum which tries 5 different ports for JMX connection 2. Fix "balancer already exists" error in TestAssignmentManager. > Stochastic Load Balancer JMX Metrics > > > Key: HBASE-13965 > URL: https://issues.apache.org/jira/browse/HBASE-13965 > Project: HBase > Issue Type: Improvement > Components: Balancer, metrics >Reporter: Lei Chen >Assignee: Lei Chen > Fix For: 2.0.0 > > Attachments: 13965-addendum.txt, HBASE-13965-branch-1.patch, > HBASE-13965-v10.patch, HBASE-13965-v11.patch, HBASE-13965-v3.patch, > HBASE-13965-v4.patch, HBASE-13965-v5.patch, HBASE-13965-v6.patch, > HBASE-13965-v7.patch, HBASE-13965-v8.patch, HBASE-13965-v9.patch, > HBASE-13965_v2.patch, HBase-13965-JConsole.png, HBase-13965-v1.patch, > stochasticloadbalancerclasses_v2.png > > > Today’s default HBase load balancer (the Stochastic load balancer) is cost > function based. The cost function weights are tunable but no visibility into > those cost function results is directly provided. > A driving example is a cluster we have been tuning which has skewed rack size > (one rack has half the nodes of the other few racks). We are tuning the > cluster for uniform response time from all region servers with the ability to > tolerate a rack failure. Balancing LocalityCost, RegionReplicaRack Cost and > RegionCountSkew Cost is difficult without a way to attribute each cost > function’s contribution to overall cost. > What this jira proposes is to provide visibility via JMX into each cost > function of the stochastic load balancer, as well as the overall cost of the > balancing plan. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (HBASE-5878) Use getVisibleLength public api from HdfsDataInputStream from Hadoop-2.
[
https://issues.apache.org/jira/browse/HBASE-5878?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14658525#comment-14658525
]
Ashish Singhi commented on HBASE-5878:
--
I believe the dependency we had was to get a publicly exposed api. Which was
done as part of one of the sub task from HDFS-3184 and we are using that in
this patch.
(sent from mobile excuse if any typos)
> Use getVisibleLength public api from HdfsDataInputStream from Hadoop-2.
> ---
>
> Key: HBASE-5878
> URL: https://issues.apache.org/jira/browse/HBASE-5878
> Project: HBase
> Issue Type: Bug
> Components: wal
>Reporter: Uma Maheswara Rao G
>Assignee: Ashish Singhi
> Fix For: 2.0.0, 1.1.2, 1.3.0, 1.2.1, 1.0.3
>
> Attachments: HBASE-5878-v2.patch, HBASE-5878-v3.patch,
> HBASE-5878-v4.patch, HBASE-5878-v5.patch, HBASE-5878-v5.patch,
> HBASE-5878.patch
>
>
> SequencFileLogReader:
> Currently Hbase using getFileLength api from DFSInputStream class by
> reflection. DFSInputStream is not exposed as public. So, this may change in
> future. Now HDFS exposed HdfsDataInputStream as public API.
> We can make use of it, when we are not able to find the getFileLength api
> from DFSInputStream as a else condition. So, that we will not have any sudden
> surprise like we are facing today.
> Also, it is just logging one warn message and proceeding if it throws any
> exception while getting the length. I think we can re-throw the exception
> because there is no point in continuing with dataloss.
> {code}
> long adjust = 0;
> try {
> Field fIn = FilterInputStream.class.getDeclaredField("in");
> fIn.setAccessible(true);
> Object realIn = fIn.get(this.in);
> // In hadoop 0.22, DFSInputStream is a standalone class. Before
> this,
> // it was an inner class of DFSClient.
> if (realIn.getClass().getName().endsWith("DFSInputStream")) {
> Method getFileLength = realIn.getClass().
> getDeclaredMethod("getFileLength", new Class []{});
> getFileLength.setAccessible(true);
> long realLength = ((Long)getFileLength.
> invoke(realIn, new Object []{})).longValue();
> assert(realLength >= this.length);
> adjust = realLength - this.length;
> } else {
> LOG.info("Input stream class: " + realIn.getClass().getName() +
> ", not adjusting length");
> }
> } catch(Exception e) {
> SequenceFileLogReader.LOG.warn(
> "Error while trying to get accurate file length. " +
> "Truncation / data loss may occur if RegionServers die.", e);
> }
> return adjust + super.getPos();
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (HBASE-14187) Add Thrift 1 RPC to batch gets in a single call
[
https://issues.apache.org/jira/browse/HBASE-14187?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14658519#comment-14658519
]
Sean Busbey commented on HBASE-14187:
-
we've had a customer use this interface in production for some time. when it
was first made, the thrift 1 api was EOL. now that it isn't, we'd like to get
this more widely available.
I'll post a first pass patch with the above definition and implementation and
then we can iterate.
> Add Thrift 1 RPC to batch gets in a single call
> ---
>
> Key: HBASE-14187
> URL: https://issues.apache.org/jira/browse/HBASE-14187
> Project: HBase
> Issue Type: Improvement
> Components: Thrift
>Reporter: Sean Busbey
>Assignee: Sean Busbey
> Fix For: 2.0.0, 1.3.0
>
>
> add a method to pull a set of columns from a set of non-contiguous rows in a
> single RPC call.
> e.g.
> {code}
>/**
> * Parallel get. For a given table and column, return for
> * the given rows.
> *
> * @param tableName table to get from
> * @param column column to get
> * @param rows a list of rows to get
> * @result list of TRowResult for each item
> */
> list parallelGet(1:Text tableName,
> 2:Text column,
> 3:list rows)
> throws (1:IOError io)
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Created] (HBASE-14187) Add Thrift 1 RPC to batch gets in a single call
Sean Busbey created HBASE-14187:
---
Summary: Add Thrift 1 RPC to batch gets in a single call
Key: HBASE-14187
URL: https://issues.apache.org/jira/browse/HBASE-14187
Project: HBase
Issue Type: Improvement
Components: Thrift
Reporter: Sean Busbey
Assignee: Sean Busbey
Fix For: 2.0.0, 1.3.0
add a method to pull a set of columns from a set of non-contiguous rows in a
single RPC call.
e.g.
{code}
/**
* Parallel get. For a given table and column, return for
* the given rows.
*
* @param tableName table to get from
* @param column column to get
* @param rows a list of rows to get
* @result list of TRowResult for each item
*/
list parallelGet(1:Text tableName,
2:Text column,
3:list rows)
throws (1:IOError io)
{code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (HBASE-12341) Overhaul logging; log4j2, machine-readable, etc.
[ https://issues.apache.org/jira/browse/HBASE-12341?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14658502#comment-14658502 ] Andrew Purtell commented on HBASE-12341: We should consider reviving this now that log4j v1 is officially EOL: https://blogs.apache.org/foundation/entry/apache_logging_services_project_announces > Overhaul logging; log4j2, machine-readable, etc. > > > Key: HBASE-12341 > URL: https://issues.apache.org/jira/browse/HBASE-12341 > Project: HBase > Issue Type: Umbrella >Reporter: stack > Fix For: 2.0.0 > > > This is a general umbrella issue for 2.x logging improvements. Hang related > work off this one. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (HBASE-10092) Move up on to log4j2
[ https://issues.apache.org/jira/browse/HBASE-10092?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrew Purtell updated HBASE-10092: --- Status: Open (was: Patch Available) Cancelling stale patch > Move up on to log4j2 > > > Key: HBASE-10092 > URL: https://issues.apache.org/jira/browse/HBASE-10092 > Project: HBase > Issue Type: Sub-task >Reporter: stack >Assignee: Alex Newman > Fix For: 2.0.0 > > Attachments: 10092.txt, 10092v2.txt, HBASE-10092-preview-v0.patch, > HBASE-10092.patch > > > Allows logging with less friction. See http://logging.apache.org/log4j/2.x/ > This rather radical transition can be done w/ minor change given they have an > adapter for apache's logging, the one we use. They also have and adapter for > slf4j so we likely can remove at least some of the 4 versions of this module > our dependencies make use of. > I made a start in attached patch but am currently stuck in maven dependency > resolve hell courtesy of our slf4j. Fixing will take some concentration and > a good net connection, an item I currently lack. Other TODOs are that will > need to fix our little log level setting jsp page -- will likely have to undo > our use of hadoop's tool here -- and the config system changes a little. > I will return to this project soon. Will bring numbers. > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (HBASE-10092) Move up on to log4j2
[ https://issues.apache.org/jira/browse/HBASE-10092?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14658505#comment-14658505 ] Andrew Purtell commented on HBASE-10092: We should consider reviving this now that log4j v1 is officially EOL: https://blogs.apache.org/foundation/entry/apache_logging_services_project_announces > Move up on to log4j2 > > > Key: HBASE-10092 > URL: https://issues.apache.org/jira/browse/HBASE-10092 > Project: HBase > Issue Type: Sub-task >Reporter: stack >Assignee: Alex Newman > Fix For: 2.0.0 > > Attachments: 10092.txt, 10092v2.txt, HBASE-10092-preview-v0.patch, > HBASE-10092.patch > > > Allows logging with less friction. See http://logging.apache.org/log4j/2.x/ > This rather radical transition can be done w/ minor change given they have an > adapter for apache's logging, the one we use. They also have and adapter for > slf4j so we likely can remove at least some of the 4 versions of this module > our dependencies make use of. > I made a start in attached patch but am currently stuck in maven dependency > resolve hell courtesy of our slf4j. Fixing will take some concentration and > a good net connection, an item I currently lack. Other TODOs are that will > need to fix our little log level setting jsp page -- will likely have to undo > our use of hadoop's tool here -- and the config system changes a little. > I will return to this project soon. Will bring numbers. > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Resolved] (HBASE-11334) Migrate to SLF4J as logging interface
[ https://issues.apache.org/jira/browse/HBASE-11334?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrew Purtell resolved HBASE-11334. Resolution: Won't Fix We also resolved HBASE-2608 as Wont Fix > Migrate to SLF4J as logging interface > - > > Key: HBASE-11334 > URL: https://issues.apache.org/jira/browse/HBASE-11334 > Project: HBase > Issue Type: Improvement >Reporter: jay vyas > > Migrating to new log implementations is underway as in HBASE-10092. > Next step would be to abstract them so that the hadoop community can > standardize on a logging layer that is easy for end users to tune. > Simplest way to do this is use SLF4j APIs as the main interface and binding/ > implementation details in the docs as necessary. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (HBASE-5878) Use getVisibleLength public api from HdfsDataInputStream from Hadoop-2.
[
https://issues.apache.org/jira/browse/HBASE-5878?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14658488#comment-14658488
]
Nick Dimiduk commented on HBASE-5878:
-
What's the dependency on HDFS-3184 -- is that really a dependency before we
commit this?
> Use getVisibleLength public api from HdfsDataInputStream from Hadoop-2.
> ---
>
> Key: HBASE-5878
> URL: https://issues.apache.org/jira/browse/HBASE-5878
> Project: HBase
> Issue Type: Bug
> Components: wal
>Reporter: Uma Maheswara Rao G
>Assignee: Ashish Singhi
> Fix For: 2.0.0, 1.1.2, 1.3.0, 1.2.1, 1.0.3
>
> Attachments: HBASE-5878-v2.patch, HBASE-5878-v3.patch,
> HBASE-5878-v4.patch, HBASE-5878-v5.patch, HBASE-5878-v5.patch,
> HBASE-5878.patch
>
>
> SequencFileLogReader:
> Currently Hbase using getFileLength api from DFSInputStream class by
> reflection. DFSInputStream is not exposed as public. So, this may change in
> future. Now HDFS exposed HdfsDataInputStream as public API.
> We can make use of it, when we are not able to find the getFileLength api
> from DFSInputStream as a else condition. So, that we will not have any sudden
> surprise like we are facing today.
> Also, it is just logging one warn message and proceeding if it throws any
> exception while getting the length. I think we can re-throw the exception
> because there is no point in continuing with dataloss.
> {code}
> long adjust = 0;
> try {
> Field fIn = FilterInputStream.class.getDeclaredField("in");
> fIn.setAccessible(true);
> Object realIn = fIn.get(this.in);
> // In hadoop 0.22, DFSInputStream is a standalone class. Before
> this,
> // it was an inner class of DFSClient.
> if (realIn.getClass().getName().endsWith("DFSInputStream")) {
> Method getFileLength = realIn.getClass().
> getDeclaredMethod("getFileLength", new Class []{});
> getFileLength.setAccessible(true);
> long realLength = ((Long)getFileLength.
> invoke(realIn, new Object []{})).longValue();
> assert(realLength >= this.length);
> adjust = realLength - this.length;
> } else {
> LOG.info("Input stream class: " + realIn.getClass().getName() +
> ", not adjusting length");
> }
> } catch(Exception e) {
> SequenceFileLogReader.LOG.warn(
> "Error while trying to get accurate file length. " +
> "Truncation / data loss may occur if RegionServers die.", e);
> }
> return adjust + super.getPos();
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (HBASE-14178) regionserver blocks because of waiting for offsetLock
[
https://issues.apache.org/jira/browse/HBASE-14178?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14658282#comment-14658282
]
Ted Yu commented on HBASE-14178:
+1
> regionserver blocks because of waiting for offsetLock
> -
>
> Key: HBASE-14178
> URL: https://issues.apache.org/jira/browse/HBASE-14178
> Project: HBase
> Issue Type: Bug
> Components: regionserver
>Affects Versions: 0.98.6
>Reporter: Heng Chen
>Priority: Critical
> Fix For: 0.98.6
>
> Attachments: HBASE-14178-0.98.patch, HBASE-14178.patch,
> HBASE-14178_v1.patch, HBASE-14178_v2.patch, HBASE-14178_v3.patch,
> HBASE-14178_v4.patch, HBASE-14178_v5.patch, HBASE-14178_v6.patch, jstack
>
>
> My regionserver blocks, and all client rpc timeout.
> I print the regionserver's jstack, it seems a lot of threads were blocked
> for waiting offsetLock, detail infomation belows:
> PS: my table's block cache is off
> {code}
> "B.DefaultRpcServer.handler=2,queue=2,port=60020" #82 daemon prio=5 os_prio=0
> tid=0x01827000 nid=0x2cdc in Object.wait() [0x7f3831b72000]
>java.lang.Thread.State: WAITING (on object monitor)
> at java.lang.Object.wait(Native Method)
> at java.lang.Object.wait(Object.java:502)
> at org.apache.hadoop.hbase.util.IdLock.getLockEntry(IdLock.java:79)
> - locked <0x000773af7c18> (a
> org.apache.hadoop.hbase.util.IdLock$Entry)
> at
> org.apache.hadoop.hbase.io.hfile.HFileReaderV2.readBlock(HFileReaderV2.java:352)
> at
> org.apache.hadoop.hbase.io.hfile.HFileBlockIndex$BlockIndexReader.loadDataBlockWithScanInfo(HFileBlockIndex.java:253)
> at
> org.apache.hadoop.hbase.io.hfile.HFileReaderV2$AbstractScannerV2.seekTo(HFileReaderV2.java:524)
> at
> org.apache.hadoop.hbase.io.hfile.HFileReaderV2$AbstractScannerV2.reseekTo(HFileReaderV2.java:572)
> at
> org.apache.hadoop.hbase.regionserver.StoreFileScanner.reseekAtOrAfter(StoreFileScanner.java:257)
> at
> org.apache.hadoop.hbase.regionserver.StoreFileScanner.reseek(StoreFileScanner.java:173)
> at
> org.apache.hadoop.hbase.regionserver.NonLazyKeyValueScanner.doRealSeek(NonLazyKeyValueScanner.java:55)
> at
> org.apache.hadoop.hbase.regionserver.KeyValueHeap.generalizedSeek(KeyValueHeap.java:313)
> at
> org.apache.hadoop.hbase.regionserver.KeyValueHeap.requestSeek(KeyValueHeap.java:269)
> at
> org.apache.hadoop.hbase.regionserver.StoreScanner.reseek(StoreScanner.java:695)
> at
> org.apache.hadoop.hbase.regionserver.StoreScanner.seekAsDirection(StoreScanner.java:683)
> at
> org.apache.hadoop.hbase.regionserver.StoreScanner.next(StoreScanner.java:533)
> at
> org.apache.hadoop.hbase.regionserver.KeyValueHeap.next(KeyValueHeap.java:140)
> at
> org.apache.hadoop.hbase.regionserver.HRegion$RegionScannerImpl.populateResult(HRegion.java:3889)
> at
> org.apache.hadoop.hbase.regionserver.HRegion$RegionScannerImpl.nextInternal(HRegion.java:3969)
> at
> org.apache.hadoop.hbase.regionserver.HRegion$RegionScannerImpl.nextRaw(HRegion.java:3847)
> at
> org.apache.hadoop.hbase.regionserver.HRegion$RegionScannerImpl.next(HRegion.java:3820)
> - locked <0x0005e5c55ad0> (a
> org.apache.hadoop.hbase.regionserver.HRegion$RegionScannerImpl)
> at
> org.apache.hadoop.hbase.regionserver.HRegion$RegionScannerImpl.next(HRegion.java:3807)
> at org.apache.hadoop.hbase.regionserver.HRegion.get(HRegion.java:4779)
> at org.apache.hadoop.hbase.regionserver.HRegion.get(HRegion.java:4753)
> at
> org.apache.hadoop.hbase.regionserver.HRegionServer.get(HRegionServer.java:2916)
> at
> org.apache.hadoop.hbase.protobuf.generated.ClientProtos$ClientService$2.callBlockingMethod(ClientProtos.java:29583)
> at org.apache.hadoop.hbase.ipc.RpcServer.call(RpcServer.java:2027)
> at org.apache.hadoop.hbase.ipc.CallRunner.run(CallRunner.java:108)
> at
> org.apache.hadoop.hbase.ipc.RpcExecutor.consumerLoop(RpcExecutor.java:114)
> at org.apache.hadoop.hbase.ipc.RpcExecutor$1.run(RpcExecutor.java:94)
> at java.lang.Thread.run(Thread.java:745)
>Locked ownable synchronizers:
> - <0x0005e5c55c08> (a
> java.util.concurrent.locks.ReentrantLock$NonfairSync)
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (HBASE-14178) regionserver blocks because of waiting for offsetLock
[
https://issues.apache.org/jira/browse/HBASE-14178?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14658266#comment-14658266
]
Hadoop QA commented on HBASE-14178:
---
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12748841/HBASE-14178_v6.patch
against master branch at commit 18c9bb8b54a5bb101f793e555272cbc74b8288cb.
ATTACHMENT ID: 12748841
{color:green}+1 @author{color}. The patch does not contain any @author
tags.
{color:red}-1 tests included{color}. The patch doesn't appear to include
any new or modified tests.
Please justify why no new tests are needed for this
patch.
Also please list what manual steps were performed to
verify this patch.
{color:green}+1 hadoop versions{color}. The patch compiles with all
supported hadoop versions (2.4.0 2.4.1 2.5.0 2.5.1 2.5.2 2.6.0 2.7.0)
{color:green}+1 javac{color}. The applied patch does not increase the
total number of javac compiler warnings.
{color:green}+1 protoc{color}. The applied patch does not increase the
total number of protoc compiler warnings.
{color:green}+1 javadoc{color}. The javadoc tool did not generate any
warning messages.
{color:green}+1 checkstyle{color}. The applied patch does not increase the
total number of checkstyle errors
{color:green}+1 findbugs{color}. The patch does not introduce any new
Findbugs (version 2.0.3) warnings.
{color:green}+1 release audit{color}. The applied patch does not increase
the total number of release audit warnings.
{color:green}+1 lineLengths{color}. The patch does not introduce lines
longer than 100
{color:green}+1 site{color}. The mvn post-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/14983//testReport/
Release Findbugs (version 2.0.3)warnings:
https://builds.apache.org/job/PreCommit-HBASE-Build/14983//artifact/patchprocess/newFindbugsWarnings.html
Checkstyle Errors:
https://builds.apache.org/job/PreCommit-HBASE-Build/14983//artifact/patchprocess/checkstyle-aggregate.html
Console output:
https://builds.apache.org/job/PreCommit-HBASE-Build/14983//console
This message is automatically generated.
> regionserver blocks because of waiting for offsetLock
> -
>
> Key: HBASE-14178
> URL: https://issues.apache.org/jira/browse/HBASE-14178
> Project: HBase
> Issue Type: Bug
> Components: regionserver
>Affects Versions: 0.98.6
>Reporter: Heng Chen
>Priority: Critical
> Fix For: 0.98.6
>
> Attachments: HBASE-14178-0.98.patch, HBASE-14178.patch,
> HBASE-14178_v1.patch, HBASE-14178_v2.patch, HBASE-14178_v3.patch,
> HBASE-14178_v4.patch, HBASE-14178_v5.patch, HBASE-14178_v6.patch, jstack
>
>
> My regionserver blocks, and all client rpc timeout.
> I print the regionserver's jstack, it seems a lot of threads were blocked
> for waiting offsetLock, detail infomation belows:
> PS: my table's block cache is off
> {code}
> "B.DefaultRpcServer.handler=2,queue=2,port=60020" #82 daemon prio=5 os_prio=0
> tid=0x01827000 nid=0x2cdc in Object.wait() [0x7f3831b72000]
>java.lang.Thread.State: WAITING (on object monitor)
> at java.lang.Object.wait(Native Method)
> at java.lang.Object.wait(Object.java:502)
> at org.apache.hadoop.hbase.util.IdLock.getLockEntry(IdLock.java:79)
> - locked <0x000773af7c18> (a
> org.apache.hadoop.hbase.util.IdLock$Entry)
> at
> org.apache.hadoop.hbase.io.hfile.HFileReaderV2.readBlock(HFileReaderV2.java:352)
> at
> org.apache.hadoop.hbase.io.hfile.HFileBlockIndex$BlockIndexReader.loadDataBlockWithScanInfo(HFileBlockIndex.java:253)
> at
> org.apache.hadoop.hbase.io.hfile.HFileReaderV2$AbstractScannerV2.seekTo(HFileReaderV2.java:524)
> at
> org.apache.hadoop.hbase.io.hfile.HFileReaderV2$AbstractScannerV2.reseekTo(HFileReaderV2.java:572)
> at
> org.apache.hadoop.hbase.regionserver.StoreFileScanner.reseekAtOrAfter(StoreFileScanner.java:257)
> at
> org.apache.hadoop.hbase.regionserver.StoreFileScanner.reseek(StoreFileScanner.java:173)
> at
> org.apache.hadoop.hbase.regionserver.NonLazyKeyValueScanner.doRealSeek(NonLazyKeyValueScanner.java:55)
> at
> org.apache.hadoop.hbase.regionserver.KeyValueHeap.generalizedSeek(KeyValueHeap.java:313)
> at
> org.apache.hadoop.hbase.regionserver.KeyValueHeap.requestSeek(KeyValueHeap.java:269)
> at
> org.apache.hadoop.hbase.regionserver.StoreScanner.reseek(StoreScanner.java:695)
> at
> org.apache.hadoop.hbase.regionserver.StoreScanne
[jira] [Updated] (HBASE-14178) regionserver blocks because of waiting for offsetLock
[
https://issues.apache.org/jira/browse/HBASE-14178?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Duo Zhang updated HBASE-14178:
--
Attachment: HBASE-14178_v6.patch
Retry.
> regionserver blocks because of waiting for offsetLock
> -
>
> Key: HBASE-14178
> URL: https://issues.apache.org/jira/browse/HBASE-14178
> Project: HBase
> Issue Type: Bug
> Components: regionserver
>Affects Versions: 0.98.6
>Reporter: Heng Chen
>Priority: Critical
> Fix For: 0.98.6
>
> Attachments: HBASE-14178-0.98.patch, HBASE-14178.patch,
> HBASE-14178_v1.patch, HBASE-14178_v2.patch, HBASE-14178_v3.patch,
> HBASE-14178_v4.patch, HBASE-14178_v5.patch, HBASE-14178_v6.patch, jstack
>
>
> My regionserver blocks, and all client rpc timeout.
> I print the regionserver's jstack, it seems a lot of threads were blocked
> for waiting offsetLock, detail infomation belows:
> PS: my table's block cache is off
> {code}
> "B.DefaultRpcServer.handler=2,queue=2,port=60020" #82 daemon prio=5 os_prio=0
> tid=0x01827000 nid=0x2cdc in Object.wait() [0x7f3831b72000]
>java.lang.Thread.State: WAITING (on object monitor)
> at java.lang.Object.wait(Native Method)
> at java.lang.Object.wait(Object.java:502)
> at org.apache.hadoop.hbase.util.IdLock.getLockEntry(IdLock.java:79)
> - locked <0x000773af7c18> (a
> org.apache.hadoop.hbase.util.IdLock$Entry)
> at
> org.apache.hadoop.hbase.io.hfile.HFileReaderV2.readBlock(HFileReaderV2.java:352)
> at
> org.apache.hadoop.hbase.io.hfile.HFileBlockIndex$BlockIndexReader.loadDataBlockWithScanInfo(HFileBlockIndex.java:253)
> at
> org.apache.hadoop.hbase.io.hfile.HFileReaderV2$AbstractScannerV2.seekTo(HFileReaderV2.java:524)
> at
> org.apache.hadoop.hbase.io.hfile.HFileReaderV2$AbstractScannerV2.reseekTo(HFileReaderV2.java:572)
> at
> org.apache.hadoop.hbase.regionserver.StoreFileScanner.reseekAtOrAfter(StoreFileScanner.java:257)
> at
> org.apache.hadoop.hbase.regionserver.StoreFileScanner.reseek(StoreFileScanner.java:173)
> at
> org.apache.hadoop.hbase.regionserver.NonLazyKeyValueScanner.doRealSeek(NonLazyKeyValueScanner.java:55)
> at
> org.apache.hadoop.hbase.regionserver.KeyValueHeap.generalizedSeek(KeyValueHeap.java:313)
> at
> org.apache.hadoop.hbase.regionserver.KeyValueHeap.requestSeek(KeyValueHeap.java:269)
> at
> org.apache.hadoop.hbase.regionserver.StoreScanner.reseek(StoreScanner.java:695)
> at
> org.apache.hadoop.hbase.regionserver.StoreScanner.seekAsDirection(StoreScanner.java:683)
> at
> org.apache.hadoop.hbase.regionserver.StoreScanner.next(StoreScanner.java:533)
> at
> org.apache.hadoop.hbase.regionserver.KeyValueHeap.next(KeyValueHeap.java:140)
> at
> org.apache.hadoop.hbase.regionserver.HRegion$RegionScannerImpl.populateResult(HRegion.java:3889)
> at
> org.apache.hadoop.hbase.regionserver.HRegion$RegionScannerImpl.nextInternal(HRegion.java:3969)
> at
> org.apache.hadoop.hbase.regionserver.HRegion$RegionScannerImpl.nextRaw(HRegion.java:3847)
> at
> org.apache.hadoop.hbase.regionserver.HRegion$RegionScannerImpl.next(HRegion.java:3820)
> - locked <0x0005e5c55ad0> (a
> org.apache.hadoop.hbase.regionserver.HRegion$RegionScannerImpl)
> at
> org.apache.hadoop.hbase.regionserver.HRegion$RegionScannerImpl.next(HRegion.java:3807)
> at org.apache.hadoop.hbase.regionserver.HRegion.get(HRegion.java:4779)
> at org.apache.hadoop.hbase.regionserver.HRegion.get(HRegion.java:4753)
> at
> org.apache.hadoop.hbase.regionserver.HRegionServer.get(HRegionServer.java:2916)
> at
> org.apache.hadoop.hbase.protobuf.generated.ClientProtos$ClientService$2.callBlockingMethod(ClientProtos.java:29583)
> at org.apache.hadoop.hbase.ipc.RpcServer.call(RpcServer.java:2027)
> at org.apache.hadoop.hbase.ipc.CallRunner.run(CallRunner.java:108)
> at
> org.apache.hadoop.hbase.ipc.RpcExecutor.consumerLoop(RpcExecutor.java:114)
> at org.apache.hadoop.hbase.ipc.RpcExecutor$1.run(RpcExecutor.java:94)
> at java.lang.Thread.run(Thread.java:745)
>Locked ownable synchronizers:
> - <0x0005e5c55c08> (a
> java.util.concurrent.locks.ReentrantLock$NonfairSync)
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (HBASE-14178) regionserver blocks because of waiting for offsetLock
[
https://issues.apache.org/jira/browse/HBASE-14178?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Duo Zhang updated HBASE-14178:
--
Attachment: (was: HBASE-14178_v6.patch)
> regionserver blocks because of waiting for offsetLock
> -
>
> Key: HBASE-14178
> URL: https://issues.apache.org/jira/browse/HBASE-14178
> Project: HBase
> Issue Type: Bug
> Components: regionserver
>Affects Versions: 0.98.6
>Reporter: Heng Chen
>Priority: Critical
> Fix For: 0.98.6
>
> Attachments: HBASE-14178-0.98.patch, HBASE-14178.patch,
> HBASE-14178_v1.patch, HBASE-14178_v2.patch, HBASE-14178_v3.patch,
> HBASE-14178_v4.patch, HBASE-14178_v5.patch, HBASE-14178_v6.patch, jstack
>
>
> My regionserver blocks, and all client rpc timeout.
> I print the regionserver's jstack, it seems a lot of threads were blocked
> for waiting offsetLock, detail infomation belows:
> PS: my table's block cache is off
> {code}
> "B.DefaultRpcServer.handler=2,queue=2,port=60020" #82 daemon prio=5 os_prio=0
> tid=0x01827000 nid=0x2cdc in Object.wait() [0x7f3831b72000]
>java.lang.Thread.State: WAITING (on object monitor)
> at java.lang.Object.wait(Native Method)
> at java.lang.Object.wait(Object.java:502)
> at org.apache.hadoop.hbase.util.IdLock.getLockEntry(IdLock.java:79)
> - locked <0x000773af7c18> (a
> org.apache.hadoop.hbase.util.IdLock$Entry)
> at
> org.apache.hadoop.hbase.io.hfile.HFileReaderV2.readBlock(HFileReaderV2.java:352)
> at
> org.apache.hadoop.hbase.io.hfile.HFileBlockIndex$BlockIndexReader.loadDataBlockWithScanInfo(HFileBlockIndex.java:253)
> at
> org.apache.hadoop.hbase.io.hfile.HFileReaderV2$AbstractScannerV2.seekTo(HFileReaderV2.java:524)
> at
> org.apache.hadoop.hbase.io.hfile.HFileReaderV2$AbstractScannerV2.reseekTo(HFileReaderV2.java:572)
> at
> org.apache.hadoop.hbase.regionserver.StoreFileScanner.reseekAtOrAfter(StoreFileScanner.java:257)
> at
> org.apache.hadoop.hbase.regionserver.StoreFileScanner.reseek(StoreFileScanner.java:173)
> at
> org.apache.hadoop.hbase.regionserver.NonLazyKeyValueScanner.doRealSeek(NonLazyKeyValueScanner.java:55)
> at
> org.apache.hadoop.hbase.regionserver.KeyValueHeap.generalizedSeek(KeyValueHeap.java:313)
> at
> org.apache.hadoop.hbase.regionserver.KeyValueHeap.requestSeek(KeyValueHeap.java:269)
> at
> org.apache.hadoop.hbase.regionserver.StoreScanner.reseek(StoreScanner.java:695)
> at
> org.apache.hadoop.hbase.regionserver.StoreScanner.seekAsDirection(StoreScanner.java:683)
> at
> org.apache.hadoop.hbase.regionserver.StoreScanner.next(StoreScanner.java:533)
> at
> org.apache.hadoop.hbase.regionserver.KeyValueHeap.next(KeyValueHeap.java:140)
> at
> org.apache.hadoop.hbase.regionserver.HRegion$RegionScannerImpl.populateResult(HRegion.java:3889)
> at
> org.apache.hadoop.hbase.regionserver.HRegion$RegionScannerImpl.nextInternal(HRegion.java:3969)
> at
> org.apache.hadoop.hbase.regionserver.HRegion$RegionScannerImpl.nextRaw(HRegion.java:3847)
> at
> org.apache.hadoop.hbase.regionserver.HRegion$RegionScannerImpl.next(HRegion.java:3820)
> - locked <0x0005e5c55ad0> (a
> org.apache.hadoop.hbase.regionserver.HRegion$RegionScannerImpl)
> at
> org.apache.hadoop.hbase.regionserver.HRegion$RegionScannerImpl.next(HRegion.java:3807)
> at org.apache.hadoop.hbase.regionserver.HRegion.get(HRegion.java:4779)
> at org.apache.hadoop.hbase.regionserver.HRegion.get(HRegion.java:4753)
> at
> org.apache.hadoop.hbase.regionserver.HRegionServer.get(HRegionServer.java:2916)
> at
> org.apache.hadoop.hbase.protobuf.generated.ClientProtos$ClientService$2.callBlockingMethod(ClientProtos.java:29583)
> at org.apache.hadoop.hbase.ipc.RpcServer.call(RpcServer.java:2027)
> at org.apache.hadoop.hbase.ipc.CallRunner.run(CallRunner.java:108)
> at
> org.apache.hadoop.hbase.ipc.RpcExecutor.consumerLoop(RpcExecutor.java:114)
> at org.apache.hadoop.hbase.ipc.RpcExecutor$1.run(RpcExecutor.java:94)
> at java.lang.Thread.run(Thread.java:745)
>Locked ownable synchronizers:
> - <0x0005e5c55c08> (a
> java.util.concurrent.locks.ReentrantLock$NonfairSync)
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (HBASE-13014) Java Tool For Region Moving
[ https://issues.apache.org/jira/browse/HBASE-13014?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14655070#comment-14655070 ] Abhishek Singh Chouhan commented on HBASE-13014: Ping [~lhofhansl] :) > Java Tool For Region Moving > > > Key: HBASE-13014 > URL: https://issues.apache.org/jira/browse/HBASE-13014 > Project: HBase > Issue Type: Improvement >Reporter: Abhishek Singh Chouhan >Assignee: Abhishek Singh Chouhan > Fix For: 2.0.0, 0.98.14, 1.3.0 > > Attachments: HBASE-13014-v2.patch, HBASE-13014-v3.patch, > HBASE-13014-v4.patch, HBASE-13014-v5.patch, HBASE-13014-v6.patch, > HBASE-13014.patch > > > As per discussion on HBASE-12989 we should move the functionality of > region_mover.rb into a Java tool and use region_mover.rb only only as a > wrapper around it. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (HBASE-14183) [Shell] Scanning hbase meta table is failing in master branch
[ https://issues.apache.org/jira/browse/HBASE-14183?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14655016#comment-14655016 ] Hudson commented on HBASE-14183: FAILURE: Integrated in HBase-TRUNK #6698 (See [https://builds.apache.org/job/HBase-TRUNK/6698/]) HBASE-14183 Scanning hbase meta table is failing in master branch.(Ashish) (anoopsamjohn: rev 18c9bb8b54a5bb101f793e555272cbc74b8288cb) * hbase-shell/src/main/ruby/hbase/table.rb * hbase-shell/src/test/ruby/hbase/table_test.rb > [Shell] Scanning hbase meta table is failing in master branch > - > > Key: HBASE-14183 > URL: https://issues.apache.org/jira/browse/HBASE-14183 > Project: HBase > Issue Type: Bug > Components: shell >Affects Versions: 2.0.0 >Reporter: Ashish Singhi >Assignee: Ashish Singhi > Fix For: 2.0.0 > > Attachments: HBASE-14183-v1.patch, HBASE-14183.patch > > > As part of HBASE-14047 cleanup this issue has been introduced. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (HBASE-14178) regionserver blocks because of waiting for offsetLock
[
https://issues.apache.org/jira/browse/HBASE-14178?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Duo Zhang updated HBASE-14178:
--
Attachment: HBASE-14178_v6.patch
A flaky test(TestFastFail) failed in pre-commit. Retry.
> regionserver blocks because of waiting for offsetLock
> -
>
> Key: HBASE-14178
> URL: https://issues.apache.org/jira/browse/HBASE-14178
> Project: HBase
> Issue Type: Bug
> Components: regionserver
>Affects Versions: 0.98.6
>Reporter: Heng Chen
>Priority: Critical
> Fix For: 0.98.6
>
> Attachments: HBASE-14178-0.98.patch, HBASE-14178.patch,
> HBASE-14178_v1.patch, HBASE-14178_v2.patch, HBASE-14178_v3.patch,
> HBASE-14178_v4.patch, HBASE-14178_v5.patch, HBASE-14178_v6.patch, jstack
>
>
> My regionserver blocks, and all client rpc timeout.
> I print the regionserver's jstack, it seems a lot of threads were blocked
> for waiting offsetLock, detail infomation belows:
> PS: my table's block cache is off
> {code}
> "B.DefaultRpcServer.handler=2,queue=2,port=60020" #82 daemon prio=5 os_prio=0
> tid=0x01827000 nid=0x2cdc in Object.wait() [0x7f3831b72000]
>java.lang.Thread.State: WAITING (on object monitor)
> at java.lang.Object.wait(Native Method)
> at java.lang.Object.wait(Object.java:502)
> at org.apache.hadoop.hbase.util.IdLock.getLockEntry(IdLock.java:79)
> - locked <0x000773af7c18> (a
> org.apache.hadoop.hbase.util.IdLock$Entry)
> at
> org.apache.hadoop.hbase.io.hfile.HFileReaderV2.readBlock(HFileReaderV2.java:352)
> at
> org.apache.hadoop.hbase.io.hfile.HFileBlockIndex$BlockIndexReader.loadDataBlockWithScanInfo(HFileBlockIndex.java:253)
> at
> org.apache.hadoop.hbase.io.hfile.HFileReaderV2$AbstractScannerV2.seekTo(HFileReaderV2.java:524)
> at
> org.apache.hadoop.hbase.io.hfile.HFileReaderV2$AbstractScannerV2.reseekTo(HFileReaderV2.java:572)
> at
> org.apache.hadoop.hbase.regionserver.StoreFileScanner.reseekAtOrAfter(StoreFileScanner.java:257)
> at
> org.apache.hadoop.hbase.regionserver.StoreFileScanner.reseek(StoreFileScanner.java:173)
> at
> org.apache.hadoop.hbase.regionserver.NonLazyKeyValueScanner.doRealSeek(NonLazyKeyValueScanner.java:55)
> at
> org.apache.hadoop.hbase.regionserver.KeyValueHeap.generalizedSeek(KeyValueHeap.java:313)
> at
> org.apache.hadoop.hbase.regionserver.KeyValueHeap.requestSeek(KeyValueHeap.java:269)
> at
> org.apache.hadoop.hbase.regionserver.StoreScanner.reseek(StoreScanner.java:695)
> at
> org.apache.hadoop.hbase.regionserver.StoreScanner.seekAsDirection(StoreScanner.java:683)
> at
> org.apache.hadoop.hbase.regionserver.StoreScanner.next(StoreScanner.java:533)
> at
> org.apache.hadoop.hbase.regionserver.KeyValueHeap.next(KeyValueHeap.java:140)
> at
> org.apache.hadoop.hbase.regionserver.HRegion$RegionScannerImpl.populateResult(HRegion.java:3889)
> at
> org.apache.hadoop.hbase.regionserver.HRegion$RegionScannerImpl.nextInternal(HRegion.java:3969)
> at
> org.apache.hadoop.hbase.regionserver.HRegion$RegionScannerImpl.nextRaw(HRegion.java:3847)
> at
> org.apache.hadoop.hbase.regionserver.HRegion$RegionScannerImpl.next(HRegion.java:3820)
> - locked <0x0005e5c55ad0> (a
> org.apache.hadoop.hbase.regionserver.HRegion$RegionScannerImpl)
> at
> org.apache.hadoop.hbase.regionserver.HRegion$RegionScannerImpl.next(HRegion.java:3807)
> at org.apache.hadoop.hbase.regionserver.HRegion.get(HRegion.java:4779)
> at org.apache.hadoop.hbase.regionserver.HRegion.get(HRegion.java:4753)
> at
> org.apache.hadoop.hbase.regionserver.HRegionServer.get(HRegionServer.java:2916)
> at
> org.apache.hadoop.hbase.protobuf.generated.ClientProtos$ClientService$2.callBlockingMethod(ClientProtos.java:29583)
> at org.apache.hadoop.hbase.ipc.RpcServer.call(RpcServer.java:2027)
> at org.apache.hadoop.hbase.ipc.CallRunner.run(CallRunner.java:108)
> at
> org.apache.hadoop.hbase.ipc.RpcExecutor.consumerLoop(RpcExecutor.java:114)
> at org.apache.hadoop.hbase.ipc.RpcExecutor$1.run(RpcExecutor.java:94)
> at java.lang.Thread.run(Thread.java:745)
>Locked ownable synchronizers:
> - <0x0005e5c55c08> (a
> java.util.concurrent.locks.ReentrantLock$NonfairSync)
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (HBASE-14178) regionserver blocks because of waiting for offsetLock
[
https://issues.apache.org/jira/browse/HBASE-14178?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Duo Zhang updated HBASE-14178:
--
Attachment: (was: HBASE-14178_v6.patch)
> regionserver blocks because of waiting for offsetLock
> -
>
> Key: HBASE-14178
> URL: https://issues.apache.org/jira/browse/HBASE-14178
> Project: HBase
> Issue Type: Bug
> Components: regionserver
>Affects Versions: 0.98.6
>Reporter: Heng Chen
>Priority: Critical
> Fix For: 0.98.6
>
> Attachments: HBASE-14178-0.98.patch, HBASE-14178.patch,
> HBASE-14178_v1.patch, HBASE-14178_v2.patch, HBASE-14178_v3.patch,
> HBASE-14178_v4.patch, HBASE-14178_v5.patch, jstack
>
>
> My regionserver blocks, and all client rpc timeout.
> I print the regionserver's jstack, it seems a lot of threads were blocked
> for waiting offsetLock, detail infomation belows:
> PS: my table's block cache is off
> {code}
> "B.DefaultRpcServer.handler=2,queue=2,port=60020" #82 daemon prio=5 os_prio=0
> tid=0x01827000 nid=0x2cdc in Object.wait() [0x7f3831b72000]
>java.lang.Thread.State: WAITING (on object monitor)
> at java.lang.Object.wait(Native Method)
> at java.lang.Object.wait(Object.java:502)
> at org.apache.hadoop.hbase.util.IdLock.getLockEntry(IdLock.java:79)
> - locked <0x000773af7c18> (a
> org.apache.hadoop.hbase.util.IdLock$Entry)
> at
> org.apache.hadoop.hbase.io.hfile.HFileReaderV2.readBlock(HFileReaderV2.java:352)
> at
> org.apache.hadoop.hbase.io.hfile.HFileBlockIndex$BlockIndexReader.loadDataBlockWithScanInfo(HFileBlockIndex.java:253)
> at
> org.apache.hadoop.hbase.io.hfile.HFileReaderV2$AbstractScannerV2.seekTo(HFileReaderV2.java:524)
> at
> org.apache.hadoop.hbase.io.hfile.HFileReaderV2$AbstractScannerV2.reseekTo(HFileReaderV2.java:572)
> at
> org.apache.hadoop.hbase.regionserver.StoreFileScanner.reseekAtOrAfter(StoreFileScanner.java:257)
> at
> org.apache.hadoop.hbase.regionserver.StoreFileScanner.reseek(StoreFileScanner.java:173)
> at
> org.apache.hadoop.hbase.regionserver.NonLazyKeyValueScanner.doRealSeek(NonLazyKeyValueScanner.java:55)
> at
> org.apache.hadoop.hbase.regionserver.KeyValueHeap.generalizedSeek(KeyValueHeap.java:313)
> at
> org.apache.hadoop.hbase.regionserver.KeyValueHeap.requestSeek(KeyValueHeap.java:269)
> at
> org.apache.hadoop.hbase.regionserver.StoreScanner.reseek(StoreScanner.java:695)
> at
> org.apache.hadoop.hbase.regionserver.StoreScanner.seekAsDirection(StoreScanner.java:683)
> at
> org.apache.hadoop.hbase.regionserver.StoreScanner.next(StoreScanner.java:533)
> at
> org.apache.hadoop.hbase.regionserver.KeyValueHeap.next(KeyValueHeap.java:140)
> at
> org.apache.hadoop.hbase.regionserver.HRegion$RegionScannerImpl.populateResult(HRegion.java:3889)
> at
> org.apache.hadoop.hbase.regionserver.HRegion$RegionScannerImpl.nextInternal(HRegion.java:3969)
> at
> org.apache.hadoop.hbase.regionserver.HRegion$RegionScannerImpl.nextRaw(HRegion.java:3847)
> at
> org.apache.hadoop.hbase.regionserver.HRegion$RegionScannerImpl.next(HRegion.java:3820)
> - locked <0x0005e5c55ad0> (a
> org.apache.hadoop.hbase.regionserver.HRegion$RegionScannerImpl)
> at
> org.apache.hadoop.hbase.regionserver.HRegion$RegionScannerImpl.next(HRegion.java:3807)
> at org.apache.hadoop.hbase.regionserver.HRegion.get(HRegion.java:4779)
> at org.apache.hadoop.hbase.regionserver.HRegion.get(HRegion.java:4753)
> at
> org.apache.hadoop.hbase.regionserver.HRegionServer.get(HRegionServer.java:2916)
> at
> org.apache.hadoop.hbase.protobuf.generated.ClientProtos$ClientService$2.callBlockingMethod(ClientProtos.java:29583)
> at org.apache.hadoop.hbase.ipc.RpcServer.call(RpcServer.java:2027)
> at org.apache.hadoop.hbase.ipc.CallRunner.run(CallRunner.java:108)
> at
> org.apache.hadoop.hbase.ipc.RpcExecutor.consumerLoop(RpcExecutor.java:114)
> at org.apache.hadoop.hbase.ipc.RpcExecutor$1.run(RpcExecutor.java:94)
> at java.lang.Thread.run(Thread.java:745)
>Locked ownable synchronizers:
> - <0x0005e5c55c08> (a
> java.util.concurrent.locks.ReentrantLock$NonfairSync)
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (HBASE-14178) regionserver blocks because of waiting for offsetLock
[
https://issues.apache.org/jira/browse/HBASE-14178?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14654987#comment-14654987
]
Hadoop QA commented on HBASE-14178:
---
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12748782/HBASE-14178_v6.patch
against master branch at commit 18c9bb8b54a5bb101f793e555272cbc74b8288cb.
ATTACHMENT ID: 12748782
{color:green}+1 @author{color}. The patch does not contain any @author
tags.
{color:red}-1 tests included{color}. The patch doesn't appear to include
any new or modified tests.
Please justify why no new tests are needed for this
patch.
Also please list what manual steps were performed to
verify this patch.
{color:green}+1 hadoop versions{color}. The patch compiles with all
supported hadoop versions (2.4.0 2.4.1 2.5.0 2.5.1 2.5.2 2.6.0 2.7.0)
{color:green}+1 javac{color}. The applied patch does not increase the
total number of javac compiler warnings.
{color:green}+1 protoc{color}. The applied patch does not increase the
total number of protoc compiler warnings.
{color:green}+1 javadoc{color}. The javadoc tool did not generate any
warning messages.
{color:green}+1 checkstyle{color}. The applied patch does not increase the
total number of checkstyle errors
{color:green}+1 findbugs{color}. The patch does not introduce any new
Findbugs (version 2.0.3) warnings.
{color:green}+1 release audit{color}. The applied patch does not increase
the total number of release audit warnings.
{color:green}+1 lineLengths{color}. The patch does not introduce lines
longer than 100
{color:green}+1 site{color}. The mvn post-site goal succeeds with this patch.
{color:red}-1 core tests{color}. The patch failed these unit tests:
Test results:
https://builds.apache.org/job/PreCommit-HBASE-Build/14981//testReport/
Release Findbugs (version 2.0.3)warnings:
https://builds.apache.org/job/PreCommit-HBASE-Build/14981//artifact/patchprocess/newFindbugsWarnings.html
Checkstyle Errors:
https://builds.apache.org/job/PreCommit-HBASE-Build/14981//artifact/patchprocess/checkstyle-aggregate.html
Console output:
https://builds.apache.org/job/PreCommit-HBASE-Build/14981//console
This message is automatically generated.
> regionserver blocks because of waiting for offsetLock
> -
>
> Key: HBASE-14178
> URL: https://issues.apache.org/jira/browse/HBASE-14178
> Project: HBase
> Issue Type: Bug
> Components: regionserver
>Affects Versions: 0.98.6
>Reporter: Heng Chen
>Priority: Critical
> Fix For: 0.98.6
>
> Attachments: HBASE-14178-0.98.patch, HBASE-14178.patch,
> HBASE-14178_v1.patch, HBASE-14178_v2.patch, HBASE-14178_v3.patch,
> HBASE-14178_v4.patch, HBASE-14178_v5.patch, HBASE-14178_v6.patch, jstack
>
>
> My regionserver blocks, and all client rpc timeout.
> I print the regionserver's jstack, it seems a lot of threads were blocked
> for waiting offsetLock, detail infomation belows:
> PS: my table's block cache is off
> {code}
> "B.DefaultRpcServer.handler=2,queue=2,port=60020" #82 daemon prio=5 os_prio=0
> tid=0x01827000 nid=0x2cdc in Object.wait() [0x7f3831b72000]
>java.lang.Thread.State: WAITING (on object monitor)
> at java.lang.Object.wait(Native Method)
> at java.lang.Object.wait(Object.java:502)
> at org.apache.hadoop.hbase.util.IdLock.getLockEntry(IdLock.java:79)
> - locked <0x000773af7c18> (a
> org.apache.hadoop.hbase.util.IdLock$Entry)
> at
> org.apache.hadoop.hbase.io.hfile.HFileReaderV2.readBlock(HFileReaderV2.java:352)
> at
> org.apache.hadoop.hbase.io.hfile.HFileBlockIndex$BlockIndexReader.loadDataBlockWithScanInfo(HFileBlockIndex.java:253)
> at
> org.apache.hadoop.hbase.io.hfile.HFileReaderV2$AbstractScannerV2.seekTo(HFileReaderV2.java:524)
> at
> org.apache.hadoop.hbase.io.hfile.HFileReaderV2$AbstractScannerV2.reseekTo(HFileReaderV2.java:572)
> at
> org.apache.hadoop.hbase.regionserver.StoreFileScanner.reseekAtOrAfter(StoreFileScanner.java:257)
> at
> org.apache.hadoop.hbase.regionserver.StoreFileScanner.reseek(StoreFileScanner.java:173)
> at
> org.apache.hadoop.hbase.regionserver.NonLazyKeyValueScanner.doRealSeek(NonLazyKeyValueScanner.java:55)
> at
> org.apache.hadoop.hbase.regionserver.KeyValueHeap.generalizedSeek(KeyValueHeap.java:313)
> at
> org.apache.hadoop.hbase.regionserver.KeyValueHeap.requestSeek(KeyValueHeap.java:269)
> at
> org.apache.hadoop.hbase.regionserver.StoreScanner.reseek(StoreScanner.java:695)
> at
> org.apache.hadoop.hbase.regionserver.Stor
[jira] [Commented] (HBASE-13590) TestEnableTableHandler.testEnableTableWithNoRegionServers is flakey
[ https://issues.apache.org/jira/browse/HBASE-13590?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14654943#comment-14654943 ] Andrey Stepachev commented on HBASE-13590: -- [~ndimiduk] no, sorry, don't working on that for now. > TestEnableTableHandler.testEnableTableWithNoRegionServers is flakey > --- > > Key: HBASE-13590 > URL: https://issues.apache.org/jira/browse/HBASE-13590 > Project: HBase > Issue Type: Test > Components: master >Reporter: Nick Dimiduk > Fix For: 2.0.0, 1.3.0, 1.2.1, 1.1.3 > > > Looking at our [build > history|https://builds.apache.org/job/HBase-1.1/buildTimeTrend], it seems > this test is flakey. See builds 429, 431, 439. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (HBASE-13590) TestEnableTableHandler.testEnableTableWithNoRegionServers is flakey
[ https://issues.apache.org/jira/browse/HBASE-13590?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrey Stepachev updated HBASE-13590: - Assignee: (was: Andrey Stepachev) > TestEnableTableHandler.testEnableTableWithNoRegionServers is flakey > --- > > Key: HBASE-13590 > URL: https://issues.apache.org/jira/browse/HBASE-13590 > Project: HBase > Issue Type: Test > Components: master >Reporter: Nick Dimiduk > Fix For: 2.0.0, 1.3.0, 1.2.1, 1.1.3 > > > Looking at our [build > history|https://builds.apache.org/job/HBase-1.1/buildTimeTrend], it seems > this test is flakey. See builds 429, 431, 439. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (HBASE-14021) Quota table has a wrong description on the UI
[ https://issues.apache.org/jira/browse/HBASE-14021?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14654929#comment-14654929 ] Hudson commented on HBASE-14021: FAILURE: Integrated in HBase-1.2 #91 (See [https://builds.apache.org/job/HBase-1.2/91/]) HBASE-14021 Quota table has a wrong description on the UI (Ashish Singhi) (tedyu: rev 64511ec8984118638d63217abf5ff8a4ecb9f40d) * hbase-server/src/main/jamon/org/apache/hadoop/hbase/tmpl/master/MasterStatusTmpl.jamon > Quota table has a wrong description on the UI > - > > Key: HBASE-14021 > URL: https://issues.apache.org/jira/browse/HBASE-14021 > Project: HBase > Issue Type: Bug > Components: UI >Affects Versions: 1.1.0 >Reporter: Ashish Singhi >Assignee: Ashish Singhi >Priority: Minor > Fix For: 2.0.0, 1.3.0, 1.2.1 > > Attachments: HBASE-14021.patch, HBASE-14021.patch, error.png, fix.png > > > !error.png! -- This message was sent by Atlassian JIRA (v6.3.4#6332)
