- Troubleshooting: Ingest start-up issues
If the default NiFi connectors were not properly created, restarting the Ingest service does not create them.
- Troubleshooting: Ingest service stops responding
If any business tasks are performed using Management Center for HCL Commerce before all NiFi connectors are created, then the Ingest service stops responding.
- Troubleshooting: ConnectionLoss error during first full index build
After the first full index build, the data-query service loses its connection to ZooKeeper. Characteristic error messages are written to the logs which allow you to diagnose and resolve this problem.
- Troubleshooting: Improving facet count accuracy
You can achieve more accurate facet counts. The process may result in slower performance in certain configurations.
- Troubleshooting: NiFi connector issues
If some or all of your connectors fail during Ingest service startup, you can refresh them or do a manual repair of individual connectors.
- Troubleshooting: Numerous NiFi "unable to write flowfile" messages
After deploying Version 9.1.14 updates, a large number of NiFi interface warnings are generated, stating that the system is unable to write flowfile contents due to archive file size constraints
. This issue can be resolved by changing the nifi.content.repository.archive.max.usage.percentage property in the nifi.properties file or setting it as an environment variable in the NiFi container.
- Troubleshooting: Index changes are not reflected in storefront after Elasticsearch push-to-live
In Version 9.1.4.0 only, you need to ensure that WCT+ESINDEX invalidation is triggered after a push-to-live operation. This ensures that index changes are reflected in the live store.
- Troubleshooting: Elasticsearch index build issues
Identify potential errors when building the HCL Commerce Search index using Elasticsearch.
- Troubleshooting: Errors in first CAS indexing run
You may encounter indexing errors when changing from the eSite indexing model to the Catalog Asset Store model. The solution is to delete the auth.workspace index and run the index again.
- Troubleshooting: CAS Ingest with 500+ stores loses Natural Language Processing (NLP) data
Catalog Asset Store Ingest with 500+ stores loses NLP data due to the Ingest process running out of scroll space in Elasticsearch.
- CAS ingest error for auth.validate.cas in 500- and 200-type stores
Running CAS ingest with 500- and 200-type stores, the auth.validate.cas
pipeline step shows errors with unmatched attributes.
- Troubleshooting: CustomFieldDocumentProcessor.java compilation error
Compiling with the same version of a commerce-search-processor
artifact as the search bundle project throws a compilation error.
- Troubleshooting: Errors when building default Catalog Asset Store 10501
When you index the default Catalog Asset Store 10501, it fails intermittently with a [FORBIDDEN/8/index write (api)]
error.
- Troubleshooting: indexing fails on Price Stage 1a (Database)
Indexing can fail when your catalog dataset is large, for example: 200,000+ catalog entries with multiple price lists. Distributed File System (DFS) configurations are particularly susceptible to this failure mode.
- Troubleshooting: queries failing after Docker Compose setup
In the Docker Compose environment, you may run a search Query while the Elasticsearch index is not yet available. When the index does become available, you receive the error message ** java.io.IOException: Unable to open "custom-ner-en_US.txt" as class path, filename or UR"
.
- Troubleshooting: auth.product pipeline causes Oracle PGA limit error
- Troubleshooting: Live storefront displays corrupt data or no data after performing Elasticsearch push-to-live operation
Push-to-live operation does not update the live store appropriately. On performing the push-to-live operation, the live storefront displays corrupt data or no data.
- Troubleshooting: Push-to-Live returns "Failed to produce invalidations" error
Extended sites that share the same master catalog fail during Push-to-Live (PTL).
- Troubleshooting: NRT update errors
On performing NRT update, NiFi UI and logs display errors.
- Troubleshooting: Solr fails to start after migrating to HCL Commerce Version 9.1
After migrating from HCL Commerce Version 9 to HCL Commerce Version 9.1, the search server fails to start.
- Troubleshooting: Data query log shows error CWWKS3005E
The logfile for the data-query service may show a CWWKS3005E error. This error has no effect on the processing of queries and can be ignored.
- Troubleshooting: Search index fails for newly created aurora esite
With a newly created an Aurora e-site store, the search index build can fail with a Null Pointer Exception (NPE) error.
- Troubleshooting: Live store does not show SKU price index updates
On a Live storefront, cached pages do not update in the storefront after changing a product SKU price and reindexing, even though the REST API shows that they have changed.
- Troubleshooting: Category with empty product storefront behavior
When a category is created in the Management Center without a product, it does not appear on the page menu.
- Troubleshooting: Standing up NiFi in Ubuntu
In the Ubuntu environment, when deploying NiFi it may fail to startup.
- Troubleshooting: NiFi warning messages while uploading catalog data
If the data load problems are experienced when loading 5000 or more products/ SKUs under a single category. The system provides warning messages for large data with data load NRT search index build during data load LOT testing.
- Troubleshooting: Out-of-storage issue with NiFi
The Nifi Content repository archives all the flow file content in the system. The purpose of archiving is so that the user can view or replay the content from the provenance user interface only for troubleshooting purposes.
- Troubleshooting: Ingest status "unknown' messages during build
During the postreindex stage of a full index run, the Ingest status is listed as "Unknown" numerous times.
- Troubleshooting: Facets visible but no search results
When the product name, SKU and description are unrelated, search terms will not show the product.
- Troubleshooting: Search Term Association issues in the extended language set
Search Term Association (STA) updates may not take effect immediately in the Authoring environment due to cached data from the Query service. Time-based invalidation for the STA cache can correct this behavior. To enable this, use the Data Query Configuration API to set the STA cache time-to-live to a desired value.
- Troubleshooting: Search gives 500 Internal server error when FacetPageSize is more than 1000
When a large number of attributes are enabled as searchable and the component configuration property FacetPageSize is set to a value above the default of 1000, search queries time out with a 500 internal server
error.
- Troubleshooting: Wildcard searches with NLP disabled
If you disable the Natural Language Processing (NLP) service, storefront users can still use wildcard characters in their searches. You can disable wildcards using a setting in the Zookeeper wc-component node.
- Troubleshooting: Missing custom NiFi processor dependencies
When creating a custom NiFi processor by extending the default Ingest processor in the NiFi Toolkit, one or more dependency errors can occur.
- Troubleshooting: "canapé"(sofa) term has 0 or empty result in French
Accented characters in certain search terms provide 0 or empty results.
- Troubleshooting: Changes to the header if English is not the default language
Make changes to the header if the language is not English while using postman.
- Troubleshooting: Slow search performance with 504 error
When too many business functions have been added to an Elasticsearch query, causing very high CPU utilization and long query response time from Elasticsearch.
- Troubleshooting : Validation pipeline error after triggering reverse pipeline on Auth
After triggering a reverse pipeline operation in the Authoring environment, a Severity E pipeline error is returned.