Impala will begin failing to read or write Kudu tables with errors in the Impala daemon logs resembling: Hosts where hostname only returns the short name, pass the command-line flag -hostname= fully_qualified_domain_name in the startup options of all Impala-related daemons. Workaround: Test if a host is affected by checking whether the output of the hostname command includes the FQDN. Even on systems with fixes for both of these issues, the workaround might still be required in some cases. Resolution: The issue is expected to occur less frequently on systems with fixes for IMPALA-4978, IMPALA-5253, or both. (See the issue "hostname parameter is not passed to Impala catalog role" at the Cloudera Manager Known Issues page.)
#Mem patch error could not get debug privilege are you admin upgrade#
This problem might occur immediately after an upgrade of a CDH cluster, due to changes in Cloudera Manager that supplies the -hostname flag automatically If the daemons cannot determine the FQDN, Impala does not start on a kerberized cluster. Return the fully qualified domain name, depending on the network configuration. The method Impala uses to retrieve the host name while constructing the Kerberos principal is the gethostname() system call.
0 kommentar(er)
