[jira] [Commented] (HBASE-21648) [rsgroup] hbase shell "move_servers_rsgroup" or "balance_rsgroup" will be failed when meet a split region.

2018-12-29 Thread xuming (JIRA)
[ https://issues.apache.org/jira/browse/HBASE-21648?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16730638#comment-16730638 ] xuming commented on HBASE-21648: OK,I will do it recent day > [rsgroup] hbase shell

[jira] [Updated] (HBASE-21648) [rsgroup] hbase shell "move_servers_rsgroup" or "balance_rsgroup" will be failed when meet a split region.

2018-12-27 Thread xuming (JIRA)
[ https://issues.apache.org/jira/browse/HBASE-21648?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] xuming updated HBASE-21648: --- Summary: [rsgroup] hbase shell "move_servers_rsgroup" or "balance_rsgroup" will be failed when meet a split

[jira] [Updated] (HBASE-21648) hbase shell "move_servers_rsgroup" or "balance_rsgroup" will be failed when meet a split region.

2018-12-27 Thread xuming (JIRA)
[ https://issues.apache.org/jira/browse/HBASE-21648?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] xuming updated HBASE-21648: --- Attachment: (was: HBASE-21648.v1.patch) > hbase shell "move_servers_rsgroup" or "balance_rsgroup" will

[jira] [Updated] (HBASE-21648) hbase shell "move_servers_rsgroup" or "balance_rsgroup" will be failed when meet a split region.

2018-12-27 Thread xuming (JIRA)
[ https://issues.apache.org/jira/browse/HBASE-21648?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] xuming updated HBASE-21648: --- Attachment: HBASE-21648.v1.patch > hbase shell "move_servers_rsgroup" or "balance_rsgroup" will be failed

[jira] [Updated] (HBASE-21648) hbase shell "move_servers_rsgroup" or "balance_rsgroup" will be failed when meet a split region.

2018-12-27 Thread xuming (JIRA)
[ https://issues.apache.org/jira/browse/HBASE-21648?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] xuming updated HBASE-21648: --- Description: A  example： We have a table "A" which is in RSGroup "group1". 

[jira] [Updated] (HBASE-21648) hbase shell "move_servers_rsgroup" or "balance_rsgroup" will be failed when meet a split region.

2018-12-27 Thread xuming (JIRA)
[ https://issues.apache.org/jira/browse/HBASE-21648?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] xuming updated HBASE-21648: --- Attachment: HBASE-21648.v1.patch > hbase shell "move_servers_rsgroup" or "balance_rsgroup" will be failed

[jira] [Updated] (HBASE-21648) hbase shell "move_servers_rsgroup" or "balance_rsgroup" will be failed when meet a split region.

2018-12-26 Thread xuming (JIRA)
[ https://issues.apache.org/jira/browse/HBASE-21648?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] xuming updated HBASE-21648: --- Description: A  example： We have a table "A" which is in RSGroup "group1". 

[jira] [Updated] (HBASE-21648) hbase shell "move_servers_rsgroup" or "balance_rsgroup" will be failed when meet a split region.

2018-12-26 Thread xuming (JIRA)
[ https://issues.apache.org/jira/browse/HBASE-21648?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] xuming updated HBASE-21648: --- Description: A  example： We have a table "A" which is in RSGroup "group1".

[jira] [Updated] (HBASE-21648) hbase shell "move_servers_rsgroup" and "balance_rsgroup" will be failed when meet a split region.

2018-12-26 Thread xuming (JIRA)
[ https://issues.apache.org/jira/browse/HBASE-21648?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] xuming updated HBASE-21648: --- Description: If i  > hbase shell "move_servers_rsgroup" and "balance_rsgroup" will be failed when > meet a

[jira] [Created] (HBASE-21648) hbase shell "move_servers_rsgroup" and "balance_rsgroup" will be failed when meet a split region.

2018-12-26 Thread xuming (JIRA)
xuming created HBASE-21648: -- Summary: hbase shell "move_servers_rsgroup" and "balance_rsgroup" will be failed when meet a split region. Key: HBASE-21648 URL: https://issues.apache.org/jira/browse/HBASE-21648

[jira] [Updated] (HBASE-21648) hbase shell "move_servers_rsgroup" or "balance_rsgroup" will be failed when meet a split region.

2018-12-26 Thread xuming (JIRA)
[ https://issues.apache.org/jira/browse/HBASE-21648?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] xuming updated HBASE-21648: --- Summary: hbase shell "move_servers_rsgroup" or "balance_rsgroup" will be failed when meet a split region.

[jira] [Updated] (HBASE-21648) hbase shell "move_servers_rsgroup" and "balance_rsgroup" will be failed when meet a split region.

2018-12-26 Thread xuming (JIRA)
[ https://issues.apache.org/jira/browse/HBASE-21648?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] xuming updated HBASE-21648: --- Component/s: rsgroup > hbase shell "move_servers_rsgroup" and "balance_rsgroup" will be failed when > meet

[jira] [Updated] (HBASE-21648) hbase shell "move_servers_rsgroup" and "balance_rsgroup" will be failed when meet a split region.

2018-12-26 Thread xuming (JIRA)
[ https://issues.apache.org/jira/browse/HBASE-21648?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] xuming updated HBASE-21648: --- Affects Version/s: 2.1.0 > hbase shell "move_servers_rsgroup" and "balance_rsgroup" will be failed when >

[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.

2018-11-21 Thread xuming (JIRA)
[ 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] [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

2018-11-21 Thread xuming (JIRA)
[ 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

2018-11-21 Thread xuming (JIRA)
[ 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) 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

2018-11-21 Thread xuming (JIRA)
[ 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) 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

2018-11-21 Thread xuming (JIRA)
[ 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. These case hfiles will never be archived by FIFOCompactionPolicy

2018-11-21 Thread xuming (JIRA)
[ 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 commit a initial hfile whose maxTimeStamp is Long.MAX_VALUE. These initial hfile will never be archived by FIFOCompactio

2018-11-21 Thread xuming (JIRA)
[ 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] [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

2018-11-21 Thread xuming (JIRA)
[ 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) 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

2018-11-21 Thread xuming (JIRA)
[ 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) 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

2018-11-21 Thread xuming (JIRA)
[ 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) 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

2018-11-21 Thread xuming (JIRA)
[ 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 write a zero-entryCounter hfile, the hfile will never be TTL expired and it will stay forever

2018-11-21 Thread xuming (JIRA)
[ 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 write a zero-entryCounter hfile, the hfile will never be TTL expired

2018-11-21 Thread xuming (JIRA)
[ 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, the hfile will never be TTL expired

2018-11-21 Thread xuming (JIRA)
[ 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, the hfile will never be TTL expired

2018-11-21 Thread xuming (JIRA)
[ 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 write a zero-entry-counter hfile which will never be TTL expired

2018-11-21 Thread xuming (JIRA)
[ 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) When Using FIFOCompactionPolicy, in some case, doing a compaction will write a initial hfile which will never be TTL expired

2018-11-21 Thread xuming (JIRA)
[ 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 empty hfile which will never be TTL expired

2018-11-21 Thread xuming (JIRA)
[ 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] [Created] (HBASE-21504) Using FIFOCompactionPolicy, a compact my write a empty HFile. And the HFile will never be expired

2018-11-21 Thread xuming (JIRA)
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