Skip to content

Raise the managed mesh peer-outage grace from 4 s to 300 s #259

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
FujitsuPolycom merged 2 commits into from
Sep 11, 2026
Merged

Raise the managed mesh peer-outage grace from 4 s to 300 s #259

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
207963b
Raise the managed mesh peer-outage grace from 4 s to 300 s
Sep 10, 2026
0edce9d
Merge branch 'main' into mtp3-peer-outage-grace
FujitsuPolycom Sep 11, 2026
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
4 changes: 2 additions & 2 deletions runtime/glm53-spark-mtp3-mesh/MANAGED_MESH.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -361,15 +361,15 @@ The bounded `--run-seconds` mode is for isolated diagnostics only.
| Check | Configured interval or bound |
|---|---|
| Child-process and peer checks | 1-second loop; peer HTTP timeout 2 seconds |
| Unavailable peer connection | 4-second grace after the first transport failure; degraded health blocks model startup |
| Unavailable peer connection | 300-second grace after the first transport failure (covers a management-switch reboot); degraded health blocks model startup |
| Docker container status | One background query at a time, 3-second timeout; unknown status blocks model startup |
| MAC/IP, Ethernet MTU, sysfs GID/netdev, routes, qdiscs, TC state | 5-second periodic check |
| Full RDMA active-MTU probe | Startup and approximately every 60 seconds |
| Health progress freshness | Readiness rejected after 10 seconds without supervisor progress |
| systemd watchdog | 15 seconds |

A connection timeout or other peer transport error enters a degraded state.
Existing serving is retained during a four-second grace interval measured
Existing serving is retained during a 300-second grace interval measured
from the first observed transport failure. Successful authenticated peer
responses clear that interval. Degraded peer health blocks model startup.
An authentication failure, explicit negative readiness, or changed process
Expand Down
2 changes: 1 addition & 1 deletion runtime/glm53-spark-mtp3-mesh/managed_service.py
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -29,7 +29,7 @@
PROTOCOL = 'sparkring-managed-mesh/v1'
POLL_SECONDS = 1.0
PEER_TIMEOUT = 2.0
PEER_OUTAGE_GRACE = 4.0
PEER_OUTAGE_GRACE = 300.0
NETWORK_POLL_SECONDS = 5.0
HEALTH_MAX_AGE = 10.0

Expand Down
4 changes: 2 additions & 2 deletions runtime/glm53-spark-mtp3-mesh/test_managed_service.py
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -50,9 +50,9 @@ def test_sustained_peer_connection_loss_latches_failure():
watch = service.PeerWatch()
watch.observe(rows())
watch.transport_error(10.0)
watch.transport_error(13.9)
watch.transport_error(309.9)
with pytest.raises(RuntimeError, match='grace'):
watch.transport_error(14.0)
watch.transport_error(310.0)


def test_generation_change_is_not_given_a_transport_grace():
Expand Down
Loading