IMPORTANT ANNOUNCEMENT: On May 6, 2024, Carbon Black User eXchange (UeX) and Case Management will move to a new platform!
The Community will be in read-only mode starting April 19th, 7:00 AM PDT. Check out the blog post!
You will still be able to use the case portal to create and interact with your support cases until the transition, view more information here!

EDR: How is Data Retention Determined?

EDR: How is Data Retention Determined?

Environment

  • EDR Server:  All Supported Versions 

Question

How is Data Retention Determined?

Answer

Event retention is based on the first hit configuration in /etc/cb/cb.conf. 
  • MaxEventStoreDays: Default is set to 30 days. If event data is older than 30 days the oldest event core will be removed or converted to cold storage if enabled.
  • MaxEventStoreSizeInMB: Similar to MaxEventStoreSizeInPercent, if the size of the total event store hits this parameter, the oldest event cores will be removed or converted to cold storage until the size is back under the limit.
  • MaxEventStoreSizeInPercent: Default is 90%. Determines if the partitioned disk size where the event cores reside has hit the total disk percentage. This is to avoid filling the disk, causing the EDR  Server to no longer function. The oldest core will be deleted or converted to cold storage if enabled.
  • MinAvailableSizeInMB: This is set when AlwaysDeleteColdPartitions is set to False. This parameter when set will remove the oldest warm core instead of converting to cold storage if conditions are met.
  • SolrTimePartitioningActivePartitions: This setting controls the number of actively searched Solr partitions that remain in the query index i.e warm cores. 
  • SolrTimePartitioningMinutes: This setting controls how many minutes a partition will be written to before moving to the next writer core.

Additional Notes


Related Content


Labels (1)
Tags (2)
Was this article helpful? Yes No
100% helpful (3/3)
Article Information
Author:
Creation Date:
‎11-06-2019
Views:
4342
Contributors