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

InvalidateL1Command during ST should not cancel writing the entry by ST


    • Icon: Bug Bug
    • Resolution: Done
    • Icon: Critical Critical
    • 6.0.0.Final
    • 5.3.0.Final
    • Core

      When a node which is about to receive the entries for some segment receives InvalidateL1Command, this puts the key into StateConsumer.updatedKeys. After the entries for ST are received, the entry which was invalidated is not updated -> this result in losing the entry.

      Btw., in EntryWrappingInterceptor.visitInvalidateL1Command the trace logs all looked up entries for each entry - this causes some performance problems when tracing is on and there are many invalidated entries. Please, do this only once.

            wburns@redhat.com Will Burns
            rvansa1@redhat.com Radim Vansa (Inactive)
            0 Vote for this issue
            3 Start watching this issue