[ 
https://issues.apache.org/jira/browse/NIFI-16432?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=18145838#comment-18145838
 ] 

ASF subversion and git services commented on NIFI-16432:
--------------------------------------------------------

Commit bb236b9b4f3eef5770f44cbd48821def1e475cc5 in nifi's branch 
refs/heads/main from David Szabo
[ https://gitbox.apache.org/repos/asf?p=nifi.git;h=bb236b9b4f3 ]

NIFI-16432 Catch exceptions for Cluster Leader status checks to avoid breaking 
scheduling (#11796)

Signed-off-by: David Handermann <[email protected]>

> KubernetesLeaderElectionManager errors may stop the scheduling of primary 
> only, CRON driven processors
> ------------------------------------------------------------------------------------------------------
>
>                 Key: NIFI-16432
>                 URL: https://issues.apache.org/jira/browse/NIFI-16432
>             Project: Apache NiFi
>          Issue Type: Bug
>            Reporter: David Szabo
>            Assignee: David Szabo
>            Priority: Minor
>          Time Spent: 1h 10m
>  Remaining Estimate: 0h
>
> Cron driven processor executions are scheduled one at a time after a 
> successful previous execution. If an exception is thrown at that time the 
> processor will not get scheduled again as this scheduling chain is broken.
> Restarting the processors manually resets the scheduling.



--
This message was sent by Atlassian Jira
(v10.3.26#10030026)

Reply via email to