TODO: Ensure running container cleanup, node connections shutdown and other terminations for reliability

[sukhman-sukh]

Current Scenario

Currently, Beast gracefully terminates only database connections. In the future, for better reliability, it should gracefully shut down and end all connections, maintaining proper data and process safety, ensuring no orphan node or process.

[kunrex]

Which Connections to Terminate?

cleanup.go contains

	// TODO: Add your specific cleanup tasks here
	// For example:
	// - Stop the scheduler (api.BeastScheduler.Stop())
	// - Stop worker queue (manager.Q - note: no Stop() method exists, may need to implement)
	// - Stop remote manager queue
	// - Close database connections (Done)
	// - Stop running containers
	// - Clean up temporary files
	// - Close network connections
	// - Stop background goroutines
	// - Store leaderboard cache and graph cache if leaderboard is frozen and competition not ended. and make sure to fill it abck on restart.

Implement cleanup on all above tasks or only specific ones?

[v1bh475u]

Yes. You have pretty much covered the requirements.