[jira] [Commented] (HBASE-19064) Synchronous replication for HBase

[ https://issues.apache.org/jira/browse/HBASE-19064?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16457403#comment-16457403 ] Hudson commented on HBASE-19064: Results for branch HBASE-19064 [build #112 on b

[jira] [Commented] (HBASE-20378) Provide a hbck option to cleanup replication barrier for a table

[ https://issues.apache.org/jira/browse/HBASE-20378?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16457393#comment-16457393 ] Hadoop QA commented on HBASE-20378: --- | (x) *{color:red}-1 overall{color}* | \\ \\ || Vo

[jira] [Commented] (HBASE-20500) [rsgroup] should keep at least one server in default group

[ https://issues.apache.org/jira/browse/HBASE-20500?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16457388#comment-16457388 ] Yechao Chen commented on HBASE-20500: - try qa > [rsgroup] should keep at least one s

[jira] [Updated] (HBASE-20500) [rsgroup] should keep at least one server in default group

[ https://issues.apache.org/jira/browse/HBASE-20500?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Yechao Chen updated HBASE-20500: Attachment: HBASE-20500-master.v1.patch > [rsgroup] should keep at least one server in default grou

[jira] [Updated] (HBASE-20500) [rsgroup] should keep at least one server in default group

[ https://issues.apache.org/jira/browse/HBASE-20500?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Yechao Chen updated HBASE-20500: Status: Patch Available (was: Open) > [rsgroup] should keep at least one server in default group >

[jira] [Commented] (HBASE-20327) When qualifier is not specified, append and incr operation do not work (shell)

[ https://issues.apache.org/jira/browse/HBASE-20327?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16457361#comment-16457361 ] Chia-Ping Tsai commented on HBASE-20327: Have pushed the patch to master and bran

[jira] [Commented] (HBASE-20497) The getRecoveredQueueStartPos always return 0 in RecoveredReplicationSourceShipper

[ https://issues.apache.org/jira/browse/HBASE-20497?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16457348#comment-16457348 ] Zheng Hu commented on HBASE-20497: -- [~Apache9]  [~zghaobac], Hope for a review.  The RB

[jira] [Updated] (HBASE-20497) The getRecoveredQueueStartPos always return 0 in RecoveredReplicationSourceShipper

[ https://issues.apache.org/jira/browse/HBASE-20497?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Zheng Hu updated HBASE-20497: - Attachment: HBASE-20497.v1.patch > The getRecoveredQueueStartPos always return 0 in > RecoveredReplicati

[jira] [Updated] (HBASE-20497) The getRecoveredQueueStartPos always return 0 in RecoveredReplicationSourceShipper

[ https://issues.apache.org/jira/browse/HBASE-20497?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Zheng Hu updated HBASE-20497: - Status: Patch Available (was: Open) > The getRecoveredQueueStartPos always return 0 in > RecoveredRepli

[jira] [Updated] (HBASE-20378) Provide a hbck option to cleanup replication barrier for a table

[ https://issues.apache.org/jira/browse/HBASE-20378?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jingyun Tian updated HBASE-20378: - Attachment: HBASE-20378.master.008.patch > Provide a hbck option to cleanup replication barrier f

[jira] [Updated] (HBASE-20497) The getRecoveredQueueStartPos always return 0 in RecoveredReplicationSourceShipper

[ https://issues.apache.org/jira/browse/HBASE-20497?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Zheng Hu updated HBASE-20497: - Summary: The getRecoveredQueueStartPos always return 0 in RecoveredReplicationSourceShipper (was: The ge

[jira] [Commented] (HBASE-20475) Fix the flaky TestReplicationDroppedTables unit test.

[ https://issues.apache.org/jira/browse/HBASE-20475?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16457281#comment-16457281 ] Zheng Hu commented on HBASE-20475: -- The TestReplicationDroppedTables is becoming more st

[jira] [Commented] (HBASE-20040) Master UI should include "Cluster Key" needed to use the cluster as a replication sink

[ https://issues.apache.org/jira/browse/HBASE-20040?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16457231#comment-16457231 ] Hadoop QA commented on HBASE-20040: --- | (x) *{color:red}-1 overall{color}* | \\ \\ || Vo

[jira] [Commented] (HBASE-20482) Print a link to the ref guide chapter for the shell during startup

[ https://issues.apache.org/jira/browse/HBASE-20482?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16457201#comment-16457201 ] Hadoop QA commented on HBASE-20482: --- | (x) *{color:red}-1 overall{color}* | \\ \\ || Vo

[jira] [Commented] (HBASE-20482) Print a link to the ref guide chapter for the shell during startup

[ https://issues.apache.org/jira/browse/HBASE-20482?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16457193#comment-16457193 ] Sakthi commented on HBASE-20482: [~busbey] , Could you please review the patches? > Prin

[jira] [Commented] (HBASE-19924) hbase rpc throttling does not work for multi() with request count rater.

[ https://issues.apache.org/jira/browse/HBASE-19924?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16457191#comment-16457191 ] Hudson commented on HBASE-19924: Results for branch branch-1.3 [build #310 on bu

[jira] [Updated] (HBASE-20482) Print a link to the ref guide chapter for the shell during startup

[ https://issues.apache.org/jira/browse/HBASE-20482?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sakthi updated HBASE-20482: --- Attachment: hbase-20482.branch-2.0.001.patch > Print a link to the ref guide chapter for the shell during sta

[jira] [Commented] (HBASE-20503) [AsyncFSWAL] Failed to get sync result after 300000 ms for txid=160912, WAL system stuck?

[ https://issues.apache.org/jira/browse/HBASE-20503?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16457190#comment-16457190 ] stack commented on HBASE-20503: --- Its a version of hadoop3 [~Apache9] Also, this hang has ha

[jira] [Updated] (HBASE-20482) Print a link to the ref guide chapter for the shell during startup

[ https://issues.apache.org/jira/browse/HBASE-20482?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sakthi updated HBASE-20482: --- Attachment: hbase-20482.branch-1.2.001.patch > Print a link to the ref guide chapter for the shell during sta

[jira] [Commented] (HBASE-20476) Open sequence number could go backwards in AssignProcedure

[ https://issues.apache.org/jira/browse/HBASE-20476?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16457187#comment-16457187 ] Duo Zhang commented on HBASE-20476: --- Pushed to master. Wait a while to see if it works

[jira] [Created] (HBASE-20505) PE should support multi column family read and write cases

Andrew Purtell created HBASE-20505: -- Summary: PE should support multi column family read and write cases Key: HBASE-20505 URL: https://issues.apache.org/jira/browse/HBASE-20505 Project: HBase

[jira] [Created] (HBASE-20504) A few tests in TestHeapSize fail on CentOS 7.4 on branch-2

Sakthi created HBASE-20504: -- Summary: A few tests in TestHeapSize fail on CentOS 7.4 on branch-2 Key: HBASE-20504 URL: https://issues.apache.org/jira/browse/HBASE-20504 Project: HBase Issue Type:

[jira] [Commented] (HBASE-20040) Master UI should include "Cluster Key" needed to use the cluster as a replication sink

[ https://issues.apache.org/jira/browse/HBASE-20040?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16457136#comment-16457136 ] Sakthi commented on HBASE-20040: [~busbey] , Could you review the patch for branch-1? >

[jira] [Updated] (HBASE-20040) Master UI should include "Cluster Key" needed to use the cluster as a replication sink

[ https://issues.apache.org/jira/browse/HBASE-20040?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sakthi updated HBASE-20040: --- Attachment: hbase-20040.branch-1.001.patch > Master UI should include "Cluster Key" needed to use the cluster

[jira] [Commented] (HBASE-20502) Document HBase incompatible with Yarn 2.9.0 and 3.0.x due to YARN-7190

[ https://issues.apache.org/jira/browse/HBASE-20502?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16457131#comment-16457131 ] Andrew Purtell commented on HBASE-20502: [~mdrob] Added a link between the issues

[jira] [Commented] (HBASE-20503) [AsyncFSWAL] Failed to get sync result after 300000 ms for txid=160912, WAL system stuck?

[ https://issues.apache.org/jira/browse/HBASE-20503?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16457127#comment-16457127 ] Duo Zhang commented on HBASE-20503: --- Which hadoop version do you use sir? Stream broken

[jira] [Commented] (HBASE-19924) hbase rpc throttling does not work for multi() with request count rater.

[ https://issues.apache.org/jira/browse/HBASE-19924?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16457122#comment-16457122 ] Hudson commented on HBASE-19924: Results for branch branch-1.2 [build #314 on bu

[jira] [Comment Edited] (HBASE-20492) UnassignProcedure is stuck in retry loop on region stuck in OPENING state

[ https://issues.apache.org/jira/browse/HBASE-20492?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16455782#comment-16455782 ] stack edited comment on HBASE-20492 at 4/27/18 9:48 PM: Made a su

[jira] [Commented] (HBASE-20502) Document HBase incompatible with Yarn 2.9.0 and 3.0.x due to YARN-7190

[ https://issues.apache.org/jira/browse/HBASE-20502?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16457115#comment-16457115 ] Hadoop QA commented on HBASE-20502: --- | (/) *{color:green}+1 overall{color}* | \\ \\ ||

[jira] [Commented] (HBASE-20502) Document HBase incompatible with Yarn 2.9.0 and 3.0.x due to YARN-7190

[ https://issues.apache.org/jira/browse/HBASE-20502?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16457091#comment-16457091 ] Mike Drob commented on HBASE-20502: --- [~apurtell] - FYI this patch will likely conflict

[jira] [Updated] (HBASE-20502) Document HBase incompatible with Yarn 2.9.0 and 3.0.x due to YARN-7190

[ https://issues.apache.org/jira/browse/HBASE-20502?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mike Drob updated HBASE-20502: -- Assignee: Mike Drob Status: Patch Available (was: Open) > Document HBase incompatible with Yarn

[jira] [Updated] (HBASE-20502) Document HBase incompatible with Yarn 2.9.0 and 3.0.x due to YARN-7190

[ https://issues.apache.org/jira/browse/HBASE-20502?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mike Drob updated HBASE-20502: -- Attachment: HBASE-20502.patch > Document HBase incompatible with Yarn 2.9.0 and 3.0.x due to YARN-7190

[jira] [Created] (HBASE-20503) [AsyncFSWAL] Failed to get sync result after 300000 ms for txid=160912, WAL system stuck?

stack created HBASE-20503: - Summary: [AsyncFSWAL] Failed to get sync result after 30 ms for txid=160912, WAL system stuck? Key: HBASE-20503 URL: https://issues.apache.org/jira/browse/HBASE-20503 Project:

[jira] [Commented] (HBASE-20502) Document HBase incompatible with Yarn 2.9.0 and 3.0.x due to YARN-7190

[ https://issues.apache.org/jira/browse/HBASE-20502?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16457051#comment-16457051 ] Haibo Chen commented on HBASE-20502: I think at least we should have something like a

[jira] [Commented] (HBASE-20499) Replication/Priority executors can use specific max queue length as default value instead of general maxQueueLength

[ https://issues.apache.org/jira/browse/HBASE-20499?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16457049#comment-16457049 ] Ted Yu commented on HBASE-20499: Planning to commit Monday if there is no further review

[jira] [Commented] (HBASE-19924) hbase rpc throttling does not work for multi() with request count rater.

[ https://issues.apache.org/jira/browse/HBASE-19924?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16457026#comment-16457026 ] Hudson commented on HBASE-19924: Results for branch branch-1.4 [build #303 on bu

[jira] [Commented] (HBASE-20499) Replication/Priority executors can use specific max queue length as default value instead of general maxQueueLength

[ https://issues.apache.org/jira/browse/HBASE-20499?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16457025#comment-16457025 ] Hadoop QA commented on HBASE-20499: --- | (x) *{color:red}-1 overall{color}* | \\ \\ || Vo

[jira] [Created] (HBASE-20502) Document HBase incompatible with Yarn 2.9.0 and 3.0.x due to YARN-7190

Mike Drob created HBASE-20502: - Summary: Document HBase incompatible with Yarn 2.9.0 and 3.0.x due to YARN-7190 Key: HBASE-20502 URL: https://issues.apache.org/jira/browse/HBASE-20502 Project: HBase

[jira] [Updated] (HBASE-20501) Change the Hadoop minimum version to 2.7.1

[ https://issues.apache.org/jira/browse/HBASE-20501?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrew Purtell updated HBASE-20501: --- Summary: Change the Hadoop minimum version to 2.7.1 (was: Update Hadoop minimum version to 2

[jira] [Updated] (HBASE-20501) Update Hadoop minimum version to 2.7

[ https://issues.apache.org/jira/browse/HBASE-20501?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrew Purtell updated HBASE-20501: --- Priority: Blocker (was: Major) > Update Hadoop minimum version to 2.7 >

[jira] [Created] (HBASE-20501) Update Hadoop minimum version to 2.7

Andrew Purtell created HBASE-20501: -- Summary: Update Hadoop minimum version to 2.7 Key: HBASE-20501 URL: https://issues.apache.org/jira/browse/HBASE-20501 Project: HBase Issue Type: Task

[jira] [Updated] (HBASE-20498) [AMv2] Stuck in UnexpectedStateException

[ https://issues.apache.org/jira/browse/HBASE-20498?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] stack updated HBASE-20498: -- Fix Version/s: 2.0.1 > [AMv2] Stuck in UnexpectedStateException > > >

[jira] [Updated] (HBASE-20498) [AMv2] Stuck in UnexpectedStateException

[ https://issues.apache.org/jira/browse/HBASE-20498?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] stack updated HBASE-20498: -- Priority: Critical (was: Major) > [AMv2] Stuck in UnexpectedStateException > -

[jira] [Commented] (HBASE-19121) HBCK for AMv2 (A.K.A HBCK2)

[ https://issues.apache.org/jira/browse/HBASE-19121?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16456901#comment-16456901 ] Umesh Agashe commented on HBASE-19121: -- For region states: {code:java} "scan 'hbase:

[jira] [Updated] (HBASE-20487) Sorting table regions by region name does not work on web UI

[ https://issues.apache.org/jira/browse/HBASE-20487?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ted Yu updated HBASE-20487: --- Resolution: Fixed Hadoop Flags: Reviewed Status: Resolved (was: Patch Available) Thanks for

[jira] [Updated] (HBASE-20499) Replication/Priority executors can use specific max queue length as default value instead of general maxQueueLength

[ https://issues.apache.org/jira/browse/HBASE-20499?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ted Yu updated HBASE-20499: --- Attachment: 20499.master.002.patch > Replication/Priority executors can use specific max queue length as defa

[jira] [Commented] (HBASE-20499) Replication/Priority executors can use specific max queue length as default value instead of general maxQueueLength

[ https://issues.apache.org/jira/browse/HBASE-20499?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16456815#comment-16456815 ] Ted Yu commented on HBASE-20499: Rerun test suite with patch v2. > Replication/Priority

[jira] [Commented] (HBASE-20499) Replication/Priority executors can use specific max queue length as default value instead of general maxQueueLength

[ https://issues.apache.org/jira/browse/HBASE-20499?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16456768#comment-16456768 ] Ted Yu commented on HBASE-20499: {code} [ERROR] org.apache.hadoop.hbase.regionserver.Tes

[jira] [Commented] (HBASE-20499) Replication/Priority executors can use specific max queue length as default value instead of general maxQueueLength

[ https://issues.apache.org/jira/browse/HBASE-20499?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16456755#comment-16456755 ] Hadoop QA commented on HBASE-20499: --- | (x) *{color:red}-1 overall{color}* | \\ \\ || Vo

[jira] [Commented] (HBASE-20476) Open sequence number could go backwards in AssignProcedure

[ https://issues.apache.org/jira/browse/HBASE-20476?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16456741#comment-16456741 ] Hadoop QA commented on HBASE-20476: --- | (x) *{color:red}-1 overall{color}* | \\ \\ || Vo

[jira] [Commented] (HBASE-20475) Fix the flaky TestReplicationDroppedTables unit test.

[ https://issues.apache.org/jira/browse/HBASE-20475?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16456682#comment-16456682 ] Hadoop QA commented on HBASE-20475: --- | (x) *{color:red}-1 overall{color}* | \\ \\ || Vo

[jira] [Commented] (HBASE-19121) HBCK for AMv2 (A.K.A HBCK2)

[ https://issues.apache.org/jira/browse/HBASE-19121?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16456597#comment-16456597 ] stack commented on HBASE-19121: --- TODOs from a debug session w/ [~uagashe] yesterday: * "

[jira] [Commented] (HBASE-19543) Abstract a replication storage interface to extract the zk specific code

[ https://issues.apache.org/jira/browse/HBASE-19543?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16456553#comment-16456553 ] Mike Drob commented on HBASE-19543: --- It's used for monitoring and reporting - how many

[jira] [Commented] (HBASE-20500) [rsgroup] should keep at least one server in default group

[ https://issues.apache.org/jira/browse/HBASE-20500?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16456533#comment-16456533 ] Ted Yu commented on HBASE-20500: Once patch for master is accepted, it would be merged to

[jira] [Commented] (HBASE-19893) restore_snapshot is broken in master branch when region splits

[ https://issues.apache.org/jira/browse/HBASE-19893?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16456516#comment-16456516 ] Toshihiro Suzuki commented on HBASE-19893: -- Ping [~yuzhih...@gmail.com] [~ram_kr

[jira] [Commented] (HBASE-20499) Replication/Priority executors can use specific max queue length as default value instead of general maxQueueLength

[ https://issues.apache.org/jira/browse/HBASE-20499?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16456497#comment-16456497 ] Nihal Jain commented on HBASE-20499: Test cases pass locally. Re-triggering build. >

[jira] [Updated] (HBASE-20499) Replication/Priority executors can use specific max queue length as default value instead of general maxQueueLength

[ https://issues.apache.org/jira/browse/HBASE-20499?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nihal Jain updated HBASE-20499: --- Attachment: (was: HBASE-20499.master.002.patch) > Replication/Priority executors can use specific

[jira] [Updated] (HBASE-20499) Replication/Priority executors can use specific max queue length as default value instead of general maxQueueLength

[ https://issues.apache.org/jira/browse/HBASE-20499?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nihal Jain updated HBASE-20499: --- Attachment: HBASE-20499.master.002.patch > Replication/Priority executors can use specific max queue

[jira] [Commented] (HBASE-20499) Replication/Priority executors can use specific max queue length as default value instead of general maxQueueLength

[ https://issues.apache.org/jira/browse/HBASE-20499?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16456463#comment-16456463 ] Hadoop QA commented on HBASE-20499: --- | (x) *{color:red}-1 overall{color}* | \\ \\ || Vo

[jira] [Commented] (HBASE-20475) Fix the flaky TestReplicationDroppedTables unit test.

[ https://issues.apache.org/jira/browse/HBASE-20475?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16456444#comment-16456444 ] Zheng Hu commented on HBASE-20475: -- Thanks [~Apache9] for reviewing,  Pushed the addendu

[jira] [Commented] (HBASE-20476) Open sequence number could go backwards in AssignProcedure

[ https://issues.apache.org/jira/browse/HBASE-20476?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16456381#comment-16456381 ] Duo Zhang commented on HBASE-20476: --- I believe there are some magics in the code... >

[jira] [Updated] (HBASE-20476) Open sequence number could go backwards in AssignProcedure

[ https://issues.apache.org/jira/browse/HBASE-20476?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Duo Zhang updated HBASE-20476: -- Attachment: HBASE-20476-v2.patch > Open sequence number could go backwards in AssignProcedure > ---

[jira] [Commented] (HBASE-20476) Open sequence number could go backwards in AssignProcedure

[ https://issues.apache.org/jira/browse/HBASE-20476?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16456329#comment-16456329 ] Hadoop QA commented on HBASE-20476: --- | (x) *{color:red}-1 overall{color}* | \\ \\ || Vo

[jira] [Commented] (HBASE-20426) Give up replicating anything in S state

[ https://issues.apache.org/jira/browse/HBASE-20426?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16456322#comment-16456322 ] Duo Zhang commented on HBASE-20426: --- The failed UT is not related. PTAL, [~zghaobac] [~

[jira] [Commented] (HBASE-20475) Fix the flaky TestReplicationDroppedTables unit test.

[ https://issues.apache.org/jira/browse/HBASE-20475?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16456321#comment-16456321 ] Duo Zhang commented on HBASE-20475: --- {code} peersSnapshot = new HashMap<>(); replicatio

[jira] [Commented] (HBASE-20499) Replication/Priority executors can use specific max queue length as default value instead of general maxQueueLength

[ https://issues.apache.org/jira/browse/HBASE-20499?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16456306#comment-16456306 ] Hadoop QA commented on HBASE-20499: --- | (x) *{color:red}-1 overall{color}* | \\ \\ || Vo

[jira] [Updated] (HBASE-20475) Fix the flaky TestReplicationDroppedTables unit test.

[ https://issues.apache.org/jira/browse/HBASE-20475?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Zheng Hu updated HBASE-20475: - Attachment: HBASE-20475-addendum-v3.patch > Fix the flaky TestReplicationDroppedTables unit test. > -

[jira] [Updated] (HBASE-20499) Replication/Priority executors can use specific max queue length as default value instead of general maxQueueLength

[ https://issues.apache.org/jira/browse/HBASE-20499?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nihal Jain updated HBASE-20499: --- Release Note: Added new config 'hbase.ipc.server.replication.max.callqueue.length' > Replication/Pri

[jira] [Commented] (HBASE-20475) Fix the flaky TestReplicationDroppedTables unit test.

[ https://issues.apache.org/jira/browse/HBASE-20475?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16456255#comment-16456255 ] Hadoop QA commented on HBASE-20475: --- | (x) *{color:red}-1 overall{color}* | \\ \\ || Vo

[jira] [Commented] (HBASE-20499) Replication/Priority executors can use specific max queue length as default value instead of general maxQueueLength

[ https://issues.apache.org/jira/browse/HBASE-20499?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16456247#comment-16456247 ] Nihal Jain commented on HBASE-20499: This patch adds the config  *RpcScheduler.IPC_SE

[jira] [Updated] (HBASE-20499) Replication/Priority executors can use specific max queue length as default value instead of general maxQueueLength

[ https://issues.apache.org/jira/browse/HBASE-20499?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nihal Jain updated HBASE-20499: --- Attachment: HBASE-20499.master.002.patch > Replication/Priority executors can use specific max queue

[jira] [Commented] (HBASE-20496) TestGlobalThrottler failing on branch-1 since revert of HBASE-9465

[ https://issues.apache.org/jira/browse/HBASE-20496?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16456225#comment-16456225 ] Hudson commented on HBASE-20496: Results for branch branch-1 [build #297 on buil

[jira] [Commented] (HBASE-19994) Create a new class for RPC throttling exception, make it retryable.

[ https://issues.apache.org/jira/browse/HBASE-19994?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16456227#comment-16456227 ] Hudson commented on HBASE-19994: Results for branch branch-1 [build #297 on buil

[jira] [Commented] (HBASE-19924) hbase rpc throttling does not work for multi() with request count rater.

[ https://issues.apache.org/jira/browse/HBASE-19924?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16456224#comment-16456224 ] Hudson commented on HBASE-19924: Results for branch branch-1 [build #297 on buil

[jira] [Updated] (HBASE-20476) Open sequence number could go backwards in AssignProcedure

[ https://issues.apache.org/jira/browse/HBASE-20476?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Duo Zhang updated HBASE-20476: -- Affects Version/s: 2.0.0 2.1.0 3.0.0 > Open sequence numb

[jira] [Commented] (HBASE-20493) Port HBASE-19994 (Create a new class for RPC throttling exception, make it retryable) to branch-1

[ https://issues.apache.org/jira/browse/HBASE-20493?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16456226#comment-16456226 ] Hudson commented on HBASE-20493: Results for branch branch-1 [build #297 on buil

[jira] [Commented] (HBASE-20431) Store commit transaction for filesystems that do not support an atomic rename

[ https://issues.apache.org/jira/browse/HBASE-20431?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16456203#comment-16456203 ] Steve Loughran commented on HBASE-20431: FWIW, I've been discussing with Stephan

[jira] [Updated] (HBASE-20476) Open sequence number could go backwards in AssignProcedure

[ https://issues.apache.org/jira/browse/HBASE-20476?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Duo Zhang updated HBASE-20476: -- Attachment: HBASE-20476-v1.patch > Open sequence number could go backwards in AssignProcedure > ---

[jira] [Updated] (HBASE-20476) Open sequence number could go backwards in AssignProcedure

[ https://issues.apache.org/jira/browse/HBASE-20476?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Duo Zhang updated HBASE-20476: -- Status: Patch Available (was: Open) > Open sequence number could go backwards in AssignProcedure > ---

[jira] [Updated] (HBASE-20476) Open sequence number could go backwards in AssignProcedure

[ https://issues.apache.org/jira/browse/HBASE-20476?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Duo Zhang updated HBASE-20476: -- Component/s: Region Assignment > Open sequence number could go backwards in AssignProcedure > -

[jira] [Updated] (HBASE-20476) Open sequence number could go backwards in AssignProcedure

[ https://issues.apache.org/jira/browse/HBASE-20476?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Duo Zhang updated HBASE-20476: -- Summary: Open sequence number could go backwards in AssignProcedure (was: Fix the flaky TestReplicatio

[jira] [Commented] (HBASE-20476) Fix the flaky TestReplicationSmallTests unit test

[ https://issues.apache.org/jira/browse/HBASE-20476?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16456188#comment-16456188 ] Duo Zhang commented on HBASE-20476: --- OK, skimmed the code, seems the zero is from here.

[jira] [Commented] (HBASE-20433) HBase Export Snapshot utility does not close FileSystem instances

[ https://issues.apache.org/jira/browse/HBASE-20433?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16456185#comment-16456185 ] Steve Loughran commented on HBASE-20433: Maybe we could do a special build of had

[jira] [Commented] (HBASE-20476) Fix the flaky TestReplicationSmallTests unit test

[ https://issues.apache.org/jira/browse/HBASE-20476?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16456180#comment-16456180 ] Duo Zhang commented on HBASE-20476: --- OK I think the problem is here {noformat} 2018-04

[jira] [Comment Edited] (HBASE-20500) [rsgroup] should keep at least one server in default group

[ https://issues.apache.org/jira/browse/HBASE-20500?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16456159#comment-16456159 ] Yechao Chen edited comment on HBASE-20500 at 4/27/18 9:29 AM: -

[jira] [Commented] (HBASE-20485) Copy constructor of Scan doesn't copy the readType and replicaId

[ https://issues.apache.org/jira/browse/HBASE-20485?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16456160#comment-16456160 ] Hadoop QA commented on HBASE-20485: --- | (/) *{color:green}+1 overall{color}* | \\ \\ ||

[jira] [Commented] (HBASE-20500) [rsgroup] should keep at least one server in default group

[ https://issues.apache.org/jira/browse/HBASE-20500?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16456159#comment-16456159 ] Yechao Chen commented on HBASE-20500: - [~yuzhih...@gmail.com] yes sir ,submit a patch

[jira] [Commented] (HBASE-20500) [rsgroup] should keep at least one server in default group

[ https://issues.apache.org/jira/browse/HBASE-20500?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16456158#comment-16456158 ] Ted Yu commented on HBASE-20500: Can you generate patch for master branch ? Also, can yo

[jira] [Commented] (HBASE-20499) Replication/Priority executors can use specific max queue length as default value instead of general maxQueueLength

[ https://issues.apache.org/jira/browse/HBASE-20499?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16456157#comment-16456157 ] Nihal Jain commented on HBASE-20499: Okay I will make the appropriate changes and upd

[jira] [Updated] (HBASE-20500) [rsgroup] should keep at least one server in default group

[ https://issues.apache.org/jira/browse/HBASE-20500?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Yechao Chen updated HBASE-20500: Attachment: HBASE-20500-branch-2.v1.patch > [rsgroup] should keep at least one server in default gr

[jira] [Commented] (HBASE-20499) Replication/Priority executors can use specific max queue length as default value instead of general maxQueueLength

[ https://issues.apache.org/jira/browse/HBASE-20499?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16456156#comment-16456156 ] Ted Yu commented on HBASE-20499: Sounds good to me. Please update release note. > Repli

[jira] [Commented] (HBASE-20476) Fix the flaky TestReplicationSmallTests unit test

[ https://issues.apache.org/jira/browse/HBASE-20476?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16456154#comment-16456154 ] Duo Zhang commented on HBASE-20476: --- {noformat} 2018-04-27 08:59:21,255 INFO [PEWorker

[jira] [Commented] (HBASE-20500) [rsgroup] should keep at least one server in default group

[ https://issues.apache.org/jira/browse/HBASE-20500?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16456151#comment-16456151 ] Ted Yu commented on HBASE-20500: There seems to be some typo in the error above. Here is

[jira] [Commented] (HBASE-20499) Replication/Priority executors can use specific max queue length as default value instead of general maxQueueLength

[ https://issues.apache.org/jira/browse/HBASE-20499?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16456152#comment-16456152 ] Nihal Jain commented on HBASE-20499: We're actually already doing it in the above pat

[jira] [Updated] (HBASE-20500) [rsgroup] should keep at least one server in default group

[ https://issues.apache.org/jira/browse/HBASE-20500?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Yechao Chen updated HBASE-20500: Description: we move all the servers from default group the default group will has  no servers, t

[jira] [Commented] (HBASE-20500) [rsgroup] should keep at least one server in default group

[ https://issues.apache.org/jira/browse/HBASE-20500?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16456150#comment-16456150 ] Yechao Chen commented on HBASE-20500: - !create_table_with_empty_default_group.png! >

[jira] [Issue Comment Deleted] (HBASE-20500) [rsgroup] should keep at least one server in default group

[ https://issues.apache.org/jira/browse/HBASE-20500?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Yechao Chen updated HBASE-20500: Comment: was deleted (was: !create_table_with_empty_default_group.png!) > [rsgroup] should keep at

[jira] [Updated] (HBASE-20500) [rsgroup] should keep at least one server in default group

[ https://issues.apache.org/jira/browse/HBASE-20500?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Yechao Chen updated HBASE-20500: Attachment: (was: create_table_with_empty_default_group.png) > [rsgroup] should keep at least o

[jira] [Created] (HBASE-20500) [rsgroup] should keep at least one server in default group

Yechao Chen created HBASE-20500: --- Summary: [rsgroup] should keep at least one server in default group Key: HBASE-20500 URL: https://issues.apache.org/jira/browse/HBASE-20500 Project: HBase Issu

[jira] [Commented] (HBASE-20499) Replication/Priority executors can use specific max queue length as default value instead of general maxQueueLength

[ https://issues.apache.org/jira/browse/HBASE-20499?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16456148#comment-16456148 ] Ted Yu commented on HBASE-20499: What would be a proper default value for the new config

  1   2   >