Details
Description
I have an executor that closes unknown file descriptors when it starts up:
2018/05/14 20:54:43.210293 util_linux.go:65: closing extraneous fd 126 (/srv/mesos/work/meta/slaves/30d57187-99b4-4e63-aba8-f425a80a6702-S8/resource_provider_registry/000008.log) 2018/05/14 20:54:43.210345 util_linux.go:47: unable to call fcntl() to get fd options for fd 3: errno bad file descriptor 2018/05/14 20:54:43.210385 util_linux.go:65: closing extraneous fd 321 (/srv/mesos/work/meta/slaves/30d57187-99b4-4e63-aba8-f425a80a6702-S8/resource_provider_registry/LOG) 2018/05/14 20:54:43.210438 util_linux.go:65: closing extraneous fd 322 (/srv/mesos/work/meta/slaves/30d57187-99b4-4e63-aba8-f425a80a6702-S8/resource_provider_registry/LOCK) 2018/05/14 20:54:43.210501 util_linux.go:65: closing extraneous fd 324 (/srv/mesos/work/meta/slaves/30d57187-99b4-4e63-aba8-f425a80a6702-S8/resource_provider_registry/MANIFEST-000006)
It is closing leveldb descriptors leaked by the resource provider manager registry in the agent.
Attachments
Issue Links
- is broken by
-
MESOS-8917 Agent leaking file descriptors into forked processes
- Resolved
- is caused by
-
MESOS-8917 Agent leaking file descriptors into forked processes
- Resolved