Project

General

Profile

Actions
Copy link

Bug #3910

closed
VJ SB

datasets: for type string the memcap isn't applied to the string data

Bug #3910: datasets: for type string the memcap isn't applied to the string data

Added by Victor Julien over 5 years ago. Updated almost 2 years ago.

Status:
Closed
Priority:
Normal
Assignee:
Shivani Bhardwaj
Target version:
8.0.0-beta1
Affected Versions:
Effort:
Difficulty:
Label:

Description

The memcap checking and tracking only tracks the fixed size THashData and StringType, but not the length of the data in StringType::ptr.

VJ Updated by Victor Julien over 5 years ago Actions
Copy link
 #1

  • Description updated (diff)

VJ Updated by Victor Julien over 5 years ago Actions
Copy link
 #2

  • Status changed from New to Assigned
  • Assignee set to Shivani Bhardwaj
  • Target version set to 7.0.0-beta1

VJ Updated by Victor Julien almost 5 years ago Actions
Copy link
 #3

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.

JI Updated by Jason Ish almost 5 years ago Actions
Copy link
 #4

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?

VJ Updated by Victor Julien over 4 years ago Actions
Copy link
 #5

  • Target version changed from 7.0.0-beta1 to 8.0.0-beta1

SB Updated by Shivani Bhardwaj almost 2 years ago Actions
Copy link
 #6

  • Status changed from Assigned to In Review

SB Updated by Shivani Bhardwaj almost 2 years ago Actions
Copy link
 #7

  • Status changed from In Review to Closed
Actions
Copy link

Also available in: PDF Atom