Deployment Architecture

Cannot replicate remote storage enabled warm bucket

John_Littleton
Explorer

8.2.5 Enterprise 

_internal index has 5 buckets with this error:

ClusterSlaveBucketHandler [xxxxxx TcpChannelThread] - Failed to trigger replication (err='Cannot replicate remote storage enabled warm bucket, bid=_internal~xx~xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx until it's uploaded

Restarting the CM dropped the bucket in fixup from 25 to 5, but these 5 remain.

Anyone facing this or have any resolution tips?

Thanks!

Labels (1)
Tags (2)
0 Karma
1 Solution

gcusello
SplunkTrust
SplunkTrust

Hi @John_Littleton,

being production data, I hint to open a case to Splunk Support.

Ciao.

Giuseppe

View solution in original post

John_Littleton
Explorer

Thank you @gcusello and sorry for the delayed acceptance. FYI for anyone looking for the specific solution, it was a known 8.2.6 issue

https://docs.splunk.com/Documentation/Splunk/8.2.6/ReleaseNotes/Knownissues
SPL-200532

0 Karma

gcusello
SplunkTrust
SplunkTrust

Hi @John_Littleton,

being production data, I hint to open a case to Splunk Support.

Ciao.

Giuseppe

Got questions? Get answers!

Join the Splunk Community Slack to learn, troubleshoot, and make connections with fellow Splunk practitioners in real time!

Meet up IRL or virtually!

Join Splunk User Groups to connect and learn in-person by region or remotely by topic or industry.

Get Updates on the Splunk Community!

Data Outage Monitoring and Reporting

We’ve all been there, right? Living our best life, working on our Splunk environment, when out of nowhere a ...

Manage Datasets and Connections in Catalog on Splunk Cloud Platform

Set Up Data Where You Use It Catalog already helps teams find and understand data across Splunk indexes, ...

Persistent Queue at TcpOut — One of Splunk's Most Practical Features

Splunk introduced persistent queueing at the tcpout layer as one of the most practical resilience features in ...