Page MenuHomePhabricator

Where should I run the repository pull daemon with `--no-discovery`
OpenPublic

Asked by joshuaspence on Oct 15 2015, 1:58 AM.

Details

Currently I have (amongst others) a "repo" host and a "worker" host. All working-copy operations are proxied to the repo host using an Almanac service, with the exception of the issues mentioned in T2783. As a result, I currently need to run PhabricatorRepositoryPullLocalDaemon on the "worker" host. Currently I am running PhabricatorRepositoryPullLocalDaemon on the worker host with no arguments and am running PhabricatorRepositoryPullLocalDaemon on the repo host with --no-discovery. I'm not actually entirely sure what --no-discovery does but I am guessing that I should switch these two hosts around (i.e. run with --no-discovery on the worker host and with no flags on the repo host), is this correct?

If this is the case, I have one issue in that I can't start an autoscaling taskmaster pool independently of running PhabricatorRepositoryPullLocalDaemon without --no-discovery. I currently use two different upstart scripts to manage the daemons, P1866 on the worker host and P1867 on the repo host. This works host except that the taskmaster pool is static (i.e. it does not autoscale).

New Answer