[ https://issues.jboss.org/browse/ISPN-8908?page=com.atlassian.jira.plugin.... ] Pedro Ruivo commented on ISPN-8908: ----------------------------------- This isn't a bug but a feature request. This behaviour was never supported. Besides the data lost that we can't prevent, if the state transfer is turn off, it may create inconsistencies in the data, when used with concurrent remove operation. As an example, assuming a backup owner of a key, this events can happen: * It receives a {{remove_operation}} from the primary owner and applies it. The key is removed. * It performs a local {{get()}}. The value isn't found so it asks to all the other owners. If the other owners haven't applied the {{remove_operation}} yet, the old value is returned * And it stores the old value again. In the end, this backup owner keeps the value while the remaining owners remove it. To solve this, we need to support tombstones. We currently don't have that. IMO, enabling the state transfer and disabling {{awaitInitialTransfer}} is the best option. [~dan.berindei] or [~rvansa], do you have another suggestion/opinion? -- This message was sent by Atlassian JIRA (v7.5.0#75005)