Submit Feedback
Legacy Knowledge Base
Published Jun. 30, 2025

Re-enabling CCR, errors appear indicating that an open index with the same name already existed

Written By

Julián Vela Cubas

How To articles are not official guidelines or officially supported documentation. They are community-contributed content and may not always reflect the latest updates to Liferay DXP. We welcome your feedback to improve How To articles!

While we make every effort to ensure this Knowledge Base is accurate, it may not always reflect the most recent updates or official guidelines.We appreciate your understanding and encourage you to reach out with any feedback or concerns.

Legacy Article

You are viewing an article from our legacy "FastTrack" publication program, made available for informational purposes. Articles in this program were published without a requirement for independent editing or verification and are provided"as is" without guarantee.

Before using any information from this article, independently verify its suitability for your situation and project.

Issue

  • In a CCR scenario where the leader cluster is down and the system continues operating by reading and writing to the follower after disabling CCR, an HTTP/1.1 500 Internal Server Error occurs when attempting to re-enable CCR after communication with the leader cluster is restored.

  • [HTTP/1.1 500 Internal Server Error]
    {"error":{"root_cause":[{"type":"snapshot_restore_exception","reason":"[_ccr_xxx:_latest_/_latest_] cannot restore index [liferay-303371-workflow-metrics-transitions] because an open index with same name already exists in the cluster. Either close or delete the existing index or restore the index under a different name by providing a rename pattern and replacement name"}],"type":"snapshot_restore_exception","reason":"[_ccr_xxx:_latest_/_latest_] cannot restore index [liferay-303371-workflow-metrics-transitions] because an open index with same name already exists in the cluster. Either close or delete the existing index or restore the index under a different name by providing a rename pattern and replacement name"},"status":500}

Environment

  • Liferay DXP for Elasticsearch versions 7 and above.
  • A LES license is necessary to enable CCR feature.

Resolution

  • Once the communication of the 'Leader' cluster is restored, we delete the cluster index using the following command:
  • curl -X DELETE "http://${nodo_leader}:9200/_all"

Additional Information

 

Did this article resolve your issue ?
Legacy Knowledge Base
Did this article resolve your issue ?