-
Notifications
You must be signed in to change notification settings - Fork 26
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
Give the vdb verification exactly once semantics for vrpq #781
Give the vdb verification exactly once semantics for vrpq #781
Conversation
The e2e failures are likely something we inherit from the latest server image. I see them in my PR too. |
Yeah, I noticed that the log rotation on my server (e2e-leg-6) failed with the latest server image. I will open a pull request (PR) to fix it. |
I am following up with a server issue. In the mean time, to get the e2e tests clean, I rolled back the latest image to point to the day before. So, lets see if that resolves things. |
The image from the day before worked well; I noticed that it ran successfully for all e2e tests in your PR. |
Yes, I resubmitted the failed runs after reverting the latest images. |
To follow up on #781, we will verify the presence of QueryReady instead of checking if QueryReady is true. This ensures the verification of exactly-once semantics for vrep.
To follow up on #781, we will verify the presence of QueryReady instead of checking if QueryReady is true. This ensures the verification of exactly-once semantics for vrep.
To follow up on #781, we will verify the presence of QueryReady instead of checking if QueryReady is true. This ensures the verification of exactly-once semantics for vrep.
To follow up on #781, we will verify the presence of QueryReady instead of checking if QueryReady is true. This ensures the verification of exactly-once semantics for vrep.
To follow up on #781, we will verify the presence of QueryReady instead of checking if QueryReady is true. This ensures the verification of exactly-once semantics for vrep.
To follow up on #781, we will verify the presence of QueryReady instead of checking if QueryReady is true. This ensures the verification of exactly-once semantics for vrep.
The VerticaRestorePointsQuery reconciler will keep retrying the query when a previous query has failed. We should check if QueryComplete is present instead of checking if QueryComplete is true to ensure the verification of exactly-once semantics.
The VRep reconciler change will be opened in another PR in vnext branch