Open krestjaninoff opened 8 years ago
I am seeing the very same issue using 2.4.0 and 0.28.1. It only is able to run if I delete the job and create again.
When you are scheduling the chronos Job, giving the parameter as R0/Time when it has to run/Repeating time
Even if you planning to run the chronos job only once it is important to give all the 3 parameters for the scheduler
{
"schedule": "R/2014-09-25T17:22:00Z/PT2M",
"name": "dockerjob",
"container": {
"type": "DOCKER",
"image": "libmesos/ubuntu",
"network": "BRIDGE",
"volumes": [
{
"containerPath": "/var/log/",
"hostPath": "/logs/",
"mode": "RW"
}
]
},
"cpus": "0.5",
"mem": "512",
"fetch": [],
"command": "while sleep 10; do date =u %T; done"
}
I'm trying to use Chronos for starting maintenance jobs. The most tricky moment is I don't need them running on scheduler - I want to invoke a job manually (e.g. during CI deployments).
For that, I've created the following manifest
and uploaded it into Chronos using
scheduler/iso8601
endpoint:After that I tried to trigger my job using
scheduler/job
endpoint:But my job wasn't started :( In Chronos logs I found the following:
I'm using Chronos 2.4.0 with Mesos 0.28.1.