Thanks. It worked. ... View more

Thanks for all the information. ... View more

@kal,   Yup, you can stop Service Monitor and Host Monitor and then remove the contents of cloudera-host-monitor and cloudera-service-monitor directories. When you restart Servcie and Host Monitor, new indexes will be start from scratch.   You will only lose the historical information. ... View more

This looks like a case of edit logs getting reordered. As @bgooley noted, it is similar to HDFS-12369, where the OP_CLOSE is appearing after OP_DELETE causing the file to be absent when replaying the edits. The simplest fix, depending on if this is the only file instance of the reordered issue in your edit logs, would be to run the NameNode manually in an edits-recovery mode and "skip" this edit when it catches the error. The rest of the edits should apply normally and let you start up your NameNode. The recovery mode of NameNode is detailed at https://blog.cloudera.com/blog/2012/05/namenode-recovery-tools-for-the-hadoop-distributed-file-system/ If you're using CM, you'll need to use the NameNode's most recent generated configuration directory under /var/run/cloudera-scm-agent/process/ on the NameNode host as the HADOOP_CONF_DIR, while logged in as 'hdfs' user, before invoking the manual NameNode startup command. Once you've followed the prompts and the NameNode appears to start up, quit out/kill it to restart from Cloudera Manager normally. If you have a Support subscription, I'd recommend filing a case for this, as the process could get more involved depending on how widespread this issue is. ... View more

@MichalAR ,   Right, so SAML can be used for Authentication and then LDAP for user/group sync. If you are not using LDAP for authentication, then "Create LDAP users on login" won't impact you. If you want to prevent the creation of a Hue user for a new user login, you can set the following: [libsaml] create_users_on_login=False   If you do that, though, you need to be sure that you have all of your users already in Hue before they authenticate; otherwise, they will get an error.   If you would like to leave create_users_on_login "True" but change the default group membership, you can adjust the "default" group that is set for new users.   To do so, set:   [useradmin] default_user_group=<name_of_your_preferred_group>   That way, you don't prevent users from authenticating via SAML if they don't already exist as Hue users, but you can restrict the resources they can access.   It's just another thing to consider that may help you achieve the type of configuration you want.     ... View more