Bug #4261
closedShorten events/search output in case of too long events
100%
Description
If events to show are too big (lot of sources/targets), search output chokes.
Trim those lists (all lists, even Categories or whatever may get screwed up by sending clients) early in the process to not choke reading, processing, templating and client browser on it.
Related issues
Updated by Pavel Kácha over 5 years ago
- Related to Bug #4253: Handling of too big events added
Updated by Pavel Kácha over 5 years ago
Note that Aug 7 labrea reporter got silenced (produces trimmed and split events), so look for older examples. (Maybe based on original Radko's example https://mentat-hub.cesnet.cz/mentat/events/show/26aa5f45-1a36-4bf4-b1ee-f2d5e9e1c140).
Updated by Radko Krkoš over 5 years ago
Another related effect is overload of disk subsystem (sustained disk utilization of ~80%) somewhere during import chain when processing such large events, leaving very little room for other activities, severely degrading overall performance. This has to be investigated further as it is effectively a DoS vector and there is a real chance of such events appearing from aggregators in near future.
Updated by Pavel Kácha over 5 years ago
- Related to Feature #4273: Consider/choose/implement different communication protocol added
Updated by Pavel Kácha over 5 years ago
- Related to deleted (Feature #4273: Consider/choose/implement different communication protocol)
Updated by Jan Mach over 5 years ago
- Status changed from New to Feedback
- % Done changed from 0 to 100
I think that with attached commit the issue should be resolved.