-
Notifications
You must be signed in to change notification settings - Fork 796
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
Duplicate handler name: HttpStreamsClientHandler #1903
Comments
@oripwk can you reproduce the issue consistently? Can you provide a repro case? |
It looks like this issue hasn’t been active in longer than a week. In the absence of more information, we will be closing this issue soon. If you find that this is still a problem, please add a comment to prevent automatic closure, or if the issue is already closed please feel free to reopen it. |
I hit the same issue as can be seen in the below stack trace:
I wonder if it could be an async race condition? Unfortunately I cannot reliable reproduce it. |
I can also confirm this is occuring again:
|
I have these issues as well (exactly the same exception and cause), but can not reproduce it consistently. I have multiple sessions open as well (around 40). The use case is periodically dumping data from a db in files by certain properties.. sometimes 0 bytes for the file, sometimes a few hundred megabytes. |
…ea2251150 Pull request: release <- staging/076b46f0-e15d-414b-aaaa-62bea2251150
still present in 2.17.191. We have a scenario that reproduces consistently, its doing 16 S3 async put operations with chained futures that trigger a corresponding 16 S3 put acls (on a 0.5vCPU fargate task). It started as soon as we started chaining the async put acl on to the result of the put future. When changing the S3 clients completion executor to use the same executor that our non blocking futures use the issue stopped.
|
Describe the bug
Getting
Duplicate handler name: HttpStreamsClientHandler
with 16 concurrent requests when using S3 clientputObject
Expected Behavior
This exception should not be thrown
Current Behavior
Here's the stacktrace
Steps to Reproduce
Create 16 threads where each thread does 3 concurrent
putObject
requests.Possible Solution
No possible solution.
Context
It's an Apache Flink sink that's writing to S3 finished sessions
Your Environment
The text was updated successfully, but these errors were encountered: