I create a job and I loose it when restart chronos. about chronos HOT 11 CLOSED

Do you have Zookeeper setup?

On Fri, Jul 19, 2013 at 3:06 PM, mdfmbs [email protected] wrote:

when I run a job the following command line:
sudo curl-L-X GET chronos: 4400/scheduler/jobs. Then I can see the work I
have scheduled.
My problem is that when I restart chronos the job disappears.

Thanks,

—
Reply to this email directly or view it on GitHubhttps://github.com//issues/73
.

from chronos.

I don't really know what is Zookeeper setup.

Thanks again.

2013/7/19 jeid64 [email protected]

Do you have Zookeeper setup?

On Fri, Jul 19, 2013 at 3:06 PM, mdfmbs [email protected] wrote:

when I run a job the following command line:
sudo curl-L-X GET chronos: 4400/scheduler/jobs. Then I can see the work
I
have scheduled.
My problem is that when I restart chronos the job disappears.

Thanks,

—
Reply to this email directly or view it on GitHub<
https://github.com/airbnb/chronos/issues/73>
.

—
Reply to this email directly or view it on GitHubhttps://github.com//issues/73#issuecomment-21270751
.

Saludos,
Marcelo

from chronos.

You are probably running the instance of chronos with no zookeeper.
This is the step i am trying to figure out!

You probably have this running, which is what comes out of the box:

/usr/bin/java -cp "$CHRONOS_HOME"/target/chronos*.jar com.airbnb.scheduler.Main server "$CHRONOS_HOME"/config/local_scheduler_nozk.yml

Try to get one running with zookeeper, that is the challenge I am facing.
And would also like to know where on earth the jobs are being saved once created.
See my thread for a sample of my configuration chronos config file.
Might not want to copy it since it's not working LOL, but it gives an idea of the direction you want to head.

from chronos.

By the way, zookeeper is what you need for "persistent data", per the documentation.

This is the attribute required in your chronos config, per the documentation:

zookeeperServers

Default: "localhost:2181"

Reference to the zookeepers used:

Chronos leader election
Backing the job and task persistence store

from chronos.

Yes, it looks to me like you have local mode setup. Local mode just keeps the data in memory - thus it's not durable.

from chronos.

Thanks for your reply, I will try installing zookeeping.

2013/7/19 Florian Leibert [email protected]

Yes, it looks to me like you have local mode setup. Local mode just keeps
the data in memory - thus it's not durable.

—
Reply to this email directly or view it on GitHubhttps://github.com//issues/73#issuecomment-21273929
.

Saludos,
Marcelo

from chronos.

Thanks very much for your reply, I will try installing zookeepers.

2013/7/19 nmohajery [email protected]

By the way, zookeeper is what you need for "persistent data", per the
documentation.

This is the attribute required in your chronos config, per the
documentation:

zookeeperServers

Default: "localhost:2181"

Reference to the zookeepers used:

Chronos leader election
Backing the job and task persistence store

—
Reply to this email directly or view it on GitHubhttps://github.com//issues/73#issuecomment-21272087
.

Saludos,
Marcelo

from chronos.

Question?, The only way to keep jobs in chronos would then installing
apache zookeeper?

Thank you again.

2013/7/22 Marcelo Fernández [email protected]

Thanks for your reply, I will try installing zookeeping.

2013/7/19 Florian Leibert [email protected]

Yes, it looks to me like you have local mode setup. Local mode just keeps
the data in memory - thus it's not durable.

—
Reply to this email directly or view it on GitHubhttps://github.com//issues/73#issuecomment-21273929
.

Saludos,
Marcelo

Saludos,
Marcelo

from chronos.

@mdfmbs - As far as I am aware yes.

from chronos.

Good morning,

Question?

Where Chronos stores scheduled jobs?

Use some temporary file? each job or directly stored in memory?

Im trying not to have to install Zookeeper as it is quite complicated

Thanks

2013/7/19 nmohajery [email protected]

By the way, zookeeper is what you need for "persistent data", per the
documentation.

This is the attribute required in your chronos config, per the
documentation:

zookeeperServers

Default: "localhost:2181"

Reference to the zookeepers used:

Chronos leader election
Backing the job and task persistence store

—
Reply to this email directly or view it on GitHubhttps://github.com//issues/73#issuecomment-21272087
.

Saludos,
Marcelo

from chronos.

It stores them in Zookeeper or memory. You can setup zookeeper in standalone mode if you like, it's pretty straightforward and upon downloading and extracting the tarball, all that's required is to run "./bin/zkServer.sh start". I'll mark this closed.

from chronos.