yarn-similar logs when starting up container

15/12/09 16:47:52 INFO yarn.ExecutorRunnable: Setting up executor with environment: Map(CLASSPATH -> {{PWD}}<CPS>{{PWD}}/__spark__.jar<CPS>$HADOOP_CONF_DIR<CPS>$HADOOP_COMMON_HOME/s
hare/hadoop/common/*<CPS>$HADOOP_COMMON_HOME/share/hadoop/common/lib/*<CPS>$HADOOP_HDFS_HOME/share/hadoop/hdfs/*<CPS>$HADOOP_HDFS_HOME/share/hadoop/hdfs/lib/*<CPS>$HADOOP_YARN_HOME/
share/hadoop/yarn/*<CPS>$HADOOP_YARN_HOME/share/hadoop/yarn/lib/*<CPS>$HADOOP_MAPRED_HOME/share/hadoop/mapreduce/*<CPS>$HADOOP_MAPRED_HOME/share/hadoop/mapreduce/lib/*, SPARK_LOG_UR
L_STDERR -> http://gzsw-11:8042/node/containerlogs/container_1441038159113_0018_01_000003/hadoop/stderr?start=0, SPARK_YARN_STAGING_DIR -> .sparkStaging/application_1441038159113_00
18, SPARK_YARN_CACHE_FILES_FILE_SIZES -> 157585209, SPARK_USER -> hadoop, SPARK_YARN_CACHE_FILES_VISIBILITIES -> PRIVATE, SPARK_YARN_MODE -> true, SPARK_YARN_CACHE_FILES_TIME_STAMPS
 -> 1449650858015, SPARK_LOG_URL_STDOUT -> http://gzsw-11:8042/node/containerlogs/container_1441038159113_0018_01_000003/hadoop/stdout?start=0, SPARK_YARN_CACHE_FILES -> hdfs://mycl
uster/user/hadoop/.sparkStaging/application_1441038159113_0018/spark-assembly-1.4.1-hadoop2.4.0.jar#__spark__.jar)

15/12/09 16:47:52 INFO yarn.ExecutorRunnable: Setting up executor with commands: List({{JAVA_HOME}}/bin/java, -server, -XX:OnOutOfMemoryError='kill %p', -Xms2048m, -Xmx2048m, '-Xlog
gc:~/spark-executor.gc', '-XX:+UseCMSCompactAtFullCollection', '-XX:CMSFullGCsBeforeCompaction=2', '-XX:CMSInitiatingOccupancyFraction=65', '-XX:+UseCMSInitiatingOccupancyOnly', '-X
X:PermSize=64m', '-XX:MaxPermSize=256m', '-XX:NewRatio=5', '-XX:+UseParNewGC', '-XX:+UseConcMarkSweepGC', '-XX:+PrintGCDateStamps', '-XX:+PrintGCDetails', '-XX:ParallelGCThreads=5',
 -Djava.io.tmpdir={{PWD}}/tmp, '-Dspark.master.ui.port=7102', '-Dspark.worker.ui.port=7105', '-Dspark.ui.port=7106', '-Dspark.driver.port=56894', -Dspark.yarn.app.container.log.dir=
<LOG_DIR>, org.apache.spark.executor.CoarseGrainedExecutorBackend, --driver-url, akka.tcp://sparkDriver@192.168.100.4:56894/user/CoarseGrainedScheduler, --executor-id, 2, --hostname
, gzsw-11, --cores, 2, --app-id, application_1441038159113_0018, --user-class-path, file:$PWD/__app__.jar, 1>, <LOG_DIR>/stdout, 2>, <LOG_DIR>/stderr)

   by one more checking ,that's one launched command for executor,and here one container will startup as executor says CoarseGrainedExecutorBackend,ie same jvm with container instead of spawning up new jvm process.