-
Notifications
You must be signed in to change notification settings - Fork 910
firehoseAsyncClient intermittently fails to publishBatchRecords #2312
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
Comments
Forgot to mention, K8s shows no 'Events' indicating an issue with the pod. |
@aiasmartakis is it possible to log the whole exception object, instead of the exceptions parts? Having the stacktrace would be very helpful in the investigation. |
@debora-ito changing to: I'll get back to you. |
Let us know what you find. |
apologies it took longer than it should: this is the full error:
I also see these similar but slightly different traces:
|
@aiasmartakis I'm sorry for loosing track of this. Are you still experiencing the issue?
|
I admit also forgetting about it. I don't think it has showed up again. We did increase memory etc on our k8s cluster but I'm hesitant to point in a certain direction as far as what could've fixed it. |
That's ok, glad you are not seeing this anymore. I'll go ahead and close this, feel free to reach out if you have any other question. |
|
…b9d95f04b Pull request: release <- staging/224b5b02-7f71-46fc-9c45-a2fb9d95f04b
Describe the issue
A java client (running in docker container on k8s cluster) sends metrics to firehose through the SDK (v2.7.10). We use AWS Organizations so have different production vs QA (staging) environments. In our production environment (that has significant extra load) this issue has not shown, however in our QA environment this fails some of the time. I estimate over 80% is send using this same code fi
full_code.zip
ne. The load per invoke of putRecordBatch is in the KBs, well below documented limits. Annoyingly I also do not receive any details as to why it fails, using the ASyncClient I extended the BIConsumer to override the accept method.
Steps to Reproduce
Current Behavior
Your Environment
The text was updated successfully, but these errors were encountered: