Created on 11-21-2015 06:17 AM - edited 09-16-2022 02:49 AM
I have been completing a set of prototypes using Director to build a cluster on AWS (so this is all dev work).
I have defined a private AMI based on the Cloudera ami-8767d1ec (from Cloudera Github) that I am using for the cluster nodes (basically I installed java 1.8 and loaded some additional software)
Can I use the rootVolumeSizeGB to expand the disk size defined in the AMI or is the ami definitinon the max limit (i.e. do I need to tweak the AMI to add additional diskspace)?
Also, how can I manage the size dfs uses for its data directories. Does Director/CM have keywords/commands that help define that on build that I cna include in my Director AWS script?
I am using the batch script mechanism to create my cluster.
Thanks
- rd
Created 11-23-2015 11:11 PM
You can use rootVolumeSizeGB to expand a custom AMI.
The size of DFS can be managed indirectly by your choice of instance types. We have no other ways to control the number of ephemeral drives and we don't support EBS for data disks (only as the root partition).
Created 11-23-2015 11:11 PM
You can use rootVolumeSizeGB to expand a custom AMI.
The size of DFS can be managed indirectly by your choice of instance types. We have no other ways to control the number of ephemeral drives and we don't support EBS for data disks (only as the root partition).
Created 11-29-2015 06:58 AM