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

DAOS-16721 dtx: handle potential DTX ID reusing trouble - b26 #15409

Merged
merged 1 commit into from
Nov 5, 2024

Commits on Nov 1, 2024

  1. DAOS-16721 dtx: handle potential DTX ID reusing trouble - b26

    The patch contains the following improvements:
    
    1. When VOS level logic returns -DER_TX_RESATRT, the object level RPC
       handler should set 'RESEND' flag then restart the transaction with
       newer epoch. Because dtx_abort() logic cannot guarantee all former
       prepared DTX entries (on all related participants) can be aborted,
       especially if the former one failed for some network trouble, that
       may cause restarted transaction hit -DER_TX_ID_REUSED unexpectedly.
    
    2. Compare the epoch for DTX entries with the same transaction ID for
       distinguishing potential reused TX ID more accurately.
    
    3. Add DTX entry into DTX CoS cache if cannot commit it synchronously.
       Then subsequent batched commit logic can handle it.
    
    4. If server complains suspected TX ID reusing, then reports -EIO to
       related application instead of assertion on client.
    
    5. Control DTX related warning message frequency to avoid log flood.
    
    6. Collect more information when generate some error/warning message.
    
    Allow-unstable-test: true
    
    Signed-off-by: Fan Yong <[email protected]>
    Nasf-Fan committed Nov 1, 2024
    Configuration menu
    Copy the full SHA
    c4c195d View commit details
    Browse the repository at this point in the history