[GitHub] [pulsar] mkozioro commented on issue #8008: Can't send message due to PulsarClientException$TimeoutException when 1 zookeeper, bookie and broker are down

[GitBox <gi...@apache.org>]

mkozioro commented on issue #8008:
URL: https://github.com/apache/pulsar/issues/8008#issuecomment-688939321


   Hi @sijie 
   Do you know what can be wrong? We're using almost unchanged pulsar kubernetes chart on AKS, but this should be visible rather on any cloud. 
   Only important changes in helm values are:
       managedLedgerDefaultEnsembleSize: "3"
       managedLedgerDefaultWriteQuorum: "3"
       managedLedgerDefaultAckQuorum: "2"
   in broker configuration. We tested also with:
       managedLedgerDefaultEnsembleSize: "3"
       **managedLedgerDefaultWriteQuorum: "2"**
       managedLedgerDefaultAckQuorum: "2"
   
   But with no success.
   Terminating single pods of zookeepers, brokers, bookies, proxies seems to not cause problems. Problems seems to exist only when different types of pods exist on single node and we are calling kubectl drain <node>.
   


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