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

NearCache: it is possible to read stale data with a put/remove followed by a get

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

XMLWordPrintable

    • Hide

      It cannot be reproduced systematically, but the steps are "simple":

      • write an value, value=A
      • write an value, value=B
      • issue a get on the entry, it could return value=A in case of high network load (or slow network connection)

      it is simpler to reproduce while using a network of 2-3 servers, when the entry is hosted not on the same server that the listener is attechad to

      Show
      It cannot be reproduced systematically, but the steps are "simple": write an value, value=A write an value, value=B issue a get on the entry, it could return value=A in case of high network load (or slow network connection) it is simpler to reproduce while using a network of 2-3 servers, when the entry is hosted not on the same server that the listener is attechad to

      Writes to the NearCache do not invalidate/update local data on put/remove operations, and so the NearCache (LAZY MODE) is invalidated using an eventlistener in an asynch way.
      It is possible for a client to write a value and issue a get on the same key, and the result of the get would not be the latest value but the one which was present before the update operation.
      This happens frequently when there is very much traffic on the connection of the listener which receives the events for the NearCache.
      It would be better at least to invalidate locally every entry modified from the client itself

              rh-ee-galder Galder Zamarreño
              enrico.olivelli Enrico Olivelli (Inactive)
              Archiver:
              rhn-support-adongare Amol Dongare

                Created:
                Updated:
                Resolved:
                Archived: