[ https://issues.jboss.org/browse/ISPN-6919?page=com.atlassian.jira.plugin.... ] Dan Berindei edited comment on ISPN-6919 at 9/7/16 10:58 AM: ------------------------------------------------------------- [~ksobolew] I'm afraid the functional API's commands can't run without exclusive access to the entries they modify, either. [~pruivo] numOwners == 1 should really be described separately. If we exclude that, the first case becomes "originator != primary" What happens when the backups install a new topology in which they're no longer owners, or if the backups crash? Also, why do we need the replication to the backups to be ordered? That won't help if the primary owner crashes, and another node becomes the primary owner. More general, we should really have some diagrams to discuss how the triangle is supposed to handle the various corner cases that appear when a node joins/leaves/crashes, or when there's a split+merge. I'm not saying this approach won't work with topology changes, it's just that I have no idea how it's supposed to work. was (Author: dan.berindei): [~ksobolew] I'm afraid the functional API's commands can't run without exclusive access to the entries they modify, either. [~pruivo] numOwners == 1 should really be described separately. If we exclude that, the first case becomes "originator != primary" What happens when the backups install a new topology in which they're no longer owners, or if the backups crash? Also, why do we need the replication to the backups to be ordered? That won't help if the primary owner crashes, and another node becomes the primary owner. More general, we should really have some diagrams to discuss how the triangle is supposed to handle the various corner cases that appear when a node joins/leaves/crashes, or when there's a split+merge. I'm not saying this approach won't work with topology changes, it's just that I have no idea whether how it's supposed to work. -- This message was sent by Atlassian JIRA (v6.4.11#64026)