[
https://issues.jboss.org/browse/AS7-5907?page=com.atlassian.jira.plugin.s...
]
Clebert Suconic commented on AS7-5907:
--------------------------------------
I chat I had with Tom Jenkinson:
clebert: tomjenkinson: but now you have compatibility issues to deal
[08:56am] clebert: tomjenkinson: what if you start a new version...
[08:56am] clebert: you didn't have the data there.. then you will add it
[08:56am] clebert: tomjenkinson: you would have to only set the UUID if there is no data
folder.. no Objects pending at all
[08:57am] clebert: tomjenkinson: well.. you can easily do a check on.. if
(objects.counts() == 0) and ID=default, ID = new UUID, store it on the folder and recover
on restart
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