-
Notifications
You must be signed in to change notification settings - Fork 2k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Issues with streams during rolling deploy (Orleans.Streams.QueueCacheMissException) #8986
Comments
erikljung
changed the title
Issues with Orleans.Streams.QueueCacheMissException during rolling deploy
Issues with streams during rolling deploy (Orleans.Streams.QueueCacheMissException)
May 8, 2024
We are also getting this error during a rolling deploy. We dont have very high frequency events so I dont believe we are losing events due to this, but I havent actually checked for this. Would be great to hear some official advice here as I will likely just disable the error logging from this callback or force a hard rollout when upgrading the cluster, neither seem like great solutions tbh. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
I've spent a couple of days fighting issues with stream events gone missing during rolling deploy. I created a minimal repro, to rule out any business logic issues, but I can still reproduce the error. It's possible that this configuration is sub-optimal or that I'm doing something wrong, so please advice me.
Setup
Orleans version: 7.2.6
Stream pub sub configuration: StreamPubSubType.ImplicitOnly
Stream storage: MemoryGrainStorage for "PubSubStore" (if this is applicable with ImplicitOnly?)
GrainDirectory: Redis
DefaultCompatibilityStrategy: BackwardCompatible
DefaultVersionSelectorStrategy: LatestVersion
Using Postgres as grain storage/membership
Repro
Orleans.Streams.QueueCacheMissException
occurs on Silo B at the consumers end. This is the only error I get. No error occur at the producers endQuestions
The text was updated successfully, but these errors were encountered: