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
Is your feature request related to a problem? Please describe.
Currently, when performing a stoppable check, users are required to specify the selection base (zone_based, cross_zone_based, or non_topo_based). This adds an unnecessary burden on users and increases the potential for errors. A more efficient approach would be for the server to automatically determine the appropriate selection base by reading the cluster configuration.
Describe the solution you'd like
The server should automatically configure the selection base based on the cluster's topology. By default, if the cluster has no defined topology, the server should use non_topo_based. If a topology is present, the server should default to cross_zone_based. This would simplify the user experience and minimize configuration errors.
Here’s a revised version of your message for improved clarity and professionalism:
Additional context
Add any other context or screenshots about the feature request here.
The text was updated successfully, but these errors were encountered:
Is your feature request related to a problem? Please describe.
Currently, when performing a stoppable check, users are required to specify the selection base (
zone_based
,cross_zone_based
, ornon_topo_based
). This adds an unnecessary burden on users and increases the potential for errors. A more efficient approach would be for the server to automatically determine the appropriate selection base by reading the cluster configuration.Describe the solution you'd like
The server should automatically configure the selection base based on the cluster's topology. By default, if the cluster has no defined topology, the server should use
non_topo_based
. If a topology is present, the server should default tocross_zone_based
. This would simplify the user experience and minimize configuration errors.Here’s a revised version of your message for improved clarity and professionalism:
Additional context
Add any other context or screenshots about the feature request here.
The text was updated successfully, but these errors were encountered: