failover: issue network partitioning alert
Nobody has claimed this yet.
Assessment
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Newbie friendliness
- 68/100
- Issue type
- Documentation
- Clarity
- Mostly clear
- Activity status
- Active
- Domain
- documentation
Research direction
Start by reviewing the coordinator's alerts field under the state key /failover/info/by-uuid/ and the described network-partitioning behavior. Document the warning and error timing, alert fields, withdrawal condition, and example message so the published documentation matches the stated behavior.
Written by the indexing model from the issue text.
Description
Since: 3.9.0
The coordinator reports its alerts in the alerts field of its state
key in the stateboard, <prefix>/failover/info/by-uuid/<uuid>.
The network partitioning alert is issued when alive instances of a
replicaset exchange no data with their master, directly or through
other members, while the coordinator reaches them. It carries
replicaset_name, master_name and disconnected (the names of the
instances). It is a warning (type: warn) once the situation is
confirmed by the next monitoring probe of the instances (about
failover.probe_interval later) and an error (type: error) once it
lasts for at least failover.lease_interval. The alert is withdrawn when
the data flows again.
Requested by @georgiy-belyanin in https://github.com/tarantool/tarantool-ee/commit/b669f7a99cf4d591eb1af68ff09445c481bca673.
Example (how it looks like in etcd):
active: true
term: 3
uuid: e5c1a4b2-7f3d-4c8e-9a1b-2d6f0e8c3b71
hostname: coordinator-1
pid: 41237
alerts:
- timestamp: 2026-09-28T12:32:47.871002+0300
master_name: i-004
type: error
disconnected:
- i-005
- i-006
message: 'The master "i-004" of the replicaset "r-002" exchanges no data with 2
of its 2 alive peers (i-005, i-006), while the coordinator reaches all of them:
the network may be partitioned between the peers or the replication may be broken.
A client that reaches only a part of the replicaset may be unable to write.'
replicaset_name: r-002
- Dominant language
- CSS
- Stars
- 15
- Forks
- 49
- Avg merge
- 2d 2h
- Merged PRs (30d)
- 1
Getting set up
- No Dockerfile or Docker Compose file
- No pull request template
- Read the contributing guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from tarantool/doc
-
c api
Difficulty 1/5 1-3 hours Newbie friendliness 74/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
-
memcs
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
Similar issues
-
Difficulty 1/5 Under an hour Newbie friendliness 82/100
-
bug
Difficulty 1/5 Under an hour Newbie friendliness 88/100
openwisp/openwisp-utils#777 ·
-
Difficulty 1/5 Under an hour Newbie friendliness 75/100
RustCrypto/SSH#596 ·
-
Translation TwigBridge
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
symfony/symfony-docs#23308 ·
Maintainers usually reply within 3 days
-
sync-en
Difficulty 1/5 Under an hour Newbie friendliness 84/100
Maintainers usually reply within 1 day