-
Notifications
You must be signed in to change notification settings - Fork 1.1k
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
Not able to scale down a docker cluster gracefully #112
Labels
kind/bug
This issue is a bug
Comments
@ttyusupov - is this related to your recent fix? Do we just need to publish a new container? |
Yes, looks like #97 which has been already fixed. |
mbautin
pushed a commit
that referenced
this issue
Jun 20, 2019
tvesely
pushed a commit
to tvesely/yugabyte-db
that referenced
this issue
Feb 28, 2024
Currently, parallel hints on single relations cannot be enforced properly without the GUCs related to parallelism to be reset first. Perhaps there is not much of a use-case when it comes to that, but let's add some regression tests to check this default behavior, as there was nothing to check that in the existing test suite. Per pull request yugabyte#112. Backpatch-through: 10
devansh-ism
pushed a commit
to devansh-ism/yugabyte-db
that referenced
this issue
Jul 17, 2024
Resolves yugabyte#112.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Hitting an assert on scaling down a docker container based cluster.
All the nodes go down. The error from any one container:
Version:
The text was updated successfully, but these errors were encountered: