原创

失敗後、AWS S3 非同期クライアントでそれ以上の接続を取得できません

温馨提示:
本文最后更新于 2024年04月12日,已超过 37 天没有更新。若文章内的图片失效(无法正常加载),请留言反馈或直接联系我

Java AWS SDK V2 と netty nio クライアント V2 を使用すると、アプリケーションを DDOS してエラーが発生する現場に遭遇しました。

"Caused by: java.lang.Throwable: Acquire operation took longer than the configured maximum time. This indicates that a request cannot get a connection from the pool within the specified maximum time. This can be due to high request rate.
Consider taking any of the following actions to mitigate the issue: increase max connections, increase acquire timeout, or slowing the request rate.
Increasing the max connections can increase client throughput (unless the network interface is already fully utilized), but can eventually start to hit operation system limitations on the number of file descriptors used by the process. If you already are fully utilizing your network interface or cannot further increase your connection count, increasing the acquire timeout gives extra time for requests to acquire a connection before timing out. If the connections doesn't free up, the subsequent requests will still timeout.
If the above mechanisms are not able to fix the issue, try smoothing out your requests so that large traffic bursts cannot overload the client, being more efficient with the number of times you need to call AWS, or by increasing the number of hosts sending requests."

チューニングはさておき、なぜアプリケーションはこの問題から回復できないので?続行のすべてのリクエストは、イベントから数時間後であっても、引き続き例外をスローします。回復する唯一の方法はアプリケーションを再起動しますすることですが、これは面白いと思います。

ありがとう

正文到此结束
热门推荐
本文目录