[
https://issues.apache.org/jira/browse/HADOOP-3618?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12607542#action_12607542
]
Amar Kamat commented on HADOOP-3618:
------------------------------------
bq. 1. If the thread is interrupted ...
We can do that.
bq. in other projects, .....
Steve, here the jobs that wait are few. The jobs that are immediately submitted
as the jobtracker comes up are the ones that will see this problem. Once the
jobtracker is up, there is no waiting. If you say that there are lots and lots
of jobs that (can) get fired as soon as the JT comes up then yeah its is a
problem. But adding a random part to the sleep sounds ok. I purposefully didnt
keep it as a configurable param since the jt restart takes few seconds (on a
decent enough cluster) and hence the wait time is in the order of millisecs. I
had no strong reason to make it configurable. Let me know if thats not the case.
bq. If this sleep-until-ready pattern is common ..
Yup. If its a common pattern it can be factored out.
----
Thanks for the review.
> JobClient should keep on retrying if the jobtracker is still initializing
> -------------------------------------------------------------------------
>
> Key: HADOOP-3618
> URL: https://issues.apache.org/jira/browse/HADOOP-3618
> Project: Hadoop Core
> Issue Type: Improvement
> Components: mapred
> Reporter: Amar Kamat
> Assignee: Amar Kamat
> Attachments: HADOOP-3618.patch
>
>
> When the user submits the job while the jobtracker is still initializing, the
> jobclient comes out with an exception. ideally the jobclient should keep on
> retrying until the jobtracker is up and ready. This will also take care of
> HADOOP-3289.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
