Hi Sergey, Is this a free or trial-licensed CM deployment? For some reason does this deployment lack the "Reports Manager" role or any other roles missing from the 'mgmt1' (Management Services) section? ... View more

Hi Sergey,   For some reason do you lack a Role type of "Balancer" within that HDFS config? A Balancer role must be present in order for that option to be available. Check in HDFS > Instances to see if a Balancer exists. If not, use the Add button to assign it to one host (it's not terribly critical which host you assign it to). ... View more

Hi there,   The "[Errno 99] Cannot assign requested address" points to hostname resolution rather than a port conflict. Please run this on the node:   $  python -c 'import socket; print socket.getfqdn(), socket.gethostbyname(socket.getfqdn())'   This should return the fully-qualified domain name as well as the IP address, confirming forward and reverse name resolution. Sanity-check this output against:   $ dig NexusHadoopVM $ dig -x [IP returned in above dig command]   You may also wish to check your /etc/hosts file to make sure everything is OK there.   Regards, -- ... View more

Did you apply this new dfs value to ALL datanode roles globally, or did you set it as an override to just one datanode (perhaps you have a node with fewer or more data volumes for a datanode, and you wanted it to inherit different values than the rest of the DN's).   If you've set this as a "one-off" configuration, look for an overrride [1] within the HDFS > Configuration > View & Edit for the property you've altered.   More to the point, this configuration would be picked up for the scope in which you applied it. If globally, you'd find that after restarting Datanodes that the DN's are using the new values set. A new hdfs-site.xml is generated each time a service starts, and these can be referenced by going to    Services > hdfs > Instances > [click on a Datanode from the list] > Processes    Then on this page, expand the link near the middle of the page that says "Show" under "Configuration Files/Environment". This will give links to ALL the configuration files used for that specific processes start of the Datanode. The hdfs-site.xml should reflect the dfs.data.dir settings you applied, if it is intended to be a recipient of that property/value.   If it is not, then there could be some other explanation such as use of Role Config Groups, or unintended overrides.   [1] = http://www.cloudera.com/content/cloudera-content/cloudera-docs/CM4Ent/latest/Cloudera-Manager-Managing-Clusters/cmmc_mod_configs.html?scroll=cmug_topic_5_3_1_unique_1__title_149_unique_3 ... View more

Thanks for your report. This is a confirmed issue, and a very near-term release will address pardel_dir= not properly enumerating parcels when a symlink is present.   You likely already discovered that you can in the short term change parcel_dir= to the end target and restart the agent, though we'll get this resolved ASAP.   Best, -- ... View more

The cloudera-manager-installer.bin uses an ncurses / text-based menu if invoked from the commandline, though if you do have gnome or similar it will display properly as well. ... View more