https://community.cloudera.com/t5/Support-Questions/RECEIVED-SIGNAL-15-SIGTERM/m-p/48965#M56308 <P>Is that log snippet from the AM or task logs? &nbsp;Have you checked the other? &nbsp;I have seen this message on the AM log side when something has terminated a task and the task log contains the detail as to why.</P><P>&nbsp;</P><P>Is pre-emption enabled? &nbsp;This message will be received, on the AM side, when tasks are killed by YARN when pre-emption kicks in. &nbsp;Pre-emption works on the container level and there is always the risk that an AM container is killed in the process. &nbsp;You could run the driver on the local client, --deploy-mode client, you launch from if you aren't already.</P><P>&nbsp;</P><P>Turn up the logging to DEBUG. &nbsp;Either in the Spark Gateway or by passing your own log4j.properties to the application.</P><P>&nbsp;</P><P>Also check if <SPAN>spark.dynamicAllocation.enabled is on as I have seen sigterm 15 messages when it trims down the containers. &nbsp;Cloudera also does not recommend having it turned on.</SPAN></P> Tue, 03 Jan 2017 00:41:43 GMT mbigelow 2017-01-03T00:41:43Z