[jboss-jira] [JBoss JIRA] (AS7-5907) Assign an unique NodeID automatically
[
https://issues.jboss.org/browse/AS7-5907?page=com.atlassian.jira.plugin.s...
]
Tom Jenkinson edited comment on AS7-5907 at 11/8/12 10:01 AM:
--------------------------------------------------------------
This was deferred in JBTM, but I think it might be something AS7 would like to provide for
usability aspects.
Generally: assuming the user does not define the node-identifier themselves, use Cleberts
algorithm to persistently store a unique node-identifier.
Note the node-identifier must be unique for any server that talks to another server or
shares an object store, it may be that UUID is not considered to be guaranteed to be
unique enough.
was (Author: tomjenkinson):
This was deferred in JBTM, but I think it might be something AS7 would like to provide
for usability aspects.
Generally: assuming the user does not define the node-identifier themselves, use Cleberts
algorithm to persistently store a unique node-identifier.
Note the node-identifier must be unique for any server that talks to another server or
shares an object store, it may be that UUID is not considered unique enough.
Assign an unique NodeID automatically
-------------------------------------
Key: AS7-5907
URL: https://issues.jboss.org/browse/AS7-5907
Project: Application Server 7
Issue Type: Feature Request
Reporter: Clebert Suconic
Assignee: Stefano Maestri
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 is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira