hive-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Eugene Koifman (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HIVE-11008) webhcat GET /jobs retries on getting job details from history server is too agressive
Date Tue, 16 Jun 2015 00:37:00 GMT

    [ https://issues.apache.org/jira/browse/HIVE-11008?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14587229#comment-14587229
] 

Eugene Koifman commented on HIVE-11008:
---------------------------------------

there are 2 places where StatusDelegator.run() is called Server.showJobList() and Server.showJobId().
Don't we need the same logic in both places?

Can the setting of the 2 properties be moved into StatusDelegator.run() just before
ShimLoader.getHadoopShims().getWebHCatShim()?

> 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)

Mime
View raw message