We are hitting this limit, any way to increase this limit? error message points to Akka documentation. Do we need to compile marathon again to update this limit?
Sep 20 12:46:15 prd-XXXXXXXXXXX marathon[17315]: akka.stream.BufferOverflowException: Exceeded configured max-open-requests value of [32]. This means that the request queue of this pool (HostConnectionPoolSetup(prd-XXXXXXX,8080,ConnectionPoolSetup(ConnectionPoolSettings(4,0,0,32,1,30 seconds,ClientConnectionSettings(Some(User-Agent: akka-http/10.0.11),5000 milliseconds,10000 milliseconds,512,None,,List(),ParserSettings(2048,16,64,64,8192,64,268435456,256,1048576,Strict,RFC6265,true,Full,Error,Map(If-Range -> 0, If-Modified-Since -> 0, If-Unmodified-Since -> 0, default -> 12, Content-MD5 -> 0, Date -> 0, If-Match -> 0, If-None-Match -> 0, User-Agent -> 32),false,true,akka.stream.impl.ConstantFun$$$Lambda$571/1407428730@25a6c17b,akka.stream.impl.ConstantFun$$$Lambda$571/1407428730@25a6c17b,akka.stream.impl.ConstantFun$$$Lambda$572/1077316166@58aadde7),None),Legacy,1 second,TCPTransport),akka.http.scaladsl.HttpConnectionContext$@1dab33ce,akka.event.MarkerLoggingAdapter@398ab66b))) has completely filled up because the pool currently does not process requests fast enough to handle the incoming request load. Please retry the request later. See http://doc.akka.io/docs/akka-http/current/scala/http/client-side/pool-overflow.html for more information.
Head over to JIRA!
Please note that we use JIRA for issue tracking and only keep GitHub issues around to not break existing links. Please prefer filing issues directly in JIRA.
Use Improvement or Bug depending on the context of your report. Also make sure to create the issue in project MARATHON, which is the preset as per the provided link. You don't need to set any labels, components, or designate an assignee. Yet what helps us triaging your request is used version and environment, steps to reproduce, or any specific use case you have in mind.
You can sign in to JIRA using Github or Google as identity providers.
We are hitting this limit, any way to increase this limit? error message points to Akka documentation. Do we need to compile marathon again to update this limit?
Sep 20 12:46:15 prd-XXXXXXXXXXX marathon[17315]: akka.stream.BufferOverflowException: Exceeded configured max-open-requests value of [32]. This means that the request queue of this pool (HostConnectionPoolSetup(prd-XXXXXXX,8080,ConnectionPoolSetup(ConnectionPoolSettings(4,0,0,32,1,30 seconds,ClientConnectionSettings(Some(User-Agent: akka-http/10.0.11),5000 milliseconds,10000 milliseconds,512,None,,List(),ParserSettings(2048,16,64,64,8192,64,268435456,256,1048576,Strict,RFC6265,true,Full,Error,Map(If-Range -> 0, If-Modified-Since -> 0, If-Unmodified-Since -> 0, default -> 12, Content-MD5 -> 0, Date -> 0, If-Match -> 0, If-None-Match -> 0, User-Agent -> 32),false,true,akka.stream.impl.ConstantFun$$$Lambda$571/1407428730@25a6c17b,akka.stream.impl.ConstantFun$$$Lambda$571/1407428730@25a6c17b,akka.stream.impl.ConstantFun$$$Lambda$572/1077316166@58aadde7),None),Legacy,1 second,TCPTransport),akka.http.scaladsl.HttpConnectionContext$@1dab33ce,akka.event.MarkerLoggingAdapter@398ab66b))) has completely filled up because the pool currently does not process requests fast enough to handle the incoming request load. Please retry the request later. See http://doc.akka.io/docs/akka-http/current/scala/http/client-side/pool-overflow.html for more information.
Head over to JIRA!
Please note that we use JIRA for issue tracking and only keep GitHub issues around to not break existing links. Please prefer filing issues directly in JIRA.
Use
ImprovementorBugdepending on the context of your report. Also make sure to create the issue in projectMARATHON, which is the preset as per the provided link. You don't need to set any labels, components, or designate an assignee. Yet what helps us triaging your request is used version and environment, steps to reproduce, or any specific use case you have in mind.You can sign in to JIRA using Github or Google as identity providers.