aurora-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Zameer Manji (JIRA)" <>
Subject [jira] [Commented] (AURORA-1593) PubSubEventModule fails to dispatch events to TaskHistoryPruner on startup
Date Fri, 22 Jan 2016 23:24:39 GMT


Zameer Manji commented on AURORA-1593:

The problem here is that the {{TaskStateChange}} event is created when the storage is started
(when the scheduler becomes the leader), but the {{TaskHistoryPruner}} is started up after
the scheduler is registered with Mesos.

It might be possible to avoid this error by delaying pubsub registration until the scheduler
is registred with Mesos. Kevin left a comment suggesting this:
    // TODO(ksweeney): Would this be better as a scheduler active service?

> PubSubEventModule fails to dispatch events to TaskHistoryPruner on startup
> --------------------------------------------------------------------------
>                 Key: AURORA-1593
>                 URL:
>             Project: Aurora
>          Issue Type: Bug
>            Reporter: Zameer Manji
>            Assignee: John Sirois
> On latest master I see several exceptions that look like:
> {noformat}
> E0122 22:59:19.272 [AsyncProcessor-7, PubsubEventModule:84] Failed to dispatch event
to public void org.apache.aurora.scheduler.pruning.TaskHistoryPruner.recordStateChange($TaskStateChange):
java.lang.IllegalStateException j
> ava.lang.IllegalStateException: null
>         at ~[guava-19.0.jar:na]
>         at org.apache.aurora.scheduler.pruning.TaskHistoryPruner.recordStateChange(
>         at sun.reflect.GeneratedMethodAccessor116.invoke(Unknown Source) ~[na:na]
>         at sun.reflect.DelegatingMethodAccessorImpl.invoke(
>         at java.lang.reflect.Method.invoke( ~[na:1.8.0_66-Tw8r9b2]
>         at
>         at$SynchronizedSubscriber.invokeSubscriberMethod(
>         at$ ~[guava-19.0.jar:na]
>         at java.util.concurrent.Executors$ ~[na:1.8.0_66-Tw8r9b2]
>         at ~[na:1.8.0_66-Tw8r9b2]
>         at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$201(
>         at java.util.concurrent.ScheduledThreadPoolExecutor$
>         at java.util.concurrent.ThreadPoolExecutor.runWorker(
>         at java.util.concurrent.ThreadPoolExecutor$
>         at ~[na:1.8.0_66-Tw8r9b2]
> {noformat}
> The problem is that {{TaskHistoryPruner}} assumes it is started before the event bus
starts sending events to the service. This appears to not be the case.

This message was sent by Atlassian JIRA

View raw message