EntityGroupFSTimelineStore now depends on an RM being up and running; the configuration pointing to it. This is a new change, and impacts testing where you have historically been able to test without an RM running.
The sole purpose of the probe is to automatically determine if an app is running; it falls back to "unknown" if not. If the RM connection was optional, the "unknown" codepath could be called directly, relying on age of file as a metric of completion
- add a flag to disable RM connect
- skip automatically if RM not defined/set to 0.0.0.0
- disable retries on yarn client IPC; if it fails, tag app as unknown.