[infinispan-issues] [JBoss JIRA] (ISPN-3633) InvalidateL1Command during ST should not cancel writing the entry by ST
[
https://issues.jboss.org/browse/ISPN-3633?page=com.atlassian.jira.plugin....
]
William Burns commented on ISPN-3633:
-------------------------------------
I was never able to reproduce this except when the issue was related to when the ST
occurred in the middle of a prepare commit step, but I will revisit and see if I can find
anything else.
Do you happen to have a trace of when this occurs with non tx caches?
InvalidateL1Command during ST should not cancel writing the entry by
ST
-----------------------------------------------------------------------
Key: ISPN-3633
URL: https://issues.jboss.org/browse/ISPN-3633
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.0.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