This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2015-07-29
Channels
- # admin-announcements (48)
- # announcements (1)
- # beginners (80)
- # boot (150)
- # cljs-dev (12)
- # clojure (133)
- # clojure-dev (1)
- # clojure-italy (27)
- # clojure-japan (1)
- # clojure-russia (77)
- # clojurescript (236)
- # clojutre (3)
- # code-reviews (1)
- # core-async (14)
- # core-logic (4)
- # core-matrix (15)
- # cursive (5)
- # datomic (30)
- # editors (16)
- # events (1)
- # hoplon (1)
- # ldnclj (17)
- # off-topic (30)
- # om (2)
- # onyx (47)
- # reagent (8)
@lowl4tency: what do you mean cloudwatch metrics to see if ZK is “working"
erichmond: so, for example I wanna a thing, it’s checking my zookeeper application if it fails the instance is terminated
I ask for a definition of working, because there could be a number of reasons why ZK wouldn’t be working (crashed process, network interruptions, the os layer getting disrupted, etc)
I did a simple solution for it, add a loop to start script
If the app is down I need a new one instance
so, you want something that will notify you if the process on the box fails for some reason?
Not notify, do some actions with instances
Terminate old and start new
yeah, if you are interested in restarting the app on a single instance, if ZK fails, then a script that runs on your instance itself is probably the best solution
At Indaba we do two things, we have a script that runs on each instance itself to reboot instance
but we also have a service that listens to cloudwatch messages, and if we get a message that a box is unreachable, that service spins up a new instance in response via ansible
CLoudWatch is able to check a port access from outside?
well, both route53 and the ELBs have a “health check” option that you can setup, where amazon will ping the instance for you
you can setup cloudwatch to send an email / SNS / whatever if that health check fails
I’ve not an ELB for zookeper instances
If I’ve got an ELB it’s not a trouble
It’s simple to configure
yeah, I am not sure if you can configure health check at the ec2 level, but we have found elb’s useful
18 usd per month
I prefer reduce costs as much as possible
erichmond: do you use cloudwatch with a 3d-party monitoring tool?
yep! we use http://www.librato.com
we’re actually moving to a unified log architecture, so we stopped using CW, but we used it with them for years
@lowl4tency: Perhaps a bit more advanced, I usually run my stuff ontop of Mesos and Marathon. Marathon is like a global upstart for your cluster. It can relocate crashed Docker containers to healthy machines.
Might only be worth it when the stakes are higher though.
Looks like overhead for my case
michaeldrogalis: but thank you for advise
One thing I have been curious about: :onyx/medium :kafka I searched the codebase and this key (:onyx/medium) isn't used anywhere or I missed it. Yet the schema complains if it is not there. What is its purpose?
@chrisn: Convention, and reserved for future use.
Easier to loosen the schema later than tighten it.