You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@hbase.apache.org by "Biju Nair (JIRA)" <ji...@apache.org> on 2015/09/11 20:59:45 UTC

[jira] [Created] (HBASE-14412) remove_peer of replication peers with hyphens in name doesn't remove ZK entries

Biju Nair created HBASE-14412:
---------------------------------

             Summary: remove_peer of replication peers with hyphens in name doesn't remove ZK entries
                 Key: HBASE-14412
                 URL: https://issues.apache.org/jira/browse/HBASE-14412
             Project: HBase
          Issue Type: Bug
          Components: Replication
            Reporter: Biju Nair
            Priority: Minor


- Created replication peer POB3-HBASE-LL-A. By mistake used hyphens in the replication peer name.
- Did {{remove_peer POB3-HBASE-LL-A}}
- Created a new peer POB3_HBASE_LL_A
- Verified zk for entries
{{
ls /hbase/replication/peers 
[POB3_HBASE_LL_A] 

ls /hbase/replication/rs 
[r2n14,60200,1441836473749, r1n16,60200,1441836441250, r1n14,60200,1441836352689, r3n15,60200,1441836547607, r2n15,60200,1441836551992, r3n14,60200,1441836230275, r1n15,60200,1441836355145] 

ls /hbase/replication/rs/r2n14,60200,1441836473749 
[POB3_HBASE_LL_A, POB3-HBASE-LL-A] 

ls /hbase/replication/rs/r2n14,60200,1441836473749/POB3-HBASE-LL-A 
[r2n14%2C60200%2C1441836473749.1441865284930, r2n14%2C60200%2C1441836473749.1441847284451, r2n14%2C60200%2C1441836473749.1441890379203, r2n14%2C60200%2C1441836473749.1441890384725, r2n14%2C60200%2C1441836473749.1441840084237, r2n14%2C60200%2C1441836473749.1441876085231, r2n14%2C60200%2C1441836473749.1441890367559, r2n14%2C60200%2C1441836473749.1441883285466, r2n14%2C60200%2C1441836473749.1441890370829, r2n14%2C60200%2C1441836473749.1441879685329, r2n14%2C60200%2C1441836473749.1441890382514, r2n14%2C60200%2C1441836473749.1441890381514, r2n14%2C60200%2C1441836473749.1441890380286, r2n14%2C60200%2C1441836473749.1441890378164, r2n14%2C60200%2C1441836473749.1441872485132, r2n14%2C60200%2C1441836473749.1441868885039, r2n14%2C60200%2C1441836473749.1441890374603, r2n14%2C60200%2C1441836473749.1441890377072, r2n14%2C60200%2C1441836473749.1441858084739, r2n14%2C60200%2C1441836473749.1441890369005, r2n14%2C60200%2C1441836473749.1441850884549, r2n14%2C60200%2C1441836473749.1441886885548, r2n14%2C60200%2C1441836473749.1441890372063, r2n14%2C60200%2C1441836473749.1441890375866, r2n14%2C60200%2C1441836473749.1441890373369, r2n14%2C60200%2C1441836473749.1441890383608, r2n14%2C60200%2C1441836473749.1441836483297, r2n14%2C60200%2C1441836473749.1441843684350, r2n14%2C60200%2C1441836473749.1441890366118, r2n14%2C60200%2C1441836473749.1441861684834, r2n14%2C60200%2C1441836473749.1441854484648] 
}}

Even though the peer got removed, there are still some ZK entries left which need to be cleaned.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)