Uploaded image for project: 'Infinispan'
  1. Infinispan
  2. ISPN-8676

Non-writing functional command should not go to backup

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

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Done
    • Icon: Major Major
    • None
    • 9.2.0.Final
    • Core
    • None

      When a functional read/write or write-only command results in the entry not being changed, the command should not be sent to the backup owner.

      Solving this for single entry is trivial (setting successful = false), the routing logic for multi-key commands is more complex.

              rvansa1@redhat.com Radim Vansa (Inactive)
              rvansa1@redhat.com Radim Vansa (Inactive)
              Archiver:
              rhn-support-adongare Amol Dongare

                Created:
                Updated:
                Resolved:
                Archived: