A Splunk architect notices that Data Model Acceleration summaries are consuming excessive disk space. Which configuration setting in datamodels.conf should be adjusted to limit the storage impact of these summaries?
Trap 1: acceleration.earliest_time
This defines the start time for the acceleration, not the retention limit.
Trap 2: acceleration.backfill
This controls the initial creation of the summary.
Trap 3: acceleration.cron_schedule
This determines how often the summary is updated.
- A
acceleration.earliest_time
Why it fails: This defines the start time for the acceleration, not the retention limit.
- B
acceleration.backfill
Why it fails: This controls the initial creation of the summary.
- C
acceleration.max_time
This limits how far back in time the summary is kept on disk.
- D
acceleration.cron_schedule
Why it fails: This determines how often the summary is updated.