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
Event table can grow without limits. This may lead to crash or server may hang, especially when badly written application registers interest to events in uncontrolled way (quick loop etc.). Engine should prevent this situation by imposing a hard limit to event table size, preferably as configurable value.
The text was updated successfully, but these errors were encountered:
This limit should be on memory size, not on number of events registered. Right now event table can grow without limits (and when it exceeds several hundred MB's it will cause serious problems, especially when event table management code in engine will not be changed to be more effective and faster). I guess that sensible default limit of 128MB with possibility to change it in configuration would be a good start. Event registration data structure has variable size in relation to event names, so actual number how many events could registered in total will vary.
This request was sparked by real situation when badly written application registered interest for event notification every 20ms. This eventually hangs the server. Right now engine doesn't have any defense to this scenario.
Submitted by: @pcisar
Replaces CORE5604
Event table can grow without limits. This may lead to crash or server may hang, especially when badly written application registers interest to events in uncontrolled way (quick loop etc.). Engine should prevent this situation by imposing a hard limit to event table size, preferably as configurable value.
The text was updated successfully, but these errors were encountered: