[jira] [Updated] (HBASE-24781) [Replication] When execute shell cmd "disable_peer peerId" and "enable_peer peerId"，the master web UI show a wrong number of SizeOfLogQueue

[ https://issues.apache.org/jira/browse/HBASE-24781?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] leizhang updated HBASE-24781: - Summary: [Replication] When execute shell cmd "disable_peer peerId" and "enable_peer peerId"，the

[jira] [Updated] (HBASE-24781) [Replication] When execute shell cmd "disable_peer peerId"，the master web UI show a wrong number of SizeOfLogQueue

[ https://issues.apache.org/jira/browse/HBASE-24781?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] leizhang updated HBASE-24781: - Description:   Supposed that we have an peer with id 1,  when execute shell cmd disable_peer  '1'  and

[jira] [Updated] (HBASE-24781) [Replication] When execute shell cmd "disable_peer peerId"，the master web UI show a wrong number of SizeOfLogQueue

[ https://issues.apache.org/jira/browse/HBASE-24781?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] leizhang updated HBASE-24781: - Description:   Supposed that we have an peer with id 1,  when execute shell cmd disable_peer  '1'  and

[jira] [Updated] (HBASE-24781) [Replication] When execute shell cmd "disable_peer peerId"，the master web UI show a wrong number of SizeOfLogQueue

[ https://issues.apache.org/jira/browse/HBASE-24781?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] leizhang updated HBASE-24781: - Description:   Supposed that we have an peer with id 1,  when execute shell cmd disable_peer  '1' ,

[jira] [Issue Comment Deleted] (HBASE-24781) [Replication] When execute shell cmd "disable_peer peerId"，the master web UI show a wrong number of SizeOfLogQueue

[ https://issues.apache.org/jira/browse/HBASE-24781?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] leizhang updated HBASE-24781: - Comment: was deleted (was: h1. ReplicationSource do not update metrics after refresh) > [Replication]

[jira] [Updated] (HBASE-24781) [Replication] When execute shell cmd "disable_peer peerId"，the master web UI show a wrong number of SizeOfLogQueue

[ https://issues.apache.org/jira/browse/HBASE-24781?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] leizhang updated HBASE-24781: - Description:   Supposed that we have an peer with id 1,  when execute shell cmd disable_peer  '1' ,

[jira] [Commented] (HBASE-24781) [Replication] When execute shell cmd "disable_peer peerId"，the master web UI show a wrong number of SizeOfLogQueue

[ https://issues.apache.org/jira/browse/HBASE-24781?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17166934#comment-17166934 ] leizhang commented on HBASE-24781: -- h1. ReplicationSource do not update metrics after refresh >

[jira] [Updated] (HBASE-24781) [Replication] When execute shell cmd "disable_peer peerId"，the master web UI show a wrong number of SizeOfLogQueue

[ https://issues.apache.org/jira/browse/HBASE-24781?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] leizhang updated HBASE-24781: - Description:   Supposed that we have an peer with id 1,  when execute shell cmd disable_peer  '1' ,

[jira] [Updated] (HBASE-24781) [Replication] When execute shell cmd "disable_peer peerId"，the master web UI show a wrong number of SizeOfLogQueue

[ https://issues.apache.org/jira/browse/HBASE-24781?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] leizhang updated HBASE-24781: - Description:   Supposed that we have an peer with id 1,  when execute shell cmd disable_peer  '1' ,

[jira] [Updated] (HBASE-24781) [Replication] When execute shell cmd "disable_peer peerId"，the master web UI show a wrong number of SizeOfLogQueue

[ https://issues.apache.org/jira/browse/HBASE-24781?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] leizhang updated HBASE-24781: - Description:   Supposed that we have an peer with id 1,  when execute shell cmd disable_peer  '1' ,

[jira] [Updated] (HBASE-24781) [Replication] When execute shell cmd "disable_peer peerId"，the master web UI show a wrong number of SizeOfLogQueue

[ https://issues.apache.org/jira/browse/HBASE-24781?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] leizhang updated HBASE-24781: - Description:   Supposed that we have an peer with id 1,  when execute shell cmd disable_peer  '1' ,

[jira] [Updated] (HBASE-24781) [Replication] When execute shell cmd "disable_peer peerId"，the master web UI show a wrong number of SizeOfLogQueue

[ https://issues.apache.org/jira/browse/HBASE-24781?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] leizhang updated HBASE-24781: - Description:   Supposed that we have an peer with id 1,  when execute shell cmd disable_peer  '1' ,

[jira] [Updated] (HBASE-24781) [Replication] When execute shell cmd "disable_peer peerId"，the master web UI show a wrong number of SizeOfLogQueue

[ https://issues.apache.org/jira/browse/HBASE-24781?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] leizhang updated HBASE-24781: - Description:   Supposed that we have an peer with id 1,  when execute shell cmd disable_peer  '1' ,

[jira] [Updated] (HBASE-24781) [Replication] When execute shell cmd "disable_peer peerId"，the master web UI show a wrong number of SizeOfLogQueue

[ https://issues.apache.org/jira/browse/HBASE-24781?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] leizhang updated HBASE-24781: - Description:   Supposed that we have an peer with id 1,  when execute shell cmd disable_peer  '1' ,

[jira] [Updated] (HBASE-24781) [Replication] When execute shell cmd "disable_peer peerId"，the master web UI show a wrong number of SizeOfLogQueue

[ https://issues.apache.org/jira/browse/HBASE-24781?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] leizhang updated HBASE-24781: - Summary: [Replication] When execute shell cmd "disable_peer peerId"，the master web UI show a wrong

[jira] [Updated] (HBASE-24781) when execute shell cmd "disable_peer peerId"，the master web UI show a wrong number of SizeOfLogQueue

[ https://issues.apache.org/jira/browse/HBASE-24781?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] leizhang updated HBASE-24781: - Description:   Supposed that we have an peer with id 1,  when execute shell cmd disable_peer  '1' ,

[jira] [Updated] (HBASE-24781) when execute shell cmd "disable_peer peerId"，the master web UI show a wrong number of SizeOfLogQueue

[ https://issues.apache.org/jira/browse/HBASE-24781?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] leizhang updated HBASE-24781: - Description:   Supposed that we have an peer with id 1,  when execute shell cmd disable_peer  '1' ,

[jira] [Updated] (HBASE-24781) when execute shell cmd "disable_peer peerId"，the master web UI show a wrong number of SizeOfLogQueue

[ https://issues.apache.org/jira/browse/HBASE-24781?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] leizhang updated HBASE-24781: - Description:   Supposed that we have an source peer with id 1,  when execute shell cmd disable_peer 

[jira] [Created] (HBASE-24781) when execute shell cmd "disable_peer peerId"，the master web UI show a wrong number of SizeOfLogQueue

leizhang created HBASE-24781: Summary: when execute shell cmd "disable_peer peerId"，the master web UI show a wrong number of SizeOfLogQueue Key: HBASE-24781 URL: https://issues.apache.org/jira/browse/HBASE-24781

[jira] [Issue Comment Deleted] (HBASE-22620) When a cluster open replication,regionserver will not clean up the walLog references on zk due to no wal entry need to be replicated

[ https://issues.apache.org/jira/browse/HBASE-22620?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] leizhang updated HBASE-22620: - Comment: was deleted (was: I think this problem still exist in Hbase2.x , when i use Hbase2.2.5 , I

[jira] [Commented] (HBASE-22620) When a cluster open replication,regionserver will not clean up the walLog references on zk due to no wal entry need to be replicated

[ https://issues.apache.org/jira/browse/HBASE-22620?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17166100#comment-17166100 ] leizhang commented on HBASE-22620: -- I think this problem still exist in Hbase2.x , when i use

[jira] [Updated] (HBASE-22620) When a cluster open replication,regionserver will not clean up the walLog references on zk due to no wal entry need to be replicated

[ https://issues.apache.org/jira/browse/HBASE-22620?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] leizhang updated HBASE-22620: - Affects Version/s: (was: 1.2.4) 2.2.5 > When a cluster open

[jira] [Commented] (HBASE-22620) When a cluster open replication,regionserver will not clean up the walLog references on zk due to no wal entry need to be replicated

[ https://issues.apache.org/jira/browse/HBASE-22620?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16876588#comment-16876588 ] leizhang commented on HBASE-22620: -- {code:java} //代码占位符 WALEntryBatch entryBatch =

[jira] [Updated] (HBASE-22620) When a cluster open replication,regionserver will not clean up the walLog references on zk due to no wal entry need to be replicated

[ https://issues.apache.org/jira/browse/HBASE-22620?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] leizhang updated HBASE-22620: - Affects Version/s: 2.1.0 1.4.8 > When a cluster open replication,regionserver

[jira] [Updated] (HBASE-22620) When a cluster open replication,regionserver will not clean up the walLog references on zk due to no wal entry need to be replicated

[ https://issues.apache.org/jira/browse/HBASE-22620?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] leizhang updated HBASE-22620: - Fix Version/s: (was: 2.1.0) > When a cluster open replication,regionserver will not clean up the

[jira] [Commented] (HBASE-22620) When a cluster open replication,regionserver will not clean up the walLog references on zk due to no wal entry need to be replicated

[ https://issues.apache.org/jira/browse/HBASE-22620?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16874710#comment-16874710 ] leizhang commented on HBASE-22620: -- not only the pressure on zk.consider when there is a large amount

[jira] [Reopened] (HBASE-22620) When a cluster open replication,regionserver will not clean up the walLog references on zk due to no wal entry need to be replicated

[ https://issues.apache.org/jira/browse/HBASE-22620?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] leizhang reopened HBASE-22620: -- > When a cluster open replication,regionserver will not clean up the walLog > references on zk due to no

[jira] [Issue Comment Deleted] (HBASE-22620) When a cluster open replication,regionserver will not clean up the walLog references on zk due to no wal entry need to be replicated

[ https://issues.apache.org/jira/browse/HBASE-22620?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] leizhang updated HBASE-22620: - Comment: was deleted (was: thank you very much !  I check the  source code of Hbase2.1.0 ，and find the 

[jira] [Resolved] (HBASE-22620) When a cluster open replication,regionserver will not clean up the walLog references on zk due to no wal entry need to be replicated

[ https://issues.apache.org/jira/browse/HBASE-22620?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] leizhang resolved HBASE-22620. -- Resolution: Fixed Fix Version/s: 2.1.0 > When a cluster open replication,regionserver will not

[jira] [Commented] (HBASE-22620) When a cluster open replication,regionserver will not clean up the walLog references on zk due to no wal entry need to be replicated

[ https://issues.apache.org/jira/browse/HBASE-22620?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16874063#comment-16874063 ] leizhang commented on HBASE-22620: -- thank you very much !  I check the  source code of Hbase2.1.0 ，and

[jira] [Updated] (HBASE-22620) When a cluster open replication,regionserver will not clean up the walLog references on zk due to no wal entry need to be replicated

[ https://issues.apache.org/jira/browse/HBASE-22620?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] leizhang updated HBASE-22620: - Affects Version/s: (was: 2.0.3) > When a cluster open replication,regionserver will not clean up

[jira] [Updated] (HBASE-22620) When a cluster open replication,regionserver will not clean up the walLog references on zk due to no wal entry need to be replicated

[ https://issues.apache.org/jira/browse/HBASE-22620?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] leizhang updated HBASE-22620: - Affects Version/s: 1.2.4 > When a cluster open replication,regionserver will not clean up the walLog >

[jira] [Commented] (HBASE-22620) When a cluster open replication,regionserver will not clean up the walLog references on zk due to no wal entry need to be replicated

[ https://issues.apache.org/jira/browse/HBASE-22620?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16873771#comment-16873771 ] leizhang commented on HBASE-22620: -- Yesterday， I found the Hbase 1.2.4 also exists the same problem >

[jira] [Comment Edited] (HBASE-22620) When a cluster open replication,regionserver will not clean up the walLog references on zk due to no wal entry need to be replicated

[ https://issues.apache.org/jira/browse/HBASE-22620?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16873771#comment-16873771 ] leizhang edited comment on HBASE-22620 at 6/27/19 2:41 AM: --- Yesterday，when I

[jira] [Commented] (HBASE-22620) When a cluster open replication,regionserver will not clean up the walLog references on zk due to no wal entry need to be replicated

[ https://issues.apache.org/jira/browse/HBASE-22620?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16873770#comment-16873770 ] leizhang commented on HBASE-22620: -- Sorry ， I only check the code in Hbase 2.x， I find it is same as

[jira] [Updated] (HBASE-22620) When a cluster open replication,regionserver will not clean up the walLog references on zk due to no wal entry need to be replicated

[ https://issues.apache.org/jira/browse/HBASE-22620?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] leizhang updated HBASE-22620: - Description: When I open the replication feature on my hbase cluster (20 regionserver nodes) and added

[jira] [Updated] (HBASE-22620) When a cluster open replication,regionserver will not clean up the walLog references on zk due to no wal entry need to be replicated

[ https://issues.apache.org/jira/browse/HBASE-22620?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] leizhang updated HBASE-22620: - Issue Type: Bug (was: Improvement) > When a cluster open replication,regionserver will not clean up

[jira] [Commented] (HBASE-22620) When a cluster open replication,regionserver will not clean up the walLog references on zk due to no wal entry need to be replicated

[ https://issues.apache.org/jira/browse/HBASE-22620?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16873305#comment-16873305 ] leizhang commented on HBASE-22620: --   did you expect one just like this ?  Hbase version 1.4.9

[jira] [Comment Edited] (HBASE-22620) When a cluster open replication,regionserver will not clean up the walLog references on zk due to no wal entry need to be replicated

[ https://issues.apache.org/jira/browse/HBASE-22620?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16870944#comment-16870944 ] leizhang edited comment on HBASE-22620 at 6/26/19 8:12 AM: ---   I view the code

[jira] [Commented] (HBASE-22620) When a cluster open replication,regionserver will not clean up the walLog references on zk due to no wal entry need to be replicated

[ https://issues.apache.org/jira/browse/HBASE-22620?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16871929#comment-16871929 ] leizhang commented on HBASE-22620: -- I print the stack info of my regionserver, and find the thread

[jira] [Commented] (HBASE-22620) When a cluster open replication,regionserver will not clean up the walLog references on zk due to no wal entry need to be replicated

[ https://issues.apache.org/jira/browse/HBASE-22620?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16871918#comment-16871918 ] leizhang commented on HBASE-22620: -- "regionserver/x:16020.replicationSource,1-EventThread" #421

[jira] [Issue Comment Deleted] (HBASE-22620) When a cluster open replication,regionserver will not clean up the walLog references on zk due to no wal entry need to be replicated

[ https://issues.apache.org/jira/browse/HBASE-22620?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] leizhang updated HBASE-22620: - Comment: was deleted (was: "regionserver/x:16020.replicationSource,1-EventThread" #421 daemon

[jira] [Commented] (HBASE-22620) When a cluster open replication,regionserver will not clean up the walLog references on zk due to no wal entry need to be replicated

[ https://issues.apache.org/jira/browse/HBASE-22620?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16871917#comment-16871917 ] leizhang commented on HBASE-22620: -- I print the stack info of my regionserver，and find the thread

[jira] [Issue Comment Deleted] (HBASE-22620) When a cluster open replication,regionserver will not clean up the walLog references on zk due to no wal entry need to be replicated

[ https://issues.apache.org/jira/browse/HBASE-22620?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] leizhang updated HBASE-22620: - Comment: was deleted (was: I print the stack info of my regionserver，and find the thread blocking

[jira] [Commented] (HBASE-22620) When a cluster open replication,regionserver will not clean up the walLog references on zk due to no wal entry need to be replicated

[ https://issues.apache.org/jira/browse/HBASE-22620?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16870983#comment-16870983 ] leizhang commented on HBASE-22620: -- sorry , i mean logPositionAndCleanOldLogs() > When a cluster open

[jira] [Issue Comment Deleted] (HBASE-22620) When a cluster open replication,regionserver will not clean up the walLog references on zk due to no wal entry need to be replicated

[ https://issues.apache.org/jira/browse/HBASE-22620?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] leizhang updated HBASE-22620: - Comment: was deleted (was: Thank you, you can just  keep a replication cluster with no data write for

[jira] [Commented] (HBASE-22620) When a cluster open replication,regionserver will not clean up the walLog references on zk due to no wal entry need to be replicated

[ https://issues.apache.org/jira/browse/HBASE-22620?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16870944#comment-16870944 ] leizhang commented on HBASE-22620: --   I view the code that create the entryBatch,just as follows :

[jira] [Commented] (HBASE-22620) When a cluster open replication,regionserver will not clean up the walLog references on zk due to no wal entry need to be replicated

[ https://issues.apache.org/jira/browse/HBASE-22620?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16870875#comment-16870875 ] leizhang commented on HBASE-22620: -- Thank you, you can just  keep a replication cluster with no data

[jira] [Commented] (HBASE-22620) When a cluster open replication,regionserver will not clean up the walLog references on zk due to no wal entry need to be replicated

[ https://issues.apache.org/jira/browse/HBASE-22620?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16870854#comment-16870854 ] leizhang commented on HBASE-22620: -- {code:java} WALEntryBatch entryBatch = entryReader.take();

[jira] [Commented] (HBASE-22620) When a cluster open replication,regionserver will not clean up the walLog references on zk due to no wal entry need to be replicated

[ https://issues.apache.org/jira/browse/HBASE-22620?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16870837#comment-16870837 ] leizhang commented on HBASE-22620: -- No, we don't modify the logic in ReplicationSource Endpoint > When

[jira] [Comment Edited] (HBASE-22620) When a cluster open replication,regionserver will not clean up the walLog references on zk due to no wal entry need to be replicated

[ https://issues.apache.org/jira/browse/HBASE-22620?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16870829#comment-16870829 ] leizhang edited comment on HBASE-22620 at 6/24/19 6:12 AM: --- Thank you for

[jira] [Updated] (HBASE-22620) When a cluster open replication,regionserver will not clean up the walLog references on zk due to no wal entry need to be replicated

[ https://issues.apache.org/jira/browse/HBASE-22620?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] leizhang updated HBASE-22620: - Summary: When a cluster open replication,regionserver will not clean up the walLog references on zk due

[jira] [Updated] (HBASE-22620) When a cluster open replication,regionserver will not clean up the walLog references on zk due to no wal entry need to replicate

[ https://issues.apache.org/jira/browse/HBASE-22620?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] leizhang updated HBASE-22620: - Summary: When a cluster open replication,regionserver will not clean up the walLog references on zk due

[jira] [Commented] (HBASE-22620) When a cluster open replication,regionserver will not clean up the walLog references on zk due to no data to replicate

[ https://issues.apache.org/jira/browse/HBASE-22620?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16870829#comment-16870829 ] leizhang commented on HBASE-22620: -- Thank you for reply ,no data to replicate, I mean that no entry in

[jira] [Updated] (HBASE-22620) When a cluster open replication,regionserver will not clean up the walLog references on zk due to no data to replicate

[ https://issues.apache.org/jira/browse/HBASE-22620?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] leizhang updated HBASE-22620: - Description: When I open the replication feature on my hbase cluster (20 regionserver nodes), for

[jira] [Updated] (HBASE-22620) When a cluster open replication,regionserver will not clean up the walLog references on zk due to no data to replicate

[ https://issues.apache.org/jira/browse/HBASE-22620?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] leizhang updated HBASE-22620: - Description: When I open the replication feature on my hbase cluster (20 regionserver nodes), for

[jira] [Updated] (HBASE-22620) When a cluster open replication,regionserver will not clean up the walLog references on zk due to no data to replicate

[ https://issues.apache.org/jira/browse/HBASE-22620?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] leizhang updated HBASE-22620: - Issue Type: Improvement (was: Bug) > When a cluster open replication,regionserver will not clean up

[jira] [Resolved] (HBASE-22619) Hbase

[ https://issues.apache.org/jira/browse/HBASE-22619?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] leizhang resolved HBASE-22619. -- Resolution: Not A Bug > Hbase > - > > Key: HBASE-22619 > URL:

[jira] [Updated] (HBASE-22620) When a cluster open replication,regionserver will not clean up the walLog references on zk due to no data to replicate

[ https://issues.apache.org/jira/browse/HBASE-22620?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] leizhang updated HBASE-22620: - Summary: When a cluster open replication,regionserver will not clean up the walLog references on zk due

[jira] [Created] (HBASE-22620) When a cluster open replication,regionserver will not clean the walLog reference on zk due to no data to replicate

leizhang created HBASE-22620: Summary: When a cluster open replication,regionserver will not clean the walLog reference on zk due to no data to replicate Key: HBASE-22620 URL:

[jira] [Created] (HBASE-22619) Hbase

leizhang created HBASE-22619: Summary: Hbase Key: HBASE-22619 URL: https://issues.apache.org/jira/browse/HBASE-22619 Project: HBase Issue Type: Bug Reporter: leizhang -- This