aurora-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Zameer Manji (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (AURORA-1769) Enabling webhook is synchronous and could cause longer leader reelection cycle
Date Mon, 12 Sep 2016 18:13:21 GMT

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

Zameer Manji commented on AURORA-1769:
--------------------------------------

Agreed that a solution to this problem involves two components:
* Not sending the {{TaskStateChange}} on scheduler restart (that's very surprising to me)
* Sending data asynchronously to no block in the event bus callback.

I don't think this has to be a blocker either for 0.16.0, but I just wanted to surface it
incase [~joshua.cohen] agreed.

> 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