You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@trafficcontrol.apache.org by GitBox <gi...@apache.org> on 2019/11/20 18:16:12 UTC

[GitHub] [trafficcontrol] rob05c commented on issue #1739: Traffic Monitor CRConfig and monitoring.json polls aren't synchronized

rob05c commented on issue #1739: Traffic Monitor CRConfig and monitoring.json polls aren't synchronized
URL: https://github.com/apache/trafficcontrol/issues/1739#issuecomment-556198180
 
 
   No, this isn't fixed. It's still a dangerous race condition in the Monitor.
   
   The related issue https://github.com/apache/trafficcontrol/issues/1738 was fixed. That synchronizes the snapshots themselves in Traffic Ops.
   
   But, even though the Snapshots are created in Traffic Ops at the same time, the Monitor has 2 separate polling threads, which aren't synchronized.
   
   Therefore, for example, if a Profile is renamed, if the Monitor might poll the CRConfig, which has the new name, but it might be several seconds before the Monitor polls the Monitoring.json, which has the polling locations. During that time, the Monitor will be unable to find the polling location URL for the cache with the renamed Profile, and will be unable to poll that cache.
   
   The Monitor's internal polls for those 2 objects need to happen at the same time, to fix this race condition.

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