Skip to content
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

Jump to bottom

Throubleshooting page #52

Merged
merged 2 commits into from
Jul 3, 2023
Merged

Throubleshooting page #52

Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
dbbf225
throubleshooting page
slinkydeveloper Jun 30, 2023
80c5490
Feedback
slinkydeveloper Jul 3, 2023
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
13 changes: 13 additions & 0 deletions docs/deployment-operations/throubleshooting.md
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -0,0 +1,13 @@
---
sidebar_position: 5
---

# Throubleshooting

This page describes some known throubleshooting scenarios when operating Restate.

## Sleep/Delayed call and other Timers operations are triggered too early/too late

Make sure the system clock of the runtime is synchronized with the clock of the service endpoint and they use the same time zone.

When you do timer-based actions with the SDK (e.g. sleep, delayed calls), their execution time gets calculated based on the system clock of the service endpoint. But subsequently, the runtime registers these timer on its own system clock. So if these two clocks are out-of-sync, you get unwanted behavior.