[GitHub] [pulsar-client-go] merlimat commented on issue #221: Auto update the client to handle changes in number of partitions

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

merlimat commented on issue #221: Auto update the client to handle changes in number of partitions
URL: https://github.com/apache/pulsar-client-go/pull/221#issuecomment-613689417
 
 
   Yes, I was trying to avoid getting the extra mutex on the write path, though I think it shouldn't be too bad. 
   
   > when multiple threads are waiting on a lock. In what order are the locks released? FIFO? 
   
   I haven't really seen it specified, though a mutex always should include some sort of queuing for fairness. I'm not worried about that aspect. Also, the thread that updates the list of producers is not "critical" in the sense that it only needs to get executed eventually, with no hard time bound.

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