<?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 Why the 72 hours wait before installing a new node on a host that shares the same IP? in Dynatrace Managed Q&amp;A</title>
    <link>https://community.dynatrace.com/t5/Dynatrace-Managed-Q-A/Why-the-72-hours-wait-before-installing-a-new-node-on-a-host/m-p/277956#M4293</link>
    <description>&lt;P&gt;Good morning managed fans,&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&lt;SPAN&gt;In the documentation I read below:&lt;/SPAN&gt;&lt;/P&gt;
&lt;P&gt;&lt;SPAN&gt;Following removal of an existing cluster node, you must wait 72 hours before installing a new node on a host that shares the same IP (i.e., when re-installing on the same host).&lt;/SPAN&gt;&lt;/P&gt;
&lt;P&gt;&lt;SPAN&gt;&lt;A href="https://docs.dynatrace.com/managed/managed-cluster/installation/add-a-new-cluster-node" target="_blank" rel="noopener"&gt;https://docs.dynatrace.com/managed/managed-cluster/installation/add-a-new-cluster-node&lt;/A&gt;&lt;/SPAN&gt;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&lt;SPAN&gt;I really like to know the why behind this, and what happens if you do not wait and also underlying, can we speedup this?&lt;/SPAN&gt;&lt;/P&gt;
&lt;P&gt;&lt;SPAN&gt;To make it more interesting, what if we replace the hardware, keep original IP and restore all Dyntrace files?&lt;/SPAN&gt;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&lt;SPAN&gt;KR Henk&lt;/SPAN&gt;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
    <pubDate>Mon, 05 Jan 2026 12:57:44 GMT</pubDate>
    <dc:creator>henk_stobbe</dc:creator>
    <dc:date>2026-01-05T12:57:44Z</dc:date>
    <item>
      <title>Why the 72 hours wait before installing a new node on a host that shares the same IP?</title>
      <link>https://community.dynatrace.com/t5/Dynatrace-Managed-Q-A/Why-the-72-hours-wait-before-installing-a-new-node-on-a-host/m-p/277956#M4293</link>
      <description>&lt;P&gt;Good morning managed fans,&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&lt;SPAN&gt;In the documentation I read below:&lt;/SPAN&gt;&lt;/P&gt;
&lt;P&gt;&lt;SPAN&gt;Following removal of an existing cluster node, you must wait 72 hours before installing a new node on a host that shares the same IP (i.e., when re-installing on the same host).&lt;/SPAN&gt;&lt;/P&gt;
&lt;P&gt;&lt;SPAN&gt;&lt;A href="https://docs.dynatrace.com/managed/managed-cluster/installation/add-a-new-cluster-node" target="_blank" rel="noopener"&gt;https://docs.dynatrace.com/managed/managed-cluster/installation/add-a-new-cluster-node&lt;/A&gt;&lt;/SPAN&gt;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&lt;SPAN&gt;I really like to know the why behind this, and what happens if you do not wait and also underlying, can we speedup this?&lt;/SPAN&gt;&lt;/P&gt;
&lt;P&gt;&lt;SPAN&gt;To make it more interesting, what if we replace the hardware, keep original IP and restore all Dyntrace files?&lt;/SPAN&gt;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&lt;SPAN&gt;KR Henk&lt;/SPAN&gt;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Mon, 05 Jan 2026 12:57:44 GMT</pubDate>
      <guid>https://community.dynatrace.com/t5/Dynatrace-Managed-Q-A/Why-the-72-hours-wait-before-installing-a-new-node-on-a-host/m-p/277956#M4293</guid>
      <dc:creator>henk_stobbe</dc:creator>
      <dc:date>2026-01-05T12:57:44Z</dc:date>
    </item>
    <item>
      <title>Re: Why the 72 hours wait?</title>
      <link>https://community.dynatrace.com/t5/Dynatrace-Managed-Q-A/Why-the-72-hours-wait-before-installing-a-new-node-on-a-host/m-p/277958#M4294</link>
      <description>&lt;P&gt;Hi&amp;nbsp;&lt;a href="https://community.dynatrace.com/t5/user/viewprofilepage/user-id/11427"&gt;@henk_stobbe&lt;/a&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;AFAIK its because of Cassandra.&lt;/P&gt;&lt;P&gt;Here is what ChatGPT says about how long its take Cassandra to forget the IP ...&lt;/P&gt;&lt;P&gt;&lt;span class="lia-inline-image-display-wrapper lia-image-align-inline" image-alt="Yosi_Neuman_0-1748097310576.png" style="width: 400px;"&gt;&lt;img src="https://community.dynatrace.com/t5/image/serverpage/image-id/28186i0B66C52D9B0C15B2/image-size/medium?v=v2&amp;amp;px=400" role="button" title="Yosi_Neuman_0-1748097310576.png" alt="Yosi_Neuman_0-1748097310576.png" /&gt;&lt;/span&gt;&lt;/P&gt;&lt;P&gt;If you don't wait there is a chance that the cluster will not get back to healthy state, and you will need to use&amp;nbsp;&lt;A href="https://community.dynatrace.com/t5/Dynatrace-Managed-Q-A/Node-synchronization-in-a-cluster/m-p/41847/highlight/true#M34" target="_blank" rel="noopener"&gt;cassandra-nodetool.sh&lt;/A&gt; in order to set it back to work.&lt;/P&gt;&lt;P&gt;HTH&lt;/P&gt;&lt;P&gt;Yos&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Sat, 24 May 2025 15:27:12 GMT</pubDate>
      <guid>https://community.dynatrace.com/t5/Dynatrace-Managed-Q-A/Why-the-72-hours-wait-before-installing-a-new-node-on-a-host/m-p/277958#M4294</guid>
      <dc:creator>Yosi_Neuman</dc:creator>
      <dc:date>2025-05-24T15:27:12Z</dc:date>
    </item>
    <item>
      <title>Re: Why the 72 hours wait?</title>
      <link>https://community.dynatrace.com/t5/Dynatrace-Managed-Q-A/Why-the-72-hours-wait-before-installing-a-new-node-on-a-host/m-p/277959#M4295</link>
      <description>&lt;P&gt;Hi Yos,&lt;/P&gt;&lt;P&gt;Thanks for your reply, on a Saterday you earn 2 kudo's. Sorry can only give the 1&lt;/P&gt;&lt;P&gt;Thanks Henk&lt;/P&gt;</description>
      <pubDate>Sat, 24 May 2025 15:53:43 GMT</pubDate>
      <guid>https://community.dynatrace.com/t5/Dynatrace-Managed-Q-A/Why-the-72-hours-wait-before-installing-a-new-node-on-a-host/m-p/277959#M4295</guid>
      <dc:creator>henk_stobbe</dc:creator>
      <dc:date>2025-05-24T15:53:43Z</dc:date>
    </item>
  </channel>
</rss>

