enabling a second network interface in the bios causes view change issues

eclipse-ee4j / glassfish-shoal

Shoal

Other

5 stars 9 forks source link

enabling a second network interface in the bios causes view change issues #110

Closed glassfishrobot closed 13 years ago

glassfishrobot commented 13 years ago

I enabled my second interface in the bios (didn't assign an ip or anything to the interface - just enabled in the bios) and then when I start a cluster GMS does not seem to work well in the scenario thus causing shoal cache to not work well either. Once I disabled the interface in bios everything started working.

Environment

Operating System: All Platform: Windows

Affected Versions

[current]

glassfishrobot commented 6 years ago

Issue Imported From: https://github.com/javaee/shoal/issues/110
Original Issue Raised By:@glassfishrobot
Original Issue Assigned To: @jfialli
Original Issue Closed By:@glassfishrobot

glassfishrobot commented 13 years ago

@glassfishrobot Commented Reported by mode

glassfishrobot commented 13 years ago

@glassfishrobot Commented @jfialli said: request for steps to recreate this issue.

specifically, what was the order for the following operations

asadmin start-domain
asadmin create-cluster
assadmin start-cluster
enabling 2nd network interface

We can not support changes to network interfaces in the middle of first 3 methods above when GMS-BIND-INTERFACE-ADDRESS-cluster-name is not being used on DAS and all instances in the cluster.

The dynamic finding of first network address can change between DAS joining cluster and instances being started via start-cluster if network interface change is made in between.

glassfishrobot commented 13 years ago

@glassfishrobot Commented @jfialli said: additionally need to know if GMS-BIND-INTERFACE-ADDRESS is being set for clustered instances and/or DAS. (GMS-BIND-INTERFACE-ADDRESS should be set for all clustered instances AND the DAS.)

glassfishrobot commented 13 years ago

@glassfishrobot Commented @jfialli said: Enhancement scheduled for glassfish 3.2 described by https://glassfish.dev.java.net/issues/show_bug.cgi?id=13056 would enable detection of misconfiguration of network and/or glassfish cluster.

Not possible to diagnose this in gms since it is dynamic runtime configuration and there is no place defined that all instances in a cluster are configured. But in glassfish, the domain.xml has static configuration of clustered instances and DAS. That info can be used by a tool (3.2 extension of "asadmin validate-multicast" to validate if multicast is working between all members of glassfish cluster). If there is an issue detected, user is required to figure out why multicast is not working as glassfish cluster is configured.

glassfishrobot commented 7 years ago

@glassfishrobot Commented This issue was imported from java.net JIRA SHOAL-110

glassfishrobot commented 13 years ago

@glassfishrobot Commented Marked as won't fix on Wednesday, October 20th 2010, 12:19:34 am