openclaw - 💡(How to fix) Fix High host load & slow responses caused by stale openclaw worker process accumulation [3 comments, 4 participants]

TL;DR

Implement a reliable mechanism for openclaw worker processes to self-terminate after completing their tasks to prevent accumulation and load average increase.

Guidance

• Investigate why openclaw worker processes are not exiting after completing their tasks, focusing on potential issues with task completion signals or process termination logic.
• Consider implementing a timeout or idle detection mechanism to automatically terminate worker processes after a certain period of inactivity (e.g., 15 minutes).
• Review the cleanup-zombies.py script to ensure it is effectively removing stale worker processes and consider increasing its frequency or integrating it into the worker process lifecycle.
• Analyze cron job frequencies and their impact on worker process accumulation, potentially adjusting job schedules to reduce the combined rate.

Example

No specific code example is provided due to the lack of detailed implementation information, but a generic approach might involve setting up a timeout or using a process manager that can automatically handle idle process termination.

Notes

The exact cause of the worker processes not self-terminating is unclear, and resolving this issue may require deeper investigation into the application's logic and potentially its dependencies or the environment in which it's running.

Recommendation

Apply a workaround by enhancing the cleanup-zombies.py script to run more frequently or integrating an automatic termination mechanism into the worker process lifecycle, as upgrading to a fixed version is not explicitly mentioned as an option in the provided context.