Commits on Jun 10, 2017

1. allocator: Avoid assigning duplicate IPs during initialization …

   When the allocator starts up, there is a pass that "allocates" the
   existing tasks/nodes/services in the store. In fact, existing tasks are
   typically already allocated, and this is mostly populating local state
   to reflect which IPs are taken. However, if there are any tasks in the
   store which are brand new, or previously failed to allocated, these will
   actually receive new allocations.
   
   The problem is that allocation of new IPs is interspersed with updating
   local state with existing IPs. If a task, node, or service that needs an
   IP is processed before one that claims a specific IP, the IP claimed by
   the latter task be assigned.
   
   This change makes the allocator do two passes on initialization. First
   it handles objects that claim a specific IP, then it handles all other
   objects.
   
   Signed-off-by: Aaron Lehmann <aaron.lehmann@docker.com>

   

   aaronlehmann committed Jun 10, 2017
   Configuration menu

   • View commit details
   • Copy full SHA for 61483fb
   • Browse repository at this point

   Copy the full SHA

   61483fb View commit details

   Browse the repository at this point in the history