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.

Sign up for GitHub

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

Jump to bottom

Make spawn an option again #15379

Merged
merged 2 commits into from
Jun 16, 2017
Merged

Make spawn an option again #15379

merged 2 commits into from
Jun 16, 2017
+59 −1

Commits on Jun 16, 2017

  1. Make spawn an option again instead of just fork 

    Use run_single_worker script for worker spawning

Embedded ansible worker overrides start_runner to implement
a thread based worker implementation.
    @jrafanie
    jrafanie committed Jun 16, 2017
    Configuration menu
    Copy the full SHA
    6d3362f View commit details
    Browse the repository at this point in the history

  2. Allow using existing guid for run_single_worker 

    When running single workers in the context of a worker monitor, the
worker records are usually already created by the monitor process by the
time the worker is forked/spawned.

Allowing the lib/worker/bin/run_single_worker.rb script to pass a guid
allows it to use those records instead of creating new ones.  If this
option isn't used, the already created ones exist along side the other
worker records, and cause evm:stop to not function properly.
    @NickLaMuro @jrafanie
    NickLaMuro authored and jrafanie committed Jun 16, 2017
    Configuration menu
    Copy the full SHA
    3f3a823 View commit details
    Browse the repository at this point in the history