This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
Hi there. Do you have an application working in local mode yet?
Cool. The main difference is that they need to use a shared ZK server, not a local one.
Much more recommended than what we do in onyx-benchmark
It's still a bit of a work in progress but it's all mostly there
The idea with onyx nodes is that you need an ns with a main function that requires any nses used by your lifecycles and functions, and then call start-peers using a config pointing at a shared ZK server. Then they'll be ready to go, and you can call submit-job and it'll submit the job data to ZK, where all the peers will pick it up
One other thing, if you're using core async for your input tasks, you'll probably need a different input source because input tasks could end up on any peer
You're building a crawler? Cool
I have skimmed the doc of Onyx. Now I have basic idea of what each part do. I have to reread the doc and go with the ansible .
IIRC, I think one missing piece in the playbook is where you bundle your systems jar up. If you look at what the onyx-template does, it should be pretty easy to get that part up and running