[
https://issues.apache.org/jira/browse/AURORA-1879?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15837063#comment-15837063
]
Pradyumna Kaushik commented on AURORA-1879:
-------------------------------------------
Good catch of the bug. [~santhk] I think you are right in that a JobUpdate of a
pending job, that again puts in a pending state, would cause this. One way to
go about this is to remove the Veto from NearestFit once a pending job has been
updated. That way if the updated Job goes into pending state, then there won't
be any clash when /pendingTasks api is accessed.
> /pendingTasks endpoint shows 500 HTTP Error when there are multiple pending
> tasks with the same key
> ---------------------------------------------------------------------------------------------------
>
> Key: AURORA-1879
> URL: https://issues.apache.org/jira/browse/AURORA-1879
> Project: Aurora
> Issue Type: Bug
> Components: Scheduler
> Reporter: Kai Huang
> Attachments: pending_tasks.png
>
>
> When we have multiple TaskGroups that have same key but different
> TaskConfigs, the /pendingTasks endpoint will gives a 500 HTTP Error.
> This bug seems to be related to a recent commit (Added the 'reason' to the
> /pendingTasks
> endpoint)(https://github.com/apache/aurora/commit/8e07b04bbd4de23b8f492627da4a614d1e517cf1).
>
> Attached were a screenshot of the /pendingTasks endpoint.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
