Getting Data In

[AWS TA] Data being delayed after 5.0.3 upgrade.

sylim_splunk
Splunk Employee
Splunk Employee

We are seeing delay in indexing - this started to happen after the AWS TA 5.0.3 upgrade from 4.0.6.

In the TA log there are many ERROR messages which appears to be much relevant.

sylim_splunk_0-1611879747839.png

 

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

sylim_splunk
Splunk Employee
Splunk Employee

This is a code error triggered by an incompatible behavioral change since python 3.7.

Apply the following patch to fix this problem.

1. Open bin/splunk_ta_aws/modinputs/kinesis/aws_kinesis_common.py by any text editor.
2. Replace `raise StopIteration()` by `return`.

You should find three occurrence at the line 251, 258 and 273.

View solution in original post

sylim_splunk
Splunk Employee
Splunk Employee

This is a code error triggered by an incompatible behavioral change since python 3.7.

Apply the following patch to fix this problem.

1. Open bin/splunk_ta_aws/modinputs/kinesis/aws_kinesis_common.py by any text editor.
2. Replace `raise StopIteration()` by `return`.

You should find three occurrence at the line 251, 258 and 273.

Career Survey
First 500 qualified respondents will receive a $20 gift card! Tell us about your professional Splunk journey.
Get Updates on the Splunk Community!

Thanks for the Memories! Splunk University, .conf25, and our Community

Thank you to everyone in the Splunk Community who joined us for .conf25, which kicked off with our iconic ...

Data Persistence in the OpenTelemetry Collector

This blog post is part of an ongoing series on OpenTelemetry. What happens if the OpenTelemetry collector ...

Introducing Splunk 10.0: Smarter, Faster, and More Powerful Than Ever

Now On Demand Whether you're managing complex deployments or looking to future-proof your data ...