You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@geode.apache.org by "Barbara Pruijn (JIRA)" <ji...@apache.org> on 2018/04/17 20:50:00 UTC
[jira] [Comment Edited] (GEODE-4959) Attempt to create multiple gw
receivers results an error on gfsh console.
[ https://issues.apache.org/jira/browse/GEODE-4959?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16441320#comment-16441320 ]
Barbara Pruijn edited comment on GEODE-4959 at 4/17/18 8:49 PM:
----------------------------------------------------------------
When calling command
{code:java}
create gateway-receiver{code}
on a cluster but one member in the cluster already has a gateway receiver, the command will create a gateway receiver on the other members in the cluster, but will not persist the gateway receivers in the cluster. In this case we need to display a warning that the gateway receivers will not be persisted in cluster config.
{code:java}
gfsh>create gateway-receiver --member=s1
This change is not persisted in the cluster configuration, either because the cluster configuration service is not running or the command is operating on targeted members.
Member | Status
------ | --------------------------------------------------------------------------
s1 | GatewayReceiver created on member "s1" and will listen on the port "5,071"
gfsh>create gateway-receiver
Member | Status
------ | -----------------------------------------------------------------------------------------
s1 | ERROR: java.lang.IllegalStateException: A Gateway Receiver already exists on this member.
s2 | GatewayReceiver created on member "s2" and will listen on the port "5,138"
This change is not persisted in the cluster configuration, because an error occurred during execution.
{code}
was (Author: bpruijn):
When calling command
{code:java}
create gateway-receiver{code}
on a cluster but one member in the cluster already has a gateway receiver, the command will create a gateway receiver on the other members in the cluster, but will not persist the gateway receivers in the cluster. In this case we need to display a warning that the gateway receivers will not be persisted in cluster config.
{code:java}
gfsh>create gateway-receiver --member=s1
This change is not persisted in the cluster configuration, either because the cluster configuration service is not running or the command is operating on targeted members.
Member | Status
------ | --------------------------------------------------------------------------
s1 | GatewayReceiver created on member "s1" and will listen on the port "5,071"
gfsh>create gateway-receiver
This change is not persisted in the cluster configuration, because a gateway receiver already existed on a member before running this command.
Member | Status
------ | -----------------------------------------------------------------------------------------
s1 | ERROR: java.lang.IllegalStateException: A Gateway Receiver already exists on this member.
s2 | GatewayReceiver created on member "s2" and will listen on the port "5,138"
{code}
> Attempt to create multiple gw receivers results an error on gfsh console.
> -------------------------------------------------------------------------
>
> Key: GEODE-4959
> URL: https://issues.apache.org/jira/browse/GEODE-4959
> Project: Geode
> Issue Type: Bug
> Components: docs, gfsh
> Reporter: Sai Boorlagadda
> Assignee: Patrick Rhomberg
> Priority: Major
> Labels: pull-request-available
> Time Spent: 1.5h
> Remaining Estimate: 0h
>
> {{There are several issues with create gateway-receiver command.}}
> 1) Starting 1.4.0, with GEODE-3987 there is an enforcement of one gwr per node in the xsd. So when user attempts to create multiple gwr show a better error message then showing "*ERROR: java.lang.IllegalStateException*".
> {noformat}
> gfsh>start server --locators=localhost[10334]
> Starting a Geode Server in /Users/sboorlagadda/workspace/debug/geode/apache-geode-1.4.0/bin/walk-proud-feet...
> ...
> Server in /Users/sboorlagadda/workspace/debug/geode/apache-geode-1.4.0/bin/walk-proud-feet on sais-mbp-2.netgear.com[40404] as walk-proud-feet is currently online.
> Process ID: 35197
> Uptime: 4 seconds
> Geode Version: 1.4.0
> Java Version: 1.8.0_151
> Log File: /Users/sboorlagadda/workspace/debug/geode/apache-geode-1.4.0/bin/walk-proud-feet/walk-proud-feet.log
> JVM Arguments: -Dgemfire.locators=localhost[10334] -Dgemfire.start-dev-rest-api=false -Dgemfire.use-cluster-configuration=true -XX:OnOutOfMemoryError=kill -KILL %p -Dgemfire.launcher.registerSignalHandlers=true -Djava.awt.headless=true -Dsun.rmi.dgc.server.gcInterval=9223372036854775806
> Class-Path: /Users/sboorlagadda/workspace/debug/geode/apache-geode-1.4.0/lib/geode-core-1.4.0.jar:/Users/sboorlagadda/workspace/debug/geode/apache-geode-1.4.0/lib/geode-dependencies.jar
> gfsh>create gateway-receiver
> Member | Status
> --------------- | ---------------------------------------------------------------------------------------
> walk-proud-feet | GatewayReceiver created on member "walk-proud-feet" and will listen on the port "5,221"
> gfsh>create gateway-receiver
> Member | Status
> --------------- | -----------------------------------------------------------------------------------------
> walk-proud-feet | ERROR: java.lang.IllegalStateException: A Gateway Receiver already exists on this member.{noformat}
> 2) create gwr command should enforce only one gwr can be created as with GEODE-3987, xsd supports only one.
> 3) create gwr command is storing the gwr in cluster config when created with --member option.
> As there is no enforcement until 1.3 and with above stated issues with gfsh, it could happen that some one could end up a cluster with multiple gwr created in cluster configuration and could prevent them to upgrade to 1.4.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)