Hi @Iga21207 ,   So how it works in catalod is when you run any refresh commands then that is executed sequentially and once that is completed then it goes to next one. It doesn't run in parallel as per the catalogd which is a single threaded operation. There is a lock that catalogd thread creates on class getCatalogObjects().   So when you are refreshing(means they have not completed yet sequentially) and after that when the new request came in then the Catalog threw the error on that table as it can't get the lock because the lock is already there on previous table on which the refresh command was running.   Not sure on your CDH version, This may resolved in Higher version of CDP/CDH.   Note: If i answered your question please give a thumbs up and accept it as a solution.   Regards, Chethan YM     ... View more

Hi,   After you run the query you need to look at the query profile to analyse the complete memory. look for “Per node peak memory usage” in the profile to understand how much memory each host or impala daemon used to run this query.   For above snippet from your side it looks like this query has the 3gb max limit to run the query, this can be set at session level or in impala admission control pool. If you provide the complete query profile i think we can get more details. Regards, Chethan YM   ... View more