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

How do you check hive meta store version on Cloudera? ... 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

@Jay2021  Impala and hive share metadata catalog ie Hive MetaStore , when a database/table is created in HIVE it's readily available for hive users but not Impala! To successfully query a table or database created in HIVE there is a caveat you need to run the INVALIDATE METADATA from the impala-shell before the table is available for Impala queries. INVALIDATE METADATA reloads all the metadata for the table needed for a subsequent query  The next time the current Impala node performs a query against a table whose metadata is invalidated you definitely will run into errors you could use the REFRESH in the common case where you add new data files for an existing table it reloads the metadata immediately, but only loads the block location data for newly added data files, making it a less expensive operation overall. INVALIDATE METADATA [[db_name.]table_name] Example   $ impala-shell > INVALIDATE METADATA new_db_from_hive.new_table_from_hive; > SHOW TABLES IN new_db_from_hive; +---------------------+ | new_table_from_hive | +---------------------+   That should resolve your issue Happy hadooping ... View more