Closed tjtelan closed 4 years ago
This ended up being very similar to the other components. The biggest difference is needing poller to run as a privileged user, since it directly touches files within the /etc/cron.d directory.
This runs within the Vagrant environment now.
More documentation needed around poller deployment and configuration! I'm writing this issue w/o looking at the poller code, only what is in the wiki. Poller isn't included in the Vagrant setup either for this reason (#177).
Background:
From our existing production deployment, our NSQ deployment had
poll_please
andno_poll_please
topics. When I had to redeploy NSQ, these topics were deleted. (Wah wah)I had to restart Poller because it was throwing errors after losing these topics. The first thing Poller does is call
github.com/shankj3/ocelot/build_signaler/poll.WriteCronFile
and re-configure the cron timers (which is inline with my expectations!). Then rolls into this double sleep loop looking for topics in NSQ.I'm unsure if this is expected behavior because no one has created new polling rules? (which would make sense if
admin
initiates creating the topics), but we need more docs to understand how this all strings together.In particular, this needs to be paired with a detailed walkthrough for how to deploy in polling-mode or a webhook-mode. The audience for this doc is an administrator (as opposed to a regular user)