@drewverlee in case it helps, we are using aleph for the clj server-side websocket support, chord for the cljs client-side, and (non-persistent) gnatsd for the pusbub to feed the websockets - our onyx jobs output segments which get put onto user topics on gnatsd, while the aleph websocket endpoints listen on their user's gnatsd topic

hi all, if i am processing a batch of requests (using a batch-fn) and one of them fails, is there a way to allow the other segments to proceed whilst retrying the one that failed (perhaps including it with the next batch?)

i'm trying to work out how a single message can not block a load of otherwise fine messages from proceeding

i'm having a go at upgrading to onyx-0.11 - i'm seeing exceptions in my log like

org.apache.kafka.common.errors.TimeoutException: Timeout expired while fetching topic metadata
                     clojure.lang.ExceptionInfo: Caught exception inside task lifecycle :lifecycle/initializing. Rebooting the task. -> Exception type: org.apache.kafka.common.errors.TimeoutException. Exception message: Timeout expired while fetching topic metadata
       job-id: #uuid "b271ac49-f576-594f-0617-4f21bdaf289f"
     metadata: {:job-id #uuid "b271ac49-f576-594f-0617-4f21bdaf289f", :job-hash "d8f9c3d7dc5aba1064eb5871505aab9ea279452f4965bc97ae42e87d6a29708a"}
      peer-id: #uuid "eb606f46-8f7c-34e7-ad4b-ac4b96df9eb3"
    task-name: :read-routable-messages

does this seem familiar to anyone ?

nvm - i think that exception was a red herring 🐡

Will check it out when we’re back. @lucasbradstreet and I are both traveling.

i was told to come here question about kafka i just started could anyone point me to direction where to get foundation docs are good i hear any books, blogs etc? where do you get your information, best practices and such?