ReadStreamAsync produces an error log entry if the result stream is not enumerated

[alexeyzimarev]

Originated by: https://discuss.eventstore.com/t/deadlineexceeded-errors/2737

Code to reproduce the issue:

public async Task<bool> Exists(string stream) {
    await using var result = _client.ReadStreamAsync(Direction.Forwards, stream, StreamPosition.Start, 1);
    var state = await result.ReadState;
    return state != ReadState.StreamNotFound;
}

Since we're only interested in the read result and aren't enumerating the stream, gRPC client closes the stream after timeout exceeds.

Here is the log:

warn: Grpc.Net.Client.Internal.GrpcCall[7]
      gRPC call deadline exceeded.
fail: Grpc.Net.Client.Internal.GrpcCall[3]
      Call failed with gRPC error status. Status code: 'DeadlineExceeded', Message: ''.

The code still works but under load, such an app will produce lots of false warnings and errors in the logs.

The code snippet above disposes the enumerator but it doesn't seem to help.

[alexeyzimarev]

The same error appears in the log if I get one event from the result steam that has more events, even if I pass one as the count to the ReadEventsAsync. The event is returned but after a second or two, the same error appears in the log.

[pbn4]

@alexeyzimarev Any updates on this?

[ThomasBoettcherHolschen]

Hi, got the same issue. The problem is that when this error occurs the whole communication to the server failed.

Client:
EventStore.Client.Grpc (21.2.0).

Server:
eventstore:21.6.0-bionic Container.

I could get arround with an ugly workarround. I removed the single instance of EventStoreClient and replaced it with one instance per lifetimescope in my Autofac-DI. But I fear that the System will go down when under heavier load or running a less potent system. Maybe this helps someone.

[rmfaheem]

Seems to be identical to: EventStore/EventStore#2973

[tlutsyk]

Any updates on this?

[yurii-pelekh]

Any updates on this?

[gavinburge]

Any update on this?

[ylorph]

In 22.0 release of the client, we no longer set a deadline on Readstream
see here : #194

[brian-douglas]

I see the interface was changed, and I can set deadline on ReadStreamAsync(), but the problem still exists for me.

server version: 21.10.6.0
gRPC client version: 22.0.0

confirmation it was actually fixed with #194 ? If I downgrade the client back to 21.2.0, it's working again.

[KeesSchoutenEasySystems]

I ran into the same issue but fixed it by disposing the readstate.

The following code did not dispose the readstate in case the readstate was not an Ok response, see:

Fix:

@thefringeninja pointed me in the right direction:
https://discuss.eventstore.com/t/deadlineexceeded-errors/2737/11