@lowl4tency: Gonna need a little more context there to help you.

@arohner: It's not core.async specific, simply omit sending the :done message to a source of input. Onyx uses a streaming engine under the covers, and the :done message is a form of punctuation that it leverages to become a batch hybrid.

You can implement everything you described above. Next release will include state and windowing primitives to do all of that for you - but we're at least 6 weeks away.

michaeldrogalis: we have 1 clojure-onyx app and 1 zookeeper process. It's all on 1 host. Sometimes clojure app is stuck. I trying to investigate

It's from zookeeper log file

I don't see any errors or overload

Hello, I am trying to add onyx into an app. Just adding the dependency causes an error :

#error {
 :cause Could not locate clojure/tools/reader/impl/ExceptionInfo__init.class or clojure/tools/reader/impl/ExceptionInfo.clj on classpath.

I tried requiring like that :

[org.onyxplatform/onyx "0.7.3" :exclusions [org.slf4j/slf4j-api org.slf4j/slf4j-log4j12 org.slf4j/slf4j-nop]]

In the REPL, I get an error when requiring timbre (same version as in onyx project.clj)

But again, removing onyx from my dependencies and the error goes away, so I'm not sure what to do.

* I mean in the repl, when moving to the file that fails and recompiling, it gives an error on the require timbre :

CompilerException java.lang.NoClassDefFoundError: Could not initialize class taoensso.timbre__init

@nha what version of clojure are you on?

@tcrayford: I am using 1.7

oh, that's odd 😞

well that's odd to me too 😕

What version of Java? (probably not it, but it's a weird issue and I don't know what else to suggest)

REPL-y 0.3.5, nREPL 0.2.10
Clojure 1.7.0
Java HotSpot(TM) 64-Bit Server VM 1.8.0_45-b14

(on osx)

I use pedestal if it matters

I tried onyx 0.7.2 too

Yeah, it could be dependency resolution is forcing a lower dependency of something. lein deps :tree could help

well there is that :

[org.onyxplatform/onyx "0.7.3" :exclusions [org.slf4j/slf4j-api org.slf4j/slf4j-log4j12 org.slf4j/slf4j-nop]] -> [org.apache.zookeeper/zookeeper "3.4.1" :exclusions [org.slf4j/slf4j-log4j12 io.netty/netty]] -> [jline "0.9.94"] -> [junit "3.8.1"]
 overrides
[siren "0.2.0"] -> [domina "1.0.0"] -> [org.clojure/clojurescript "0.0-1424"] -> [com.google.javascript/closure-compiler "r1918"] -> [junit "4.8.2"]

oh wait there is more

it's big - sorry about that - but there are messages related to onyx

Sorry, getting a flight so I won't be able to help out for a bit

Sure no problem. Have a nice flight

@lowl4tency: I need more context is terms of "what was going on at the time?", what in particular do you mean by "stuck"? Those error messages indicate that your ZooKeeper lost data. It simply tried to read a value from a znode that apparently doesn't exist anymore. Is 4068bfc4-7049-4a9d-a4f3-0dc5dcdb3aa7 the Onyx deployment ID you're using, as indicated by that error message?

Specifically, the two values in that error message, the values for job-scheduler and messaging, are values that are required to be known before the Onyx dashboard can start, as they are set by peers which influence the way log entries are applied

@michaeldrogalis: those error messages are from creates, not gets - they're trying to create a node that already exists (which is an error in zk)

@tcrayford: Ah! Thanks for the correction. "NodeExists" and "NoNodeExists" often play a trick on my eyes.

haha yeah