-
Notifications
You must be signed in to change notification settings - Fork 3.8k
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
cli: don't allow balancer to be specified via command line flags #4732
Comments
If we're going to remove this flag, that is going to have consequences for testing cockroach with multiple nodes on a single machine (which is the reason this flag was added in the first place). There are a few ways to do this:
Additionally, I don't know if we'll ever have an "automated approach" for this use case; this flag was intended for developers to try out alternative balance strategies, and while it initially is only used to solve the "multi-node, same hard drive" conundrum, it could eventually allow developers to compare different algorithms without needing special builds. Instead, I think it should moved to gossiped cluster configuration; the main problem with this flag is that it's a cluster-wide setting, not a per-node setting, and thus makes no sense as a command line argument. |
@BramGruneir is working on the second option, to be able to cap the size of each store. |
@spencerkimball I'm fine with removing the flag, we just need to pick an alternative solution for the problem it was solving. It looks like we're going to go with solution #2. |
Just a head's up that the maximum size work will be done by end of week. |
@BramGruneir should this be closed? |
As soon as I get the size changed merged. On Sun, Mar 6, 2016 at 1:26 PM, Spencer Kimball notifications@github.com
|
|
Choosing between usage and range-count for rebalancing decisions is not something we should expect operators to specify on the command line. Let's choose the appropriate default for now and then move towards an automated approach.
@jseldess don't document the
--balance_mode
flag.The text was updated successfully, but these errors were encountered: