[ https://issues.jboss.org/browse/ISPN-1830?page=com.atlassian.jira.plugin.... ] Dan Berindei reassigned ISPN-1830: ---------------------------------- Assignee: Dan Berindei (was: Manik Surtani) -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://issues.jboss.org/browse/ISPN-1830?page=com.atlassian.jira.plugin.... ] Dan Berindei updated ISPN-1830: ------------------------------- Summary: L1: On topology changes lose key requestors information (was: L1: On topology changes we should propagate the key requestors information to the new owners) Issue Type: Bug (was: Task) This issue is causing the failures in https://infinispan.ci.cloudbees.com/job/Infinispan-master-JDK6-tcp-NON_PA... -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://issues.jboss.org/browse/ISPN-1830?page=com.atlassian.jira.plugin.... ] Mircea Markus updated ISPN-1830: -------------------------------- Priority: Critical (was: Major) -- 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

[ https://issues.jboss.org/browse/ISPN-1830?page=com.atlassian.jira.plugin.... ] Mircea Markus commented on ISPN-1830: ------------------------------------- so it is possible to have inconsistencies because of that? -- 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

[ https://issues.jboss.org/browse/ISPN-1830?page=com.atlassian.jira.plugin.... ] Mircea Markus updated ISPN-1830: -------------------------------- Fix Version/s: 5.2.0.CR1 (was: 5.2.0.Beta2) -- 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

[ https://issues.jboss.org/browse/ISPN-1830?page=com.atlassian.jira.plugin.... ] Dan Berindei commented on ISPN-1830: ------------------------------------ Yes, it's possible to get inconsistencies: in both cases, a put command will not invalidate some L1 copies, and those nodes will see stale values until their L1 entries expire. For problem 1 (requestor information on old owners is lost) we have thought about actually transferring the requestor information with the transaction data, but that gets complicated really quickly. (It would most likely require forwarding get commands, which would negate the benefit of having an L1 in the first place.) Instead we are going to remove L1 entries that have lost owners on each topology update (which should be a small fraction of the total L1 entries). For problem 2 (old owners are not added to requestor lists when they lose ownership), we can keep track of the consistent hashes in the last 10 minutes (or whatever the L1 lifespan is) and the time of the last invalidation sent for each key. When we need to send a new invalidation, we add the owners in all the consistent hashes since the last invalidation to the invalidation command recipients. -- 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

[ https://issues.jboss.org/browse/ISPN-1830?page=com.atlassian.jira.plugin.... ] Dan Berindei resolved ISPN-1830. -------------------------------- Resolution: Duplicate Issue I have separated the sub-tasks into separate issues, as there isn't enough time to fix both for 5.2. ISPN-2475 will have to wait until 6.0. -- 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