From 9ccb707335d73f06563bb5d5cc09af6f666afc09 Mon Sep 17 00:00:00 2001 From: djamp42 <25335691+djamp42@users.noreply.github.com> Date: Thu, 17 Dec 2020 16:17:59 -0500 Subject: [PATCH] Update Distributed-Poller.md Discovery using dispatcher service (#12387) * Update Distributed-Poller.md Clarify discovery when using dispatcher service. The limitation of running one discovery per server is only for cron based polling. * Update Distributed-Poller.md Co-authored-by: Neil Lathwood --- doc/Extensions/Distributed-Poller.md | 13 ++++++++++--- 1 file changed, 10 insertions(+), 3 deletions(-) diff --git a/doc/Extensions/Distributed-Poller.md b/doc/Extensions/Distributed-Poller.md index 8b749e0746..21f9597319 100644 --- a/doc/Extensions/Distributed-Poller.md +++ b/doc/Extensions/Distributed-Poller.md @@ -174,9 +174,16 @@ need to have the same `APP_KEY` value set in the `.env` file. ### Discovery -It's not necessary to run discovery services on all pollers. In fact, -you should only run one discovery process per poller group. Designate -a single poller to run discovery (or a separate server if required). +Depending on your setup will depend on how you configure your discovery processes. + +**Cron based polling** + +It's not necessary to run discovery services on all pollers. In fact, you should +only run one discovery process per poller group. +Designate a single poller to run discovery (or a separate server if required). + +**Dispatcher service** +When using the dispatcher service, discovery can run on all nodes. ### Configuration