Pedro Cunha

Hey @adamof - very good point and been want to address this for a long time, however depends on how you want to think about it. It is your machine...

We still don't know what caused this but a couple of things: 1. This only happened for a particular service that uses context timeouts 2. We have not seen this...

We had one occurrence of this issue with r6g.xlarge and 6.2. Seems that tweaking the limiter to be more aggressive and reducing the pool size has helped us. We haven't...

@KasonBraley did you find a workaround this?