Commit 0fd3693
committed
storage: fix services being nullified too late
If user tries to reconfigure vshard very often, it may happen, that
service didn't manage to notice, that it's cancelled, before
the new one is started. In such case the new fiber may encounter
assertion failure and will be restarted several times.
The approach, which makes the service nullification, when the current
one is the one stored globally was chosen, since with blocking service
cancellation reconfiguration of vshard may take huge amount of time.
The commit doesn't have test, because it applies the same approach,
which was introduced and tested for router in the previous commit.
Closes of #9
NO_DOC=bugfix
NO_TEST=<previous commit>1 parent 01fa577 commit 0fd3693
1 file changed
+12
-12
lines changed| Original file line number | Diff line number | Diff line change | |
|---|---|---|---|
| |||
1099 | 1099 | | |
1100 | 1100 | | |
1101 | 1101 | | |
1102 | | - | |
1103 | 1102 | | |
1104 | 1103 | | |
1105 | 1104 | | |
1106 | | - | |
1107 | | - | |
| 1105 | + | |
| 1106 | + | |
| 1107 | + | |
1108 | 1108 | | |
1109 | 1109 | | |
1110 | 1110 | | |
| |||
2320 | 2320 | | |
2321 | 2321 | | |
2322 | 2322 | | |
2323 | | - | |
2324 | 2323 | | |
2325 | 2324 | | |
2326 | 2325 | | |
2327 | | - | |
2328 | | - | |
| 2326 | + | |
| 2327 | + | |
| 2328 | + | |
2329 | 2329 | | |
2330 | 2330 | | |
2331 | 2331 | | |
| |||
2907 | 2907 | | |
2908 | 2908 | | |
2909 | 2909 | | |
2910 | | - | |
2911 | 2910 | | |
2912 | 2911 | | |
2913 | 2912 | | |
2914 | | - | |
2915 | | - | |
| 2913 | + | |
| 2914 | + | |
| 2915 | + | |
2916 | 2916 | | |
2917 | 2917 | | |
2918 | 2918 | | |
| |||
3463 | 3463 | | |
3464 | 3464 | | |
3465 | 3465 | | |
3466 | | - | |
3467 | 3466 | | |
3468 | 3467 | | |
3469 | 3468 | | |
3470 | | - | |
3471 | | - | |
| 3469 | + | |
| 3470 | + | |
| 3471 | + | |
3472 | 3472 | | |
3473 | 3473 | | |
3474 | 3474 | | |
| |||
0 commit comments