You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@aurora.apache.org by "Santhosh Kumar Shanmugham (JIRA)" <ji...@apache.org> on 2017/01/19 02:29:26 UTC
[jira] [Commented] (AURORA-1879) /pendingTasks endpoint shows 500
HTTP Error when there are multiple pending tasks with the same key
[ https://issues.apache.org/jira/browse/AURORA-1879?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15829186#comment-15829186 ]
Santhosh Kumar Shanmugham commented on AURORA-1879:
---------------------------------------------------
I think the issue is when we have multiple TaskGroups that have same key (3-tuple) but different TaskConfigs, which can happen when there are JobUpdates.
https://github.com/apache/aurora/blob/master/src/main/java/org/apache/aurora/scheduler/metadata/NearestFit.java#L133-L138
> /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)