This is for the REST API, and is often caused by the the UI still being open while the cluster was restarted.
The UI attempts to load the details for the now outdated jobs.
Simply reloading the UI resolves this issue most of the time.
On 05.06.2018 21:57, Hao Sun wrote:
I see a lot of errors because of a job is not found. Can I control this by config?Thanks