You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: sn-manager/README.md
+10-4Lines changed: 10 additions & 4 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -200,7 +200,7 @@ Auto-update checks run every 10 minutes when enabled.
200
200
201
201
## Version Update Scenarios
202
202
203
-
The auto-updater follows stable-only, same-major update rules and defers updates while the gateway is busy. Summary:
203
+
The auto-updater follows stable-only, same-major update rules and coordinates updates around the gateway state to minimize disruption while avoiding being stuck. Summary:
204
204
205
205
| Current | Available | Auto-Upgrade Enabled | Auto Updates? | Manual Option |
206
206
|---|---|---|---|---|
@@ -211,17 +211,23 @@ The auto-updater follows stable-only, same-major update rules and defers updates
211
211
| v1.7.4 | v1.7.4 (stable) | Yes | ❌ | — |
212
212
| v1.7.5 | v1.7.4 (stable) | Yes | ❌ | — |
213
213
| Any | Any | No | ❌ |`sn-manager get [version] && sn-manager use [version]`|
214
-
| Any | Any | Yes, but gateway busy |❌ (deferred)| Manual allowed |
214
+
| Any | Any | Yes, but gateway busy |⏳ Deferred (max 1 hour), then ✅| Manual allowed |
- Same-major only: SuperNode and sn-manager auto-update only when the latest is the same major version (the number before the first dot). Example: 1.7 → 1.8 = allowed; 1.x → 2.0 = manual.
219
-
- Gateway-aware: updates are applied only when the gateway reports no running tasks; otherwise they are deferred.
220
-
- Gateway errors: repeated check failures over a 5-minute window request a clean SuperNode restart (no version change) to recover.
219
+
- Gateway idle: updates are applied when the gateway reports no running tasks.
220
+
- Gateway busy: if tasks are running, updates are deferred for up to 1 hour for the target version; after that hard window, the update proceeds to avoid being stuck.
221
+
- Gateway unresponsive: if an update is available, it proceeds immediately to break the deadlock; if no update is available, a clean SuperNode restart is requested via marker.
221
222
- Combined tarball: when updating, sn-manager downloads a single tarball once, then updates itself first (if eligible), then installs/activates the new SuperNode version.
222
223
- Config is updated to reflect the new `updates.current_version` after a successful SuperNode update.
223
224
- Manual installs: you can always override with `sn-manager get <version>` and `sn-manager use <version>`; pre-releases are supported manually.
224
225
226
+
### Update Timing
227
+
228
+
- Checks run every 10 minutes when auto-upgrade is enabled.
229
+
- On every `sn-manager start`, the updater runs an immediate check and bypasses the gateway check once so that initial updates can be applied even if the gateway is not yet available.
230
+
225
231
## Start/Stop Behavior
226
232
227
233
sn-manager start and supernode start clear the stop marker; supernode stop sets it. How the manager and SuperNode processes behave for each command, plus systemd nuances:
0 commit comments