-
I have a three node chronos cluster. When request reach node 1 I see in the log that chronos proxying request to node2_hostname:4400 which is expected.
When I check the chronos logs on node 2, I see …
-
Currently known issues(Updates will be kept)
## Issues
1. `pytorch-tcn` and `tensorflow-tcn` cannot be called sequentially, which means that users cannot compare the performance of different framewo…
-
_please notice that the list may change according to the developing priority and progress and they are subject to change_
This issue is mainly used for the BigDL 2.0 migration process and avoid unn…
-
An intermittent issue is encountered on Chronos that when a job submitted on Mesos by Chronos is killed using API : curl -L -X DELETE Chronos-node:8080/scheduler/job/JOBNAME
It is not killed on Mesos,…
-
Good afternoon. As far as I understand you have a solution to this problem. Can we talk to you in private about this issue?
-
-
## Expected Behavior
After Chronos is setup, logged in and turned off - after starting it again, it should be logged in again to the same Jira account.
## Actual Behavior
After Chronos is restart…
-
If Zookeeper is not not running around the time Chronos starts, a situation occurs where Chronos will throw an exception and never fully start. This is almost identical to [Marathon issue 146](https:/…
-
Original release v0.14.1 (win 64bit) have sync/connection errors...
Build from source (win 64bit) (v0.14.1.0-e3ed1d0e6) have fix those errors!!!
-
Utilities for testing job management scheduling systems: https://github.com/jepsen-io/jepsen/tree/master/chronos
e.g. tests for http://mesos.apache.org/
https://github.com/jepsen-io/jepsen/blob/…