With regards dmq/dmq_usrloc and in-memory replication, doesn't dmq know when a node is down/removed from the bus? If it does, then maybe a background thread could fire to (e|se)lect one of the remaining nodes to take over from the node that is down and manipulate/override aor's of the downed host on the (ese)lected registrar. I don't think this would work for shared-db mode though.


You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub, or mute the thread.