SPLK-2002(205Q) · Question #93
Which of the following is true regarding the migration of an index cluster from single-site to multi- site?
The correct answer is C. Existing single-site attributes must be removed. According to the Splunk documentation1, when migrating an indexer cluster from single-site to multi-site, you must remove the existing single-site attributes from the server.conf file of each peer node. These attributes include replication_factor, search_factor, and…
Question
Which of the following is true regarding the migration of an index cluster from single-site to multi- site?
Options
- AMulti-site policies will apply to all data in the indexer cluster.
- BAll peer nodes must be running the same version of Splunk.
- CExisting single-site attributes must be removed.
- DSingle-site buckets cannot be converted to multi-site buckets.
How the community answered
(52 responses)- A10% (5)
- B4% (2)
- C67% (35)
- D19% (10)
Explanation
According to the Splunk documentation1, when migrating an indexer cluster from single-site to multi-site, you must remove the existing single-site attributes from the server.conf file of each peer node. These attributes include replication_factor, search_factor, and cluster_label. You must also restart each peer node after removing the attributes. The other options are false because: Multi-site policies will apply only to the data created after migration, unless you configure the manager node to convert legacy buckets to multi-site1. All peer nodes do not need to run the same version of Splunk, as long as they are compatible with the manager node2. Single-site buckets can be converted to multi-site buckets by changing the constrain_singlesite_buckets setting in the manager node's server.conf file to "false"1.
Topics
Community Discussion
No community discussion yet for this question.