Public signup for this instance is disabled. Go to our Self serve sign up page to request an account.
Share this issue
This is to make sure user is notified job finished after job is really done. This does increase client latency but can reduce some races during unregister like YARN-540
[Umbrella] RM Restart Phase 1: State storage and non-work-preserving recovery
MRAppMaster#shutDownJob shouldn't send job end notification before checking isLastRetry
RM may relaunch already KILLED / FAILED jobs after RM restarts
Race condition causing RM to potentially relaunch already unregistered AMs on RM restart