Defunct processes continue on the CloudPoint host
The CloudPoint on-host agent container might produce defunct process (mount.ntfs) after the indexing job on the Windows host is complete. Number of defunct processes depends on the number of supported file systems on the host. If the host contains 4 file systems, the number of defunct process increases by 4. This function has no functional effect on the indexing job but gradually, the defunct processes fill the system process ID table.
Workaround:
The defunct processes consume an entry in the process table. However, this process doesn't hold any system resources, such as CPU cycles or memory. To resolve this issue, restart the on-host agent container. Use the following command:
docker restart <container_name>