Description
The thermos observer relies on out-of-band communication from tasks to display state, which will prove problematic as disk isolation progresses.
Two options i can see, i'm sure there are more:
- remove the need for an observer altogether, present that data with text logs in the sandbox
- run an observer with each task, listening on an allocated port
Attachments
Issue Links
- is related to
-
AURORA-724 Support linking to sandboxes for other executors
- Open
- relates to
-
AURORA-1481 Thermos Observer Takes up to 150% CPU on default settings
- Open
-
AURORA-715 Retire GC Executor
- Resolved
-
AURORA-777 refactor observer so that task pages are generated statically from checkpoints
- Open