Details
-
Wish
-
Status: Open
-
Trivial
-
Resolution: Unresolved
-
None
-
None
-
None
Description
We're using /state.json for service discovery in our environment. Our mesas-consul bridge reads /state.json from current leader and then parses it to register all running tasks in Consul.
When using Spark framework it generates a lot of tasks, which all goes to the /state.json file as finished. The file itself can grow very large in couple days of work.
Is there any way to get only running tasks from mesos leader right now?
If there's not, can you add such possibility?
Or maybe you'll suggest using different approach for service discovery?