Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Control worker startup timeout via an env variable #11532

Merged
merged 1 commit into from
Jun 4, 2015

Conversation

amitmurthy
Copy link
Contributor

Currently, worker processes wait upto 60.0 seconds for the master process to connect upon launch, and terminate if the master fails to do so. It has been noticed that this is not sufficient in certain cases.

This PR makes this timeout configurable via env variable JWORKER_TIMEOUT . Default value continue to be 60.0 seconds. Custom cluster managers can specify this in the worker's env while launching a worker. For SSHManager, JWORKER_TIMEOUT is picked up from master process's env, if defined.

The alternative to using an env variable was to have it specified as a julia exe option, which I wanted to avoid.

cc @andreasnoack

@pao
Copy link
Member

pao commented Jun 2, 2015

Bikeshed: JULIA_WORKER_TIMEOUT or JLWORKER_TIMEOUT? I don't think we use plain "j" anywhere else after the Great File Extension Shift.

@Keno
Copy link
Member

Keno commented Jun 2, 2015

+1 for JULIA_WORKER_TIMEOUT

@StefanKarpinski
Copy link
Sponsor Member

Yes, Julia environment variables should all start with JULIA_.

@amitmurthy
Copy link
Contributor Author

Changed to JULIA_WORKER_TIMEOUT.

@andreasnoack
Copy link
Member

👍 This will be very useful on clusters.

@amitmurthy
Copy link
Contributor Author

Merging. Travis errors are due to the OOM killer.

amitmurthy added a commit that referenced this pull request Jun 4, 2015
Control worker startup timeout via an env variable
@amitmurthy amitmurthy merged commit cd7f39f into master Jun 4, 2015
@amitmurthy amitmurthy deleted the amitm/worker_timeout branch June 4, 2015 05:04
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

5 participants