aurora-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Maxim Khutornenko (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (AURORA-1769) Enabling webhook is synchronous and could cause longer leader reelection cycle
Date Sat, 10 Sep 2016 02:25:20 GMT

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

Maxim Khutornenko commented on AURORA-1769:
-------------------------------------------

Scratch the above. I read the description but completely ignored the title. I can totally
see how this can happen with a webhook enabled. Should be easy to ignore {{TaskStateChange}}
processing there until the {{DriverRegistered}} is received.

> Enabling webhook is synchronous and could cause longer leader reelection cycle
> ------------------------------------------------------------------------------
>
>                 Key: AURORA-1769
>                 URL: https://issues.apache.org/jira/browse/AURORA-1769
>             Project: Aurora
>          Issue Type: Bug
>            Reporter: Dmitriy Shirchenko
>            Assignee: Dmitriy Shirchenko
>
> We had an issue where on scheduler leader reelection EventBus was full of TaskStateChange
events and caused scheduler to not be able to post DriverRegistered() message which caused
Aurora scheduler to not register within 1 minute. 



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Mime
View raw message