As we all know, mesos will log the the stdout and stderr of any containers started as a task into the sandbox as plain text files, which is the work directory of the corresponding slave.
After running some tasks for a while, I found out that the stdout/stderr logs are never rotated and they’re filling up the slaves’ disk space. This is certainly not what I wanted.
Very luckily, mesos has supported log rotation for the containers’ stdout/stderr since 0.27.0 to address the shortcoming. But it’s not the default behaviour, you need to explicitly specify some parameters when launching the mesos slave to enable it. Here’re the steps:
Step 1: Put a json file containing the following content into anywhere of the machine but not /etc/mesos-slave/, in my case, I put it in /etc/ and name it as mesos-slave-modules.json.
The json file specifies the modules that we want to load, where to find the library and where to find the executable. In this case, I load the module “org_apache_mesos_LogrotateContainerLogger” from the “liblogrotate_container_logger.so” library and tell mesos that the launching binary is in “/usr/libexec/mesos”.
/usr/sbin/mesos-slave --container_logger=org_apache_mesos_LogrotateContainerLogger --modules=/etc/mesos-slave-modules.json
This will set the “modules” to point to the json file we created at step 1, and set the “container_logger” to the rotation logger’s name.
Please note that your old tasks won’t have log rotation immediately. You need to restart them to take effect, any new coming tasks created will have the log rotation.
mode nlink uid gid size mtime