I have a local deployment with DC/OS where I also installed chronos. My setup is one master, one agent and the boot image: m1, a1, boot.
The problem is that the jobs I send to chronos either don't get into queue or seem to not execute or...they get executed really late even tough I specified that I want them running right away. I always resort to restarting chronos so I can have 10 minutes of a responsive stack.
I tried with multiple masters and multiple agents as well with the same results. I also tried raising the RAM and CPUs on both the master and agent with no luck. There seems to be a time window after which the stack lags out badly.
My second issue after some testing. I tried adding jobs to chronos that would keep the agent's cpu capped at 100% for a while to see how it performs under load and, after 2 mins chronos crashed and my jobs all failed at once. Is this also something I could expect in production?
I'm asking this in hopes that it's only a matter with the test local deployment under vagrant before I go on with my project and enter production spending quite a few bucks.