-
Notifications
You must be signed in to change notification settings - Fork 55
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
CasbahPersistenceReadJournaller robustness of live events under DB failure #157
Comments
@scullxbones any update on this and related issues? Or do you have any tips on to how detect such DB failures so we can take some action (like restarting the service)? |
Hi @yahor-filipchyk - this ticket has totally stalled out since a year ago. I don't have a great detection approach, but I also don't see issues in production so I haven't had to develop one. That said I'm primarily using on-demand streams rather than live ones, so I'm not sure I'm really exercising the code with issues. Is there anything you're specifically seeing that hasn't already been covered in this or #156? |
Sorry for the late response @scullxbones. #156 probably covers the issue. Just wanted to check if someone has any plans of fixing this (I don't know how you guys prioritize issues). It isn't bothering us all that much but when it happens it's quite frustrating. Maybe we'll invest some time in trying to contribute after all 😉 |
Hi @yahor-filipchyk - I'm happy to review PRs, and to get this un-stalled. I'm leaning more and more to simplifying the live streams, at the cost of more load on mongodb via #199. I think that should eliminate this cluster of issues around the single shared tailing cursor. |
Fixed by #199 |
Bringing discussion over from #156
The text was updated successfully, but these errors were encountered: