-
-
Notifications
You must be signed in to change notification settings - Fork 453
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
New built in health check for the high water detection going stale #3455
Comments
I encountered highwater mark going stale this morning. I have a web client running marten, and a separate console app (single intance) running the async daemon. The highwater mark went stale during an azure maintenance operation. The web client reported The web client recovered and continued marten operations. However, the app running the daemon was no longer processing async projections since the higwatermark and all projection shards were stalled on the same seqId. This stale continued until I restarted the async daemon application. Reviewing the logs for the async daemon app, the only exceptions are related to login to server, presumably during Azure maintenance task.
Then just after the server login error, there is an error for EndOfStreamException. Following this, the highwater mark appears to remain stale until I restarted the app running the async daemon.
My plan is to update my marten health check service to also include the max event stream seqId and return unhealthy if greater than X threshold. I think this is what you are planning for the built in health check as well. |
If it's falling behind the sequence by a certain mark is the logic
The text was updated successfully, but these errors were encountered: