Description
Catalog manager tasks are edge-triggered (based on a response to a tablet report) instead of level-triggered (based on periodic state polling).
The upshot of this (original) design is that when there is a master failover, ongoing tasks will stop being retried.
Examples of these tasks include things like adding a new replica, deleting an evicted replica, etc. See SendDeleteReplicaRequest() and SendAddServerRequest() in the code base for examples.
Attachments
Issue Links
- relates to
-
KUDU-1991 Master does not retry TS maintenance task if target TS not registered
-
- Resolved
-