[
https://issues.apache.org/jira/browse/KUDU-1997?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15998959#comment-15998959
]
Mike Percy commented on KUDU-1997:
----------------------------------
Right now there are tasks such as adding and removing replicas that are edge
triggered based on configuration changes. It may be good enough to also trigger
on tablet reports instead of having a background thread although it needs a
little more investigating to make sure that would be good enough.
> Catalog manager tasks are edge-triggered
> ----------------------------------------
>
> Key: KUDU-1997
> URL: https://issues.apache.org/jira/browse/KUDU-1997
> Project: Kudu
> Issue Type: Bug
> Components: master
> Affects Versions: 1.3.1
> Reporter: Mike Percy
>
> 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.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
