Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

com.splunk.hecclient.HecException: max outstanding events have reached, pause the pull for a while #443

Open
Sreehari2001 opened this issue Oct 25, 2024 · 0 comments

Comments

@Sreehari2001
Copy link

Hi team,

I recently experienced this issue and post this Splunk isn't able to poll any messages. Is there any threshold set in the configuration or what is the default threshold?
I am trying to understand on when this problem arises?

My initial analysis is as follows:
When I try to send 100 messages to Splunk and due to its efficiency it could only take 80 and remaining 20 were paused at that moment and after sometime these remaining messages are also polled. However, these 20 will be added to offset no matter if they are polled later. I am wandering this offset got cumulated/increased in the same way and reached the threshold limit which resulted in this error.

Based on my research, many have suggested to add the offset.flush.interval.ms in properties which I have already added and gave as 10s.
Despite this property being added, I still faced this issue. Is there anything that I understood wrong or is my analysis no where related to this problem.

Apologies if its irrelevant.

It would be helpful if you suggest how to resolve this :)

Thanks in Advance.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant