[
https://issues.jboss.org/browse/ISPN-3780?page=com.atlassian.jira.plugin....
]
Radim Vansa commented on ISPN-3780:
-----------------------------------
The topology change is started on A only after the invalidation has been sent to C.
By the time the entry was requested from C on A, no value was yet present on A, but C was
registered as requestor. Registering registor when the value is null is probably
redundant, but the case we are inspecting would happen if the entry already contained some
old value.
CLONE - InvalidateL1Command during ST should not cancel writing the
entry by ST in nontx
----------------------------------------------------------------------------------------
Key: ISPN-3780
URL:
https://issues.jboss.org/browse/ISPN-3780
Project: Infinispan
Issue Type: Bug
Components: Distributed Cache
Affects Versions: 5.3.0.Final
Reporter: Radim Vansa
Assignee: William Burns
Priority: Critical
Labels: 620
Fix For: 6.1.0.Final
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.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see:
http://www.atlassian.com/software/jira