This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2017-01-18
Channels
- # bangalore-clj (1)
- # beginners (60)
- # boot (98)
- # cider (8)
- # clojure (158)
- # clojure-dusseldorf (16)
- # clojure-france (3)
- # clojure-hamburg (2)
- # clojure-mke (2)
- # clojure-russia (11)
- # clojure-serbia (1)
- # clojure-spec (123)
- # clojure-uk (59)
- # clojurescript (44)
- # code-reviews (16)
- # community-development (51)
- # core-async (46)
- # cryogen (1)
- # cursive (9)
- # datascript (5)
- # datomic (36)
- # emacs (3)
- # events (12)
- # hoplon (57)
- # jobs (1)
- # juxt (3)
- # klipse (55)
- # lein-figwheel (3)
- # leiningen (5)
- # luminus (3)
- # off-topic (8)
- # om (75)
- # om-next (9)
- # onyx (17)
- # pedestal (7)
- # portland-or (3)
- # proton (36)
- # protorepl (6)
- # re-frame (3)
- # reagent (33)
- # remote-jobs (1)
- # ring (23)
- # ring-swagger (2)
- # rum (1)
- # specter (1)
- # untangled (36)
- # yada (11)
hi all is there a way to clear out a cluster without having to rm zookeeper and resetup everything , while testing have a bunch of jobs that are stuck and constantly try to run and are unlikely to ever complete
i am aware of the kill-job api , but im not sure how to get a list of running jobs to pass to that function
If you want a quick way to start fresh in zookeeper, you can change the tenancy-id on your peers. Everything in Onyx is namespaced by the tenancy-id, so starting your peers with a fresh one will give them a clean slate in ZK.
That may or may not be viable for your situation however, as it will leave the old jobs in ZK, just under a different namespace. Those may need to be cleaned up periodically if you run out of disk space.
Another option is the Replica Query tools in lib Onyx. https://github.com/onyx-platform/lib-onyx/blob/master/README.md#replica-queries
@rc1140: you will need to restart your peers if you rm /onyx
We could add :stop-all-jobs action - that stops running jobs and clear/cancell waiting jobs.
@mariusz_jachimowicz I think that would be good. A log entry for kill-all-jobs
and a corresponding API call kill-all-jobs
would be helpful.
Cool. I will try look on this when I finish new UI.
@mariusz_jachimowicz Thanks for the contributions!
Glad to help 😄