[PR] Added ingress rate limit enabling for existing containers. [mesos]

["DevinLeamy (via GitHub)" <gi...@apache.org>]

DevinLeamy opened a new pull request, #482:
URL: https://github.com/apache/mesos/pull/482

   Previously, changes to the ingress HTB config, including ingress rate limiting and container isolation, could not be applied at runtime, to avoid droppping packets. This change introduces a flag `--ingress_isolatee_existing_containers` that enables these changes to be applied to existing containers. This allows migrations to ECN support (https://en.wikipedia.org/wiki/Explicit_Congestion_Notification) to be possible, without having to reboot hosts or restart containers.
   
   Previously the network/port_mapping isolator didn't set ingress rate limit for existing contaners without it in order to avoid dropping packets, because we thought that we will turn on ECN support without rebooting the hosts and thus restarting the containers.


-- 
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: reviews-unsubscribe@mesos.apache.org

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

Re: [PR] Added ingress rate limit enabling for existing containers. [mesos]

["bmahler (via GitHub)" <gi...@apache.org>]

bmahler merged PR #482:
URL: https://github.com/apache/mesos/pull/482


-- 
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: reviews-unsubscribe@mesos.apache.org

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