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
There are configuration values in Refinery, such as the GoalThroughputPerSec value used by the TotalThroughputSampler, that are calculated based on the value for a single instance, but the customer experience is to see refinery as an entire cluster. Can we find a way to allow these values to be adjusted by refinery based on the number of peers in the cluster?
This makes it easier to think about as well as meaning that the value wouldn't have to be adjusted when cluster size changes.
The text was updated successfully, but these errors were encountered:
## Which problem is this PR solving?
- Throughput samplers now have an extra flag, `UseClusterSize`, which
causes the `GoalThroughputPerSec` to be divided by the number of
Refinery nodes in the cluster. This way, when cluster size changes, the
configuration doesn't need to be changed.
## Short description of the changes
- Add the flag to the config
- Update metadata for the new flag
- Add code to 3 throughput samplers to support it
- Write tests to verify it works
- Regenerate docs
Fixes#533.
Fixes#608.
There are configuration values in Refinery, such as the GoalThroughputPerSec value used by the TotalThroughputSampler, that are calculated based on the value for a single instance, but the customer experience is to see refinery as an entire cluster. Can we find a way to allow these values to be adjusted by refinery based on the number of peers in the cluster?
This makes it easier to think about as well as meaning that the value wouldn't have to be adjusted when cluster size changes.
The text was updated successfully, but these errors were encountered: