Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Message that job couldn't be found after ZK reconnection #70

Open
mariusz-jachimowicz-83 opened this issue Nov 10, 2016 · 0 comments
Open

Comments

@mariusz-jachimowicz-83
Copy link
Contributor

mariusz-jachimowicz-83 commented Nov 10, 2016

In situation when:

  • run job from backend onyx.peer.dag-test
  • pick up job in the dashboard
  • restart onyx.peer.dag-test
  • job couldn't be found

Provide msg in the dashboard that 'After reconnection this Job couldn't be found . Please select another job from selectbox.

Currently I see only error on console.

org.apache.zookeeper.KeeperException$NoNodeException: KeeperErrorCode = NoNode for /onyx/515fe4de-6bc9-441b-81b1-93c361eed795/log
    code: -101
    path: "/onyx/515fe4de-6bc9-441b-81b1-93c361eed795/log"

Exception in thread "async-thread-macro-2" java.lang.IllegalArgumentException: No method in multimethod 'apply-log-entry' for dispatch value: null
	at clojure.lang.MultiFn.getFn(MultiFn.java:156)
	at clojure.lang.MultiFn.invoke(MultiFn.java:233)
	at lib_onyx.log_subscriber$apply_entries_BANG_$fn__31633.invoke(log_subscriber.clj:11)
	at clojure.core.async$thread_call$fn__8522.invoke(async.clj:434)
	at clojure.lang.AFn.run(AFn.java:22)
	at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
	at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
	at java.lang.Thread.run(Thread.java:745)
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant