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

Aliases usage/sizing guidance & scaling limits #104456

Open
DaveCTurner opened this issue Jan 17, 2024 · 1 comment
Open

Aliases usage/sizing guidance & scaling limits #104456

DaveCTurner opened this issue Jan 17, 2024 · 1 comment
Labels
:Data Management/Indices APIs APIs to create and manage indices and templates >enhancement Team:Data Management Meta label for data/management team

Comments

@DaveCTurner
Copy link
Contributor

As we adapt Elasticsearch to larger and larger clusters (see e.g. #77466) I've noticed something of an upwards trend in issues related to high alias counts. I've particularly noticed cases where the user has many (thousands or more) aliases pointing to a single index, whereas the implementation in Elasticsearch is more targetted towards situations where there are relatively few aliases each of which points to a large number of indices.

I don't think we have any docs that give guidance about alias usage or sizing, nor do we have any safety limits on alias counts, and this makes it hard for users to design their system to use aliases in Elasticsearch appropriately.

@DaveCTurner DaveCTurner added >bug :Data Management/Indices APIs APIs to create and manage indices and templates labels Jan 17, 2024
@elasticsearchmachine elasticsearchmachine added the Team:Data Management Meta label for data/management team label Jan 17, 2024
@elasticsearchmachine
Copy link
Collaborator

Pinging @elastic/es-data-management (Team:Data Management)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
:Data Management/Indices APIs APIs to create and manage indices and templates >enhancement Team:Data Management Meta label for data/management team
Projects
None yet
Development

No branches or pull requests

3 participants