Deployment Architecture

Fixing Buckets in a Cluster

agodoy
Communicator

I have 84 buckets that are in need of fixing.

The fix-up categories are:

data_safety
replication_factor
search_factor

The reason for the fix up seem to be related to some multi-site clustering configuration I was testing out earlier.

missing={ site2:2 } enough star targets=1

I have since changed the cluster configuration to single site. How do I fix those buckets?

Tags (3)
1 Solution

phoffman_splunk
Splunk Employee
Splunk Employee

after pulling the multi-site config out and confirming it's gone, did you restart the cluster? that would be a good place to start.

I would 1st restart the CM, then rolling-restart the peers and see if the issue was just a "stuck" config.

View solution in original post

phoffman_splunk
Splunk Employee
Splunk Employee

after pulling the multi-site config out and confirming it's gone, did you restart the cluster? that would be a good place to start.

I would 1st restart the CM, then rolling-restart the peers and see if the issue was just a "stuck" config.

agodoy
Communicator

Awesome! That took care of the problem. Thanks a lot.

0 Karma

phoffman_splunk
Splunk Employee
Splunk Employee
0 Karma

agodoy
Communicator

What would be the official method of verifying that the cluster is no longer running in multi-site mode? I am going based on the clustering view of the cluster master.

0 Karma
Get Updates on the Splunk Community!

More Ways To Control Your Costs With Archived Metrics | Register for Tech Talk

Tuesday, May 14, 2024  |  11AM PT / 2PM ET Register to Attend Join us for this Tech Talk and learn how to ...

.conf24 | Personalize your .conf experience with Learning Paths!

Personalize your .conf24 Experience Learning paths allow you to level up your skill sets and dive deeper ...

Threat Hunting Unlocked: How to Uplevel Your Threat Hunting With the PEAK Framework ...

WATCH NOWAs AI starts tackling low level alerts, it's more critical than ever to uplevel your threat hunting ...