Deployment Architecture

Cluster Master restarts kills s3-compliant on-prem SmartStore since upgrading to Splunk 9

javiergn
Super Champion

Hi all. I’ve got an interesting case:

  • $Customer using on-prem fully s3-compliant storage: DELL ECS
  • When restarting the Cluster Master (and only the CM, not the Indexers) that triggers thousands of timeout events from S3.
  • Is like the S3 cluster is having a denial-of-service attack
  • This is ONLY happening since we upgraded from 8.2.6 to Splunk 9.0.4 in April 29th. No issues before.
  • See screenshot below.

What exactly are the Indexers requesting from s3 when the CM is restarted?

How is this process different in Splunk 8.2.6 and Splunk 9.0.4?

Regards,

J

S2_CM_Restarts.png

Labels (1)
0 Karma
Get Updates on the Splunk Community!

[Live Demo] Watch SOC transformation in action with the reimagined Splunk Enterprise ...

Overwhelmed SOC? Splunk ES Has Your Back Tool sprawl, alert fatigue, and endless context switching are making ...

What’s New & Next in Splunk SOAR

Security teams today are dealing with more alerts, more tools, and more pressure than ever.  Join us on ...

Your Voice Matters! Help Us Shape the New Splunk Lantern Experience

Splunk Lantern is a Splunk customer success center that provides advice from Splunk experts on valuable data ...