- Subscribe to RSS Feed
- Mark Question as New
- Mark Question as Read
- Float this Question for Current User
- Bookmark
- Subscribe
- Mute
- Printer Friendly Page
Multi Tenancy on CDH 5.2.x?
Created on ‎12-29-2014 05:09 PM - edited ‎09-16-2022 02:16 AM
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Hello,
I have been tasked with creating 3 environments for my team. dev, ua and prod.
I have two choices.
1. I create 3 completely separate intances of cloudera manager and build 3 completely separate environments of CDH. The complete isolation of these 3 environments would give me maximum flexibility.
2. I build only one cloudera manager instance and then build 3 clusters on top of it. these 3 clusters can have different security policies.
option 2 would be quite efficient because I can manage and maintain all 3 from 1 place.
However suppose I want to upgrade and test how cloudera 5.4 will work, then in option 1 this is easy to do. Since my dev is totally separate I can do whatever I want with it and test.
However I am wondering how does this work in option 2. so if I have 3 clusters on the same cloudera manager .... can I just upgrade 1 cluster to say CDH 5.6 independantly?
Also... which approach does the community recommend?
Created ‎12-29-2014 06:22 PM
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Manager, each cluster can be on a different version and can be
upgraded independent of each other.
While having all three environments managed by the same Cloudera
Manager seems attractive, it doesn't offer the flexibility of having
three truly independent clusters, each with its own Cloudera Manager
instance.
Gautam Gopalakrishnan
Created ‎12-29-2014 06:22 PM
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Manager, each cluster can be on a different version and can be
upgraded independent of each other.
While having all three environments managed by the same Cloudera
Manager seems attractive, it doesn't offer the flexibility of having
three truly independent clusters, each with its own Cloudera Manager
instance.
Gautam Gopalakrishnan
