Saw the same issue and debug it by adding Java option  -Dsun.security.krb5.debug=true In the logs, I found the IP address of KDC is shown instead of the hostname. That's suspicious. So I tried adding the IP -> hostname mapping of the KDC server in /etc/hosts. It resolved the issue. There could be other causes for your issue. The debug logs can show you more clues. ... View more

Same issue as https://issues.apache.org/jira/browse/IMPALA-10756 We are working on https://issues.apache.org/jira/browse/IMPALA-10871 to fix this. Before that, please use CDP Hive (recommended) or Apache Hive 4. ... View more

CDH 5.11 and Impala 2.8 is pretty old. You should try the latest versions.   In the logs, there is one failed fragment instance and one timeout fragment instance. The failed one is on host hadoop-slave22.use1.data.ripple.com. You should check impalad logs on it for more details. The timeout one has instance_id=d6447c0a5ed591c4:47ac77680000001b. The first part (d6447c0a5ed591c4) is the same for this query. The last part (47ac77680000001b) is the id of the fragment instance. You can check previous logs to see where this instance is scheduled. Then check impalad logs of the scheduled host. Usually this might due to network saturation. Later Impala versions have more RPC improvements, e.g. KRPC. ... View more

As mentioned in the error message, you should check the catalog server log (catalogd.INFO) for more details. Usually it will explain why it failed to load the file metadata. ... View more