search

aerosol / kai

:alien: Erlang KairosDB Client
MIT License
4 stars 3 forks source link

ELB ping must be smarter #5

Open aerosol opened 10 years ago

aerosol commented 10 years ago

Right now it only keeps-alive erlang node <-> kairos but doesn't kairos <-> cassandra.

Solution: periodically put metric with timestamp=0 value=now() and tag=node().

@loucash ?

loucash commented 10 years ago

If it is just for pings, than personally, I prefer to "read" which is less invasive.

aerosol commented 10 years ago

But reads go through a different port and won't keep the write socket alive

aerosol commented 10 years ago

So perhaps version for telnet ping and read foobar for cassandra ping?

loucash commented 10 years ago

awesome :+1:

AeroNotix commented 10 years ago

:+1: I approve of this message

aerosol commented 10 years ago

Pros for write: can query kairos for client pings / writes are cheaper? Pros for read: separation of concerns, not polluting the DB with writes user may not care about, even if deploying on AWS

I'm conflicted ;-)

loucash commented 10 years ago

Exactly, that is why I wrote "if just for pings" -> read, "querying for kairos client pings" is a perfect reason for writes.

Let user decide, add option in configuration, implement both ;-)

aerosol commented 10 years ago

Shame there is no ying-yang emoji.

aerosol commented 10 years ago

Tentative start here https://github.com/aerosol/kai/pull/7

To be improved..