Open cbgrasshopper opened 1 year ago
After email exchanges with Event Store support, it turns out that the issue was having a readBatchSize greater than the buffer size; configuring the buffer size to be greater than the readBatchSize when creating the persistent subscription works. So the true unexpected behavior is more about how the error is reported back to the client.
Describe the bug Using .NET gRPC client v 23.0.0 and creating a persistent subscription to $all. When I call
CreateToAllAsync
when connecting to Event Store Cloud v 22.10.0.0, single node cluster, everything works as expected. When I run the exact same code connecting to Event Store Cloud v 21.10.4, three-node cluster, I always get a DeadlineExceeded error, even with an extremely long deadline. I've tried both with esdb+discover and with a direct connection to the leader node; no luck. Cloud provider is Microsoft Azure.To Reproduce Steps to reproduce the behavior:
Expected behavior The three-node cluster v 21.10.4 should properly create a persistent subscription as the 22.10 cluster does; no DeadlineExceeded error in the client.
Actual behavior The following exception occurs:
Config/Logs/Screenshots
EventStore details
EventStore server version: 21.10.4 and 22.10.0.0
Operating system: Managed by Event Store Cloud
EventStore client version (if applicable): .NET gRPC 23.0.0 (also tried 22.0.0)
Additional context