Skip to content

Commit f13601d

Browse files
Update link to Pekko variant of akka-quartz-scheduler (#782) (#783)
Co-authored-by: Zachary Sistrunk <[email protected]>
1 parent e3335d0 commit f13601d

File tree

1 file changed

+1
-1
lines changed

1 file changed

+1
-1
lines changed

docs/src/main/paradox/scheduler.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -42,7 +42,7 @@ instances at the same time. The implementation is based on a Hashed Wheel Timer,
4242
a known datastructure and algorithm for handling such use cases, refer to the [Hashed and Hierarchical Timing Wheels](http://www.cs.columbia.edu/~nahum/w6998/papers/sosp87-timing-wheels.pdf)
4343
whitepaper by Varghese and Lauck if you'd like to understand its inner workings.
4444

45-
The Pekko scheduler is **not** designed for long-term scheduling (see [akka-quartz-scheduler](https://github.com/enragedginger/akka-quartz-scheduler)
45+
The Pekko scheduler is **not** designed for long-term scheduling (see [pekko-quartz-scheduler](https://github.com/samueleresca/pekko-quartz-scheduler)
4646
instead for this use case) nor is it to be used for highly precise firing of the events.
4747
The maximum amount of time into the future you can schedule an event to trigger is around 8 months,
4848
which in practice is too much to be useful since this would assume the system never went down during that period.

0 commit comments

Comments
 (0)