You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Jun 17, 2024. It is now read-only.
When EventStore.JVM client subscribes too early before EventStore is fully functional (has built all of its indexes, etc), the subscription never gets notified of new additions to the stream.
The problem might be in the client, or might be in the server, but since I am not familiar with the internals, it is hard for me to gauge.
Execute ListenForChanges => will display just the 1,000,000th element to acknowledge it saw everything that was created by PushData
Execute PushData => will create 1,000,000 elements
Stop EventStore
rm -rf /var/lib/eventstore/index
Start EventStore
Wait for EventStore to have recreated all of its indexes (tail -f /var/log/eventstore/DATE/*.log)
Execute PushData => will create another 1,000,000 elements in the stream
At that point, ListenForChanges should be displaying all of the new elements. But nothing happens.
Alternative execution paths:
The code will work fine in the following cases if PushData is re-executed without steps 3 to 6 (restart EventStore and remove indexes)
The code will generally (not sure how reliably) work fine if the indexes are not removed but EventStore is restarted. Note the generally, since I am quite sure I have observed the same issue in production without manually removing indexes (but EventStore might have decided to rebuild its indexes for some reason).
The text was updated successfully, but these errors were encountered:
OK, so something related to this problem definitely changed in 4.1.1
This is what I get now:
Exception in thread "main" eventstore.OperationTimeoutException: Operation hasn't got response from server for PackOut(SubscribeTo(Stream(mystream),true),858149ff-a163-4d30-8846-5806f7e8a7c7,Some(UserCredentials(admin,***)))
Is that what you expect?
That definitely solves the issue on our side, since we would retry on any exception. Thanks!
Problem
When
EventStore.JVM
client subscribes too early before EventStore is fully functional (has built all of its indexes, etc), the subscription never gets notified of new additions to the stream.The problem might be in the client, or might be in the server, but since I am not familiar with the internals, it is hard for me to gauge.
Versions
akka:2.5.1
akka-http:10.0.5
eventstore-client:4.1.0
eventstore:4.0.1
How to reproduce
See: https://gist.github.com/samidalouche/4eaeb891dcd9c51ad987c1f87386b6d2
EventStore
instanceListenForChanges
=> will display just the 1,000,000th element to acknowledge it saw everything that was created by PushDatarm -rf /var/lib/eventstore/index
tail -f /var/log/eventstore/DATE/*.log
)At that point,
ListenForChanges
should be displaying all of the new elements. But nothing happens.Alternative execution paths:
PushData
is re-executed without steps 3 to 6 (restartEventStore
and remove indexes)generally
, since I am quite sure I have observed the same issue in production without manually removing indexes (but EventStore might have decided to rebuild its indexes for some reason).The text was updated successfully, but these errors were encountered: