Declan Messer

Assuming you are in a Linux environment, could you attempt to reproduce this in a Windows environment and let me know your results. @nikita-petko

> @DeclanFrampton these were all performed on Windows machines. Thats that idea out the window then, what are the system specs(probs not the issue, always good to have more info...

> 24 cores, 32GiB of physical memory. Windows Server 2019 Datacenter. 10GbE > > 1. Yes > 2. The version was running fine and then stopped working completely, I shrugged...

I can confirm that this issue is persistent when shards are greater than or equal to 6. Once I get some free time later on today I will take a...

Conducted some additional testing, it seems the shard that gets timed out usually reconnects directly after. Always get the exception with 7 shards and over. Can you confirm this is...

> Same but with 6 shards and over: > >  Least we can reproduce now, does the shard reconnect, if so does it continue to cause issues as time...

> The shard will just continue to timeout, but will try to reconnect. But it causes all the other shards to fail Ok, I've asked a maintainer to see if...

Seems like it will be an issue on your side rather than library. > Received an unexpected EOF or 0 bytes from the transport stream.

I am assuming this would close the PR #2765 correct? @josago97 If so, link this bug within the PR with closes tag and if/when PR is approved this will also...