If you recently upgraded to DC/OS 1.10 or configured
MESOS_CGROUPS_ENABLE_CFS=true in your Mesos agent configuration, you may see slow-running Docker applications or slow deployments.
When using Apache Mesos, you can choose to use either CPU shares or strict CPU limitations. If you use CPU shares, your task can consume more CPU cycles than initially configured in your Marathon app definition, if your host system has free CPU cycles. If you are using strict CPU limitations, your task can only consume a maximum of CPU time based on your Marathon configuration.
The default Mesos configuration uses CPU shares. CFS (Completely Fair Scheduler) strict CPU limitation was introduced as a default in DC/OS a while ago, but until recently this configuration is only respected by the Mesos executor and not by the Docker executor. MESOS-6134 was fixed in the latest Mesos release, which is also included in DC/OS 1.10.
Your apps or deployments are likely running slowly because they require more CPU cycles than they are configured to consume.
If you have slow-running Docker applications or deployments due to DC/OS upgrade or configuring
MESOS_CGROUPS_ENABLE_CFS=true, increase the required CPU amount in your Marathon app definition. Change the
"cpus" property of your app definition to a higher value and test if this change solves your issues.
In special cases, you may want to change Mesos agent configuration to not use strict CFS CPU limitations. Consider this if the majority of your applications have a CPU peak during startup and a lower consumption afterwards, or you have other advanced CPU loads. You should only change the default behavior if you do not need strict CPU separation.
You will need to change the configurations for your Mesos (or DC/OS) installation by changing your Mesos agent configuration.
Note: If you are considering changing this configuration, consult the Mesos oversubscription documentation for additional considerations and configuration options.
Create or modify the file
/var/lib/dcos/mesos-slave-common on each agent node; Add or set the line
Restart the Mesos agent process with
sudo systemctl restart dcos-mesos-slave. Note, if this is done prior to installing the Mesos agent it will pick up the configuration automatically.
After restarting all of the Mesos agents, restart all tasks. Restarting the agent won’t cause the tasks to restart but they also won’t pick up the new setting so need to be restarted.