Collecting Elasticsearch based search-related MustGather data for search Ingest service issues
Prepare the following MustGather information before you call HCL Support to help with the troubleshooting process.
About this task
This MustGather can be used to investigate the cause of ElasticSearch-based Ingest issues. If you are trying to answer one of the following questions, this is the MustGather you will want to use:
- Why am I not seeing my catalog changes show up on the storefront after a full rebuild of the search index?
- Started a full rebuild of the search index, what is the status of this rebuild?
- Ran an automated full index rebuild , what are the results of this rebuild?
Procedure
-
Execute the following REST API to start the indexing job and save the
runId value from response for later use:
https://{{ingest_hostname_port}}/connectors/{{connectorId}}/run?storeId={{storeId}}&envType={{envType}} -
Execute the following REST API to get the current status for the ingest run
(using runId from 1):
https://{{ingest_hostname_port}}/connectors/{{connectorId}}/runs/{{runId}}/statusNote: If the ingest run is not completed, periodically execute the above request until it reports the ingest run is completed. -
Collect the responses for the following REST APIs:
https://{{ingest_hostname_port}}/connectors/{{connectorId}}/runs/{{runId}}/ https://{{ingest_hostname_port}}/connectors/{{connectorId}}/runs/ https://{{ingest_hostname_port}}/connectors/{{connectorId}}
What to do next
- Reviewing the data
- Ingest Connector Definition
- The connector definition defines the structure of the ingest pipeline, referencing the process groups and their variable settings. Validating the current version of the connector definition is essential to make sure you are using the expected version of an ingest pipeline.
- Ingest Connector Run History
- The ingest run history shows the latest runs against a given connector. This
can be used to identify the recent ingest runs and confirm if other ingest
runs have been performed since a particular run has been completed. For
example, here are the latest three runs displayed for a sample
connector:
{ "items": [ { "run": "i-6ac247a6-556e-471b-8272-eb4cd52c795b", "date": "2023-08-24T05:22:51.680Z" }, { "run": "i-2e5b30ce-8d92-41cc-9d68-9db94300cb68", "date": "2023-08-23T12:25:12.956Z" }, { "run": "i-18aea9f6-83ba-412e-9ef2-9e2e18f790a9", "date": "2023-08-23T12:17:55.759Z" } ], "offset": 0, "size": 3 }
- Ingest Run Log
- The ingest run log contains information related to a specific ingest run.
Any INFO, WARNING, or ERROR level log messages reported during the run will
be compiled in the run log and summarized by the Terminal Stage process
group. For example, at the start of the Terminal Stage output for this
ingest run, the locations and number of messages reported are
listed:
{ "items": [ ... { "_index": "log", "_type": "_doc", "_id": "bc6278c7-c8a0-4bbd-80cf-e2947e1f1a9e", "_score": null, "_source": { "date": "2023-07-25T07:17:10.874Z", "severity": "I", "reference": null, "code": "DI0003I", "connector": "auth.reindex.cas", "location": "Terminal Stage", "run": "i-f14729a2-2941-4ef4-95ba-c4159044964e", "type": "summary", "attributes": null, "source": null, "message": { "start": "2023-07-25T07:14:15.147Z", "end": "2023-07-25T07:17:09.621Z", "run": "i-f14729a2-2941-4ef4-95ba-c4159044964e", "locations": { "info": { "Attribute Schema": "1", "Catalog Schema": "1", "Category Schema": "1", "Description Schema": "1", "Inventory Schema": "2", "Page Schema": "1", "Price Schema": "2", "Store Schema": "2", "Store Stage 1 (Store Locations), Find Store Locations": "1", "Workspace Schema": "2" } },