You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@pulsar.apache.org by GitBox <gi...@apache.org> on 2019/09/19 06:52:04 UTC

[GitHub] [pulsar] sydnash opened a new issue #5220: how to safely delete bookie of pulsar cluster?

sydnash opened a new issue #5220: how to safely delete bookie of pulsar cluster? 
URL: https://github.com/apache/pulsar/issues/5220
 
 
   **Describe the bug**
   I have a pulsar cluster with four bookie, and ledger set like this:
   ```
   # Number of bookies to use when creating a ledger
   managedLedgerDefaultEnsembleSize=2
   
   # Number of copies to store for each message
   managedLedgerDefaultWriteQuorum=2
   
   # Number of guaranteed copies (acks to wait before write is complete)
   managedLedgerDefaultAckQuorum=2
   ```
   when I publish some message to topic.(witch is already has subscriptions but no comsumer)
   I close tow of the bookie and run the follow command which wait until the closed bookie's ledger is re-replicated to other bokie.(I do this step one by one)
   ```
       ./bookkeeper shell decommissionbookie  --bookieid closedbookieip:3181
   ```
   after that  i couldn't  receive message on it any more, but i can produce to it.
   
   the stats of topic like this:
   ```
   {
     "msgRateIn" : 0.0,
     "msgThroughputIn" : 0.0,
     "msgRateOut" : 0.0,
     "msgThroughputOut" : 0.0,
     "averageMsgSize" : 0.0,
     "storageSize" : 318091591,
     "publishers" : [ ],
     "subscriptions" : {
       "subscription-1" : {
         "msgRateOut" : 0.0,
         "msgThroughputOut" : 0.0,
         "msgRateRedeliver" : 0.0,
         "msgBacklog" : 2379,
         "blockedSubscriptionOnUnackedMsgs" : false,
         "msgDelayed" : 0,
         "unackedMessages" : 0,
         "type" : "Exclusive",
         "msgRateExpired" : 0.0,
         "consumers" : [ ],
         "isReplicated" : false
       }
     },
     "replication" : { },
     "deduplicationStatus" : "Disabled"
   }
   ```
   
   **To Reproduce**
   Steps to reproduce the behavior:
   1. start a pulsar with four bookie
   2. publish message to topic witch has subscription .
   3. close the a bookie and run `./bookkeeper shell decommissionbookie  --bookieid  closedbookieip:3181` , then wait it report success message.
   4. delete data of the bookie, and then restart the bookie.
   5. repeat 3-4 one all bookie.
   
   **Expected behavior**
   I want i can receive message after the upon steps.
   
   **Screenshots**
   If applicable, add screenshots to help explain your problem.
   
   **Desktop (please complete the following information):**
    - OS:  linux centos 
   
   
   

----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
users@infra.apache.org


With regards,
Apache Git Services