Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Can't find a way to set the number of replicas for an Elasticsearch index #16453

Open
pvdbk opened this issue Jul 18, 2024 · 3 comments
Open
Milestone

Comments

@pvdbk
Copy link

pvdbk commented Jul 18, 2024

OrchardCore version : 1.8.2

Problem

Each time an Elasticsearch index is created, a replica is created with the index. In our case this replica is not supported, as we work with a single-node cluster.

Solution

The creation of index should be managed via an interface, as many features in Orchard. Most of the work is done by ElasticIndexManager.CreateIndexAsync. The logic implemented there is too complex to be safely reworked. It could be good to split this logic in several public methods.

Alternatives

No alternative was found for this problem. When you create an index in the administrator board, everything is managed by classes without interface. We could add a background task to remove the replicas, but we would prefer an other solution.

Copy link

Thank you for submitting your first issue, awesome! 🚀 We're thrilled to receive your input. If you haven't completed the template yet, please take a moment to do so. This ensures that we fully understand your feature request or bug report. On what happens next, see the docs.

If you like Orchard Core, please star our repo and join our community channels.

@sebastienros
Copy link
Member

The creation of index should be managed via an interface

Or maybe it should be exposed in an Elasticsearch specific setting.

@sebastienros sebastienros added this to the 2.x milestone Jul 18, 2024
Copy link

We triaged this issue and set the milestone according to the priority we think is appropriate (see the docs on how we triage and prioritize issues).

This indicates when the core team may start working on it. However, if you'd like to contribute, we'd warmly welcome you to do that anytime. See our guide on contributions here.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants