-
Notifications
You must be signed in to change notification settings - Fork 634
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 Database Outage Recovery in Lagom 1.4.0 #1250
Comments
After some further investigations, I came to the conclusion that there is nothing wrong with the All eyes are turned now to a possible deadlock in the Slick DB. Note that the
If the DB is somehow blocked, the |
Found the error in Slick. This is a regression that was introduced when fixing slick/slick#1274. I have an open PR for Slick: |
In Lagom, we still need to fix the way we are using If |
@TimMoore if the problem is that |
@TimMoore I fixed it locally using val eventualTimeout =
after(duration = 3.seconds, using = context.system.scheduler) {
Future.failed(new TimeoutException(s"Timeout while fetching read-side processor offset"))
}
val futureOffset = handler.prepare(tag).toScala
val offsetWithTimeout = Future firstCompletedOf Seq(futureOffset, eventualTimeout) @ignasi35, I rechecked the code and this is not true. The reason this particular future is never completing is that Slick Whenever we get a |
Oh, it seems that there is already something we can use.
|
There is an open PR (#1278) that fix the |
Up to now we believe there are two bugs involved:
RestartSource
stopping to retry after long period of failuresThe text was updated successfully, but these errors were encountered: