[
https://issues.apache.org/jira/browse/SQOOP-1878?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14243460#comment-14243460
]
Gwen Shapira commented on SQOOP-1878:
-------------------------------------
If GET doesn't do an update, then it returns a cached result that the thread
updated.
If we want to make sure the result makes sense to the user and avoid flooding
RM/JT, we need to invalidate the cache in the right intervals.
Also, while I agree the current behavior is highly misleading, I'm not sure it
qualifies as an urgent bug (since we discovered that we do the update even for
non-running jobs, just in different place).
Since there's no urgent fix (AFAIK), lets take few more hours to think it
properly and make sure we get the right solution.
> JobManager status method is a GET call and should not performa update
> operations
> --------------------------------------------------------------------------------
>
> Key: SQOOP-1878
> URL: https://issues.apache.org/jira/browse/SQOOP-1878
> Project: Sqoop
> Issue Type: Sub-task
> Reporter: Veena Basavaraj
> Assignee: Veena Basavaraj
> Fix For: 1.99.5
>
> Attachments: SQOOP-1878.patch
>
>
> JobManager status method is a GET call and should not performa update
> operations
> status () method on JobManager is get request from the rest API. it should
> not ever do an update.
> if we need more faster updates of job, then it is best to create a new action
> that can do it or reduce the updateSleep parameter to less than 5 minutes.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
