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

Cache node should gracefully handle over-provisioned LRU cache configs #673

Open
bryanlb opened this issue Sep 11, 2023 · 1 comment
Open
Labels
enhancement New feature or request operations

Comments

@bryanlb
Copy link
Contributor

bryanlb commented Sep 11, 2023

Description

By default Lucene allocates 32MB of ram for a LRU cache for each instance. When allocating very large amounts of cache slots (ie, 200, 500) this can represent a very large demand on memory required.

If insufficient ram is allocated to the machine, it will eventually crash with a failed socket / healthcheck (not an OOM). This is because the GC will more aggressively attempt to reclaim memory until the healthcheck becomes too slow.

We should ideally immediately fatal error the cache boot process if the allocated JVM memory is insufficient for the configured LRU cache + cache slot configuration.

@bryanlb bryanlb added the enhancement New feature or request label Sep 11, 2023
Copy link

This issue is stale because it has been open 180 days with no activity. Remove stale label or comment or this will be closed in 30 days.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request operations
Projects
None yet
Development

No branches or pull requests

1 participant