[
https://issues.apache.org/jira/browse/AURORA-1672?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15250863#comment-15250863
]
Joshua Cohen commented on AURORA-1672:
--------------------------------------
The root cause of this is the introduction of a new process to the http_example
job that references a non-existent port:
https://github.com/apache/aurora/blob/915459dac76ed0732addce87420a4ba51d916de8/src/test/sh/org/apache/aurora/e2e/http/http_example.aurora#L21
If I either remove the {{tcp port: {{thermos.ports[tcp]}};}} or add tcp to the
portmap, this issue goes away.
> Duplicate task events displayed in UI
> -------------------------------------
>
> Key: AURORA-1672
> URL: https://issues.apache.org/jira/browse/AURORA-1672
> Project: Aurora
> Issue Type: Task
> Components: Scheduler
> Reporter: Joshua Cohen
> Priority: Blocker
> Attachments: Example of duplicate task events.png
>
>
> While working on the unified containerizer support, I noticed that I was
> seeing duplicate task events in the scheduler UI. On digging further, these
> events were present in the DB as well. Initially I thought it was related to
> the storage changes for task images, but I was able to reproduce on a sha
> before those changes were introduced.
> I ran a git bisect to see what commit introduced this bug and it pointed to:
> https://github.com/apache/aurora/commit/915459dac76ed0732addce87420a4ba51d916de8
> It's not immediately obvious to me how that change is causing this,
> especially since setting {{-populate_discovery_info=false}} in
> {{aurora-scheduler.conf}} does *not* fix the problem.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
