Hi Nishan, This is also fine, so long as you configure the database appropriately to handle the load from 3 CM servers and whatever else you point at it. When concerned about handling database load from multiple applications, I would expect that it's generally better to run a single instance on a host than to run several instances on the same host, since there would be lower overhead. Multiple instances on the same host can help with isolation, but not with handling more load. Monitoring databases tend to use a lot of resources if your cluster has a lot of activity, so be cautious about sharing monitoring databases. The database for CM doesn't generally get as much load. Depending on your cluster size / activity and the hardware / tuning you have for your Oracle, you may find it better to run multiple instances on different machines to ensure each daemon performs well. Thanks, Darren ... View more

Finally resolved the Issue.   Due to space crunch on root mount space we have created a soft  link for /opt/cloudera/ to point to /data/opt/cloudera/ As a result of this the the local repo path was changed as well. Hence while installing package it was trying to download the packages again and again. But unable to find the same on the disk as correctly distributed by CM.   As I changed the local repo directory in CM Administration/parcel-repo path Every thing started working as required.   Thanks every one for your support and suggestions.   Priyabrata Patnaik ... View more

Hi,   If you look carefully at the options on the page where you enter in SSH credentials, there's an option to control how many hosts to install simultaneously. By default it is 10.   You may also want to edit the parcel distribution settings when setting up a large cluster, accessible via Administration -> Settings -> Parcels. You may need to exit a wizard (click the Cloudera Manager Logo) to access the Administration menu.   Thanks, Darren ... View more