Paul Brett created MESOS-2517:
---------------------------------
Summary: Slave fails if network interface speed lower than
bandwidth cap
Key: MESOS-2517
URL: https://issues.apache.org/jira/browse/MESOS-2517
Project: Mesos
Issue Type: Bug
Components: isolation, slave
Affects Versions: 0.22.0
Reporter: Paul Brett
Priority: Minor
When network isolation is enabled, configuring a container egress limit higher
than the host interface will cause the slave to abort when it tries to create a
container.
e.g.
I0318 16:54:09.273154 61754 containerizer.cpp:100] Using isolation:
cgroups/cpu,cgroups/mem,network/port_mapping
I0318 16:54:09.311635 61754 port_mapping.cpp:890] Using eth0 as the public
interface
I0318 16:54:09.312491 61754 port_mapping.cpp:915] Using lo as the loopback
interface
Failed to create a containerizer: Could not create MesosContainerizer: Could
not create isolator network/port_mapping: The given egress traffic limit for
containers 38400000 Bytes/s is greater than the host link speed 12500000 Bytes/s
Slave Exit Status: 1
It is clear that this should not cause the slave to fail, however should we
(for example):
(1) allow the container to be created since the network might renegotiate at
any instant
(2) kill all the existing containers since we can no longer deliver the network
they expect
(3) leave the existing containers alone but refuse to create any new ones?
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
