Is using OpenSearch with Multi-Cluster Offload a validated configuration for dataminer?
Attempted to switch priorities to put the OpenSearch priority = 0 and the Elasticsearch priority = 1, still same mapping error occurred. I connected each databases in a single offload normal db.xml configuration to each cluster and both work fine separately. Just not working for multi-offload for some reason.
Hi Michael,
Is this the setup you had in mind: https://docs.dataminer.services/user-guide/Advanced_Functionality/Databases/Indexing_database/OpenSearch_Database/Configuring_multiple_OpenSearch_clusters.html?
If so, yes, it is
This customer is running a local Elastic node on 6.8.X and is now trying to add an additional OpenSearch cluster consisting of 8 remote Linux nodes. After configuring the DBConfiguration.xml file in the Databases folder we are receiving the following error.
Attempt 1/10 failed with exception: Elasticsearch.Net.ElasticsearchClientException: The remote server returned an error: (400) Bad Request.. Call: Status code 400 from: PUT /_template/dma_43201-logentries. ServerError: Type: mapper_parsing_exception Reason: “Failed to parse mapping [_doc]: Root mapping definition has unsupported parameters:
Hi Ryan,
Could you create a new question specifically for this issue? That way our Elasticsearch/OpenSearch experts will be able to pick it up.
I wonder if offloading to Elastic 6.8 and OpenSearch 2.11 clusters simultaneously will cause mapping issues. We currently have priority = 0 to the existing local elastic and priority = 1 to the newly installed remote OpenSearch cluster.