<?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 after decommissioning nodes (delete host), we see new conf created which are identical to old conf in Archives of Support Questions (Read Only)</title>
    <link>https://community.cloudera.com/t5/Archives-of-Support-Questions/after-decommissioning-nodes-delete-host-we-see-new-conf/m-p/103251#M15509</link>
    <description>&lt;P&gt;Ambari 1.7, after decommissioning nodes (delete host), we see new version of conf created to HDFS, Yarn, HBase, Hive... but they are identical to previous conf. &lt;/P&gt;&lt;P&gt;Is it a known issue? can we make the previous version as current to avoid "restart required labels"?&lt;/P&gt;</description>
    <pubDate>Wed, 20 Jan 2016 02:41:59 GMT</pubDate>
    <dc:creator>rxu</dc:creator>
    <dc:date>2016-01-20T02:41:59Z</dc:date>
    <item>
      <title>after decommissioning nodes (delete host), we see new conf created which are identical to old conf</title>
      <link>https://community.cloudera.com/t5/Archives-of-Support-Questions/after-decommissioning-nodes-delete-host-we-see-new-conf/m-p/103251#M15509</link>
      <description>&lt;P&gt;Ambari 1.7, after decommissioning nodes (delete host), we see new version of conf created to HDFS, Yarn, HBase, Hive... but they are identical to previous conf. &lt;/P&gt;&lt;P&gt;Is it a known issue? can we make the previous version as current to avoid "restart required labels"?&lt;/P&gt;</description>
      <pubDate>Wed, 20 Jan 2016 02:41:59 GMT</pubDate>
      <guid>https://community.cloudera.com/t5/Archives-of-Support-Questions/after-decommissioning-nodes-delete-host-we-see-new-conf/m-p/103251#M15509</guid>
      <dc:creator>rxu</dc:creator>
      <dc:date>2016-01-20T02:41:59Z</dc:date>
    </item>
    <item>
      <title>Re: after decommissioning nodes (delete host), we see new conf created which are identical to old conf</title>
      <link>https://community.cloudera.com/t5/Archives-of-Support-Questions/after-decommissioning-nodes-delete-host-we-see-new-conf/m-p/103252#M15510</link>
      <description>&lt;P&gt;&lt;A rel="user" href="https://community.cloudera.com/users/273/rxu.html" nodeid="273"&gt;@rxu&lt;/A&gt; Ambari conf can be identical but node list is changed, meaning a decommissioned node is purged from list of known hosts. Going back to previous configs will not solve your problem of stale configs, you will still need to restart services. Try to restart services per node rather than per service and you'll be able to get through it. This is not an issue, it's by design. &lt;/P&gt;</description>
      <pubDate>Wed, 20 Jan 2016 10:26:38 GMT</pubDate>
      <guid>https://community.cloudera.com/t5/Archives-of-Support-Questions/after-decommissioning-nodes-delete-host-we-see-new-conf/m-p/103252#M15510</guid>
      <dc:creator>aervits</dc:creator>
      <dc:date>2016-01-20T10:26:38Z</dc:date>
    </item>
    <item>
      <title>Re: after decommissioning nodes (delete host), we see new conf created which are identical to old conf</title>
      <link>https://community.cloudera.com/t5/Archives-of-Support-Questions/after-decommissioning-nodes-delete-host-we-see-new-conf/m-p/103253#M15511</link>
      <description>&lt;P&gt;We set the previous version of conf as current, and it works.&lt;/P&gt;</description>
      <pubDate>Thu, 21 Jan 2016 04:09:49 GMT</pubDate>
      <guid>https://community.cloudera.com/t5/Archives-of-Support-Questions/after-decommissioning-nodes-delete-host-we-see-new-conf/m-p/103253#M15511</guid>
      <dc:creator>rxu</dc:creator>
      <dc:date>2016-01-21T04:09:49Z</dc:date>
    </item>
  </channel>
</rss>

