You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Currently, if verticles are deployed during the boot process of NeonBee, it can happen that JobVerticles already start their work, even though NeonBee is still in a booting state. As verticles are deployed as a last step of the boot, this is often times not critical, but especially if verticles depend on each other through the event loop, it can result in non-deterministic behavior, especially if the job verticle calls the dependent verticle immediately.
Desired Solution
Wait for starting the "clock" of execution of all job-verticles until the boot process of NeonBee signals full completion.
Alternative Solutions
No response
Additional Context
No response
The text was updated successfully, but these errors were encountered:
Is there an existing issue for this?
The Problem
Currently, if verticles are deployed during the boot process of NeonBee, it can happen that
JobVerticle
s already start their work, even though NeonBee is still in a booting state. As verticles are deployed as a last step of the boot, this is often times not critical, but especially if verticles depend on each other through the event loop, it can result in non-deterministic behavior, especially if the job verticle calls the dependent verticle immediately.Desired Solution
Wait for starting the "clock" of execution of all job-verticles until the boot process of NeonBee signals full completion.
Alternative Solutions
No response
Additional Context
No response
The text was updated successfully, but these errors were encountered: