[jira] [Resolved] (KUDU-1997) Catalog manager tasks are edge-triggered

["Adar Dembo (Jira)" <ji...@apache.org>]

     [ https://issues.apache.org/jira/browse/KUDU-1997?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Adar Dembo resolved KUDU-1997.
------------------------------
    Fix Version/s: 1.11.0
       Resolution: Won't Fix

In the years since this bug was filed we never did identify a clear need to switch from edge-triggered to level-triggered tasks.

> 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
>            Priority: Major
>             Fix For: 1.11.0
>
>
> 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
(v8.3.4#803005)