-
Notifications
You must be signed in to change notification settings - Fork 3.8k
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
stability: keep a cache of pushed transactions #627
Comments
@petermattis Could you assign this to me? I Would like to do some contribute. |
@yananzhi Github is not allowing me to assign an issue to someone who is not in the cockroachdb org. Regardless of assignment, feel free to work on this. No one else is and your comment on this issue will be enough to indicate that you are doing so. |
@petermattis thanks |
closing this for now. We have a related idea in #2632 and all of this is post-1.0 anyway. |
Now that we have SQL and dropping tables issues
That turns a single It's time to augment the This itself isn't enough: it saves the 10k pushes, but we will still have to resolve 10k intents and have the An elegant solution comes up with leader-proposed Raft: since we see the intents before proposing to Raft, we can have more complex logic which performs a single push for the first intent, and then "directly" overwrites the remaining "identical" intents it encounters for the remainder of the Even before leader-proposed Raft, we could in principle do the same thing: once a DeleteRange runs into an intent, we execute it before Raft (without committing the result, just to discover more intents) and supply a batch-resolution to Raft. But that's fairly complex when you take into account that it needs to go away anyway. My hunch is that this #7499 should be addressed first since there is a fairly clear path there to avoid these deletions in the first place (though users may still perform table deletions which have much of the same problems). |
Closing as this is a solution hatched before we've observed the problem. I for one am hoping that instead of range-wide |
Keep a cache of pushed transactions on a store to avoid repushing further intents after a txn has already been aborted or its timestamp moved forward.
The text was updated successfully, but these errors were encountered: