geode-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "ASF subversion and git services (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (GEODE-5502) Cluster configuration can contain member-specific gateway receiver definitions which cause members to fail to start during rolling
Date Wed, 01 Aug 2018 19:33:00 GMT

    [ https://issues.apache.org/jira/browse/GEODE-5502?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16565867#comment-16565867
] 

ASF subversion and git services commented on GEODE-5502:
--------------------------------------------------------

Commit 1249f0ff3a62f8a546a54a53308a44d961cd0cdc in geode's branch refs/heads/feature/GEODE-5502
from [~barry.oglesby]
[ https://gitbox.apache.org/repos/asf?p=geode.git;h=1249f0f ]

GEODE-5502: Force CI to re-run


> Cluster configuration can contain member-specific gateway receiver definitions which
cause members to fail to start during rolling
> ----------------------------------------------------------------------------------------------------------------------------------
>
>                 Key: GEODE-5502
>                 URL: https://issues.apache.org/jira/browse/GEODE-5502
>             Project: Geode
>          Issue Type: Bug
>          Components: configuration
>            Reporter: Barry Oglesby
>            Assignee: Barry Oglesby
>            Priority: Major
>              Labels: pull-request-available, swat
>          Time Spent: 0.5h
>  Remaining Estimate: 0h
>
> In versions before 1.4.0, cluster configuration could contain multiple member-specific
gateway receiver definitions like:
> {noformat}
> <cache>
>   <gateway-receiver hostname-for-senders="123.12.12.12"/>
>   <gateway-receiver hostname-for-senders="123.12.12.11"/>
> </cache>
> {noformat}
> Starting in 1.4.0, multiple receivers are no longer allowed, so a configuration like
this causes the member to throw an exception and fail to start.
> These member-specific receivers should be removed before sending the cluster configuration
to new members to avoid attempting to create multiple receivers in a single member.
> Note: In this case, the member will start with no receivers.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

Mime
View raw message