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 2021/12/13 15:35:43 UTC

[GitHub] [pulsar] thiagohernandes edited a comment on issue #13154: Consumer subscription type - behavior not working properly

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


   
   <img width="826" alt="pulsar-subscription-types" src="https://user-images.githubusercontent.com/2352110/145841258-f033f95c-38d6-4fa4-9712-58725571cd0f.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.
   


-- 
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: commits-unsubscribe@pulsar.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org