[
https://issues.apache.org/jira/browse/TEZ-3880?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16312260#comment-16312260
]
Sergey Shelukhin commented on TEZ-3880:
---------------------------------------
When AM tries to schedule on LLAP and there's no capacity, it treats task
attempt as killed with SERVICE_BUSY error.
This is not really a killed task but just an artifact of fitting the model that
is based on how RM gives out containers for LLAP that works differently
(similarly, queueing in LLAP is not accounted for in current Tez model because
YARN handles it differently thru RM).
On a full cluster, this affects killed task attempt counter in the UI.
> do not count rejected tasks as killed in vertex progress
> --------------------------------------------------------
>
> Key: TEZ-3880
> URL: https://issues.apache.org/jira/browse/TEZ-3880
> Project: Apache Tez
> Issue Type: Task
> Reporter: Sergey Shelukhin
> Assignee: Sergey Shelukhin
> Attachments: TEZ-3880.patch
>
>
> Tasks rejected from LLAP because the cluster is full are shown as killed
> tasks in the commandline query UI (CLI and beeline). This shouldn't really
> happen; killed tasks in the container case means something else, and this
> scenario doesn't exist because AM doesn't continuously try to queue tasks. We
> could change LLAP queue to use sort of a pull model (would also allow for
> better duplicate scheduling), but for now we should fix the UI
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
