-
Notifications
You must be signed in to change notification settings - Fork 20
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
Add resume from checksum #344
Conversation
26814cb
to
fdabcd1
Compare
5ba57eb
to
846175f
Compare
846175f
to
4c974e0
Compare
if r.dbConfig == nil { | ||
r.dbConfig = dbconn.NewDBConfig() | ||
} | ||
r.db.SetMaxOpenConns(r.dbConfig.MaxOpenConnections + 2) | ||
var err error | ||
for i := range 3 { // try the checksum up to 3 times. | ||
if i > 0 { | ||
r.checksumWatermark = "" // reset the watermark if we are retrying. | ||
} |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Is this intentional? so resume from checksum watermark only works if first resume is successful, otherwise it starts checksum from scratch again?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Yes that's right. If there is any failure we recheck everything.
A Pull Request should be associated with an Issue.
This fixes #317
In our case we support yield via automation (pod cycling every 24hrs), so I am going to call this fixed.. even though it only completes part of the described FR.
Also fixes #320 and fixes #315 - the root cause is depending when the context cancel is detected, the error message can vary.