something i’ve been forgetting to ask for a while - do onyx peers co-located in the same jvm each have their own classloader namespace ?

@mccraigmccraig No, they share the same classloader

I'm getting the above error and just been reading through https://clojurians-log.clojureverse.org/onyx/2016-09-07.html

was wondering if there were any other pointers other than "segments missing data" as I'm pretty certain they are not.

haha - I'm a div

the :onyx/fn of :engagement was (defn handler [state] (state))

hence: nil

it'd be convenient if onyx-dashboard represented selected tenancy in the url. would this be a welcome PR?

and is the app still maintained / used?

also: trying to figure out what this means in my datomic->elasticsearch job:

[idx-2631508155-r111c idx] java.lang.Thread.run              Thread.java:  745
[idx-2631508155-r111c idx] java.util.concurrent.ThreadPoolExecutor$Worker.run  ThreadPoolExecutor.java:  617
[idx-2631508155-r111c idx] java.util.concurrent.ThreadPoolExecutor.runWorker  ThreadPoolExecutor.java: 1142
[idx-2631508155-r111c idx] ...
[idx-2631508155-r111c idx] clojure.core.async/thread-call/fn                async.clj:  442
[idx-2631508155-r111c idx] onyx.log.commands.common/fn/start-new-lifecycle/fn/fn               common.clj:  162
[idx-2631508155-r111c idx] onyx.system.OnyxTask/start               system.clj:  130
[idx-2631508155-r111c idx] onyx.system/rethrow-component               system.clj:   86
[idx-2631508155-r111c idx] onyx.system.OnyxTask/fn               system.clj:  131
[idx-2631508155-r111c idx] com.stuartsierra.component/start-system           component.cljc:  163
[idx-2631508155-r111c idx] ...
[idx-2631508155-r111c idx] com.stuartsierra.component/update-system           component.cljc:  129
[idx-2631508155-r111c idx] com.stuartsierra.component/update-system           component.cljc:  135
[idx-2631508155-r111c idx] clojure.core/reduce                 core.clj: 6703
[idx-2631508155-r111c idx] ...
[idx-2631508155-r111c idx] com.stuartsierra.component/update-system/fn           component.cljc:  139
[idx-2631508155-r111c idx] com.stuartsierra.component/try-action           component.cljc:  117
[idx-2631508155-r111c idx] clojure.core/apply                 core.clj:  659
[idx-2631508155-r111c idx] ...
[idx-2631508155-r111c idx] com.stuartsierra.component/fn/G           component.cljc:    5 (repeats 2 times)
[idx-2631508155-r111c idx] onyx.peer.task-lifecycle.TaskLifeCycle/start       task_lifecycle.clj:  542
[idx-2631508155-r111c idx] onyx.lifecycles.lifecycle-invoke/invoke-lifecycle-gen/invoke-lifecycle    lifecycle_invoke.cljc:   26
[idx-2631508155-r111c idx] ...
[idx-2631508155-r111c idx] onyx.lifecycles.lifecycle-invoke/restartable-invocation    lifecycle_invoke.cljc:   18
[idx-2631508155-r111c idx] onyx.lifecycles.lifecycle-invoke/restartable-invocation    lifecycle_invoke.cljc:   20
[idx-2631508155-r111c idx] clojure.core/apply                 core.clj:  657
[idx-2631508155-r111c idx] ...
[idx-2631508155-r111c idx] clojure.core/comp/fn                 core.clj: 2542
[idx-2631508155-r111c idx] onyx.lifecycles.lifecycle-compile/compile-lifecycle-functions/fn/fn   lifecycle_compile.cljc:   63
[idx-2631508155-r111c idx] lab79.es-utils.onyx-ext/inject-writer             onyx_ext.clj:  107
[idx-2631508155-r111c idx] java.lang.AssertionError: Assert failed: (coll? hosts)
[idx-2631508155-r111c idx] clojure.lang.ExceptionInfo: Handling uncaught exception thrown inside task lifecycle - killing this job. -> Exception type: java.lang.AssertionError. Exception message: Assert failed: (coll? hosts)

Sometime to do with zookeeper:

:trace
 [[onyx.compression.nippy$fn__13691$fn__13692 invoke "nippy.clj" 33]
  [taoensso.nippy$read_custom_BANG_ invokeStatic "nippy.clj" 1052]
  [taoensso.nippy$read_custom_BANG_ invoke "nippy.clj" 1049]
  [taoensso.nippy$thaw_from_in_BANG_ invokeStatic "nippy.clj" 1218]
  [taoensso.nippy$thaw_from_in_BANG_ invoke "nippy.clj" 1098]
  [taoensso.nippy$thaw$thaw_data__13615 invoke "nippy.clj" 1330]
  [taoensso.nippy$thaw invokeStatic "nippy.clj" 1356]
  [taoensso.nippy$thaw invoke "nippy.clj" 1279]
  [onyx.compression.nippy$zookeeper_decompress invokeStatic "nippy.clj" 56]
  [onyx.compression.nippy$zookeeper_decompress invoke "nippy.clj" 55]
  [onyx.log.zookeeper$fn__16591$fn__16593$fn__16594 invoke "zookeeper.clj" 564]
  [onyx.log.zookeeper$clean_up_broken_connections invokeStatic "zookeeper.clj" 77]
  [onyx.log.zookeeper$clean_up_broken_connections invoke "zookeeper.clj" 75]
  [onyx.log.zookeeper$fn__16591$fn__16593 invoke "zookeeper.clj" 561]
  [onyx.monitoring.measurements$measure_latency invokeStatic "measurements.clj" 11]
  [onyx.monitoring.measurements$measure_latency invoke "measurements.clj" 5]
  [onyx.log.zookeeper$fn__16591 invokeStatic "zookeeper.clj" 560]
  [onyx.log.zookeeper$fn__16591 doInvoke "zookeeper.clj" 558]

java.lang.AssertionError: Assert failed: (coll? hosts) Maybe you’re not providing a collection of hosts to the plugin?

i'll check. my onyx-dashboard reflects the error though, so it seems that it is syncing state via zk

yeah looks right.

:zookeeper/address
  "zookeeper-0:2181,zookeeper-1:2181,zookeeper-2:2181",

ensemble looks good. 2 followers 1 leader.

found it. issue with my elasticsearch config

@devth We dont use the dashboard much internally at Distributed Masonry, but a PR would be welcome. I know a lot of companies do use it.

cool. what's your workflow for inspecting job state?

@devth That would take a while to answer since we’re hosting Onyx on behalf of multiple customers on our own hardware. The short answer is that we have a unidirectional architecture and derive all job state from the Onyx log. We use a log subscriber to follow the log and update job status in Datomic.

From there we have in-house dashboards that read from Datomic to control everything.

nice