Deployment Architecture

What is the retention period and volume limit on reserved copies in multisite indexer clustering

keerthana_k
Communicator

Hi,

Splunk documentation mentions that in case of site failure in a multisite indexer clustering deployment, the master maintains reserved copies of data to be assigned to peers of the non-functional site once it starts functioning again. Is there is any restriction on the time period upto which the reserved copy is kept alive waiting for the site to be up again? Similarly, is there any volume restriction for the same?

Thanks,
Keerthana

0 Karma

Masa
Splunk Employee
Splunk Employee
  1. Site1 and Site2 exisit, at this point all copied buckets of site2 are available in site1
  2. CM identify all CPs on Site2 become Down
  3. at this point all copied buckets of site2 are still available in site1 => The copied buckets are available until retention policy (size or time) is hit

For more information about retention policy, I recommend to read doc starting from here.
http://docs.splunk.com/Documentation/Splunk/6.5.0/Indexer/Configureindexstorage

0 Karma
Career Survey
First 500 qualified respondents will receive a $20 gift card! Tell us about your professional Splunk journey.
Get Updates on the Splunk Community!

Tech Talk Recap | Mastering Threat Hunting

Mastering Threat HuntingDive into the world of threat hunting, exploring the key differences between ...

Observability for AI Applications: Troubleshooting Latency

If you’re working with proprietary company data, you’re probably going to have a locally hosted LLM or many ...

Splunk AI Assistant for SPL vs. ChatGPT: Which One is Better?

In the age of AI, every tool promises to make our lives easier. From summarizing content to writing code, ...