<?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 Re: How to reissue a delegated token after max lifetime passes for a spark streaming application on a Kerberized cluster in Support Questions</title>
    <link>https://community.cloudera.com/t5/Support-Questions/How-to-reissue-a-delegated-token-after-max-lifetime-passes/m-p/240822#M202626</link>
    <description>&lt;P&gt;This is exactly the way we use spark-submit. A token is valid only for 24 hrs. Yarn renew the token every 24 hrs automatically until it reaches the max lifetime (which is 7 days) then the token cannot get renewed anymore and needs to be reissued. Hence, we are restarting the job every 7 days. Restarting the job every 7 days doesn't seem to be the right approach for a production environment! &lt;/P&gt;</description>
    <pubDate>Thu, 03 Jan 2019 08:52:16 GMT</pubDate>
    <dc:creator>alinazemian</dc:creator>
    <dc:date>2019-01-03T08:52:16Z</dc:date>
  </channel>
</rss>

