Impala Error updating the catalog due to lock contention

[#1]

Hello,

We are observing error in Impala Catalouge Logs as below

EI1101 14:52:24.768759  8438 jni-util.cc:308] org.apache.impala.common.InternalException: Error updating the catalog due to lock contention.
        at org.apache.impala.service.CatalogOpExecutor.updateCatalog(CatalogOpExecutor.java:3474)
        at org.apache.impala.service.JniCatalog.updateCatalog(JniCatalog.java:308)
I1101 14:52:24.768983  8438 status.cc:125] InternalException: Error updating the catalog due to lock contention.
    @           0x9812da
    @           0xd37e2f
    @           0x970728
    @           0x960e7f
    @           0xa1f263
    @           0xa1752f
    @           0x948d4a
    @           0xb420c9
    @           0xb39fc9
    @           0xb3adc2
    @           0xdab24f
    @           0xdaba4a
    @          0x13346fa
    @     0x7fb75bf7cea5
    @     0x7fb75bca59fd

CM / CDH - 5.16.2

Appericate any assistacne / guidance in fixing this issue.

Thanks 

Wert

[#2]

Hi @wert_1311 ,

Seems to be "load_catalog_in_background" option is set to true in your cluster, 

This can result in lock contention.  The recommended value for this parameter is false.  Please change the value to False and see if this helpful.

And if you are also seeing any JVM pauses in the catalog logs try to increase the catalog heap size and monitor the cluster.

https://docs.cloudera.com/documentation/enterprise/5-16-x/topics/impala_config_options.html

Regards,

Chethan YM 

Was your question answered? Make sure to mark the answer as the accepted solution.

If you find a reply useful, say thanks by clicking on the thumbs up button.

[#3 · Accepted solution]

Hi @ChethanYM 

load_catalog_in_background is unchecked, we were not observing any JVM pauses in Catalogue Logs, however, we were seeing RPC related alerts, we have restarted Impala and the issue seems to have been fixed.

Thanks 

Wert