feat: parametrized timeout on KytosEventBuffer.put and exposing buffers queue size config #429
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Closes #423
This PR is on top of #438 since it depends on
event_buffer_conf
.Summary
See updated changelog file (it also explains how to use it)
Local Tests
I ran
kytosd
with my local env, still worked as it used to.I've also explored configurations on kytos.conf it's behaving as expected
I then simulated a NApp misbehaving by sending too many events during
setup()
withmef_eline
. Notice below that you can see exactly which producer couldn't put the event anymore, and then in the tracebacks it also includes who may events it had, which other events ended up filling the queue, in this case ``kytos/mef_eline.xyz'` had more than a 1000:End-to-End Tests
I'll dispatch e2e execution with this branch and the other NApps PR which are using
timeout=1
when putting events duringsetup()
: