This version (2017/05/27 13:44) is a draft.
Approvals: 0/1

[02:29:45] <ayy> hi

[02:30:18] <ayy> anyone there?

[05:43:26] <Guest23008> hey, anyone here who has experience deploying vertx in production environments :)

[08:20:48] * ChanServ sets mode: +o temporalfox [11:44:10] * ChanServ sets mode: +o temporalfox

[12:12:53] * ChanServ sets mode: +o temporalfox [15:30:42] <melvinross> random question i've yet to find any help with [15:30:56] <melvinross> anyone know how to specifically start a timer off the event loop? [15:33:30] <melvinross> i've tried creating it inside of an execute blocking block and that didn't work. I've tried creating it inside of a regular old background thread from executors and that didn't work either [15:34:36] <Sticky> is vertx.setTimer not what you are looking for? [15:35:10] <melvinross> that sets the timer, but the thread the timer runs on is the event loop thread [15:35:47] <melvinross> i've read references to timers existing off the event loop, but can't figure out how to manage it [15:36:03] <melvinross> though now that i think about it, i could just create another thread inside of the method the timer calls and offload the work in there [15:36:10] <Sticky> well if you create a timer that is not on the eventloop vertxs single threaded model breaks down [15:37:00] <Sticky> you can probably put a timer into the worker pool [15:37:32] <melvinross> that's basically what i was trying to do [15:37:34] <melvinross> it breaks down if you start doing something that modifies state [15:37:42] <melvinross> i'm committing some values to zookeeper [15:38:25] <Sticky> that sounds like modifying state, but assuming your changes to zookeeper are atomic, probably fine [15:38:42] <melvinross> it's not modifying internal state [15:38:48] <melvinross> and it's the only thing that modifies zookeeper [15:39:43] <Sticky> no but if 2 of those threads run at the same time, both writing to the zookeeper, could they cause an invalid state in the zookeeper? [15:50:08] * ChanServ sets mode: +o temporalfox

[15:52:03] <melvinross> stupid plane internet. guess my response didn't send

[15:53:18] <Sticky> your last response was 14:38 < melvinross> and it's the only thing that modifies zookeeper

[15:53:32] <melvinross> two threads can't run at the same time. I'm using setTimer, which is one time, not setPeriodic, which is recurring. The timer is then recreated upon completion inside of the method the timer is calling. so only 1 active thread at a time

[15:56:06] <melvinross> i guess i could also wrap the method that's called inside of executeBlocking

[15:59:54] <melvinross> just not sure what's the proper way of handling it

[19:00:45] * ChanServ sets mode: +o temporalfox [20:21:36] * ChanServ sets mode: +o temporalfox

[23:49:21] *** ChanServ sets mode: +o temporalfox