[
https://issues.apache.org/jira/browse/SQOOP-1878?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14243393#comment-14243393
]
Gwen Shapira commented on SQOOP-1878:
-------------------------------------
We identified at least 3 requirements here:
1. Avoid doing updates in a GET API that should be readonly
2. Give users updates within reasonable time
3. Avoid flooding resource-manager / job manager with large number of requests
when running large number of Sqoop jobs (i.e. rate limiting of sorts)
Since it looks like we are designing a cache, and caches are notoriously
challenging to get right - I suggest a small design wiki with the proposed
solution, so we can be sure we are doing the right thing and not hacking it.
> 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)
