[jboss-dev-forums] [Clustering Development] New message: "Re: Partition and Node identities"
jaikiran pai
do-not-reply at jboss.com
Tue Mar 2 02:12:35 EST 2010
JBoss development,
A new message was posted in the thread "Partition and Node identities":
http://community.jboss.org/message/529264#529264
Author : jaikiran pai
Profile : http://community.jboss.org/people/jaikiran
Message:
--------------------------------------------------------------
> mailto:david.lloyd at jboss.com wrote:
>
>
>
> In terms of implementation, my few minutes of research on the topic indicate that the best way to calculate a default node name at boot would be as follows.
> 1. Define a system property, "jboss.host.qualified.name" or just "host.qualified.name", which, if unspecified, defaults to the value of:1. the HOSTNAME env var, or if that is not specified,
> 2. the COMPUTERNAME env var, or if that is not specified,
> 3. the value of InetAddress.getLocalHost().getHostName(), or if that does not turn up anything,
> 4. a default value such as "unknown-host.unknown-domain"
>
> 2. Define a system property, "jboss.host.name" or just "host.name", which, if unspecified, defaults to host portion of the above property
> 3. Define a system property, "jboss.node.name" which, if unspecified, defaults to the value of the above property
>
Given this above scheme, 2 +independent+ (non-clustered) instances of JBossAS running on the same machine, might end up with the same node name unless the user explicitly specifies a unique jboss.node.name for each of those instances, isn't it? Maybe we should by default take into account the -b option to determine the default node name? That way, the user can just continue doing:
run.sh -c default -b 127.0.0.1
run.sh -c custom -b 127.0.0.2
and the node names would then be 127.0.0.1 and 127.0.0.2 respectively.
--------------------------------------------------------------
To reply to this message visit the message page: http://community.jboss.org/message/529264#529264
More information about the jboss-dev-forums
mailing list