|
Ran
|
Jobs
1
|
Files
519
|
Run time
2min
|
Badge
README BADGES
|
push
github
limbo: make txn_limbo_confirm nop during fencing Before this patch a synchronous transaction could be confirmed when user lowered `replication_synchro_quorum` while limbo is in the frozen state. It could lead to the next situation: 1) server1 loses a quorum of connections and its limbo goes into the frozen state. 2) The new elected master rollbacks a non-confirmed synchronous transaction. 3) On the old master we lower `replication_synchro_quorum` to 1. Our synchronous transaction is confirmed because our node can collect sufficient number of acks. As a result, we have inconsistent state in the replicaset because on the old master we have a confirmed transaction but on the new master we have a rolledbacked transaction. Now, we fix this issue by returning from the `txn_limbo_confirm` when `txn_limbo_is_frozen` is true. It can help us to make the `txn_limbo_confirm` - nop and not confirm synchronous transactions. Needed for tarantool#11574 NO_DOC=bugfix NO_CHANGELOG=<not released> (cherry picked from commit 51999396d)
68783 of 116357 branches covered (59.11%)
2 of 2 new or added lines in 1 file covered. (100.0%)
207 existing lines in 9 files now uncovered.103494 of 118188 relevant lines covered (87.57%)
1598442.99 hits per line
| Lines | Coverage | ∆ | File |
|---|---|---|---|
| 1 |
95.84 |
-0.12% | src/box/replication.cc |
| 2 |
94.68 |
-1.06% | src/box/vy_range.c |
| 2 |
94.25 |
-0.41% | src/box/vy_read_iterator.c |
| 2 |
97.15 |
-0.2% | src/lib/msgpuck/msgpuck.h |
| 3 |
90.58 |
-0.15% | src/box/applier.cc |
| 3 |
92.39 |
-0.05% | src/box/vinyl.c |
| 5 |
86.96 |
-0.34% | src/box/vy_run.c |
| 22 |
97.28 |
0.0% | src/box/lua/net_box.c |
| 167 |
91.2 |
0.52% | src/box/box.cc |
| ID | Job ID | Ran | Files | Coverage | |
|---|---|---|---|---|---|
| 1 | 19540285022.1 | 519 |
87.57 |
GitHub Action Run |
| Coverage | ∆ | File | Lines | Relevant | Covered | Missed | Hits/Line | Branch Hits | Branch Misses |
|---|