failover: add failover priority replica option #478
Closed
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
Instead of the extra return {
sharding = {
['cbf06940-0790-498b-948d-042b62cf3d29'] = {
replicas = {
['8a274925-a26d-47fc-9e1b-af88ce939412'] = {
name = 'storage_1_a',
master = true,
failover_priority = 1
},
['3de2e3e1-9ebe-4d0d-abb1-26d301b84633'] = {
name = 'storage_1_b',
failover_priority = 2
},
['001688c3-66f8-4a31-8e19-036c17d489c2'] = {
name = 'storage_1_c',
failover_priority = 3
}
},
}
}
}In my opinion it's better not to manage with the duplicates of the replica sets and replicas UUIDs and to specify the failover priorities near the definition. Also I haven't found the corresponding issue yet. |
Add the `failover_priority` config option in the `sharding.<replicaset_id>.replicas.<replica_id>` section. Using the option you may specify the order failover will connect to the replicas. The lower the value, the higher the priority of the replica. The current replica priority: `replica's failover priority > weight of the replica's zone > is replica a master > order in the sharding configuration`. @TarantoolBot document title: failover priority per-replica option Now you can specify failover priority for the replica using the `failover_priority` property when descriping replicas in sharding section. The lower the value, the higher the priority of the replica. The failover will try to select an available replica with the highest priority out of all. Example: ```lua sharding = { ['cbf06940-0790-498b-948d-042b62cf3d29'] = { replicas = { ['8a274925-a26d-47fc-9e1b-af88ce939412'] = { master = true, failover_priority = 1 }, ['3de2e3e1-9ebe-4d0d-abb1-26d301b84633'] = { failover_priority = 3 }, ['001688c3-66f8-4a31-8e19-036c17d489c2'] = { failover_priority = 2 } }, } } ``` The config specifies three replicas. By default the master will be used. If it stops working failover will select `001688c3-...` as a new replica. To calculate the replica priority in case of the equal `failover_priority` values. with the same values of the properties the following heuristics are used: * The replica's failover priority. * The weight of the replica's zone. * The master status of the replica. * The order of the replicas in the sharding configuration.
georgiy-belyanin
force-pushed
the
replica-failover-priority
branch
from
85a32eb to
57b1a64
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Add the
failover_priorityconfig option in the]sharding.<replicaset_id>.replicas.<replica_id>section.Using the option you may specify the order failover will connect to the replicas. The lower the value, the higher the priority of the replica.