Skip to content
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

Improve error handling of transaction::commit_or_rollback_by_xid() #171

Open
wants to merge 2 commits into
base: master
Choose a base branch
from

Conversation

sciascid
Copy link
Contributor

Handle the case where a call to commit_or_rollback_by_xid() is given
a xid for which there is no corresponding streaming applier.
We distinguish two cases here:

  1. the xid might not exist at all, or the corresponding transaction
    was already committed or rolled back. The client may just return an
    error; or 2) all streaming appliers have been closed
    because the node is currently disconnected. We can't tell if a
    corresponding transaction exists. The client may want to retry.

Handle the case where a call to commit_or_rollback_by_xid() is given
a xid for which there is no corresponding streaming applier.
We distinguish two cases here:
1) the xid might not exist at all, or the corresponding transaction
was already committed or rolled back. The client may just return an
error; or 2) all streaming appliers have been closed
because the node is currently disconnected. We can't tell if a
corresponding transaction exists. The client may want to retry.
@sciascid sciascid force-pushed the unknown_xid branch 2 times, most recently from 66fc9b3 to ece5942 Compare November 12, 2021 14:32
Handle the case where server_id is undefined in before fragment
certification. This may happen if the server is disconnected right
before replicating a fragment.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant