-
Notifications
You must be signed in to change notification settings - Fork 1.3k
Validate reconciler works correctly #13648
Comments
I've been able to reproduce at least part of this:
💥 I managed to get this crash from the backend:
After restarting, the reconciler doesn't crash, but does leave the GitLab MR in the processing state. Manually kicking it back to queued results in the MR being reconciled as expected. This would imply that the crash isn't rolling back the transaction. More to come tomorrow. |
I think that's when the reset-stalled-job/
I'm sure you've found this by now, but the dequeue-and-set-to-processing happens outside the transaction: So if a worker crashes while it's processing a record the transaction that modified the record is rolled back (well, it's not committed), but the status is still set to processing. The new worker process that you boot up should reset the stalled jobs after |
btw. continually retrying is a feature, not a bug, see https://github.com/sourcegraph/sourcegraph/issues/12700#issuecomment-685419544 |
This fixes the crash in this stacktrace https://github.com/sourcegraph/sourcegraph/issues/13648#issuecomment-690817025 It was only a problem in `CloseChangesets`, but I added the check to the FakeChangesetSource in every call.
…13795) This fixes the crash in this stacktrace https://github.com/sourcegraph/sourcegraph/issues/13648#issuecomment-690817025 It was only a problem in `CloseChangesets`, but I added the check to the FakeChangesetSource in every call.
Dear all, This is your release captain speaking. 🚂🚂🚂 Branch cut for the 3.20 release is scheduled for tomorrow. Is this issue / PR going to make it in time? Please change the milestone accordingly. Thank you |
To be clear, this didn't restart after |
This hasn't been observed again, so deprioritising for now. |
Given that we had a couple of weeks to find this "by accident" and we didn't, I guess we can close this ticket? @sourcegraph/campaigns |
Yes, that's fine with me. |
I've just ran a test campaign that creates changesets on GitLab, GitHub and Bitbucket Server, and the behavior seems odd to me.
Screenshot:
![image](https://user-images.githubusercontent.com/19534377/92263018-3ead9300-eedc-11ea-8c2f-298eb1ebdd7c.png)
Logs:
The text was updated successfully, but these errors were encountered: