@tommy xiao For MESOS-3709 My draft work located in https://github.com/haosdent/mesos/commit/bac5ff1e8147517bd75f04719ea1dbcba97c8e67, while still have rest codes to refactor.
On Mon, Dec 14, 2015 at 2:05 PM, tommy xiao <[email protected]> wrote: > https://issues.apache.org/jira/browse/MESOS-3709 > > prefer moduler interface for external containerizer > > 2015-12-12 6:36 GMT+08:00 Joseph Wu <[email protected]>: > >> Hello All, >> >> As part of the work on managing the logs for executors and tasks, we're >> introducing a "ContainerLogger" module. This module will allow the >> stdout/stderr of executors and tasks to be managed or redirected. >> (Existing executor/task logs are written to plain files.) For example: >> >> - The module would make it trivial to truncate logs to a maximum >> size. Or to rotate the logs. >> - A module could redirect logs into an aggregation service, like >> syslog or journald; or to external logging, like LogStash or Splunk. >> >> See the epic for more details: >> https://issues.apache.org/jira/browse/MESOS-4086 >> >> For the MVP, we will support the Mesos and Docker containerizers. For >> the external containerizer, we plan to exit if an agent is started with >> both the external containerizer and the new ContainerLogger module. i.e. >> >> mesos-slave.sh --containerizers="mesos,external" >> --container_logger="some_custom_logger" >> >> Is there anyone, using the external containerizer, that would not prefer >> this behavior? >> >> Thanks, >> ~Joseph >> > > > > -- > Deshi Xiao > Twitter: xds2000 > E-mail: xiaods(AT)gmail.com > -- Best Regards, Haosdent Huang
