[jira] [Commented] (HBASE-21146) (2.0) Add ability for HBase Canary to ignore a configurable number of ZooKeeper down nodes

[ https://issues.apache.org/jira/browse/HBASE-21146?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16695094#comment-16695094 ] David Manning commented on HBASE-21146: --- [~stack] I applied HBASE-21145 patch (branch-2.1) and

[jira] [Commented] (HBASE-21387) Race condition surrounding in progress snapshot handling in snapshot cache leads to loss of snapshot files

[ https://issues.apache.org/jira/browse/HBASE-21387?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16695128#comment-16695128 ] Josh Elser commented on HBASE-21387: bq. Running the test locally a few times, but I think this is

[jira] [Commented] (HBASE-21479) TestHRegionReplayEvents#testSkippingEditsWithSmallerSeqIdAfterRegionOpenEvent fails with IndexOutOfBoundsException

[ https://issues.apache.org/jira/browse/HBASE-21479?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16695317#comment-16695317 ] Sean Busbey commented on HBASE-21479: - We should log what the filesystem we're writing to is at the

[jira] [Commented] (HBASE-21387) Race condition surrounding in progress snapshot handling in snapshot cache leads to loss of snapshot files

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

[jira] [Updated] (HBASE-21459) More benchmark for evaluating the checkKeyValueBytes's performance

[ https://issues.apache.org/jira/browse/HBASE-21459?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Zheng Hu updated HBASE-21459: - Attachment: 0002-Benchmark-the-checkKeyValueBytes.patch > More benchmark for evaluating the

[jira] [Commented] (HBASE-21459) More benchmark for evaluating the checkKeyValueBytes's performance

[ https://issues.apache.org/jira/browse/HBASE-21459?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16694612#comment-16694612 ] Zheng Hu commented on HBASE-21459: -- I made a benchmark by using the attached two patches. the result

[jira] [Commented] (HBASE-21034) Add new throttle type: read/write capacity unit

[ https://issues.apache.org/jira/browse/HBASE-21034?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16694520#comment-16694520 ] Anoop Sam John commented on HBASE-21034: Need a nice RN with configs way to use etc. > Add new

[jira] [Commented] (HBASE-21034) Add new throttle type: read/write capacity unit

[ https://issues.apache.org/jira/browse/HBASE-21034?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16694569#comment-16694569 ] Hudson commented on HBASE-21034: Results for branch branch-2 [build #1515 on

[jira] [Comment Edited] (HBASE-21459) More benchmark for evaluating the checkKeyValueBytes's performance

[ https://issues.apache.org/jira/browse/HBASE-21459?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16694612#comment-16694612 ] Zheng Hu edited comment on HBASE-21459 at 11/21/18 12:11 PM: - I made a

[jira] [Updated] (HBASE-21387) Race condition surrounding in progress snapshot handling in snapshot cache leads to loss of snapshot files

[ https://issues.apache.org/jira/browse/HBASE-21387?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Zheng Hu updated HBASE-21387: - Attachment: HBASE-21387.v16.patch > Race condition surrounding in progress snapshot handling in

[jira] [Commented] (HBASE-21034) Add new throttle type: read/write capacity unit

[ https://issues.apache.org/jira/browse/HBASE-21034?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16694573#comment-16694573 ] Hudson commented on HBASE-21034: Results for branch master [build #620 on

[jira] [Updated] (HBASE-21459) More benchmark for evaluating the checkKeyValueBytes's performance

[ https://issues.apache.org/jira/browse/HBASE-21459?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Zheng Hu updated HBASE-21459: - Attachment: 0001-HBASE-21401-Sanity-check-in-BaseDecoder-parseCell.patch

[jira] [Updated] (HBASE-21459) More benchmark for evaluating the checkKeyValueBytes's performance

[ https://issues.apache.org/jira/browse/HBASE-21459?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Zheng Hu updated HBASE-21459: - Attachment: (was: 0002-Benchmark-the-checkKeyValueBytes.patch) > More benchmark for evaluating the

[jira] [Comment Edited] (HBASE-21459) More benchmark for evaluating the checkKeyValueBytes's performance

[ https://issues.apache.org/jira/browse/HBASE-21459?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16694612#comment-16694612 ] Zheng Hu edited comment on HBASE-21459 at 11/21/18 12:10 PM: - I made a

[jira] [Commented] (HBASE-21387) Race condition surrounding in progress snapshot handling in snapshot cache leads to loss of snapshot files

[ https://issues.apache.org/jira/browse/HBASE-21387?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16694397#comment-16694397 ] Zheng Hu commented on HBASE-21387: -- Patch.v16 fix the checkstyle now. [~yuzhih...@gmail.com] &

[jira] [Updated] (HBASE-21481) [acl] Superuser's permissions should not be granted or revoked by any non-su global admin

[ https://issues.apache.org/jira/browse/HBASE-21481?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Reid Chan updated HBASE-21481: -- Attachment: HBASE-21481.master.003.patch > [acl] Superuser's permissions should not be granted or

[jira] [Commented] (HBASE-21503) Replication normal source can get stuck due potential race conditions between source wal reader and wal provider initialization threads.

[ https://issues.apache.org/jira/browse/HBASE-21503?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16694509#comment-16694509 ] Wellington Chevreuil commented on HBASE-21503: -- {quote} So the problem here is that, we

[jira] [Updated] (HBASE-21503) Replication normal source can get stuck due potential race conditions between source wal reader and wal provider initialization threads.

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

[jira] [Updated] (HBASE-21300) Fix the wrong reference file path when restoring snapshots for tables with MOB columns

[ https://issues.apache.org/jira/browse/HBASE-21300?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Yi Mei updated HBASE-21300: --- Attachment: HBASE-21300.master.003.patch > Fix the wrong reference file path when restoring snapshots for

[jira] [Commented] (HBASE-21387) Race condition surrounding in progress snapshot handling in snapshot cache leads to loss of snapshot files

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

[jira] [Commented] (HBASE-21498) Master OOM when SplitTableRegionProcedure new CacheConfig and instantiate a new BlockCache

[ https://issues.apache.org/jira/browse/HBASE-21498?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16694526#comment-16694526 ] Anoop Sam John commented on HBASE-21498: bq. if (!(this instanceof HMaster &&

[jira] [Updated] (HBASE-21154) Remove hbase:namespace table; fold it into hbase:meta

[ https://issues.apache.org/jira/browse/HBASE-21154?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Duo Zhang updated HBASE-21154: -- Attachment: HBASE-21154-v2.patch > Remove hbase:namespace table; fold it into hbase:meta >

[jira] [Updated] (HBASE-21504) When Using FIFOCompactionPolicy, in some case, doing a compaction will write a zero-entryCounter hfile, the hfile will never be TTL expired

[ https://issues.apache.org/jira/browse/HBASE-21504?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] xuming updated HBASE-21504: --- Description: When i use FIFOCompactionPolicy, and if all hfiles(>1) are TTL expired in a region, once we do

[jira] [Updated] (HBASE-21504) When Using FIFOCompactionPolicy, in some case, doing a compaction will commit a new hfile, but it's maxTimeStamp is Long.MAX_VALUE.The hfile will never be archived

[ https://issues.apache.org/jira/browse/HBASE-21504?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] xuming updated HBASE-21504: --- Summary: When Using FIFOCompactionPolicy, in some case, doing a compaction will commit a new hfile, but

[jira] [Updated] (HBASE-21504) If enable FIFOCompactionPolicy, a compaction may write a "empty" hfile whose maxTimeStamp is long max. This kind of hfile will never be archived.

[ https://issues.apache.org/jira/browse/HBASE-21504?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] xuming updated HBASE-21504: --- Summary: If enable FIFOCompactionPolicy, a compaction may write a "empty" hfile whose maxTimeStamp is long

[jira] [Commented] (HBASE-21504) If enable FIFOCompactionPolicy, a compaction may write a "empty" hfile whose maxTimeStamp is long max. This kind of hfile will never be archived.

[ https://issues.apache.org/jira/browse/HBASE-21504?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16694717#comment-16694717 ] Zheng Hu commented on HBASE-21504: -- Interesting, Could you please provide some UT for the bug fix ? I

[jira] [Commented] (HBASE-21503) Replication normal source can get stuck due potential race conditions between source wal reader and wal provider initialization threads.

[ https://issues.apache.org/jira/browse/HBASE-21503?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16694876#comment-16694876 ] Hudson commented on HBASE-21503: Results for branch branch-2.0 [build #1102 on

[jira] [Created] (HBASE-21505) Several inconsistencies on information reported for Replication Sources by hbase shell status 'replication' command.

Wellington Chevreuil created HBASE-21505: Summary: Several inconsistencies on information reported for Replication Sources by hbase shell status 'replication' command. Key: HBASE-21505 URL:

[jira] [Updated] (HBASE-21504) When Using FIFOCompactionPolicy, in some case, doing a compaction will write a zero-entryCounter hfile, the hfile will never be TTL expired

[ https://issues.apache.org/jira/browse/HBASE-21504?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] xuming updated HBASE-21504: --- Description: When i use FIFOCompactionPolicy, and if all hfiles(>1) are TTL expired in a region, once we do

[jira] [Updated] (HBASE-21504) When Using FIFOCompactionPolicy, in some case, doing a compaction will write a zero-entryCounter hfile whose maxTimeStamp is Long.MAX_VALUE, the hfile will never be arch

[ https://issues.apache.org/jira/browse/HBASE-21504?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] xuming updated HBASE-21504: --- Summary: When Using FIFOCompactionPolicy, in some case, doing a compaction will write a zero-entryCounter

[jira] [Updated] (HBASE-21504) When enable FIFOCompactionPolicy, a compaction may commit a initial hfile whose maxTimeStamp is Long.MAX_VALUE. These initial hfile will never be archived by FIFOCompact

[ https://issues.apache.org/jira/browse/HBASE-21504?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] xuming updated HBASE-21504: --- Summary: When enable FIFOCompactionPolicy, a compaction may commit a initial hfile whose maxTimeStamp is

[jira] [Updated] (HBASE-21504) If enable FIFOCompactionPolicy, a compaction may commit a initial hfile whose maxTimeStamp is Long.MAX_VALUE. These initial hfile will never be archived by FIFOCompactio

[ https://issues.apache.org/jira/browse/HBASE-21504?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] xuming updated HBASE-21504: --- Summary: If enable FIFOCompactionPolicy, a compaction may commit a initial hfile whose maxTimeStamp is

[jira] [Commented] (HBASE-21481) [acl] Superuser's permissions should not be granted or revoked by any non-su global admin

[ https://issues.apache.org/jira/browse/HBASE-21481?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16694722#comment-16694722 ] Reid Chan commented on HBASE-21481: --- ping [~stack], would you mind taking a look, if having free

[jira] [Commented] (HBASE-21394) Restore snapshot in parallel

[ https://issues.apache.org/jira/browse/HBASE-21394?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16694796#comment-16694796 ] Zheng Hu commented on HBASE-21394: -- Take a look the RestoreSnapshotHelper#restoreHdfsRegions carefully,

[jira] [Resolved] (HBASE-21394) Restore snapshot in parallel

[ https://issues.apache.org/jira/browse/HBASE-21394?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Zheng Hu resolved HBASE-21394. -- Resolution: Implemented > Restore snapshot in parallel > > >

[jira] [Commented] (HBASE-21300) Fix the wrong reference file path when restoring snapshots for tables with MOB columns

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

[jira] [Commented] (HBASE-21154) Remove hbase:namespace table; fold it into hbase:meta

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

[jira] [Updated] (HBASE-21504) When Using FIFOCompactionPolicy, in some case, doing a compaction will write a zero-entryCounter hfile, the hfile will never be TTL expired

[ https://issues.apache.org/jira/browse/HBASE-21504?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] xuming updated HBASE-21504: --- Summary: When Using FIFOCompactionPolicy, in some case, doing a compaction will write a zero-entryCounter

[jira] [Updated] (HBASE-21504) When Using FIFOCompactionPolicy, a compaction may commit a initial hfile whose maxTimeStamp is Long.MAX_VALUE. These initial hfile will never be archived by FIFOCompacti

[ https://issues.apache.org/jira/browse/HBASE-21504?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] xuming updated HBASE-21504: --- Summary: When Using FIFOCompactionPolicy, a compaction may commit a initial hfile whose maxTimeStamp is

[jira] [Updated] (HBASE-21504) If enable FIFOCompactionPolicy, a compaction may write a new hfile whose maxTimeStamp is Long.MAX_VALUE. This kind of hfile will never be archived by FIFOCompactionPolic

[ https://issues.apache.org/jira/browse/HBASE-21504?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] xuming updated HBASE-21504: --- Description: When i use FIFOCompactionPolicy, and if all hfiles(>1) are TTL expired in a region, once we do

[jira] [Commented] (HBASE-21387) Race condition surrounding in progress snapshot handling in snapshot cache leads to loss of snapshot files

[ https://issues.apache.org/jira/browse/HBASE-21387?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16694766#comment-16694766 ] Zheng Hu commented on HBASE-21387: -- [~yuzhih...@gmail.com], Any other concern ? For the name refactor

[jira] [Updated] (HBASE-21459) More benchmark for evaluating the checkKeyValueBytes's performance

[ https://issues.apache.org/jira/browse/HBASE-21459?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Zheng Hu updated HBASE-21459: - Attachment: result.txt > More benchmark for evaluating the checkKeyValueBytes's performance >

[jira] [Commented] (HBASE-21481) [acl] Superuser's permissions should not be granted or revoked by any non-su global admin

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

[jira] [Updated] (HBASE-21504) When Using FIFOCompactionPolicy, in some case, doing a compaction will write a empty hfile which will never be TTL expired

[ https://issues.apache.org/jira/browse/HBASE-21504?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] xuming updated HBASE-21504: --- Summary: When Using FIFOCompactionPolicy, in some case, doing a compaction will write a empty hfile which

[jira] [Updated] (HBASE-21504) When Using FIFOCompactionPolicy, in some case, doing a compaction will write a initial hfile which will never be TTL expired

[ https://issues.apache.org/jira/browse/HBASE-21504?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] xuming updated HBASE-21504: --- Summary: When Using FIFOCompactionPolicy, in some case, doing a compaction will write a initial hfile which

[jira] [Updated] (HBASE-21504) When Using FIFOCompactionPolicy, in some case, doing a compaction will write a zero-entryCounter hfile, the hfile will never be TTL expired and it will stay forever

[ https://issues.apache.org/jira/browse/HBASE-21504?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] xuming updated HBASE-21504: --- Summary: When Using FIFOCompactionPolicy, in some case, doing a compaction will write a zero-entryCounter

[jira] [Updated] (HBASE-21504) When Using FIFOCompactionPolicy, in some case, doing a compaction will commit a new hfile, but it's maxTimeStamp is Long.MAX_VALUE.The hfile will never be archived forev

[ https://issues.apache.org/jira/browse/HBASE-21504?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] xuming updated HBASE-21504: --- Summary: When Using FIFOCompactionPolicy, in some case, doing a compaction will commit a new hfile, but

[jira] [Updated] (HBASE-21504) If enable FIFOCompactionPolicy, a compaction may write a new hfile whose maxTimeStamp is Long.MAX_VALUE. These case hfiles will never be archived by FIFOCompactionPolicy

[ https://issues.apache.org/jira/browse/HBASE-21504?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] xuming updated HBASE-21504: --- Summary: If enable FIFOCompactionPolicy, a compaction may write a new hfile whose maxTimeStamp is

[jira] [Updated] (HBASE-21504) If enable FIFOCompactionPolicy, a compaction may write a new hfile whose maxTimeStamp is Long.MAX_VALUE. This kind of hfile will never be archived by FIFOCompactionPolic

[ https://issues.apache.org/jira/browse/HBASE-21504?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] xuming updated HBASE-21504: --- Summary: If enable FIFOCompactionPolicy, a compaction may write a new hfile whose maxTimeStamp is

[jira] [Commented] (HBASE-21481) [acl] Superuser's permissions should not be granted or revoked by any non-su global admin

[ https://issues.apache.org/jira/browse/HBASE-21481?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16694704#comment-16694704 ] Reid Chan commented on HBASE-21481: --- v4 fixed checkstyle warning > [acl] Superuser's permissions

[jira] [Updated] (HBASE-21481) [acl] Superuser's permissions should not be granted or revoked by any non-su global admin

[ https://issues.apache.org/jira/browse/HBASE-21481?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Reid Chan updated HBASE-21481: -- Attachment: HBASE-21481.master.004.patch > [acl] Superuser's permissions should not be granted or

[jira] [Created] (HBASE-21504) Using FIFOCompactionPolicy, a compact my write a empty HFile. And the HFile will never be expired

xuming created HBASE-21504: -- Summary: Using FIFOCompactionPolicy, a compact my write a empty HFile. And the HFile will never be expired Key: HBASE-21504 URL: https://issues.apache.org/jira/browse/HBASE-21504

[jira] [Updated] (HBASE-21504) When Using FIFOCompactionPolicy, in some case, doing a compaction will write a zero-entry-counter hfile which will never be TTL expired

[ https://issues.apache.org/jira/browse/HBASE-21504?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] xuming updated HBASE-21504: --- Summary: When Using FIFOCompactionPolicy, in some case, doing a compaction will write a zero-entry-counter

[jira] [Updated] (HBASE-21504) If enable FIFOCompactionPolicy, a compaction may write a new hfile whose maxTimeStamp is Long.MAX_VALUE. This kind of hfile will never be archived by FIFOCompactionPolic

[ https://issues.apache.org/jira/browse/HBASE-21504?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] xuming updated HBASE-21504: --- Description: When i use FIFOCompactionPolicy, and if all hfiles(>1) are TTL expired in a region, once we do

[jira] [Created] (HBASE-21506) Fix for warning: Multiple versions of scala detected in phoenix-spark

Artem Ervits created HBASE-21506: Summary: Fix for warning: Multiple versions of scala detected in phoenix-spark Key: HBASE-21506 URL: https://issues.apache.org/jira/browse/HBASE-21506 Project: HBase

[jira] [Resolved] (HBASE-21506) Fix for warning: Multiple versions of scala detected in phoenix-spark

[ https://issues.apache.org/jira/browse/HBASE-21506?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Artem Ervits resolved HBASE-21506. -- Resolution: Invalid > Fix for warning: Multiple versions of scala detected in phoenix-spark >

[jira] [Commented] (HBASE-21387) Race condition surrounding in progress snapshot handling in snapshot cache leads to loss of snapshot files

[ https://issues.apache.org/jira/browse/HBASE-21387?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16694979#comment-16694979 ] Josh Elser commented on HBASE-21387: Thanks, for the ping, Zheng. Taking a look at this now :) >

[jira] [Work started] (HBASE-21505) Several inconsistencies on information reported for Replication Sources by hbase shell status 'replication' command.

[ https://issues.apache.org/jira/browse/HBASE-21505?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Work on HBASE-21505 started by Wellington Chevreuil. > Several inconsistencies on information reported for

[jira] [Commented] (HBASE-21505) Several inconsistencies on information reported for Replication Sources by hbase shell status 'replication' command.

[ https://issues.apache.org/jira/browse/HBASE-21505?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16694992#comment-16694992 ] Wellington Chevreuil commented on HBASE-21505: -- Some output suggestions for each of the

[jira] [Commented] (HBASE-20952) Re-visit the WAL API

[ https://issues.apache.org/jira/browse/HBASE-20952?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16695000#comment-16695000 ] Josh Elser commented on HBASE-20952: {quote}I pushed a commit to move this branch to weekly tests.

[jira] [Updated] (HBASE-21387) Race condition surrounding in progress snapshot handling in snapshot cache leads to loss of snapshot files

[ https://issues.apache.org/jira/browse/HBASE-21387?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Zheng Hu updated HBASE-21387: - Attachment: HBASE-21387.v17.patch > Race condition surrounding in progress snapshot handling in

[jira] [Commented] (HBASE-21387) Race condition surrounding in progress snapshot handling in snapshot cache leads to loss of snapshot files

[ https://issues.apache.org/jira/browse/HBASE-21387?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16695529#comment-16695529 ] Zheng Hu commented on HBASE-21387: -- bq. does this method need to be synchronized? I think you are

[jira] [Updated] (HBASE-21154) Remove hbase:namespace table; fold it into hbase:meta

[ https://issues.apache.org/jira/browse/HBASE-21154?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Duo Zhang updated HBASE-21154: -- Attachment: HBASE-21154-v4.patch > Remove hbase:namespace table; fold it into hbase:meta >

[jira] [Updated] (HBASE-21154) Remove hbase:namespace table; fold it into hbase:meta

[ https://issues.apache.org/jira/browse/HBASE-21154?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Duo Zhang updated HBASE-21154: -- Release Note: Add a new family called 'ns' for meta table and store the namespace related

[jira] [Commented] (HBASE-21503) Replication normal source can get stuck due potential race conditions between source wal reader and wal provider initialization threads.

[ https://issues.apache.org/jira/browse/HBASE-21503?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16695405#comment-16695405 ] Hudson commented on HBASE-21503: Results for branch branch-2 [build #1516 on

[jira] [Commented] (HBASE-21154) Remove hbase:namespace table; fold it into hbase:meta

[ https://issues.apache.org/jira/browse/HBASE-21154?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16695600#comment-16695600 ] Duo Zhang commented on HBASE-21154: --- OK there is a problem that we should disable the namespace table

[jira] [Commented] (HBASE-21387) Race condition surrounding in progress snapshot handling in snapshot cache leads to loss of snapshot files

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

[jira] [Updated] (HBASE-21154) Remove hbase:namespace table; fold it into hbase:meta

[ https://issues.apache.org/jira/browse/HBASE-21154?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Duo Zhang updated HBASE-21154: -- Release Note: Add a new family called 'ns' for meta table and store the namespace related

[jira] [Commented] (HBASE-21401) Sanity check in BaseDecoder#parseCell

[ https://issues.apache.org/jira/browse/HBASE-21401?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16695612#comment-16695612 ] Anoop Sam John commented on HBASE-21401: bq.OK, I've revert the patch for branch-2.x firstly...

[jira] [Commented] (HBASE-21154) Remove hbase:namespace table; fold it into hbase:meta

[ https://issues.apache.org/jira/browse/HBASE-21154?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16695434#comment-16695434 ] Sean Busbey commented on HBASE-21154: - I would like to review, have started but need time. (in case

[jira] [Updated] (HBASE-21034) Add new throttle type: read/write capacity unit

[ https://issues.apache.org/jira/browse/HBASE-21034?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Yi Mei updated HBASE-21034: --- Release Note: Provides a new throttle type: capacity unit. One read/write/request capacity unit represents

[jira] [Commented] (HBASE-21505) Several inconsistencies on information reported for Replication Sources by hbase shell status 'replication' command.

[ https://issues.apache.org/jira/browse/HBASE-21505?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16695537#comment-16695537 ] Jingyun Tian commented on HBASE-21505: -- [~wchevreuil] Sir, these metrics are mainly to indicate if

[jira] [Commented] (HBASE-21387) Race condition surrounding in progress snapshot handling in snapshot cache leads to loss of snapshot files

[ https://issues.apache.org/jira/browse/HBASE-21387?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16695049#comment-16695049 ] Josh Elser commented on HBASE-21387: {code:java} +  public boolean isAnySnapshotTaking() { +   

[jira] [Updated] (HBASE-21146) (2.0) Add ability for HBase Canary to ignore a configurable number of ZooKeeper down nodes

[ https://issues.apache.org/jira/browse/HBASE-21146?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] David Manning updated HBASE-21146: -- Attachment: HBASE-21146.branch-2.0.001.patch > (2.0) Add ability for HBase Canary to ignore a

[jira] [Commented] (HBASE-21481) [acl] Superuser's permissions should not be granted or revoked by any non-su global admin

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

[jira] [Commented] (HBASE-21503) Replication normal source can get stuck due potential race conditions between source wal reader and wal provider initialization threads.

[ https://issues.apache.org/jira/browse/HBASE-21503?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16694898#comment-16694898 ] Hudson commented on HBASE-21503: Results for branch branch-2.1 [build #624 on