thiagohernandes edited a comment on issue #13154:
URL: https://github.com/apache/pulsar/issues/13154#issuecomment-992598827


   ![Captura de tela de 2021-12-13 
12-39-45](https://user-images.githubusercontent.com/2352110/145842346-f1a04c84-3b09-4ec8-8f01-39200f5783d8.png)
   
   > > > @thiagohernandes Currently, the "exclusive" only works on same 
`subscritpionName` :)
   > > 
   > > 
   > > Yes u're correctly!! But the behavior is wrong when a second, .. n.... 
consumers try to connect. Above example illustrate that.
   > 
   > I don't think so. If you want the exclusive behavior, you can use the same 
consumer name.
   
   Why don't think? It's so easy to see that behavior on **exclusive** case. If 
it is exclusive type, **no more one can connect in that**. Shared, everyone can 
connect. Key based every configured subscriber. Failover the reserve instance 
keep waiting a fail.
   
   In my example, the second consumer (consumer2) can connect and receive 
messages! At the scenery, should or not emit an exception. But, it's true and 
necessary the second consumer shouldn't receive any message.
   


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

To unsubscribe, e-mail: [email protected]

For queries about this service, please contact Infrastructure at:
[email protected]


Reply via email to