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.

Cloudera Manager root volume does not get resized

avatar
Expert Contributor

After launching a new manager node I discovered the root volume was not resized to the provisioned limit.

 

# lsblk
NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINT
xvda 202:0 0 250G 0 disk
├─xvda1 202:1 0 200M 0 part /boot
├─xvda2 202:2 0 4G 0 part [SWAP]
└─xvda3 202:3 0 10.8G 0 part /

1 ACCEPTED SOLUTION

avatar
Expert Contributor

Fixed by picking a different AMI, the original AMI had multiple partitions on the root disk which the director install did not appreciate. Switching to an AMI with a single partition on the root volume appears to have resolved this issue entirely. FWIW the picking the official centos AMI should ensure you dont have a bad time.

View solution in original post

1 REPLY 1

avatar
Expert Contributor

Fixed by picking a different AMI, the original AMI had multiple partitions on the root disk which the director install did not appreciate. Switching to an AMI with a single partition on the root volume appears to have resolved this issue entirely. FWIW the picking the official centos AMI should ensure you dont have a bad time.