Actually, by design, its meant to operate that way. All cluster nodes must be at the same release level, and this is verified on startup. What you did was pull the resources out from under the database and trigger a server service halt because it could not audit deployed vs staged parcels. If we threw away the CDH parcel, how would you add servers and additional cluster service role instances? Cloudera Manager can manage multiple CDH clusters that may at be varying release levels too. We go through the disk requirements here: http://www.cloudera.com/content/cloudera/en/documentation/core/latest/topics/cm_ig_reqs_space.html The cluster maintains parcel deployment based on the UI within the CM server, you can not manage these from the command line (by doing something like removing the files from the path). If there are additional/old unused parces you can remove them using the parcel management screen. http://www.cloudera.com/content/cloudera/en/documentation/core/latest/topics/cm_ig_parcels.html You can get the CM server down to where its only storing the current parcel in its repo, using the UI. Having Cloudera Manager on a CDH cluster node will drive your storage issues as well.
... View more
