Worker Host Session and Clean Shutdown for StickyTasklist #2369
Labels
customer
Feature asks from customer
feature
New feature
performance
stability
Server stability issues
With stickyTTL, expiring the sticky tasklists is very in-efficient, and the experience is not perfect : after worker host restarted, all the workflows in the cache have to wait for TTL. During the wait, lots of Querys and decisions are still scheduled to sticky tasklists and waiting to timeout.
Ideally, when worker host restarted, it should inform server(history engine) that the stickyTasklist is gone. So that any future activities/querys should not be scheduled to it.
We can keep a small LRU cache for thos "expired" session/stickyTaskList.
The text was updated successfully, but these errors were encountered: