cshannon commented on PR #2796:
URL: https://github.com/apache/activemq/pull/2796#issuecomment-6688162819

   > Yes, startup and any scenario where lots of destinations are added or 
removed.
   > 
   > Fast ramp-up of connections to a new host (scale up or failover) or 
high-frequency add/remove and splitting contention with destination gc (IoT).
   
   For startup this is not a problem, but i am wondering if this would 
introduce any race condition scenarios with rapid creation/destruction of 
destinations that could cause the Usage tracking to be incorrect. I doubt it 
because adding/removing destinations is guarded by locks in the broker so the 
same destination should complete destruction before being re-added again but i 
suppose it's something to just think through. I also don't think the current 
copy on write list would prevent race conditions either so this seems fine


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


---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
For further information, visit: https://activemq.apache.org/contact


Reply via email to