Timeout issue when using EventStore.read_stream_forward\3 #92
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
I am having a few issues when trying to read a large number of events from a stream (> 1,000). Obviously, I can just reduce the number of events to read and spread it out over many requests. However sometimes, my internet isn't the best (Australian internet can be shit) and reading a small number of events (~100) also fails.
I would like to add a parameter or configuration option to the
read_stream_forward
method so that we can increase theGenServer.call
timeout.The attached changes do it in a pretty crude manner, but it works for my purposes. I am open to suggestions on how we can clean it up. We should also add the timeout options to other similar methods such as
EventStore.read_all_streams_forward
.