Catalog Search reindex fails in Adobe Commerce
Catalog Search reindexing fails in Adobe Commerce, leaving the catalogsearch_fulltext indexer in a Reindex Required or stalled state. Search results don’t reflect recent catalog updates, and indexing operations return OpenSearch-related errors. To fix this issue, verify the indexer status, confirm the OpenSearch configuration, and validate cron jobs before rerunning the Catalog Search index.
Description description
Environment
- Adobe Commerce 2.4.x
- Adobe Commerce on Cloud Infrastructure
- OpenSearch
Issue/Symptoms
- Catalog Search remains in a Reindex Requiredstate after indexing attempts.
- The
catalogsearch_fulltextindexer fails to complete reindexing operations. - Search results do not reflect recent catalog updates or remain incomplete.
- Indexing operations return errors such as
Index is locked by another process, Fail in child process,orcircuit_breaking_exception. - Search functionality becomes unavaliable after catlog updates
Cause
Catalog Search reindexing fails when Adobe Commerce can’t complete thecatalogsearch_fulltext indexing process due to OpenSearch configuration issues, indexing locks, cron failures, OpenSearch resource constraints, or extension-related errors.
Resolution resolution
Follow these steps to resolve the issue
-
Verify the status of the Catalog Search indexer by running
bin/magento indexer:statusand reviewing the status ofcatalogsearch_fulltext. If the indexer shows Reindex Required, continue with the remaining troubleshooting steps. -
Confirm that Adobe Commerce uses
OpenSearchas the search engine by runningbin/magento config:show catalog/search/engine. Verify that the command returnsopensearch. -
Run a manual reindex using
bin/magento indexer:reindex catalogsearch_fulltext. After the command completes, verify that storefront search returns the expected results. -
Reset the Catalog Search indexer if it remains stuck or continues to report Reindex Required. Run
bin/magento indexer:reset catalogsearch_fulltext,then rerunbin/magento indexer:reindex catalogsearch_fulltext.Note: Resetting an indexer only resets its status within Adobe Commerce. It doesn’t delete OpenSearch indexes or remove catalog data.
-
Verify that cron jobs execute correctly by running bin/magento cron:run. Confirm that scheduled indexing processes run successfully and complete pending indexing tasks.
-
Review the exact error message if reindexing still fails.
- If Catalog Search remains in Reindex Required, verify cron functionality, run a manual reindex, and reset the indexer if necessary.
-
Check whether the error message shows Index is locked by another process.
- Verify that no indexing process is currently running.
- Reset the affected indexer.
- Retry the reindex.
-
Check whether the error message shows Fail in child process.
- Review the exception logs.
- Verify whether OpenSearch-related errors are present.
- This error is typically a symptom rather than the root cause of the failure.
- Contact Adobe Support if the issue persists.
-
Check whether the error message shows
circuit_breaking_exceptionor[parent]Data too large.- Review any available OpenSearch-related error messages.
- Contact Adobe Support for further investigation.
-
If search results remain incomplete after reindexing:
- Verify the search engine configuration.
- Verify the Catalog Search indexer status.
- Flush caches if necessary.
-
Do not delete OpenSearch indexes as a first troubleshooting step.
- Adobe Commerce can recreate search indexes during a reindex operation.
- Deleting indexes does not resolve underlying issues such as OpenSearch resource constraints, OpenSearch health issues, OpenSearch connectivity issues, or failed indexing operations.
- If the root cause is related to OpenSearch health or infrastructure, rebuilding indexes fails for the same reason.
-
Contact Adobe Supportif the issue continues.
- Catalog Search reindexing consistently fails.
- The indexer remains stuck after being reset.
- OpenSearch-related errors appear during indexing.
- Search functionality remains unavailable after reindexing.
- The issue is isolated to a specific environment.
- The root cause cannot be identified by using the troubleshooting steps above.
Include the following information:
- Output from
bin/magento indexer:status - Output from
bin/magento config:show catalog/search/engine - Relevant exception logs
- The exact error message returned during reindexing
- Steps already performed during troubleshooting