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

Support only CrateDB versions >= 4.2.0 #130

Open
chaudum opened this issue Nov 27, 2020 · 0 comments
Open

Support only CrateDB versions >= 4.2.0 #130

chaudum opened this issue Nov 27, 2020 · 0 comments
Labels
enhancement New feature or request

Comments

@chaudum
Copy link
Contributor

chaudum commented Nov 27, 2020

Due to missing AL privileges in CrateDB < 4.2 there is a workaround to RESET allocations via the client

async def reset_allocation(namespace: str, pod_name: str, has_ssl: bool) -> None:
"""
Reset all temporary node deallocations to none.
.. note::
Ideally, we'd be using the system user to reset the allocation
exclusions. However, `due to a bug
<https://github.com/crate/crate/pull/10083>`_, this isn't possible in
CrateDB <= 4.1.6. We therefore fall back to the "exce-in-container"
approach that we also use during cluster bootstrapping.

In newer CrateDB versions, this workaround is obsolete and could be removed.

@chaudum chaudum added the enhancement New feature or request label Nov 27, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

1 participant