[
https://issues.jboss.org/browse/WFLY-1119?page=com.atlassian.jira.plugin....
]
Tom Jenkinson commented on WFLY-1119:
-------------------------------------
Hi Amos, I think if the setting is "1" we should leave it alone. I think we
should only do this if the entry is empty. Perhaps by default we should remove the
node-identifier="1" from the standalone.xml so the new behaviour activates by
default. Remember we need to make this a true uuid. Take a look at our UID implementation
- remember it needs to go in the Xids we create and I think there is a max length for
node-name so will need to verify that one of those will fit in before we proceed.
It would be good to be able to verify that no other server has the same node id somehow if
that is possible with DMR to check attributes of other servers.
Assign an unique NodeID automatically
-------------------------------------
Key: WFLY-1119
URL:
https://issues.jboss.org/browse/WFLY-1119
Project: WildFly
Issue Type: Feature Request
Components: Transactions
Reporter: Clebert Suconic
Assignee: Amos Feng
Priority: Optional
It shouldn't be needed to assign the node-id manually IMO.
You could store the node-id on a file and recover it for subsequent starts.
On hornetQ for instance, we look for the nodeID on a file, if the file doesn't exist
we assign a UUID and write to the file.
In our previous experience UUID would be a best fit to assign the nodes since that was
the only way we could guarantee unique IDs between the nodes.
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)