<?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: Mix on premise and cloud nodes in Archives of Support Questions (Read Only)</title>
    <link>https://community.cloudera.com/t5/Archives-of-Support-Questions/Mix-on-premise-and-cloud-nodes/m-p/77850#M81417</link>
    <description>&lt;P&gt;&lt;a href="https://community.cloudera.com/t5/user/viewprofilepage/user-id/21823"&gt;@chriswalton007&lt;/a&gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;There are different types of latencies&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Namenode RPC latency&lt;BR /&gt;Journal Node FSync latency&lt;BR /&gt;network latency&lt;BR /&gt;etc&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;There are few points here,&lt;/P&gt;&lt;P&gt;&lt;SPAN&gt;1.&amp;nbsp;Your network latency will vary based on the traffic in your cluster.&amp;nbsp;It may create trouble during peak hours.&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN&gt;2. The latency issue may leads to follows: As we know, the master daemons will always wait for the update from child daemons in every few seconds, and&amp;nbsp;master will consider the child is not available/dead in case of any delay and look for alternate. It is&amp;nbsp;unnecessary unless it is a real issue with child.&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN&gt;3.&amp;nbsp;As far as NN RPC is the concern, in a HA cluster, both active and standby NN has to talk each other and it should be in sync with in few seconds.&amp;nbsp;If they are not in sync and if something&amp;nbsp;went wrong on active NN, the standby become active but it may not be up to date and it will lead to confusion.&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&lt;SPAN&gt;end of the day, every seconds are matter in a distributted cluster.&amp;nbsp;&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&lt;SPAN&gt;But in your use case, not sure you are going to use cloudera director if so, the link that you have shared says it will not allow&amp;nbsp;to create a&amp;nbsp;mixed cloud/on-premise cluster.&amp;nbsp;But if you are going to use a different tool and it will allow you to configure the mixed cloud/on-prem then you can&amp;nbsp;go ahead based on the below...&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN&gt;1. If you are going to try this for a non-prod environment first&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN&gt;2. if&amp;nbsp;you have less work loads&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
    <pubDate>Tue, 31 Jul 2018 13:55:37 GMT</pubDate>
    <dc:creator>saranvisa</dc:creator>
    <dc:date>2018-07-31T13:55:37Z</dc:date>
    <item>
      <title>Mix on premise and cloud nodes</title>
      <link>https://community.cloudera.com/t5/Archives-of-Support-Questions/Mix-on-premise-and-cloud-nodes/m-p/77844#M81416</link>
      <description>&lt;P&gt;Hi,&lt;BR /&gt;&lt;BR /&gt;I've read the following forumn post (&lt;A href="http://community.cloudera.com/t5/Cloudera-Director-Cloud-based/Mix-cloud-and-on-premise-Data-nodes/td-p/60212" target="_blank"&gt;http://community.cloudera.com/t5/Cloudera-Director-Cloud-based/Mix-cloud-and-on-premise-Data-nodes/td-p/60212&lt;/A&gt;) that states if mixing a cluster with both on prem and cloud bases nodes network latency could be a problem.&lt;BR /&gt;&lt;BR /&gt;I'm trying to find a little more information around what Cloudera would recommend with regards to latency.&amp;nbsp;&amp;nbsp;&lt;BR /&gt;&lt;BR /&gt;I currently have a small cluster on prem, however we also have a direct connect to AWS which i'd like to explore the option of adding new EC2 nodes to the cluster.&lt;BR /&gt;&lt;BR /&gt;Network latancy is the following:&lt;BR /&gt;&lt;BR /&gt;&lt;STRONG&gt;Office to on prem nodes:&lt;/STRONG&gt; 6ms&lt;/P&gt;&lt;P&gt;&lt;STRONG&gt;Office to EC2 nodes:&lt;/STRONG&gt; 16ms&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&lt;STRONG&gt;On-Prem nodes to EC2:&lt;/STRONG&gt; 10ms&lt;/P&gt;&lt;P&gt;&lt;STRONG&gt;EC2 to on prem nodes:&lt;/STRONG&gt; 10ms&lt;BR /&gt;&lt;BR /&gt;Given the latency seems relativly small, is there any disadvantage to using cloud with on prem?&lt;/P&gt;</description>
      <pubDate>Fri, 16 Sep 2022 13:31:44 GMT</pubDate>
      <guid>https://community.cloudera.com/t5/Archives-of-Support-Questions/Mix-on-premise-and-cloud-nodes/m-p/77844#M81416</guid>
      <dc:creator>chriswalton007</dc:creator>
      <dc:date>2022-09-16T13:31:44Z</dc:date>
    </item>
    <item>
      <title>Re: Mix on premise and cloud nodes</title>
      <link>https://community.cloudera.com/t5/Archives-of-Support-Questions/Mix-on-premise-and-cloud-nodes/m-p/77850#M81417</link>
      <description>&lt;P&gt;&lt;a href="https://community.cloudera.com/t5/user/viewprofilepage/user-id/21823"&gt;@chriswalton007&lt;/a&gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;There are different types of latencies&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Namenode RPC latency&lt;BR /&gt;Journal Node FSync latency&lt;BR /&gt;network latency&lt;BR /&gt;etc&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;There are few points here,&lt;/P&gt;&lt;P&gt;&lt;SPAN&gt;1.&amp;nbsp;Your network latency will vary based on the traffic in your cluster.&amp;nbsp;It may create trouble during peak hours.&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN&gt;2. The latency issue may leads to follows: As we know, the master daemons will always wait for the update from child daemons in every few seconds, and&amp;nbsp;master will consider the child is not available/dead in case of any delay and look for alternate. It is&amp;nbsp;unnecessary unless it is a real issue with child.&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN&gt;3.&amp;nbsp;As far as NN RPC is the concern, in a HA cluster, both active and standby NN has to talk each other and it should be in sync with in few seconds.&amp;nbsp;If they are not in sync and if something&amp;nbsp;went wrong on active NN, the standby become active but it may not be up to date and it will lead to confusion.&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&lt;SPAN&gt;end of the day, every seconds are matter in a distributted cluster.&amp;nbsp;&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&lt;SPAN&gt;But in your use case, not sure you are going to use cloudera director if so, the link that you have shared says it will not allow&amp;nbsp;to create a&amp;nbsp;mixed cloud/on-premise cluster.&amp;nbsp;But if you are going to use a different tool and it will allow you to configure the mixed cloud/on-prem then you can&amp;nbsp;go ahead based on the below...&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN&gt;1. If you are going to try this for a non-prod environment first&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN&gt;2. if&amp;nbsp;you have less work loads&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Tue, 31 Jul 2018 13:55:37 GMT</pubDate>
      <guid>https://community.cloudera.com/t5/Archives-of-Support-Questions/Mix-on-premise-and-cloud-nodes/m-p/77850#M81417</guid>
      <dc:creator>saranvisa</dc:creator>
      <dc:date>2018-07-31T13:55:37Z</dc:date>
    </item>
  </channel>
</rss>

