Bug #3910
open
datasets: for type string the memcap isn't applied to the string data
Added by Victor Julien over 3 years ago.
Updated over 2 years ago.
Description
The memcap checking and tracking only tracks the fixed size THashData and StringType, but not the length of the data in StringType::ptr.
- Description updated (diff)
- Status changed from New to Assigned
- Assignee set to Shivani Bhardwaj
- Target version set to 7.0.0-beta1
One issue is how to deal with upgrades. If suddenly more data is accounted in the memcap, existing setups might suddenly hit the memcap after upgrading.
I don't see a nice way about it. Does this mostly refer to setting of a memcap in a rule where the user will have a harder time changing it assuming they are getting it from a 3rd source?
Could we define a dataset name under datasets before loading the rule that defines that dataset, the memcap set there would serve as an override?
- Target version changed from 7.0.0-beta1 to 8.0.0-beta1
Also available in: Atom
PDF