diff options
| author | Gerhard Lazu <gerhard@lazu.co.uk> | 2020-03-12 15:37:00 +0000 |
|---|---|---|
| committer | Gerhard Lazu <gerhard@lazu.co.uk> | 2020-03-12 15:59:47 +0000 |
| commit | 1a60b43aa99bb8d97fe29a3c5266ede7678fe26e (patch) | |
| tree | 9a8cf0d73810e38090090ced63bd3ae0fa235c79 | |
| parent | f8d47976d999e8816dacf981f86b71f387dc18fc (diff) | |
| download | rabbitmq-server-git-1a60b43aa99bb8d97fe29a3c5266ede7678fe26e.tar.gz | |
Use default work pool for definition import
This unblocks node boot, otherwise the node gets stuck on waiting for
gatherer:out/1 to return.
I am not sure why we need another work pool for boot steps and don't
just use the default work pool. After all, there is nothing else running
during node boot except the boot steps, so using the default work pool
should be sufficient.
If we do decide to create a new work pool, we will need
to stop it after boot steps complete. Obviously, we will need to first
fix this work pool which currently doesn't seem to be created. We can
see all processes for the default work pool, but we cannot find any
process for this new IMPORT_WORK_POOL.
cc @michaelklishin
Signed-off-by: Philip Kuryloski <pkuryloski@pivotal.io>
(cherry picked from commit 0f86277b06b1a27ef468dcd02f1700cc99f04bf0)
| -rw-r--r-- | src/rabbit_definitions.erl | 1 |
1 files changed, 0 insertions, 1 deletions
diff --git a/src/rabbit_definitions.erl b/src/rabbit_definitions.erl index 171fb3c73f..7460b1b838 100644 --- a/src/rabbit_definitions.erl +++ b/src/rabbit_definitions.erl @@ -348,7 +348,6 @@ do_concurrent_for_all(List, WorkPoolFun) -> %% keys are expected to be atoms ok = gatherer:fork(Gatherer), worker_pool:submit_async( - ?IMPORT_WORK_POOL, fun() -> try WorkPoolFun(M) |