<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>question Container metrics do not match between spark UI and YARN resourcemanager UI in Archives of Support Questions (Read Only)</title>
    <link>https://community.cloudera.com/t5/Archives-of-Support-Questions/Container-metrics-do-not-match-between-spark-UI-and-YARN/m-p/217993#M81898</link>
    <description>&lt;P&gt;I am tuning a spark application and noticed there are discrepancies between the job's metrics shown on Spark's history server UI and YARN's resource manager UI. &lt;/P&gt;&lt;P&gt;I've specified the the following properties on my Zeppelin Notebook's spark interpreter:&lt;/P&gt;&lt;TABLE&gt;&lt;TBODY&gt;&lt;TR&gt;&lt;TD&gt;master&lt;/TD&gt;&lt;TD&gt;yarn-client&lt;/TD&gt;&lt;/TR&gt;&lt;TR&gt;&lt;TD&gt;spark.app.name&lt;/TD&gt;&lt;TD&gt;Zeppelin&lt;/TD&gt;&lt;/TR&gt;&lt;TR&gt;&lt;TD&gt;spark.cores.max&lt;/TD&gt;&lt;TD&gt;&lt;/TD&gt;&lt;/TR&gt;&lt;TR&gt;&lt;TD&gt;spark.driver.memory&lt;/TD&gt;&lt;TD&gt;3g&lt;/TD&gt;&lt;/TR&gt;&lt;TR&gt;&lt;TD&gt;spark.executor.cores&lt;/TD&gt;&lt;TD&gt;3&lt;/TD&gt;&lt;/TR&gt;&lt;TR&gt;&lt;TD&gt;spark.executor.instances&lt;/TD&gt;&lt;TD&gt;2&lt;/TD&gt;&lt;/TR&gt;&lt;TR&gt;&lt;TD&gt;spark.executor.memory&lt;/TD&gt;&lt;TD&gt;4g&lt;/TD&gt;&lt;/TR&gt;&lt;/TBODY&gt;&lt;/TABLE&gt;&lt;P&gt;When I look at the YARN ResourceManager UI I do not see evidence that the executor's containers are getting 3 cores each. I see that they each are using 1 v-core each. &lt;/P&gt;&lt;P&gt;Yet, when I check the Spark History Server... it describes each running executor has 3 cores and reflects all the properties I've specified.&lt;/P&gt;&lt;P&gt;What's up with this? Which of these should I be looking at?&lt;/P&gt;&lt;P&gt;YARN  3.1.0             Zeppelin  0.8.0             Spark2  2.3.1&lt;/P&gt;</description>
    <pubDate>Fri, 10 Aug 2018 01:02:21 GMT</pubDate>
    <dc:creator>matt_krueger</dc:creator>
    <dc:date>2018-08-10T01:02:21Z</dc:date>
    <item>
      <title>Container metrics do not match between spark UI and YARN resourcemanager UI</title>
      <link>https://community.cloudera.com/t5/Archives-of-Support-Questions/Container-metrics-do-not-match-between-spark-UI-and-YARN/m-p/217993#M81898</link>
      <description>&lt;P&gt;I am tuning a spark application and noticed there are discrepancies between the job's metrics shown on Spark's history server UI and YARN's resource manager UI. &lt;/P&gt;&lt;P&gt;I've specified the the following properties on my Zeppelin Notebook's spark interpreter:&lt;/P&gt;&lt;TABLE&gt;&lt;TBODY&gt;&lt;TR&gt;&lt;TD&gt;master&lt;/TD&gt;&lt;TD&gt;yarn-client&lt;/TD&gt;&lt;/TR&gt;&lt;TR&gt;&lt;TD&gt;spark.app.name&lt;/TD&gt;&lt;TD&gt;Zeppelin&lt;/TD&gt;&lt;/TR&gt;&lt;TR&gt;&lt;TD&gt;spark.cores.max&lt;/TD&gt;&lt;TD&gt;&lt;/TD&gt;&lt;/TR&gt;&lt;TR&gt;&lt;TD&gt;spark.driver.memory&lt;/TD&gt;&lt;TD&gt;3g&lt;/TD&gt;&lt;/TR&gt;&lt;TR&gt;&lt;TD&gt;spark.executor.cores&lt;/TD&gt;&lt;TD&gt;3&lt;/TD&gt;&lt;/TR&gt;&lt;TR&gt;&lt;TD&gt;spark.executor.instances&lt;/TD&gt;&lt;TD&gt;2&lt;/TD&gt;&lt;/TR&gt;&lt;TR&gt;&lt;TD&gt;spark.executor.memory&lt;/TD&gt;&lt;TD&gt;4g&lt;/TD&gt;&lt;/TR&gt;&lt;/TBODY&gt;&lt;/TABLE&gt;&lt;P&gt;When I look at the YARN ResourceManager UI I do not see evidence that the executor's containers are getting 3 cores each. I see that they each are using 1 v-core each. &lt;/P&gt;&lt;P&gt;Yet, when I check the Spark History Server... it describes each running executor has 3 cores and reflects all the properties I've specified.&lt;/P&gt;&lt;P&gt;What's up with this? Which of these should I be looking at?&lt;/P&gt;&lt;P&gt;YARN  3.1.0             Zeppelin  0.8.0             Spark2  2.3.1&lt;/P&gt;</description>
      <pubDate>Fri, 10 Aug 2018 01:02:21 GMT</pubDate>
      <guid>https://community.cloudera.com/t5/Archives-of-Support-Questions/Container-metrics-do-not-match-between-spark-UI-and-YARN/m-p/217993#M81898</guid>
      <dc:creator>matt_krueger</dc:creator>
      <dc:date>2018-08-10T01:02:21Z</dc:date>
    </item>
    <item>
      <title>Re: Container metrics do not match between spark UI and YARN resourcemanager UI</title>
      <link>https://community.cloudera.com/t5/Archives-of-Support-Questions/Container-metrics-do-not-match-between-spark-UI-and-YARN/m-p/217994#M81899</link>
      <description>&lt;P&gt; &lt;A rel="user" href="https://community.cloudera.com/users/65186/mattkrueger.html" nodeid="65186"&gt;@Matt Krueger&lt;/A&gt; you should look at spark history server/spark ui to see the correct environment settings being used. Setting executor cores to 3 is actually going to use 3 concurrent threads in each executor. AFAIK this might not be same as yarn v-core concept.  &lt;/P&gt;&lt;P&gt;HTH&lt;/P&gt;&lt;P&gt;*** If you found this answer addressed your question, please take a moment to login and click the "accept" link on the answer.&lt;/P&gt;</description>
      <pubDate>Fri, 10 Aug 2018 03:03:25 GMT</pubDate>
      <guid>https://community.cloudera.com/t5/Archives-of-Support-Questions/Container-metrics-do-not-match-between-spark-UI-and-YARN/m-p/217994#M81899</guid>
      <dc:creator>falbani</dc:creator>
      <dc:date>2018-08-10T03:03:25Z</dc:date>
    </item>
  </channel>
</rss>

