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
feat: Add "Speeding up migrations" section to "State persistence" (#1365)
We've recently added support to speed up Actor migrations by rebooting
the run when it's migrating. This adds docs about that, with code
examples.
The support for this in the Apify SDK is not released yet, it'll go out
in the next SDK release, I'll only merge the docs then.
---------
Co-authored-by: Michał Olender <[email protected]>
Copy file name to clipboardExpand all lines: sources/platform/actors/development/builds_and_runs/state_persistence.md
+51-4Lines changed: 51 additions & 4 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -51,7 +51,7 @@ By default, an Actor keeps its state in the server's memory. During a server swi
51
51
52
52
The [Apify SDKs](/sdk) handle state persistence automatically.
53
53
54
-
This is done using the `Actor.on()` method and the `migrating` event.
54
+
This is done using the `Actor.on()` method and the `migrating` event.
55
55
56
56
- The `migrating` event is triggered just before a migration occurs, allowing you to save your state.
57
57
- To retrieve previously saved state, you can use the [`Actor.getValue`](/sdk/js/reference/class/Actor#getValue)/[`Actor.get_value`](/sdk/python/reference/class/Actor#get_value) methods.
0 commit comments