[jira] [Updated] (HBASE-14082) Add replica id to JMX metrics names
[
https://issues.apache.org/jira/browse/HBASE-14082?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Lei Chen updated HBASE-14082:
-
Attachment: HBASE-14082-v5.patch
Updates:
1. Javadoc fix
> Add replica id to JMX metrics names
> ---
>
> Key: HBASE-14082
> URL: https://issues.apache.org/jira/browse/HBASE-14082
> Project: HBase
> Issue Type: Improvement
> Components: metrics
>Reporter: Lei Chen
>Assignee: Lei Chen
> Attachments: HBASE-14082-v1.patch, HBASE-14082-v2.patch,
> HBASE-14082-v3.patch, HBASE-14082-v4.patch, HBASE-14082-v5.patch
>
>
> Today, via JMX, one cannot distinguish a primary region from a replica. A
> possible solution is to add replica id to JMX metrics names. The benefits may
> include, for example:
> # Knowing the latency of a read request on a replica region means the first
> attempt to the primary region has timeout.
> # Write requests on replicas are due to the replication process, while the
> ones on primary are from clients.
> # In case of looking for hot spots of read operations, replicas should be
> excluded since TIMELINE reads are sent to all replicas.
> To implement, we can change the format of metrics names found at
> {code}Hadoop->HBase->RegionServer->Regions->Attributes{code}
> from
> {code}namespace__table__region__metric_{code}
> to
> {code}namespace__table__region__replicaid__metric_{code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (HBASE-14165) The initial size of RWQueueRpcExecutor.queues should be (numWriteQueues + numReadQueues + numScanQueues)
[
https://issues.apache.org/jira/browse/HBASE-14165?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14698540#comment-14698540
]
stack commented on HBASE-14165:
---
[~cuijianwei] You going to commit? You have two +1s sir.
> The initial size of RWQueueRpcExecutor.queues should be (numWriteQueues +
> numReadQueues + numScanQueues)
> -
>
> Key: HBASE-14165
> URL: https://issues.apache.org/jira/browse/HBASE-14165
> Project: HBase
> Issue Type: Improvement
> Components: rpc
>Affects Versions: 0.99.2
>Reporter: cuijianwei
>Priority: Minor
> Attachments: HBASE-14165-trunk.patch
>
>
> The RWQueueRpcExecutor.queues will be initialized as:
> {code}
> queues = new ArrayList>(writeHandlersCount +
> readHandlersCount);
> {code}
> It seems this could be improved as:
> {code}
> queues = new ArrayList>(numWriteQueues +
> numReadQueues + numScanQueues);
> {code}
> Suggestions are welcomed.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (HBASE-14177) Full GC on client may lead to missing scan results
[ https://issues.apache.org/jira/browse/HBASE-14177?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14698539#comment-14698539 ] stack commented on HBASE-14177: --- Thanks for digging in [~housejester] Nice test. Scan got redone for 1.1. It is not something easily backportable. > Full GC on client may lead to missing scan results > -- > > Key: HBASE-14177 > URL: https://issues.apache.org/jira/browse/HBASE-14177 > Project: HBase > Issue Type: Bug > Components: Client >Affects Versions: 1.1.0, 0.98.12, 0.98.13 >Reporter: James Estes >Priority: Critical > Labels: dataloss > Fix For: 2.0.0, 1.3.0 > > > After adding a large row, scanning back that row winds up being empty. After > a few attempts it will succeed (all attempts over the same data on an hbase > getting no other writes). > Looking at logs, it seems this happens when there is memory pressure on the > client and there are several Full GCs that happen. Then messages that > indicate that region locations are being removed from the local client cache: > 2015-07-31 12:50:24,647 [main] DEBUG > org.apache.hadoop.hbase.client.HConnectionManager$HConnectionImplementation > - Removed 192.168.1.131:50981 as a location of > big_row_1438368609944,,1438368610048.880c849594807bdc7412f4f982337d6c. for > tableName=big_row_1438368609944 from cache > Blaming the GC may sound fanciful, but if the test is run with -Xms4g -Xmx4g > then it always passes on the first scan attempt. Maybe the pause is enough to > remove something from the cache, or the client is using weak references > somewhere? > More info > http://mail-archives.apache.org/mod_mbox/hbase-user/201507.mbox/%3CCAE8tVdnFf%3Dob569%3DfJkpw1ndVWOVTkihYj9eo6qt0FrzihYHgw%40mail.gmail.com%3E > Test used to reproduce: > https://github.com/housejester/hbase-debugging#fullgctest > I tested and had failures in: > 0.98.12 client/server > 0.98.13 client 0.98.12 server > 0.98.13 client/server > 1.1.0 client 0.98.13 server > 0.98.13 client and 1.1.0 server > 0.98.12 client and 1.1.0 server > I tested without failure in: > 1.1.0 client/server -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (HBASE-14190) Assign system tables ahead of user region assignment
[
https://issues.apache.org/jira/browse/HBASE-14190?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14698533#comment-14698533
]
stack commented on HBASE-14190:
---
See 'Issue Links' at top of this issue: "HBASE-13556 In assignment, treat
system tables as 'special'; assign after hbase:meta and before user-space
tables"
> Assign system tables ahead of user region assignment
>
>
> Key: HBASE-14190
> URL: https://issues.apache.org/jira/browse/HBASE-14190
> Project: HBase
> Issue Type: Bug
>Reporter: Ted Yu
>Assignee: Ted Yu
>Priority: Critical
> Attachments: 14190-v12.txt, 14190-v6.txt, 14190-v7.txt, 14190-v8.txt
>
>
> Currently the namespace table region is assigned like user regions.
> I spent several hours working with a customer where master couldn't finish
> initialization.
> Even though master was restarted quite a few times, it went down with the
> following:
> {code}
> 2015-08-05 17:16:57,530 FATAL [hdpmaster1:6.activeMasterManager]
> master.HMaster: Master server abort: loaded coprocessors are: []
> 2015-08-05 17:16:57,530 FATAL [hdpmaster1:6.activeMasterManager]
> master.HMaster: Unhandled exception. Starting shutdown.
> java.io.IOException: Timedout 30ms waiting for namespace table to be
> assigned
> at
> org.apache.hadoop.hbase.master.TableNamespaceManager.start(TableNamespaceManager.java:104)
> at org.apache.hadoop.hbase.master.HMaster.initNamespace(HMaster.java:985)
> at
> org.apache.hadoop.hbase.master.HMaster.finishActiveMasterInitialization(HMaster.java:779)
> at org.apache.hadoop.hbase.master.HMaster.access$500(HMaster.java:182)
> at org.apache.hadoop.hbase.master.HMaster$1.run(HMaster.java:1646)
> at java.lang.Thread.run(Thread.java:744)
> {code}
> During previous run(s), namespace table was created, hence leaving an entry
> in hbase:meta.
> The following if block in TableNamespaceManager#start() was skipped:
> {code}
> if (!MetaTableAccessor.tableExists(masterServices.getConnection(),
> TableName.NAMESPACE_TABLE_NAME)) {
> {code}
> TableNamespaceManager#start() spins, waiting for namespace region to be
> assigned.
> There was issue in master assigning user regions.
> We tried issuing 'assign' command from hbase shell which didn't work because
> of the following check in MasterRpcServices#assignRegion():
> {code}
> master.checkInitialized();
> {code}
> This scenario can be avoided if we assign hbase:namespace table after
> hbase:meta is assigned but before user table region assignment.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (HBASE-12812) Update Netty dependency to latest release
[ https://issues.apache.org/jira/browse/HBASE-12812?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] stack updated HBASE-12812: -- Resolution: Fixed Hadoop Flags: Reviewed Fix Version/s: 2.0.0 Status: Resolved (was: Patch Available) Pushed to master branch. Thanks for patch [~jurmous] > Update Netty dependency to latest release > - > > Key: HBASE-12812 > URL: https://issues.apache.org/jira/browse/HBASE-12812 > Project: HBase > Issue Type: Improvement >Reporter: Jurriaan Mous >Assignee: Jurriaan Mous > Fix For: 2.0.0 > > Attachments: 12812v2.txt, HBASE-12812.patch > > > Netty version was 4.0.23.Release of august 15th. > Lets update to 4.0.25 which contains some performance improvements and bug > fixes. > http://netty.io/news/2014/10/29/4-0-24-Final.html > http://netty.io/news/2014/12/31/4-0-25-Final.html -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (HBASE-13127) Add timeouts on all tests so less zombie sightings
[ https://issues.apache.org/jira/browse/HBASE-13127?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] stack updated HBASE-13127: -- Attachment: 13127.alternate.v3.txt These tests are not failing because of timeouts so probably unrelated. Retry. > Add timeouts on all tests so less zombie sightings > -- > > Key: HBASE-13127 > URL: https://issues.apache.org/jira/browse/HBASE-13127 > Project: HBase > Issue Type: Improvement > Components: test >Reporter: stack >Assignee: stack > Attachments: 13127.alternate.txt, 13127.alternate.txt, > 13127.alternate.txt, 13127.alternate.txt, 13127.alternate.v2.txt, > 13127.alternate.v3.txt, 13127.alternate.v3.txt, 13127.txt, 13127v2.txt > > > [~Apache9] and [~octo47] have been working hard at trying to get our builds > passing again. They are almost there. TRUNK just failed with a zombie > TestMasterObserver. Help the lads out by adding timeouts on all tests so less > zombie incidence... will help identify the frequent failing issues. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (HBASE-14228) Close BufferedMutator and connection in MultiTableOutputFormat
[ https://issues.apache.org/jira/browse/HBASE-14228?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14698501#comment-14698501 ] Jerry He commented on HBASE-14228: -- Hi, [~ndimiduk] Are you good with the patch? On top of your HBASE-12728 > Close BufferedMutator and connection in MultiTableOutputFormat > -- > > Key: HBASE-14228 > URL: https://issues.apache.org/jira/browse/HBASE-14228 > Project: HBase > Issue Type: Bug > Components: mapreduce >Affects Versions: 1.1.1 >Reporter: Jerry He >Assignee: Jerry He >Priority: Minor > Fix For: 2.0.0, 1.2.0 > > Attachments: HBASE-14228-branch-1.patch > > > Close BufferedMutator and connection in MultiTableRecordWriter of > MultiTableOutputFormat. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (HBASE-14228) Close BufferedMutator and connection in MultiTableOutputFormat
[
https://issues.apache.org/jira/browse/HBASE-14228?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14698462#comment-14698462
]
Hadoop QA commented on HBASE-14228:
---
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12750664/HBASE-14228-branch-1.patch
against branch-1 branch at commit ecba08829da149aca11929b5b88a6df880e0da35.
ATTACHMENT ID: 12750664
{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/15118//testReport/
Release Findbugs (version 2.0.3)warnings:
https://builds.apache.org/job/PreCommit-HBASE-Build/15118//artifact/patchprocess/newFindbugsWarnings.html
Checkstyle Errors:
https://builds.apache.org/job/PreCommit-HBASE-Build/15118//artifact/patchprocess/checkstyle-aggregate.html
Console output:
https://builds.apache.org/job/PreCommit-HBASE-Build/15118//console
This message is automatically generated.
> Close BufferedMutator and connection in MultiTableOutputFormat
> --
>
> Key: HBASE-14228
> URL: https://issues.apache.org/jira/browse/HBASE-14228
> Project: HBase
> Issue Type: Bug
> Components: mapreduce
>Affects Versions: 1.1.1
>Reporter: Jerry He
>Assignee: Jerry He
>Priority: Minor
> Fix For: 2.0.0, 1.2.0
>
> Attachments: HBASE-14228-branch-1.patch
>
>
> Close BufferedMutator and connection in MultiTableRecordWriter of
> MultiTableOutputFormat.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (HBASE-13127) Add timeouts on all tests so less zombie sightings
[
https://issues.apache.org/jira/browse/HBASE-13127?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14698421#comment-14698421
]
Hadoop QA commented on HBASE-13127:
---
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12750658/13127.alternate.v3.txt
against master branch at commit ecba08829da149aca11929b5b88a6df880e0da35.
ATTACHMENT ID: 12750658
{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.util.TestProcessBasedCluster
org.apache.hadoop.hbase.mapreduce.TestImportExport
Test results:
https://builds.apache.org/job/PreCommit-HBASE-Build/15117//testReport/
Release Findbugs (version 2.0.3)warnings:
https://builds.apache.org/job/PreCommit-HBASE-Build/15117//artifact/patchprocess/newFindbugsWarnings.html
Checkstyle Errors:
https://builds.apache.org/job/PreCommit-HBASE-Build/15117//artifact/patchprocess/checkstyle-aggregate.html
Console output:
https://builds.apache.org/job/PreCommit-HBASE-Build/15117//console
This message is automatically generated.
> Add timeouts on all tests so less zombie sightings
> --
>
> Key: HBASE-13127
> URL: https://issues.apache.org/jira/browse/HBASE-13127
> Project: HBase
> Issue Type: Improvement
> Components: test
>Reporter: stack
>Assignee: stack
> Attachments: 13127.alternate.txt, 13127.alternate.txt,
> 13127.alternate.txt, 13127.alternate.txt, 13127.alternate.v2.txt,
> 13127.alternate.v3.txt, 13127.txt, 13127v2.txt
>
>
> [~Apache9] and [~octo47] have been working hard at trying to get our builds
> passing again. They are almost there. TRUNK just failed with a zombie
> TestMasterObserver. Help the lads out by adding timeouts on all tests so less
> zombie incidence... will help identify the frequent failing issues.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (HBASE-14228) Close BufferedMutator and connection in MultiTableOutputFormat
[ https://issues.apache.org/jira/browse/HBASE-14228?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jerry He updated HBASE-14228: - Hadoop Flags: Incompatible change Fix Version/s: 1.2.0 2.0.0 Status: Patch Available (was: Open) > Close BufferedMutator and connection in MultiTableOutputFormat > -- > > Key: HBASE-14228 > URL: https://issues.apache.org/jira/browse/HBASE-14228 > Project: HBase > Issue Type: Bug > Components: mapreduce >Affects Versions: 1.1.1 >Reporter: Jerry He >Assignee: Jerry He >Priority: Minor > Fix For: 2.0.0, 1.2.0 > > Attachments: HBASE-14228-branch-1.patch > > > Close BufferedMutator and connection in MultiTableRecordWriter of > MultiTableOutputFormat. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (HBASE-14228) Close BufferedMutator and connection in MultiTableOutputFormat
[ https://issues.apache.org/jira/browse/HBASE-14228?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jerry He updated HBASE-14228: - Attachment: HBASE-14228-branch-1.patch mutator.close() does flush and releases any resources held. > Close BufferedMutator and connection in MultiTableOutputFormat > -- > > Key: HBASE-14228 > URL: https://issues.apache.org/jira/browse/HBASE-14228 > Project: HBase > Issue Type: Bug > Components: mapreduce >Affects Versions: 1.1.1 >Reporter: Jerry He >Assignee: Jerry He >Priority: Minor > Attachments: HBASE-14228-branch-1.patch > > > Close BufferedMutator and connection in MultiTableRecordWriter of > MultiTableOutputFormat. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (HBASE-14228) Close BufferedMutator and connection in MultiTableOutputFormat
Jerry He created HBASE-14228: Summary: Close BufferedMutator and connection in MultiTableOutputFormat Key: HBASE-14228 URL: https://issues.apache.org/jira/browse/HBASE-14228 Project: HBase Issue Type: Bug Components: mapreduce Affects Versions: 1.1.1 Reporter: Jerry He Assignee: Jerry He Priority: Minor Close BufferedMutator and connection in MultiTableRecordWriter of MultiTableOutputFormat. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (HBASE-12812) Update Netty dependency to latest release
[
https://issues.apache.org/jira/browse/HBASE-12812?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14698389#comment-14698389
]
Hadoop QA commented on HBASE-12812:
---
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12750654/12812v2.txt
against master branch at commit ecba08829da149aca11929b5b88a6df880e0da35.
ATTACHMENT ID: 12750654
{color:green}+1 @author{color}. The patch does not contain any @author
tags.
{color:green}+0 tests included{color}. The patch appears to be a
documentation, build,
or dev-support patch that doesn't require 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:red}-1 javadoc{color}. The javadoc tool appears to have generated 1
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/15115//testReport/
Release Findbugs (version 2.0.3)warnings:
https://builds.apache.org/job/PreCommit-HBASE-Build/15115//artifact/patchprocess/newFindbugsWarnings.html
Checkstyle Errors:
https://builds.apache.org/job/PreCommit-HBASE-Build/15115//artifact/patchprocess/checkstyle-aggregate.html
Javadoc warnings:
https://builds.apache.org/job/PreCommit-HBASE-Build/15115//artifact/patchprocess/patchJavadocWarnings.txt
Console output:
https://builds.apache.org/job/PreCommit-HBASE-Build/15115//console
This message is automatically generated.
> Update Netty dependency to latest release
> -
>
> Key: HBASE-12812
> URL: https://issues.apache.org/jira/browse/HBASE-12812
> Project: HBase
> Issue Type: Improvement
>Reporter: Jurriaan Mous
>Assignee: Jurriaan Mous
> Attachments: 12812v2.txt, HBASE-12812.patch
>
>
> Netty version was 4.0.23.Release of august 15th.
> Lets update to 4.0.25 which contains some performance improvements and bug
> fixes.
> http://netty.io/news/2014/10/29/4-0-24-Final.html
> http://netty.io/news/2014/12/31/4-0-25-Final.html
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Comment Edited] (HBASE-14227) Fold special cased MOB APIs into existing APIs
[ https://issues.apache.org/jira/browse/HBASE-14227?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14698364#comment-14698364 ] Andrew Purtell edited comment on HBASE-14227 at 8/15/15 5:30 PM: - Another strong reason for doing this work is there is no coprocessor API nor AccessController support for securing the MOB admin APIs, at least as far as a case insensitive grep for "mob" of o.a.h.h.coprocessor and o.a.h.h.security.access in master branch can determine. Adding APIs specific to MOB could be reasonable at the coprocessor level, I think we'd want to look at that on a case by case basis, and again avoid wherever possible. was (Author: apurtell): Another strong reason for doing this work is there is no coprocessor API nor AccessController support for securing the MOB admin APIs. Adding APIs specific to MOB could be reasonable at the coprocessor level, I think we'd want to look at that on a case by case basis, and again avoid wherever possible. > Fold special cased MOB APIs into existing APIs > -- > > Key: HBASE-14227 > URL: https://issues.apache.org/jira/browse/HBASE-14227 > Project: HBase > Issue Type: Task > Components: mob >Affects Versions: 2.0.0 >Reporter: Andrew Purtell >Priority: Blocker > Fix For: 2.0.0 > > > There are a number of APIs that came in with MOB that are not new actions for > HBase, simply new actions for a MOB implementation: > - compactMob > - compactMobs > - majorCompactMob > - majorCompactMobs > - getMobCompactionState > And in HBaseAdmin: > - validateMobColumnFamily > Remove these special cases from the Admin API where possible by folding them > into existing APIs. > We definitely don't need one method for a singleton and another for > collections. > Ideally we will not have any APIs named *Mob when finished, whether MOBs are > in use on a table or not should be largely an internal detail. Exposing as > schema option would be fine, this conforms to existing practice for other > features. > Marking critical because I think removing the *Mob special cased APIs should > be a precondition for release of this feature either in 2.0 or as a backport. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (HBASE-14227) Fold special cased MOB APIs into existing APIs
[ https://issues.apache.org/jira/browse/HBASE-14227?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrew Purtell updated HBASE-14227: --- Priority: Blocker (was: Critical) Making this a blocker > Fold special cased MOB APIs into existing APIs > -- > > Key: HBASE-14227 > URL: https://issues.apache.org/jira/browse/HBASE-14227 > Project: HBase > Issue Type: Task > Components: mob >Affects Versions: 2.0.0 >Reporter: Andrew Purtell >Priority: Blocker > Fix For: 2.0.0 > > > There are a number of APIs that came in with MOB that are not new actions for > HBase, simply new actions for a MOB implementation: > - compactMob > - compactMobs > - majorCompactMob > - majorCompactMobs > - getMobCompactionState > And in HBaseAdmin: > - validateMobColumnFamily > Remove these special cases from the Admin API where possible by folding them > into existing APIs. > We definitely don't need one method for a singleton and another for > collections. > Ideally we will not have any APIs named *Mob when finished, whether MOBs are > in use on a table or not should be largely an internal detail. Exposing as > schema option would be fine, this conforms to existing practice for other > features. > Marking critical because I think removing the *Mob special cased APIs should > be a precondition for release of this feature either in 2.0 or as a backport. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (HBASE-14227) Fold special cased MOB APIs into existing APIs
[ https://issues.apache.org/jira/browse/HBASE-14227?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14698364#comment-14698364 ] Andrew Purtell commented on HBASE-14227: Another strong reason for doing this work is there is no coprocessor API nor AccessController support for securing the MOB admin APIs. Adding APIs specific to MOB could be reasonable at the coprocessor level, I think we'd want to look at that on a case by case basis, and again avoid wherever possible. > Fold special cased MOB APIs into existing APIs > -- > > Key: HBASE-14227 > URL: https://issues.apache.org/jira/browse/HBASE-14227 > Project: HBase > Issue Type: Task > Components: mob >Affects Versions: 2.0.0 >Reporter: Andrew Purtell >Priority: Critical > Fix For: 2.0.0 > > > There are a number of APIs that came in with MOB that are not new actions for > HBase, simply new actions for a MOB implementation: > - compactMob > - compactMobs > - majorCompactMob > - majorCompactMobs > - getMobCompactionState > And in HBaseAdmin: > - validateMobColumnFamily > Remove these special cases from the Admin API where possible by folding them > into existing APIs. > We definitely don't need one method for a singleton and another for > collections. > Ideally we will not have any APIs named *Mob when finished, whether MOBs are > in use on a table or not should be largely an internal detail. Exposing as > schema option would be fine, this conforms to existing practice for other > features. > Marking critical because I think removing the *Mob special cased APIs should > be a precondition for release of this feature either in 2.0 or as a backport. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (HBASE-14227) Fold special cased MOB APIs into existing APIs
[ https://issues.apache.org/jira/browse/HBASE-14227?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrew Purtell updated HBASE-14227: --- Affects Version/s: 2.0.0 Fix Version/s: 2.0.0 Component/s: mob > Fold special cased MOB APIs into existing APIs > -- > > Key: HBASE-14227 > URL: https://issues.apache.org/jira/browse/HBASE-14227 > Project: HBase > Issue Type: Task > Components: mob >Affects Versions: 2.0.0 >Reporter: Andrew Purtell >Priority: Critical > Fix For: 2.0.0 > > > There are a number of APIs that came in with MOB that are not new actions for > HBase, simply new actions for a MOB implementation: > - compactMob > - compactMobs > - majorCompactMob > - majorCompactMobs > - getMobCompactionState > And in HBaseAdmin: > - validateMobColumnFamily > Remove these special cases from the Admin API where possible by folding them > into existing APIs. > We definitely don't need one method for a singleton and another for > collections. > Ideally we will not have any APIs named *Mob when finished, whether MOBs are > in use on a table or not should be largely an internal detail. Exposing as > schema option would be fine, this conforms to existing practice for other > features. > Marking critical because I think removing the *Mob special cased APIs should > be a precondition for release of this feature either in 2.0 or as a backport. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (HBASE-14227) Fold special cased MOB APIs into existing APIs
Andrew Purtell created HBASE-14227: -- Summary: Fold special cased MOB APIs into existing APIs Key: HBASE-14227 URL: https://issues.apache.org/jira/browse/HBASE-14227 Project: HBase Issue Type: Task Reporter: Andrew Purtell Priority: Critical There are a number of APIs that came in with MOB that are not new actions for HBase, simply new actions for a MOB implementation: - compactMob - compactMobs - majorCompactMob - majorCompactMobs - getMobCompactionState And in HBaseAdmin: - validateMobColumnFamily Remove these special cases from the Admin API where possible by folding them into existing APIs. We definitely don't need one method for a singleton and another for collections. Ideally we will not have any APIs named *Mob when finished, whether MOBs are in use on a table or not should be largely an internal detail. Exposing as schema option would be fine, this conforms to existing practice for other features. Marking critical because I think removing the *Mob special cased APIs should be a precondition for release of this feature either in 2.0 or as a backport. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (HBASE-14226) Merge group admin APIs into Admin
Andrew Purtell created HBASE-14226: -- Summary: Merge group admin APIs into Admin Key: HBASE-14226 URL: https://issues.apache.org/jira/browse/HBASE-14226 Project: HBase Issue Type: Sub-task Reporter: Andrew Purtell The initial implementation strategy proposed for group based assignment was coprocessor based, but we went a different route. Support for the group admin APIs will be universal with it in core, so consider merging these APIs into Admin. When doing so, consider where existing APIs can be overloaded to hold down the number of methods in Admin. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (HBASE-7043) Region Server Group CLI commands
[ https://issues.apache.org/jira/browse/HBASE-7043?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrew Purtell updated HBASE-7043: -- Labels: hbase-6721 (was: ) > Region Server Group CLI commands > > > Key: HBASE-7043 > URL: https://issues.apache.org/jira/browse/HBASE-7043 > Project: HBase > Issue Type: Sub-task >Reporter: Francis Liu >Assignee: Francis Liu > Labels: hbase-6721 > Attachments: HBASE-6721_94_2.patch, HBASE-7043_94.patch, > HBASE-7043_94_2.patch, HBASE-7043_94_3.patch, HBASE-7043_94_4.patch > > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (HBASE-9191) Update Loadbalancer method to throw HBaseIOException
[ https://issues.apache.org/jira/browse/HBASE-9191?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrew Purtell updated HBASE-9191: -- Labels: hbase-6721 (was: ) > Update Loadbalancer method to throw HBaseIOException > > > Key: HBASE-9191 > URL: https://issues.apache.org/jira/browse/HBASE-9191 > Project: HBase > Issue Type: Sub-task >Reporter: Francis Liu >Assignee: Francis Liu > Labels: hbase-6721 > Fix For: 0.98.0, 0.95.2 > > Attachments: HBASE-9191.patch, HBASE-9191_2.patch > > > Some load balancers need a way to communicate failure scenarios so the AM has > the opportunity to better handle them. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (HBASE-6837) RegionServer Groups corpcoessor apis
[ https://issues.apache.org/jira/browse/HBASE-6837?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrew Purtell updated HBASE-6837: -- Labels: hbase-6721 (was: ) > RegionServer Groups corpcoessor apis > > > Key: HBASE-6837 > URL: https://issues.apache.org/jira/browse/HBASE-6837 > Project: HBase > Issue Type: Sub-task >Reporter: Francis Liu >Assignee: Francis Liu > Labels: hbase-6721 > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (HBASE-7257) Region server group based configuration
[ https://issues.apache.org/jira/browse/HBASE-7257?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrew Purtell updated HBASE-7257: -- Labels: hbase-6721 (was: ) > Region server group based configuration > --- > > Key: HBASE-7257 > URL: https://issues.apache.org/jira/browse/HBASE-7257 > Project: HBase > Issue Type: Sub-task >Reporter: Ted Yu > Labels: hbase-6721 > > The read/write load pattern would be different across region server groups. > It is desirable for each group to have unique configuration parameters. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (HBASE-9263) Add initialize method to load balancer interface
[ https://issues.apache.org/jira/browse/HBASE-9263?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrew Purtell updated HBASE-9263: -- Labels: hbase-6721 (was: ) > Add initialize method to load balancer interface > > > Key: HBASE-9263 > URL: https://issues.apache.org/jira/browse/HBASE-9263 > Project: HBase > Issue Type: Sub-task >Affects Versions: 0.98.0, 0.96.0 >Reporter: Francis Liu >Assignee: Francis Liu > Labels: hbase-6721 > Fix For: 0.98.0, 0.96.0 > > Attachments: HBASE-9263.patch > > > The load balancer has two methods setMasterServices and setConf that needs to > be called prior to it being functional. Some balancers will need to go > through an initialization procedure once these methods have been called. An > initialize() method would be helpful in this regard. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (HBASE-6723) Implement RegionServer Group Based Balancer
[ https://issues.apache.org/jira/browse/HBASE-6723?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrew Purtell updated HBASE-6723: -- Labels: hbase-6721 (was: ) > Implement RegionServer Group Based Balancer > --- > > Key: HBASE-6723 > URL: https://issues.apache.org/jira/browse/HBASE-6723 > Project: HBase > Issue Type: Sub-task >Reporter: Francis Liu >Assignee: Vandana Ayyalasomayajula > Labels: hbase-6721 > > Re-purposing this Jira after the discussion last week. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (HBASE-7042) Master Coprocessor Endpoint
[ https://issues.apache.org/jira/browse/HBASE-7042?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrew Purtell updated HBASE-7042: -- Labels: hbase-6721 (was: ) > Master Coprocessor Endpoint > --- > > Key: HBASE-7042 > URL: https://issues.apache.org/jira/browse/HBASE-7042 > Project: HBase > Issue Type: Sub-task >Reporter: Francis Liu >Assignee: Francis Liu > Labels: hbase-6721 > Fix For: 0.94.4, 0.95.0 > > Attachments: HBASE-7042.patch, HBASE-7042_2.patch, > HBASE-7042_3.patch, HBASE-7042_94.patch, HBASE-7042_94_2.patch, > HBASE-7042_94_3.patch, HBASE-7042_94_4.patch, HBASE-7042_94_4.patch > > > Having support for a master coprocessor endpoint would enable developers to > easily extended HMaster functionality/features. As is the case for region > server grouping. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (HBASE-6721) RegionServer Group based Assignment
[ https://issues.apache.org/jira/browse/HBASE-6721?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrew Purtell updated HBASE-6721: -- Labels: hbase-6721 (was: ) > 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 > Labels: hbase-6721 > Attachments: 6721-master-webUI.patch, HBASE-6721 > GroupBasedLoadBalancer Sequence Diagram.xml, HBASE-6721-DesigDoc.pdf, > HBASE-6721-DesigDoc.pdf, HBASE-6721-DesigDoc.pdf, HBASE-6721-DesigDoc.pdf, > HBASE-6721_0.98_2.patch, 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_98_1.patch, HBASE-6721_98_2.patch, HBASE-6721_trunk.patch, > HBASE-6721_trunk.patch, HBASE-6721_trunk.patch, HBASE-6721_trunk1.patch, > HBASE-6721_trunk2.patch, balanceCluster Sequence Diagram.svg, > immediateAssignments Sequence Diagram.svg, randomAssignment Sequence > Diagram.svg, retainAssignment Sequence Diagram.svg, roundRobinAssignment > Sequence Diagram.svg > > > 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] [Updated] (HBASE-13127) Add timeouts on all tests so less zombie sightings
[ https://issues.apache.org/jira/browse/HBASE-13127?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] stack updated HBASE-13127: -- Attachment: 13127.alternate.v3.txt Retry > Add timeouts on all tests so less zombie sightings > -- > > Key: HBASE-13127 > URL: https://issues.apache.org/jira/browse/HBASE-13127 > Project: HBase > Issue Type: Improvement > Components: test >Reporter: stack >Assignee: stack > Attachments: 13127.alternate.txt, 13127.alternate.txt, > 13127.alternate.txt, 13127.alternate.txt, 13127.alternate.v2.txt, > 13127.alternate.v3.txt, 13127.txt, 13127v2.txt > > > [~Apache9] and [~octo47] have been working hard at trying to get our builds > passing again. They are almost there. TRUNK just failed with a zombie > TestMasterObserver. Help the lads out by adding timeouts on all tests so less > zombie incidence... will help identify the frequent failing issues. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (HBASE-13127) Add timeouts on all tests so less zombie sightings
[
https://issues.apache.org/jira/browse/HBASE-13127?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14698337#comment-14698337
]
Hadoop QA commented on HBASE-13127:
---
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12750656/13127.alternate.v2.txt
against master branch at commit ecba08829da149aca11929b5b88a6df880e0da35.
ATTACHMENT ID: 12750656
{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.TestTimeout
{color:red}-1 core zombie tests{color}. There are 1 zombie test(s):
at
org.apache.sqoop.test.hive.InternalMetastoreServerRunner$1.call(InternalMetastoreServerRunner.java:53)
at
org.apache.sqoop.test.hive.InternalMetastoreServerRunner$1.call(InternalMetastoreServerRunner.java:50)
at
org.apache.sqoop.common.test.db.DatabaseProvider.executeQuery(DatabaseProvider.java:249)
at
org.apache.sqoop.common.test.db.DatabaseProvider.getRows(DatabaseProvider.java:413)
at
org.apache.sqoop.common.test.asserts.ProviderAsserts.assertRow(ProviderAsserts.java:61)
at
org.apache.sqoop.common.test.asserts.ProviderAsserts.assertRow(ProviderAsserts.java:46)
at
org.apache.sqoop.integration.connector.hive.FromRDBMSToKiteHiveTest.testCities(FromRDBMSToKiteHiveTest.java:128)
at
org.testng.internal.MethodInvocationHelper.invokeMethod(MethodInvocationHelper.java:85)
at org.testng.internal.Invoker.invokeMethod(Invoker.java:696)
at org.testng.internal.Invoker.invokeTestMethod(Invoker.java:882)
at org.testng.internal.Invoker.invokeTestMethods(Invoker.java:1189)
at
org.testng.internal.TestMethodWorker.invokeTestMethods(TestMethodWorker.java:124)
at org.testng.internal.TestMethodWorker.run(TestMethodWorker.java:108)
at org.testng.TestRunner.privateRun(TestRunner.java:767)
at org.testng.TestRunner.run(TestRunner.java:617)
at org.testng.SuiteRunner.runTest(SuiteRunner.java:348)
at org.testng.SuiteRunner.runSequentially(SuiteRunner.java:343)
at org.testng.SuiteRunner.privateRun(SuiteRunner.java:305)
at org.testng.SuiteRunner.run(SuiteRunner.java:254)
at org.testng.SuiteRunnerWorker.runSuite(SuiteRunnerWorker.java:52)
at org.testng.SuiteRunnerWorker.run(SuiteRunnerWorker.java:86)
at org.testng.TestNG.runSuitesSequentially(TestNG.java:1224)
at org.testng.TestNG.runSuitesLocally(TestNG.java:1149)
at org.testng.TestNG.run(TestNG.java:1057)
at
org.apache.maven.surefire.testng.TestNGExecutor.run(TestNGExecutor.java:295)
at
org.apache.maven.surefire.testng.TestNGXmlTestSuite.execute(TestNGXmlTestSuite.java:84)
at
org.apache.maven.surefire.testng.TestNGProvider.invoke(TestNGProvider.java:90)
Test results:
https://builds.apache.org/job/PreCommit-HBASE-Build/15116//testReport/
Release Findbugs (version 2.0.3)warnings:
https://builds.apache.org/job/PreCommit-HBASE-Build/15116//artifact/patchprocess/newFindbugsWarnings.html
Checkstyle Errors:
https://builds.apache.org/job/PreCommit-HBASE-Build/15116//artifact/patchprocess/checkstyle-aggregate.html
Console output:
https://builds.apache.org/job/PreCommit-HBASE-Build/15116//console
This message is automatically generated.
> Add timeouts on all tests so less zombie sightings
> --
>
> Key: HBASE-13127
> URL: https://issues.apache.org/jira/browse/HBASE-13127
> Project: HBase
> Issue Type: Improvement
> Components: test
>Reporter: stack
[jira] [Updated] (HBASE-13127) Add timeouts on all tests so less zombie sightings
[ https://issues.apache.org/jira/browse/HBASE-13127?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] stack updated HBASE-13127: -- Attachment: 13127.alternate.v2.txt Fix release audit warning and javadoc item (though not mine). > Add timeouts on all tests so less zombie sightings > -- > > Key: HBASE-13127 > URL: https://issues.apache.org/jira/browse/HBASE-13127 > Project: HBase > Issue Type: Improvement > Components: test >Reporter: stack >Assignee: stack > Attachments: 13127.alternate.txt, 13127.alternate.txt, > 13127.alternate.txt, 13127.alternate.txt, 13127.alternate.v2.txt, 13127.txt, > 13127v2.txt > > > [~Apache9] and [~octo47] have been working hard at trying to get our builds > passing again. They are almost there. TRUNK just failed with a zombie > TestMasterObserver. Help the lads out by adding timeouts on all tests so less > zombie incidence... will help identify the frequent failing issues. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (HBASE-12812) Update Netty dependency to latest release
[ https://issues.apache.org/jira/browse/HBASE-12812?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] stack updated HBASE-12812: -- Attachment: 12812v2.txt Rebase. Go to netty 4.0.30 since it is out now. > Update Netty dependency to latest release > - > > Key: HBASE-12812 > URL: https://issues.apache.org/jira/browse/HBASE-12812 > Project: HBase > Issue Type: Improvement >Reporter: Jurriaan Mous >Assignee: Jurriaan Mous > Attachments: 12812v2.txt, HBASE-12812.patch > > > Netty version was 4.0.23.Release of august 15th. > Lets update to 4.0.25 which contains some performance improvements and bug > fixes. > http://netty.io/news/2014/10/29/4-0-24-Final.html > http://netty.io/news/2014/12/31/4-0-25-Final.html -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (HBASE-14210) Create test for cell level ACLs involving user group
[
https://issues.apache.org/jira/browse/HBASE-14210?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14698194#comment-14698194
]
Hadoop QA commented on HBASE-14210:
---
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12750642/HBASE-14210-v2.patch
against master branch at commit ecba08829da149aca11929b5b88a6df880e0da35.
ATTACHMENT ID: 12750642
{color:green}+1 @author{color}. The patch does not contain any @author
tags.
{color:green}+1 tests included{color}. The patch appears to include 8 new
or modified tests.
{color:green}+1 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:red}-1 javadoc{color}. The javadoc tool appears to have generated 1
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 .
{color:red}-1 core zombie tests{color}. There are 2 zombie test(s):
at
org.apache.camel.component.jetty.jettyproducer.HttpJettyProducerRecipientListCustomThreadPoolTest.testRecipientList(HttpJettyProducerRecipientListCustomThreadPoolTest.java:40)
Test results:
https://builds.apache.org/job/PreCommit-HBASE-Build/15113//testReport/
Release Findbugs (version 2.0.3)warnings:
https://builds.apache.org/job/PreCommit-HBASE-Build/15113//artifact/patchprocess/newFindbugsWarnings.html
Checkstyle Errors:
https://builds.apache.org/job/PreCommit-HBASE-Build/15113//artifact/patchprocess/checkstyle-aggregate.html
Javadoc warnings:
https://builds.apache.org/job/PreCommit-HBASE-Build/15113//artifact/patchprocess/patchJavadocWarnings.txt
Console output:
https://builds.apache.org/job/PreCommit-HBASE-Build/15113//console
This message is automatically generated.
> Create test for cell level ACLs involving user group
>
>
> Key: HBASE-14210
> URL: https://issues.apache.org/jira/browse/HBASE-14210
> Project: HBase
> Issue Type: Test
>Reporter: Ted Yu
>Assignee: Ashish Singhi
> Attachments: HBASE-14210-v1.patch, HBASE-14210-v2.patch,
> HBASE-14210.patch
>
>
> Currently we have TestCellACLs and TestCellACLWithMultipleVersions which
> exercise cell level ACLs for users.
> However, test for cell level ACLs involving user group is missing.
> This issue is to add such test(s)
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (HBASE-14082) Add replica id to JMX metrics names
[
https://issues.apache.org/jira/browse/HBASE-14082?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14698192#comment-14698192
]
Hadoop QA commented on HBASE-14082:
---
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12750643/HBASE-14082-v4.patch
against master branch at commit ecba08829da149aca11929b5b88a6df880e0da35.
ATTACHMENT ID: 12750643
{color:green}+1 @author{color}. The patch does not contain any @author
tags.
{color:green}+1 tests included{color}. The patch appears to include 11 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:red}-1 javadoc{color}. The javadoc tool appears to have generated 1
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:
{color:red}-1 core zombie tests{color}. There are 1 zombie test(s):
at
org.apache.hadoop.hbase.mapreduce.TestHFileOutputFormat2.testMRIncrementalLoadWithSplit(TestHFileOutputFormat2.java:385)
Test results:
https://builds.apache.org/job/PreCommit-HBASE-Build/15114//testReport/
Release Findbugs (version 2.0.3)warnings:
https://builds.apache.org/job/PreCommit-HBASE-Build/15114//artifact/patchprocess/newFindbugsWarnings.html
Checkstyle Errors:
https://builds.apache.org/job/PreCommit-HBASE-Build/15114//artifact/patchprocess/checkstyle-aggregate.html
Javadoc warnings:
https://builds.apache.org/job/PreCommit-HBASE-Build/15114//artifact/patchprocess/patchJavadocWarnings.txt
Console output:
https://builds.apache.org/job/PreCommit-HBASE-Build/15114//console
This message is automatically generated.
> Add replica id to JMX metrics names
> ---
>
> Key: HBASE-14082
> URL: https://issues.apache.org/jira/browse/HBASE-14082
> Project: HBase
> Issue Type: Improvement
> Components: metrics
>Reporter: Lei Chen
>Assignee: Lei Chen
> Attachments: HBASE-14082-v1.patch, HBASE-14082-v2.patch,
> HBASE-14082-v3.patch, HBASE-14082-v4.patch
>
>
> Today, via JMX, one cannot distinguish a primary region from a replica. A
> possible solution is to add replica id to JMX metrics names. The benefits may
> include, for example:
> # Knowing the latency of a read request on a replica region means the first
> attempt to the primary region has timeout.
> # Write requests on replicas are due to the replication process, while the
> ones on primary are from clients.
> # In case of looking for hot spots of read operations, replicas should be
> excluded since TIMELINE reads are sent to all replicas.
> To implement, we can change the format of metrics names found at
> {code}Hadoop->HBase->RegionServer->Regions->Attributes{code}
> from
> {code}namespace__table__region__metric_{code}
> to
> {code}namespace__table__region__replicaid__metric_{code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
