[
https://issues.apache.org/jira/browse/HIVE-11008?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14588483#comment-14588483
]
Thejas M Nair commented on HIVE-11008:
--------------------------------------
[~jianhe] would have more background on the fix from [~cwelch].
What is the behavior in above case mentioned by [~ekoifman] ? I understand
that in above case as well we can have the RM having the job information, but
History server not having it.
Would you recommend having retries in that case ? Can that result in timeouts ?
> webhcat GET /jobs retries on getting job details from history server is too
> agressive
> -------------------------------------------------------------------------------------
>
> Key: HIVE-11008
> URL: https://issues.apache.org/jira/browse/HIVE-11008
> Project: Hive
> Issue Type: Bug
> Components: WebHCat
> Affects Versions: 1.2.0
> Reporter: Thejas M Nair
> Assignee: Thejas M Nair
> Attachments: HIVE-11008.1.patch
>
>
> Webhcat "jobs" api gets the list of jobs from RM and then gets details from
> history server.
> RM has a policy of retaining fixed number of jobs to accommodate for the
> memory it has, while HistoryServer retains jobs based on their age. As a
> result, jobs that RM returns might not be present in HistoryServer and can
> result in a failure. HistoryServer also ends up retrying on failures even if
> they happen because the job actually does not exist.
> The retries to get details from HistoryServer in such cases is too aggressive.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
