As per-title, the is a new Cloudera Manager 5.15 setting for Impala called " Impala Daemon KRPC Port" which is a setting for parm called "krpc_port" and is set to port 27000   We use a mix of SSSD, Kerberos, Sentry and Active Directory for our clusters. Jumping from CDH 5.13.0 to 5.15.0 in one of our clusters results in Impala queries failing with...   TransmitData() to 10.0.1.204:27000 failed: Not authorized: Client connection negotiation failed: client connection to 10.0.1.204 :27000: Cannot determine realm for numeric host address Rolling back to CDH 5.13.0 confirms all ok again, rolling forward to CDH 5.15.0 breaks this.    The query error appears in both Hue and Impala Shell. Of note you can still traverse though the use database commands and show tables OK, just when quering the data.    I've checked everything I can think of so far, /etc/hosts is fine, along with /etc/krb5.conf (and importantly haven't changed for years), reverse DNS digs work OK, Kerberos tickets are issued etc.    Just throwing this out there in-case someone else is/has experienced this issue.   ... View more

Noticed this in CM 5.13   When changing the value Node Manager config item Dish Health Checker Max Disk Utilization Percent  ( yarn.nodemanager.disk-health-checker.max-disk-utilization-per-disk-percentage) - in my case increasing it from 90 to 95, CM doesn't flag the already running instances as being out of date/stale and flagged for restart   This is confirmed by looking in the running processes yarn-site.xml file   Also I think the "Dish Health" might mean "Disk"   No further support required here, just pointing it out   Regards   Neil ... View more

Hi, I can find specific information for the Linux OS for Cloudera Manager's disk space allocation...   http://www.cloudera.com/content/cloudera/en/documentation/core/v5-3-x/topics/cm_ig_cm_requirements.html   ...but not for CDH. ??   I understand that CDH can form many roles, but I need to develop a generic Linux OS build for hosts that may use one or more roles with CDH (Flume/Datanodes etc) so we can deploy quickly and easily. I guess what I am after is a broad example of mount point disk space requirements (like the ones outlined for CM)    Can anyone point me in the right direction please?    Thanks in advance   Neil     ... View more

We have a Flume Agent running well currently...   agent1.sources.http-source.type = http agent1.sources.http-source.port = 8989   It is doing its job, but I was interested to know why it does not display as an open/listening port via the box standard NETSTAT Linux command?   Thanks in advance!   Neil ... View more