onyx

FYI: alternative Onyx :onyx: chat is at <https://gitter.im/onyx-platform/onyx> ; log can be found at <https://clojurians-log.clojureverse.org/onyx/index.html>
sparkofreason 2018-05-08T00:07:35.000181Z

I must have done something wrong with docker.

dbernal 2018-05-08T14:51:16.000437Z

I'm getting a bunch of http async request exceptions on a Spandex output plugin that I built for writing to Elasticsearch. Is there a certain strategy I could employ to avoid these timeouts? Maybe something similar to the http-client? And more generally is this an issue with how thread heavy the peers are? I'm getting the exception pretty consistently after I input about 100 segments into the job.

dbernal 2018-05-08T15:09:24.000079Z

I think it might be an issue with the client and not Onyx. nvm

lucasbradstreet 2018-05-08T16:14:30.000250Z

Ah k. If it comes up again and you’re making a lot of async requests you may want to add some back pressure into prepare-batch/write-batch

dbernal 2018-05-08T18:32:31.000714Z

is there a good example of how to properly do back pressure somewhere? Running into some issues trying to set it up

lucasbradstreet 2018-05-08T18:35:02.000160Z

You can see an example of onyx-amazon-s3 doing some backpressure

lucasbradstreet 2018-05-08T18:35:51.000071Z

https://github.com/onyx-platform/onyx-amazon-s3/blob/0.12.x/src/onyx/plugin/s3_output.clj#L88 only take max-concurrent-uploads at a time, and return false to stay at this state in the state machine https://github.com/onyx-platform/onyx-amazon-s3/blob/0.12.x/src/onyx/plugin/s3_output.clj#L103

lucasbradstreet 2018-05-08T18:36:02.000048Z

by returning false it’ll call write-batch over and over, heartbeating in between

dbernal 2018-05-08T18:54:16.000572Z

thank you!