[ https://issues.jboss.org/browse/ISPN-4650?page=com.atlassian.jira.plugin.... ] Gustavo Fernandes edited comment on ISPN-4650 at 8/20/14 1:27 PM: ------------------------------------------------------------------ The auto switch ended up being trickier than it appears. Considering that IndexMappers are sent over the wire to all nodes, and each node has its own query interceptor, and indexing operations can be async depending on the stack used, and the mass indexer can be started from any node (the same applies to regular writes) there are plenty of opportunities for race conditions to provoke duplicate documents if using the MassIndexer at the same time as normal operations. I'd like to explore a 3rd alternative besides using auto switch and queues, which is relying on UpdateExtWorkDelegate. Some local tests demonstrated this kind of delegate to be very closer performance wise to the AddWorkDelegate. I'm aware the implications of its usage (being recommended if keys are unique in an index), and I think infinispan ticks the boxes, doesn't it? was (Author: gustavonalle): The auto switch ended up being trickier than it appears. Considering that IndexMappers are sent over the wire to all nodes, and each node has its own query interceptor, and indexing operations can be async depending on the stack used, and the mass indexer can be started from any node (the same applies to regular writes) there are plenty of opportunities for race conditions to provoke duplicate documents if using the MassIndexer at the same time as normal operations. I'd like to explore a 3rd alternative besides using auto switch and queues, which is relying on UpdateExtWorkDelegate. Some local tests demonstrated this kind of delegate to be very close performance wise to the AddWorkDelegate. I'm aware the implications of its usage (being recommended if keys are unique in an index), and I think infinispan ticks the boxes, doesn't it? -- This message was sent by Atlassian JIRA (v6.2.6#6264)