You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
PR #6820 added an experimental driver interface which allowed operators to disable logmon process spawning. This interface is only available to builtin drivers as it was not added to the driver capabilities functionality to allow for UX improvements and modifications to the interface.
In some cases, cluster operators would like to disable spawning logmon processes to avoid this additional overhead where the functionality it delivers is not required. It would be good therefore to discuss what changes we should make to the interface, if any, and what needs to be done in order to have this functionality, or equivalent exposed to external drivers.
The text was updated successfully, but these errors were encountered:
The `DisableLogCollection` capability was introduced as an experimental
interface for the Docker driver in 0.10.4. The interface has been stable and
allowing third-party task drivers the same capability would be useful for those
drivers that don't need the additional overhead of logmon.
This PR only makes the capability public. It doesn't yet add it to the
configuration options for the other internal drivers.
Fixes: #14636#15686
PR #6820 added an experimental driver interface which allowed operators to disable logmon process spawning. This interface is only available to builtin drivers as it was not added to the driver capabilities functionality to allow for UX improvements and modifications to the interface.
In some cases, cluster operators would like to disable spawning logmon processes to avoid this additional overhead where the functionality it delivers is not required. It would be good therefore to discuss what changes we should make to the interface, if any, and what needs to be done in order to have this functionality, or equivalent exposed to external drivers.
The text was updated successfully, but these errors were encountered: