Correct:
KV store can reside on a search head cluster. However, the search head cluster does not coordinate replication of KV store data or otherwise involve itself in the operation of KV store. For information on KV store, see About KV store in the Admin Manual.
Actually yes.. page 219 of Cluster Admin pdf is correct too. it says: SHC captain and KV store primary synchronize their member lust everytime there is a status change -> so must be all ABCD than.
can't believe no one noticed this lol..D is definitely wrong, because the term "search peers" is another name for indexers and a captain doesn't replicate to search peers, it replicates to search head cluster members
ABD
The KV store and search head clustering operate pretty much independently.
The KV store captain is elected by its peers, just like the search head captain, although it is different code that runs those two elections. It's possible that one node would end up hosting both captains, but not necessary.
The potential warning you point out is not a warning, but rather information about how kv store handles reads and writes. And where exactly do you think the docs are in conflict? KV store runs on a search head cluster, but search head clustering doesn't interact with the KV store.
Option D is incorrect because the SHC captain is not responsible for replicating the SHC's knowledge bundle to the search peers. The SHC captain is responsible for managing the configuration and state of the SHC, including distributing the knowledge bundle to the other search heads in the cluster. However, it is the search peers that perform the actual searching against the indexed data, and they do not rely on the SHC captain to replicate the knowledge bundle.
ABCD
C: Slide219 (cluster) SHC captain and KV store primary synchronize their member lust everytime there is a status change The captain also coordinates activities among all cluster members
D:slide186 cluster: Bundle replication to search peers happens only from the captain
Answers A, B and D
https://docs.splunk.com/Documentation/Splunk/latest/DistSearch/SHCarchitecture#Role_of_the_captain
In the last topic ("Search head clustering and KV store") we can read:
KV store can reside on a search head cluster. However, the search head cluster does not coordinate replication of KV store data or otherwise involve itself in the operation of KV store. For information on KV store, see About KV store in the Admin Manual.
ABCD:
c: Slide219 (cluster) SHC captain and KV store primary synchronize their member lust everytime there is a status change
The captain also coordinates activities among all cluster members. Its responsibilities include:
Scheduling jobs. It assigns jobs to members, including itself, based on relative current loads.
Coordinating alerts and alert suppressions across the cluster. The captain tracks each alert but the member running an initiating search fires it.
Pushing the knowledge bundle to search peers.
Coordinating artifact replication. The captain ensures that search artifacts get replicated as necessary to fulfill the replication factor. See Choose the replication factor for the search head cluster.
Replicating configuration updates. The captain replicates any runtime changes to knowledge objects on one cluster member to all other members. This includes, for example, changes or additions to saved searches, lookup tables, and dashboards. See Configuration updates that the cluster replicates.
It's slippery terminology. In the pdf they say replicate, in the docs push.
upvoted 1 times
...
...
...
Log in to ExamTopics
Sign in:
Community vote distribution
A (35%)
C (25%)
B (20%)
Other
Most Voted
A voting comment increases the vote count for the chosen answer by one.
Upvoting a comment with a selected answer will also increase the vote count towards that answer by one.
So if you see a comment that you already agree with, you can upvote it instead of posting a new comment.
ChantreyC
Highly Voted 4 years agoSpTester
3 years, 8 months agoSpTester
3 years, 8 months agoqtygbapjpesdayazko
1 year, 6 months agohamzaissam92
Highly Voted 2 years ago5fdcf4a
3 days, 2 hours ago580ce47
Most Recent 3 weeks, 3 days agoCactiAZ
4 months agoMntman77
9 months, 2 weeks agob5white
1 year, 7 months agoMaryKey
1 year, 7 months agoqtygbapjpesdayazko
1 year, 8 months agodeepali_2710
1 year, 10 months agoHemnaath
1 year, 11 months agoProctor
2 years, 4 months agoqtygbapjpesdayazko
1 year, 6 months agoorezaie
2 years, 5 months agoRedYeti
2 years, 10 months agomanu78
3 years, 10 months ago[Removed]
3 years, 11 months ago[Removed]
3 years, 11 months agoHamiltonian
3 years, 7 months ago