Design Documentation For Elasticsearch
(Doc ID 2694261.1)
Last updated on MARCH 23, 2022
Applies to:Oracle Communications Messaging Server - Version 8.1.0 and later
Information in this document applies to any platform.
Conversations that have occurred about Elasticsearch have involved questions being asked about plans to configure the index and things similar to that.
It is assumed that those things are performed by stored when it first starts up with Elasticsearch configured.
The only option that customers have access to set is numshards.
It seems the “normal” use of Elasticsearch involves someone designing how it will be used.
It would be helpful to have a say in this design phase and would expedite this whole process if those details about Elastic were shared.
Is there any documentation available that would assist a Messaging Server customer who plans to use Elasticsearch, that could be handed to an Elasticsearch architect to only have to answer questions related to email delivery/access rates and not the general design of what is Elasticsearch going to be used for, etc.? We are basically looking for design documentation for Elasticsearch.
To view full details, sign in with your My Oracle Support account.
Don't have a My Oracle Support account? Click to get started!
In this Document