question Re: Anyone knows how to disable the replication of table column statistics? in Support Questions

Anyone knows how to disable the replication of table column statistics?

DNADatangineer — Tue, 21 Apr 2026 07:48:08 GMT

I found the problem while i run the hive BDR and it took 2 hours.

Cloudera support inform us that's the bug and workaround is to disable

The possible way to work around is to disable the replication of table column statistics but we don't know how?

Anyone has idea?

This slowness is most probably because of a fix (OPSAPS-62843) that was introduced in 7.1.7 SP1 to have a hotfix of a functional error (reported in ENGESC-8654), but having the disadvantage of decline in performance.

The performance decline has already been reported and discussed in several other escalations, e.g. ENGESC-15274.

So the possible ways to go forward with the solution is

---> to wait until the fix for the performance decline (OPSAPS-65104) gets released,

---> or to apply a workaround on the nodes of the target cluster that would disable the replication of table column statistics, but would enhance the performance. For that the file /opt/cloudera/cm-agent/service/dr/chive.sh would have to be modified on each node of the target cluster.

Thank you,

Re: Anyone knows how to disable the replication of table column statistics?

paras — Thu, 29 Dec 2022 12:27:03 GMT

This issue would be fixed in our upcoming release. You can check for a hotfix.

You can try adding the below workaround as well to see if performance improves.

a. On the target cluster, Go to CM-> Hive-> Configuration
b. Add "HIVE_REPL_STATS_ENGINE=hive" to the "Hive Replication Environment Advanced Configuration Snippet (Safety Valve)" configuration .

Hope this helps,
Paras
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.

Re: Anyone knows how to disable the replication of table column statistics?

DianaTorres — Tue, 10 Jan 2023 17:00:24 GMT

@DNADatangineer Has the reply helped resolve your issue? If so, please mark the appropriate reply as the solution, as it will make it easier for others to find the answer in the future. Thanks