2020-08-06 14:35:45 UTC - Pramiti Guha: @Pramiti Guha has joined the channel ---- 2020-08-06 14:40:21 UTC - Pramiti Guha: Hello everyone - need help on this error I am facing while developing a springboot consumer client for pulsar - I am using 'Exclusive' subscription type and when I deploy this application to my openshift kubernetes cluster with min replica 2 - I keep receiving an error PulsarClientException$ConsumerBusyException in one of the pods - can anyone please help me identifying if there's something wrong with my design or is there a way to circumvent this error? ---- 2020-08-06 16:25:15 UTC - Addison Higham: @Pramiti Guha `exclusive` subscriptions can only have a single consumer, so you either need to make sure each node is using a different subscription name (if you want them both to receive their own copy of the message) OR use a different subscription type. `Failover` is good if you need to process in order and just want to minimize latency if one consumer dies. `shared` is more like a work queue ---- 2020-08-06 16:57:12 UTC - Pramiti Guha: Thanks for suggesting the work around @Addison Higham -just curious - so it follows that a consumer application with sub type Exclusive cannot scale up even with an increase in load? ---- 2020-08-06 17:03:48 UTC - Addison Higham: A broker can still serve lots of traffic into a single subscription, but if it is more than a single consumer can handle you have a few options: - use a shared subscription, this lets you have multiple consumers connected, but you loose some ordering guarantees - use a key_shared subscription if you need order, but can segment your data by some key, then a key_shared subscription will make sure that data with the same key always arrives to the same consumer - use either multiple topics or a partitioned topic, this is similar idea to a `key_shared` subscription, if you need order, then partitioning your data is how you can scale up +1 : Pramiti Guha ---- 2020-08-06 17:49:45 UTC - Pramiti Guha: got it...thanks a ton! ----
