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.

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!

Index This | What travels the world but is also stuck in place?

April 2026 Edition  Hayyy Splunk Education Enthusiasts and the Eternally Curious!   We’re back with this ...

Discover New Use Cases: Unlock Greater Value from Your Existing Splunk Data

Realizing the full potential of your Splunk investment requires more than just understanding current usage; it ...

Continue Your Journey: Join Session 2 of the Data Management and Federation Bootcamp ...

As data volumes continue to grow and environments become more distributed, managing and optimizing data ...