> when the executor is overwhelmed with tasks or execute() is called while >shutting down. I'm confounded as to why this would be an issue suddenly.
> Container container_e23_1466828114374_53316_01_000018 finished with >diagnostics set to Container failed, exitCode=-1000. Task >java.util.concurrent.ExecutorCompletionService$QueueingFuture@6c5f576 rejected from java.util.concurrent.ThreadPoolExecutor@9bf8295 Terminated, pool size = 0, active threads = 0, queued tasks = 0, completed tasks = 111 As always, this needs more info mostly from the yarn logs -applicationId <application>. It's not entirely clear whether this is happening in the NM or the task itself. The active threads = 0, suggests this might be related to pam_limits nproc, causing threads to exit without running. Did you reboot the system recently? Cheers, Gopal
