Our Community is getting an upgrade! To get everything ready for the relaunch, we’ll be placing the site in read-only mode starting September 21st.
We really appreciate your understanding while we get things set up behind the scenes. Catch up on all the exciting details about the move here.
Need help or have questions? Drop us a line at [email protected]

Archives of Support Questions (Read Only)

This is an archived board for historical reference. Information and links may no longer be available or relevant
Announcements
This board is archived and read-only for historical reference. To ask a new question, please post a new topic on the appropriate active board.

Mix cloud and on premise Data nodes

avatar
Expert Contributor

Hi, is it supported to have some Worker/Data nodes on premise and others in the AWS or Azure cloud within the same cluster managed by the same NN/YARN? What are the issues with this? 

1 ACCEPTED SOLUTION

avatar
Expert Contributor

ebeb,

 

Cloudera Director is designed for provisioning cloud clusters and cannot create a mixed cloud/on-premise cluster.

 

My initial thoughts on a mixed cluster is that network latency between the cloud nodes and on-premise nodes would lead to poor performance. You may be better served by creating two separate clusters and using some other mechanism for sharing data. For example, you can export/import data to S3.

 

 

View solution in original post

1 REPLY 1

avatar
Expert Contributor

ebeb,

 

Cloudera Director is designed for provisioning cloud clusters and cannot create a mixed cloud/on-premise cluster.

 

My initial thoughts on a mixed cluster is that network latency between the cloud nodes and on-premise nodes would lead to poor performance. You may be better served by creating two separate clusters and using some other mechanism for sharing data. For example, you can export/import data to S3.