You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
After #1336, we've changed the underlying API that YugaWare uses to figure out if a universe is back to a balanced state.
While this new API guarantees that a client will stop exactly when the load balancer no longer does work, it has a small caveat that, if called before the load balancer even begins doing any work, it might get back an early OK, that the cluster is balanced, because it does not yet know of the incoming work it is supposed to start doing.
The text was updated successfully, but these errors were encountered:
Summary:
Adding a 10 second timeout before querying the load balancer to check if the load has been
balanced. This can prevent the condition of YW querying the load balancer before it even starts the
task, resulting it to return instantly.
Test Plan: Tested by creating a universe, running a load and then adding a couple of nodes and verifying that the load is balanced on completion of the edit universe.
Reviewers: bogdan
Reviewed By: bogdan
Subscribers: yugaware
Differential Revision: https://phabricator.dev.yugabyte.com/D6931
After #1336, we've changed the underlying API that YugaWare uses to figure out if a universe is back to a balanced state.
While this new API guarantees that a client will stop exactly when the load balancer no longer does work, it has a small caveat that, if called before the load balancer even begins doing any work, it might get back an early OK, that the cluster is balanced, because it does not yet know of the incoming work it is supposed to start doing.
The text was updated successfully, but these errors were encountered: