[
https://issues.apache.org/jira/browse/AURORA-1769?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15478914#comment-15478914
]
Maxim Khutornenko commented on AURORA-1769:
-------------------------------------------
Are you sure that was due to the backed up {{EventBus}}? The only way for the
{{TaskStateChange}} events to get there before the driver registration is due
to re-populating the {{TaskStore}} while [reading snapshot/replaying
transactions|https://github.com/apache/aurora/blob/b24619b28c4dbb35188871bacd0091a9e01218e3/src/main/java/org/apache/aurora/scheduler/storage/CallOrderEnforcingStorage.java#L99].
This is usually very fast for the {{MemTaskStore}} but I can see how it
_might_ take longer when using the {{DBTaskStore}}. Are you setting the
{{use_beta_db_task_store=true}}?
> 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)
