<?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>topic Spark job looking MapR ticket in only tmp directory in HPE Ezmeral Software platform</title>
    <link>https://community.hpe.com/t5/hpe-ezmeral-software-platform/spark-job-looking-mapr-ticket-in-only-tmp-directory/m-p/7225572#M745</link>
    <description>&lt;P&gt;Hi All,&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;I've one crazy issue, few jobs looking for mapr ticket in /tmp even though i exported "export MAPR_TICKETFILE_LOCATION=$HOME/maprticket_$UID" . It's working fine on few servers and getting issues on few servers. I did checked all servers there are no other variables overriding the property i set in every user profile. Can someone please let me know if you faced this kind of issue.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Thanks&lt;/P&gt;</description>
    <pubDate>Wed, 18 Sep 2024 18:58:36 GMT</pubDate>
    <dc:creator>Akkism</dc:creator>
    <dc:date>2024-09-18T18:58:36Z</dc:date>
    <item>
      <title>Spark job looking MapR ticket in only tmp directory</title>
      <link>https://community.hpe.com/t5/hpe-ezmeral-software-platform/spark-job-looking-mapr-ticket-in-only-tmp-directory/m-p/7225572#M745</link>
      <description>&lt;P&gt;Hi All,&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;I've one crazy issue, few jobs looking for mapr ticket in /tmp even though i exported "export MAPR_TICKETFILE_LOCATION=$HOME/maprticket_$UID" . It's working fine on few servers and getting issues on few servers. I did checked all servers there are no other variables overriding the property i set in every user profile. Can someone please let me know if you faced this kind of issue.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Thanks&lt;/P&gt;</description>
      <pubDate>Wed, 18 Sep 2024 18:58:36 GMT</pubDate>
      <guid>https://community.hpe.com/t5/hpe-ezmeral-software-platform/spark-job-looking-mapr-ticket-in-only-tmp-directory/m-p/7225572#M745</guid>
      <dc:creator>Akkism</dc:creator>
      <dc:date>2024-09-18T18:58:36Z</dc:date>
    </item>
    <item>
      <title>Re: Spark job looking MapR ticket in only tmp directory</title>
      <link>https://community.hpe.com/t5/hpe-ezmeral-software-platform/spark-job-looking-mapr-ticket-in-only-tmp-directory/m-p/7225692#M746</link>
      <description>&lt;P&gt;You can check the following on the node where the crash occurs (referred to as the 'bad node') and compare it to a node where the job runs successfully ('good node'). I assume there is a distinct set of good and bad nodes with no overlap.&lt;/P&gt;&lt;UL&gt;&lt;LI&gt;Verify the environment settings for the user running the Spark job, not just the &lt;EM&gt;mapr&lt;/EM&gt; user.&lt;/LI&gt;&lt;LI&gt;Check the&lt;EM&gt; java.io.tmpdir&lt;/EM&gt; configuration on these nodes.&lt;/LI&gt;&lt;/UL&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;If the issue persists after checking the above, please share the logs for both successful and failed job attempts.&lt;/P&gt;</description>
      <pubDate>Thu, 19 Sep 2024 18:49:01 GMT</pubDate>
      <guid>https://community.hpe.com/t5/hpe-ezmeral-software-platform/spark-job-looking-mapr-ticket-in-only-tmp-directory/m-p/7225692#M746</guid>
      <dc:creator>hiteshingole</dc:creator>
      <dc:date>2024-09-19T18:49:01Z</dc:date>
    </item>
    <item>
      <title>Re: Spark job looking MapR ticket in only tmp directory</title>
      <link>https://community.hpe.com/t5/hpe-ezmeral-software-platform/spark-job-looking-mapr-ticket-in-only-tmp-directory/m-p/7225696#M747</link>
      <description>&lt;P&gt;Hello,&lt;/P&gt;&lt;P&gt;Can you please let us know how this jobs are being run?&lt;/P&gt;&lt;P&gt;Are you using same user or any service user? Are you using any tools? Please share sample steps in more details.&lt;/P&gt;&lt;P&gt;Please ensure yarn-site.xml and spark-default.conf have same values on all nodes.&lt;/P&gt;&lt;P&gt;Please ensure&amp;nbsp;&lt;SPAN&gt;&lt;STRONG&gt;MAPR_TICKETFILE_LOCATION&lt;/STRONG&gt; path location exists on all nodes.&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;Please check&amp;nbsp; spark job logs and see env variable set for each tasks matches.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Thanks,&lt;/P&gt;&lt;P&gt;Saikant&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Thu, 19 Sep 2024 19:05:57 GMT</pubDate>
      <guid>https://community.hpe.com/t5/hpe-ezmeral-software-platform/spark-job-looking-mapr-ticket-in-only-tmp-directory/m-p/7225696#M747</guid>
      <dc:creator>Saikant</dc:creator>
      <dc:date>2024-09-19T19:05:57Z</dc:date>
    </item>
    <item>
      <title>Query: Spark job looking MapR ticket in only tmp directory</title>
      <link>https://community.hpe.com/t5/hpe-ezmeral-software-platform/spark-job-looking-mapr-ticket-in-only-tmp-directory/m-p/7225895#M748</link>
      <description>&lt;P style="margin: 0;"&gt;Hello,&lt;/P&gt;
&lt;P style="margin: 0;"&gt;&amp;nbsp;&lt;/P&gt;
&lt;P style="margin: 0;"&gt;Let us know if you were able to resolve the issue.&lt;/P&gt;
&lt;P style="margin: 0;"&gt;&amp;nbsp;&lt;/P&gt;
&lt;P style="margin: 0;"&gt;If you have no further query, and you are satisfied with the answer then kindly mark the topic as Solved so that it is helpful for all community members.&lt;/P&gt;
&lt;P style="margin: 0;"&gt;&amp;nbsp;&lt;/P&gt;
&lt;P style="margin: 0;"&gt;Please click on "Thumbs Up/Kudo" icon to give a "Kudo".&lt;/P&gt;
&lt;P style="margin: 0;"&gt;&amp;nbsp;&lt;/P&gt;
&lt;P style="margin: 0;"&gt;Thank you for being a HPE valuable community member.&lt;/P&gt;</description>
      <pubDate>Mon, 23 Sep 2024 11:21:30 GMT</pubDate>
      <guid>https://community.hpe.com/t5/hpe-ezmeral-software-platform/spark-job-looking-mapr-ticket-in-only-tmp-directory/m-p/7225895#M748</guid>
      <dc:creator>support_s</dc:creator>
      <dc:date>2024-09-23T11:21:30Z</dc:date>
    </item>
  </channel>
</rss>

