Fork me on GitHub

has anyone ran into any issues with C3P0 deadlocks on the onyx-sql plugin before?


I haven’t seen them, but onyx-sql is mostly user maintained so I’ve never run it in prod


I have seen initial connection timeouts lately on CI, but it was because our CI was using latest for docker images, and we ended up with an incompatible mysql version.


i know the code quite well and it’s definitely not normal to have deadlocks, especially since the whole thing is single threaded. how are you using the plugin, mysql ?


also, when you say deadlocks, do you mean a timeout when acquiring a connection from the pool ? those are two different things.


@lucasbradstreet congrats with the release :)


very happy to see curator updated


Thanks. Just checking over everything before announcing 🙂


Hi everyone! Onyx 0.13.0 is out with a very minor breaking change that probably won’t affect anyone. It bumps curator so that ZooKeeper SSL is now supported.


Hey, we recently updated our code, everything passes unit tests and works fine for several days, but randomly our job goes from processing messages, then dumps something like this out, and then...... nothing. The job looks like it is running, the peers look like they are fine, but there is zero application or onyx level logging that appears again from the peers. (this is in an environment on a single box with 22 virtual peers). Just throwing it out there in case anyone has seen something similar, the only major addition is switching to an onyx output plugin that does Amazonica Lambda invocation.


Looks like the uri is missing for your request? uri=-}


not sure if something changed in how your urls got passed down to your lambda plugin but I’d check on the segments at that plugin.


yes i'm trying to debug the output plugin itself and throwing more judicious try-catch, I'm more concerned that this seems to shut the entire system down with zero logging from onyx, no missed heartbeats, virtual peers closing down, aeron messages, etc... it's like once this triggers, everything just stops. My understanding is there is a threadpool for the virtual peers so just curious that this seems to just freeze the entire thing


Ah right. Um, this is a plugin you wrote right?


If you’re not checking whether your async requests failed in the plugin, from Onyx’s perspective everything may be working fine.


Just a stab in the dark


From the point that error dump happens, no further messages seem to be processed. Literally the log file just stops, though the peers remain reporting as up and things seem like they are running from zk / onyx perspective, just no messages are consumed. I get that the output plugin might be FUBAR and not actually saving anything and fine with that, more concerned that everything else fails silently. Will circle back around once the error is figured out.


I assume it’s not possible that it just processed everything?


Anyway, let me know how you go.


Correct, input is a kafka stream that receives messages every minute, and we have another onyx cluster running with the former version of code which has no hiccups.


In that case I could see a situation where the plugin is returning false from synced?, prepare-batch, or write-batch


In that case it will continue to heartbeat, because Onyx is waiting for your work to finish, and the plugin is signalling to wait. In that case it’s still probably a problem dealing with the async requests


There are metrics/health checks that you’d be able to use to detect when it’s processing a certain epoch for a long time.