[ https://issues.jboss.org/browse/ISPN-4650?page=com.atlassian.jira.plugin.... ] Sanne Grinovero commented on ISPN-4650: --------------------------------------- The finding is certainly correct, I've witnesses as will significant slowdowns caused by delete operations. But for the MassIndexer to ignore put operations which could be triggered "in parallel" has some dangers, you'd need to carefully test this and see if you don't need to queue up update operations which are triggered by normal transactional operations while the MassIndexer is running. I suspect you'll need to make sure that any update operation triggered by cache write operations needs to be applied after the MassIndexer is done. For sake of simplicity, you could make this an option which is disabled by default and properly explains the drawback of enabling it: it would be perfectly fine for a batch upload if the user simply knows because of how his application is designed, that no concurrent updates will be applied to the cache while the indexer is running. Alternatively rather than using a queue - which poses questions on where to store it and how to limit it from uncontrolled size - is to go with the optimistic approach and automatically switch to the safer approach if any other indexing event is generated. -- This message was sent by Atlassian JIRA (v6.2.6#6264)