Github user tgravescs commented on a diff in the pull request:

    https://github.com/apache/spark/pull/95#discussion_r10361302
  
    --- Diff: docs/running-on-yarn.md ---
    @@ -82,35 +84,30 @@ For example:
             ./bin/spark-class org.apache.spark.deploy.yarn.Client \
               --jar 
examples/target/scala-{{site.SCALA_BINARY_VERSION}}/spark-examples-assembly-{{site.SPARK_VERSION}}.jar
 \
               --class org.apache.spark.examples.SparkPi \
    -          --args yarn-standalone \
    +          --args yarn-cluster \
               --num-workers 3 \
               --master-memory 4g \
               --worker-memory 2g \
               --worker-cores 1
     
    -    # Examine the output (replace $YARN_APP_ID in the following with the 
"application identifier" output by the previous command)
    -    # (Note: YARN_APP_LOGS_DIR is usually /tmp/logs or 
$HADOOP_HOME/logs/userlogs depending on the Hadoop version.)
    -    $ cat $YARN_APP_LOGS_DIR/$YARN_APP_ID/container*_000001/stdout
    -    Pi is roughly 3.13794
    -
    -The above starts a YARN Client programs which start the default 
Application Master. Then SparkPi will be run as a child thread of Application 
Master, YARN Client will  periodically polls the Application Master for status 
updates and displays them in the console. The client will exit once your 
application has finished running.
    +The above starts a YARN client program which starts the default 
Application Master. Then SparkPi will be run as a child thread of Application 
Master. The client will periodically poll the Application Master for status 
updates and display them in the console. The client will exit once your 
application has finished running.
    --- End diff --
    
    It might be nice to state that the output goes to the log files then they 
can see the section you added below for more details.


---
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 infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

Reply via email to