Github user jongyoul commented on the pull request:
https://github.com/apache/spark/pull/2126#issuecomment-53552876
@tgravescs ,
I've found the reason. :-)
YARN node manager(exactly?) chnages LOGNAME, USER to id which run
application while running applications. But mesos doesn't change yet. I'm
printing logs at the first of security manager. Here is System.getproperties,
System.getenv below. You can also find a USER and a LOGNAME, my id is also
"1001079" and yarn's id is "hdfs".
SLF4J: Class path contains multiple SLF4J bindings.
SLF4J: Found binding in
[jar:file:/tmp/mapred/hdfs/nm-local-dir/usercache/1001079/filecache/13/spark-assembly-1.0.3-SNAPSHOT-hadoop2.3.0-cdh5.0.1.jar!/org/slf4j/impl/StaticLoggerBinder.class]
SLF4J: Found binding in
[jar:file:/tmp/mapred/hdfs/nm-local-dir/usercache/1001079/filecache/14/spark-examples-1.0.3-SNAPSHOT-hadoop2.3.0-cdh5.0.1.jar!/org/slf4j/impl/StaticLoggerBinder.class]
SLF4J: See http://www.slf4j.org/codes.html#multiple_bindings for an
explanation.
SLF4J: Actual binding is of type [org.slf4j.impl.Log4jLoggerFactory]
14/08/27 19:26:33 INFO YarnSparkHadoopUtil: java.runtime.name -> Java(TM)
SE Runtime Environment
...
user.home -> /app/home/hdfs
...
user.name -> hdfs
...
SPARK_USER -> 1001079
...
HADOOP_CONF_DIR -> /app/hadoop-2.3.0-cdh5.0.1/conf
HADOOP_DATANODE_OPTS -> ...
SPARK_YARN_STAGING_DIR -> ...
HADOOP_NAMENODE_OPTS -> ...
SPARK_YARN_CACHE_FILES_TIME_STAMPS -> 1409135190565,1409135191296
NM_PORT -> 38930
LOGNAME -> 1001079
YARN_CONF_DIR -> /app/hadoop-2.3.0-cdh5.0.1/conf
...
SHELL -> /bin/bash
SPARK_YARN_CACHE_FILES -> ...
CLASSPATH -> ...
USER -> 1001079
HADOOP_HDFS_HOME -> /app/hadoop-2.3.0-cdh5.0.1
CONTAINER_ID -> container_1409105908837_0012_01_000002
HOME -> /home/
...
YARN_NICENESS -> 0
YARN_IDENT_STRING -> hdfs
HADOOP_MAPRED_HOME -> /app/hadoop-2.3.0-cdh5.0.1
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at [email protected] or file a JIRA ticket
with INFRA.
---
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
