michaeldrogalis: hi Michael

I have next errors on zookeeper

2015-09-18 22:04:24,249 [myid:] - INFO [ProcessThread(sid:0 cport:-1)::PrepRequestProcessor@645] - Got user-level KeeperException when processing sessionid:0x14fd65dd8ff00df type:create cxid:0xe zxid:0xd280 txntype:-1 reqpath:n/a Error Path:/onyx/4068bfc4-7049-4a9d-a4f3-0dc5dcdb3aa7/job-scheduler Error:KeeperErrorCode = NodeExists for /onyx/4068bfc4-7049-4a9d-a4f3-0dc5dcdb3aa7/job-scheduler 2015-09-18 22:04:24,250 [myid:] - INFO [ProcessThread(sid:0 cport:-1)::PrepRequestProcessor@645] - Got user-level KeeperException when processing sessionid:0x14fd65dd8ff00df type:create cxid:0xf zxid:0xd281 txntype:-1 reqpath:n/a Error Path:/onyx/4068bfc4-7049-4a9d-a4f3-0dc5dcdb3aa7/messaging Error:KeeperErrorCode = NodeExists for /onyx/4068bfc4-7049-4a9d-a4f3-0dc5dcdb3aa7/messaging

Have not an idea what is it and how to fix

are there any docs on how to do real-time processing? I’ve perused the docs, and I think I understand how to make onyx do map-reduce style jobs, but I don’t understand how to make it do storm-style jobs

taking a step back, I have some time-series data. I’d like to do some transducer-style processing to it, breaking into buckets and computing metrics, etc, then store those metrics in different buckets, per-minute, per-hour, per-day.

ideally, I’d also like to be able to get a real-time view on the current hour “for the hour that is currently in process, the metric is X”. Does that sound like a good fit for onyx?

@lowl4tency: that zookeeper error is probably fine

Zookeeper is bad and logs a lot of "errors" that aren't actually errors

ah, so for realtime, it’s all just core.async, so I don’t stick :done in the channel

so then I just need an output channel that behaves the way I want

one tap sending unique values to the DB, one tap that has the ‘current’ value