geode-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "ASF subversion and git services (JIRA)" <>
Subject [jira] [Commented] (GEODE-77) Replace JGroups 2.2.9
Date Fri, 09 Oct 2015 17:39:05 GMT


ASF subversion and git services commented on GEODE-77:

Commit 8de790397e2abd0dac9c0c0d347812f540ab625e in incubator-geode's branch refs/heads/feature/GEODE-77
from [~bschuchardt]
[;h=8de7903 ]

GEODE-77 improved suspect processing, multicast fix for Windows

GMSHealthMonitor was allowing the service to watch itself if it ran out of other members to
watch.  This change set modifies that behavior to set the "next neighbor" to null, causing
suspect processing to halt until a member transitions out of "suspect" state or a new membership
view is installed.

I also found that GMSHealthMonitor wasn't notifying the Manager when a member goes into final-check
state, so that membership listeners weren't being notified of suspect events.  This was causing
a unit test failure.

JGroupsMessenger now fools the JGroups stack into thinking an IPv4 stack is being used even
if IPv6 is available, so that JGroups will use an IPv4 address.  JGroups was selecting an
IPv6 address, making communications with IPv4 members impossible and causing a schizm between
the GemFire member address and the JGroups address.

The JGroups log level is now set to WARN in the default log4j2.xml settings file.

> Replace JGroups 2.2.9
> ---------------------
>                 Key: GEODE-77
>                 URL:
>             Project: Geode
>          Issue Type: Bug
>            Reporter: Bruce Schuchardt
>            Assignee: Bruce Schuchardt
>            Priority: Blocker
>             Fix For: 1.0.0-incubating
>         Attachments: GEODE-MembershipManagerFunctionalSpecification-130715-1604-29054.pdf
> The JGroups 2.2.9 sources that are currently included in Geode must be replaced in order
for Geode to leave incubation.  A wiki document has been created to investigate alternatives.

This message was sent by Atlassian JIRA

View raw message