Member since
07-25-2018
5
Posts
1
Kudos Received
0
Solutions
08-27-2018
10:45 PM
1 Kudo
@krb, What you provided appears to be an agent log message that indicates an attempt to kinit with the HTTP principal on the host where HTTPFS role runs was not successful. Check on the host where the httpfs role runs and make sure the krb5.conf file is correct. This shoud not impact HDFS as a whole since HTTPFS is a client of HDFS really. Cloudera Manager should merge the HTTP principal automatically, so please run the following to make sure the keytab has the right keys: # klist -kte /run/cloudera-scm-agent/process/1330-hdfs-HTTPFS/httpfs.keytab
... View more
07-30-2018
02:16 AM
When CM is set to managing services, its central source of configs lie within the DB. For every time a role instance is spawned, the config is generated into a special (non-/etc/…) path and the service is started with the special config dir. You could do an ls -l /var/run/cloudera-scm-agent/process on any host to see this, for example (the same files are available in the UI under any instance's Processes tab). So even if you remove the packages, CM faces no impact since it still has the Parcel location now for the actual binaries, and the configs are within its DB, away from being affected by RPM removals. source: https://community.cloudera.com/t5/Cloudera-Manager-Installation/Package-installs-detected-on-host-with-parcel/td-p/32442
... View more