<?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 Re: Dynatrace Managed Cluster in Dynatrace Managed Q&amp;A</title>
    <link>https://community.dynatrace.com/t5/Dynatrace-Managed-Q-A/Dynatrace-Managed-failover-mechanism/m-p/163867#M1624</link>
    <description>&lt;P&gt;Hello&amp;nbsp;&lt;a href="https://community.dynatrace.com/t5/user/viewprofilepage/user-id/36508"&gt;@SB_12&lt;/a&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Quick summary - If you have 3node servers if say 1node is down. Still Dynatrace is capable to monitor with 2node servers.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Latency required is 10ms across 3node servers to sync between them. When a transaction is monitored its evenly distributed across 3nodes. So that no data are missed even if you have large volume of data coming to node servers.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Note- If their is high latency between Node servers. Then case can be upside down.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Cheers&lt;/P&gt;&lt;P&gt;R&lt;/P&gt;</description>
    <pubDate>Tue, 06 Apr 2021 12:28:14 GMT</pubDate>
    <dc:creator>RazTN7</dc:creator>
    <dc:date>2021-04-06T12:28:14Z</dc:date>
    <item>
      <title>Dynatrace Managed failover mechanism</title>
      <link>https://community.dynatrace.com/t5/Dynatrace-Managed-Q-A/Dynatrace-Managed-failover-mechanism/m-p/163860#M1623</link>
      <description>&lt;P&gt;Hi , can someone please help me understand&amp;nbsp;&lt;SPAN&gt;Managed failover mechanism . the explanation in document is confusing .&lt;/SPAN&gt;&lt;/P&gt;
&lt;P&gt;&lt;SPAN&gt;&lt;A href="https://docs.dynatrace.com/managed/shortlink/managed-cluster-failover" target="_blank" rel="noopener"&gt;Managed failover mechanism&lt;/A&gt;&lt;/SPAN&gt;&lt;/P&gt;
&lt;P&gt;&lt;SPAN&gt;Is it correct to say that incase of a node failure , I will be able to have details of user session and metrics . However , transactional data will be lost for the time when node was down?&lt;/SPAN&gt;&lt;/P&gt;
&lt;P&gt;&lt;SPAN&gt;What is the replication factor of 3 means?&lt;/SPAN&gt;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&lt;SPAN&gt;Thanks in advance.&lt;/SPAN&gt;&lt;/P&gt;</description>
      <pubDate>Mon, 17 Mar 2025 14:53:27 GMT</pubDate>
      <guid>https://community.dynatrace.com/t5/Dynatrace-Managed-Q-A/Dynatrace-Managed-failover-mechanism/m-p/163860#M1623</guid>
      <dc:creator>SB_12</dc:creator>
      <dc:date>2025-03-17T14:53:27Z</dc:date>
    </item>
    <item>
      <title>Re: Dynatrace Managed Cluster</title>
      <link>https://community.dynatrace.com/t5/Dynatrace-Managed-Q-A/Dynatrace-Managed-failover-mechanism/m-p/163867#M1624</link>
      <description>&lt;P&gt;Hello&amp;nbsp;&lt;a href="https://community.dynatrace.com/t5/user/viewprofilepage/user-id/36508"&gt;@SB_12&lt;/a&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Quick summary - If you have 3node servers if say 1node is down. Still Dynatrace is capable to monitor with 2node servers.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Latency required is 10ms across 3node servers to sync between them. When a transaction is monitored its evenly distributed across 3nodes. So that no data are missed even if you have large volume of data coming to node servers.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Note- If their is high latency between Node servers. Then case can be upside down.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Cheers&lt;/P&gt;&lt;P&gt;R&lt;/P&gt;</description>
      <pubDate>Tue, 06 Apr 2021 12:28:14 GMT</pubDate>
      <guid>https://community.dynatrace.com/t5/Dynatrace-Managed-Q-A/Dynatrace-Managed-failover-mechanism/m-p/163867#M1624</guid>
      <dc:creator>RazTN7</dc:creator>
      <dc:date>2021-04-06T12:28:14Z</dc:date>
    </item>
    <item>
      <title>Re: Dynatrace Managed Cluster</title>
      <link>https://community.dynatrace.com/t5/Dynatrace-Managed-Q-A/Dynatrace-Managed-failover-mechanism/m-p/163870#M1625</link>
      <description>&lt;P&gt;hi , thanks for your reply. So that means that Transactional data will not be completely captured incase one of the nodes get down.&amp;nbsp;&lt;/P&gt;&lt;P&gt;Metrics and user session will be available on either of the two nodes( which are up) .&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Tue, 06 Apr 2021 12:43:01 GMT</pubDate>
      <guid>https://community.dynatrace.com/t5/Dynatrace-Managed-Q-A/Dynatrace-Managed-failover-mechanism/m-p/163870#M1625</guid>
      <dc:creator>SB_12</dc:creator>
      <dc:date>2021-04-06T12:43:01Z</dc:date>
    </item>
    <item>
      <title>Re: Dynatrace Managed Cluster</title>
      <link>https://community.dynatrace.com/t5/Dynatrace-Managed-Q-A/Dynatrace-Managed-failover-mechanism/m-p/163872#M1626</link>
      <description>&lt;P&gt;Yes. In any case one of your node goes down. Still data is available on other node servers&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Cheers!&lt;/P&gt;&lt;P&gt;R&lt;/P&gt;</description>
      <pubDate>Tue, 06 Apr 2021 12:46:06 GMT</pubDate>
      <guid>https://community.dynatrace.com/t5/Dynatrace-Managed-Q-A/Dynatrace-Managed-failover-mechanism/m-p/163872#M1626</guid>
      <dc:creator>RazTN7</dc:creator>
      <dc:date>2021-04-06T12:46:06Z</dc:date>
    </item>
    <item>
      <title>Re: Dynatrace Managed Cluster</title>
      <link>https://community.dynatrace.com/t5/Dynatrace-Managed-Q-A/Dynatrace-Managed-failover-mechanism/m-p/164159#M1627</link>
      <description>&lt;P&gt;&lt;a href="https://community.dynatrace.com/t5/user/viewprofilepage/user-id/36508"&gt;@SB_12&lt;/a&gt;&amp;nbsp;hope this helped.&lt;/P&gt;</description>
      <pubDate>Mon, 12 Apr 2021 15:13:04 GMT</pubDate>
      <guid>https://community.dynatrace.com/t5/Dynatrace-Managed-Q-A/Dynatrace-Managed-failover-mechanism/m-p/164159#M1627</guid>
      <dc:creator>RazTN7</dc:creator>
      <dc:date>2021-04-12T15:13:04Z</dc:date>
    </item>
    <item>
      <title>Re: Dynatrace Managed Cluster</title>
      <link>https://community.dynatrace.com/t5/Dynatrace-Managed-Q-A/Dynatrace-Managed-failover-mechanism/m-p/164750#M1628</link>
      <description>&lt;P&gt;He,&lt;/P&gt;&lt;P&gt;Ideally for critical environments you should have at least 3 servers to work properly. We have managed and 3 servers, very recently one of the disks of 1 server was corrupted and we had to repair it together with the system administrators. If we did not have 3 nodes and only 1, we would lose all the data. 100% recommended to have 3 nodes. NOTE, latency is important as well as time synchronization or time zone, you must use NTP.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;regard!&lt;/P&gt;</description>
      <pubDate>Wed, 21 Apr 2021 19:08:22 GMT</pubDate>
      <guid>https://community.dynatrace.com/t5/Dynatrace-Managed-Q-A/Dynatrace-Managed-failover-mechanism/m-p/164750#M1628</guid>
      <dc:creator>Marcelo_santand</dc:creator>
      <dc:date>2021-04-21T19:08:22Z</dc:date>
    </item>
  </channel>
</rss>

