@kvbigdata  What happens if you set Cloudera Manager > Hive > Configuration > Service Monitor Client Config Overrides > Add Name: hive.metastore.client.socket.timeout Value: 600 We have provided the below information regarding the current situation of the canary jira . https://my.cloudera.com/knowledge/quotError--The-Hive-Metastore-canary-failed-to-create-a?id=337839   You have only one workaround ,that is to disable the canary test as you already did currently and that will not harm anything on your cluster . Currently the workaround is to disable the Canary tests on the HMS.    # Access HIve Service # Configuration Tab >> Look for Hive Metastore Canary Health Test # Uncheck the box # Restart the service.   ... View more

GM Asish... Thanks for sharing difference between two parameter. Will take note on  tez.task.resource.memory.mb should be set < hive.tez.container.size    Appreciate for your support.   Regards, Pankaj shivankar ... View more

@drgenious    1. Impala is always faster. Impala does not use yarn. Impala stores catalog data locally which fetches information faster. Impala backend gthread is built on C++ which is very fast. 2. Impala is not fault tolerant , it is best suited for adhoc queries and ETL is best suited for Hive as Hive is fault tolerant. If the query fails due to network/disk failure,hive will retry but Impala would fail. 3. For stemaming/ingestion like Kafka flow you need to put it in EXTERNAL tables not in Managed(ACID) tables. Managed tabled can be used,if you want to perform alteration of the data like Update/Delete . Please let me know,if you have any queries. Please click "Accept As Solution" , if your query is answered. ... View more