Thanks Val. Because the user attributes are a map of <String, Object>, so "attributes are static and can't be changed after the node is started. Nodes exchange attributes with each other during the join process" means that the maps are merged together with new key added, and old key unchanged?
If there's change for old key, will it raise an exception? e.g. there're three nodes in cluster now: A1, B2, C3 and their user attribute map is [<A, 1>, <B, 2>, <C, 3>]. Then add a new node D2 whose map is [<A, 2>, <B, 2>, <C,3>, <D,4>] where A's group is changed from 1 to 2, what will happen? all the nodes will have a map of [<A, 2>, <B, 2>, <C,3>, <D,4>] or [<A, 1>, <B, 2>, <C,3>, <D,4>] or throw exception? Thanks, -Jason -- View this message in context: http://apache-ignite-users.70518.x6.nabble.com/How-to-use-BackupFilter-to-assign-all-backups-to-different-machine-groups-tp6513p6529.html Sent from the Apache Ignite Users mailing list archive at Nabble.com.
