DataHub v1.2.0 - Slow performance when hard delete and restoring indices

[chenteddybear]

I recently tested DataHub v1.2.0 and found it noticeably slower than v1.1.0 when hard-deleting aspects and restoring indices—around 3–4 times slower in the Docker deployment. Additionally, there seems to be an issue with index restoration: the process gets stuck in the “building” phase while the index storage size keeps increasing, causing Elasticsearch to enter a loop.

[yoonhyejin]

Hello, thanks for raising the issue! Could you share any related logs from Elasticsearch or the deletion process, if available?

[chenteddybear]

Hi, sorry I no longer have the log for you. This is the yaml file i used to deploy datahub v1.2.0 docker: https://github.com/datahub-project/datahub/blob/master/docker/quickstart/docker-compose-without-neo4j-m1.quickstart.yml

I noticed it uses new version for cp-schema-registry, cp-kafka, and cp-zookeeper.