AnsweredAssumed Answered

Yarn Site XML Changes Require Restarts?

Question asked by john.humphreys on Mar 2, 2018
Latest reply on Mar 2, 2018 by MichaelSegel

A while back I had another question about Spark Streaming jobs dying after a week: MapR Ticket expiry in spark streaming? 


The answer was to override yarn.mapr.ticket.expiration in the yarn-site.xml (which defaults to a week) as shown below.


yarn.mapr.ticket.expirationDefault value: 604800000 Default source: code

It doesn't look like it worked.  Do we need to restart any processes on the cluster nodes to make changes to the yarn-site.xml apply to newly scheduled YARN jobs?