Uploaded image for project: 'Infinispan'
  1. Infinispan
  2. ISPN-2410 A command forwarded back to the originator can time out waiting on a key already locked by itself
  3. ISPN-2473

Forwarding for non-transactional write commands should be asynchronous

This issue belongs to an archived project. You can view it, but you can't modify it. Learn more

XMLWordPrintable

    • Icon: Sub-task Sub-task
    • Resolution: Done
    • Icon: Critical Critical
    • 5.2.0.Final
    • 5.2.0.Final
    • State Transfer
    • None

      A write command keeps a lock on the originator while doing the RPC on the actual owners, so forwarding the command back to the originator synchronously leads to a deadlock.

      Keeping track of the real originator for forwarded commands could allow us to avoid the deadlock, but it would be too complicated. OTOH, non-tx caches don't guarantee consistency, so we could just do the forwarding asynchronously.

              dberinde@redhat.com Dan Berindei (Inactive)
              dberinde@redhat.com Dan Berindei (Inactive)
              Archiver:
              rhn-support-adongare Amol Dongare

                Created:
                Updated:
                Resolved:
                Archived: