Commit eeeda62
committed
Log partition processor effective-leadership readiness and bootstrap duration
become_leader runs synchronous initialization (invoker construction,
active-lock load, a legacy invocation-status scan, actuator setup,
durability read) before the partition transitions to effective
leadership. There was no info-level signal marking that transition or
how long it took to get there -- only a coarse, scrape-interval-limited
gauge and a debug-only "resumed invocations" line. Add one structured
INFO log at the readiness point, with the epoch and elapsed bootstrap
duration, so failover latency can be measured from logs.1 parent 061157b commit eeeda62
1 file changed
Lines changed: 10 additions & 2 deletions
| Original file line number | Diff line number | Diff line change | |
|---|---|---|---|
| |||
24 | 24 | | |
25 | 25 | | |
26 | 26 | | |
27 | | - | |
| 27 | + | |
28 | 28 | | |
29 | 29 | | |
30 | 30 | | |
| |||
458 | 458 | | |
459 | 459 | | |
460 | 460 | | |
| 461 | + | |
461 | 462 | | |
462 | 463 | | |
463 | 464 | | |
| |||
715 | 716 | | |
716 | 717 | | |
717 | 718 | | |
| 719 | + | |
718 | 720 | | |
719 | 721 | | |
720 | | - | |
| 722 | + | |
721 | 723 | | |
722 | 724 | | |
723 | 725 | | |
| |||
737 | 739 | | |
738 | 740 | | |
739 | 741 | | |
| 742 | + | |
| 743 | + | |
| 744 | + | |
| 745 | + | |
| 746 | + | |
| 747 | + | |
740 | 748 | | |
741 | 749 | | |
742 | 750 | | |
| |||
0 commit comments