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

The first write to a joiner in invalidation mode can be ignored

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
    • 5.3.0.Final
    • 5.2.6.Final, 5.3.0.Final
    • State Transfer

      In invalidation mode we don't wait for the initial state transfer to finish, or even for the joiner to become a member in the "write" CH, before returning to the user from getCache().

      Writes to the joiner before it becomes a member of the write CH are not committed to the local cache, because of a check in EntryWrappingInterceptor.shouldWrap(). So it's possible for the joiner to ignore the first write completely.

      If StateTransferConfigurationBuilder enabled awaitInitialTransfer by default in invalidation mode, like it does in distributed/replicated mode, this wouldn't happen.

      The fact that it will still be possible for the user to disable awaitInitialTransfer manually shouldn't be a problem, because in invalidation mode the user should expect values to be invalidated at any time. This is just about improving the default configuration.

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

                Created:
                Updated:
                Resolved:
                Archived: