[jira] [Commented] (GEODE-3540) unable to gfsh destroy gateway-sender
[
https://issues.apache.org/jira/browse/GEODE-3540?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16357721#comment-16357721
]
ASF subversion and git services commented on GEODE-3540:
Commit bbea69a1e0c153e28f5958a58387b80f70fcdc89 in geode's branch
refs/heads/develop from [~sai.boorlaga...@gmail.com]
[ https://gitbox.apache.org/repos/asf?p=geode.git;h=bbea69a ]
GEODE-3540: unable to gfsh destroy gateway-sender (#1414)
GW sender bean is not unregistered during destroy command which
is why it appears when you list gateways after destroy. This fix is to
unregistered the MX bean from SystemManagementService
> unable to gfsh destroy gateway-sender
> -
>
> Key: GEODE-3540
> URL: https://issues.apache.org/jira/browse/GEODE-3540
> Project: Geode
> Issue Type: Bug
> Components: gfsh, wan
>Reporter: Raphaël Enrici
>Assignee: Sai Boorlagadda
>Priority: Major
> Labels: pull-request-available
> Time Spent: 0.5h
> Remaining Estimate: 0h
>
> Dear all,
> while playing with wan setup we found that we are unable to destroy a
> declared sender configuration.
> You can reproduce this in a simple one node setup with apache geode 1.2.0:
> * start a locator
> * start a server
> * create a gateway-sender
> * destroy the gateway-sender => messages are ok
> * list gateways, the gateway-sender is still here although we just destroyed
> it
> * if you try to destroy it again, you get "ERROR: GateWaySender with Id
> sender not found"
> * if you list gateways again, the gateway is still here, you can even start
> and stop it although it is not functional anymore.
> * restarting the whole cluster does not change anything.
> Maybe we missed something concerning this, if the answer to this is a RTFM
> one, sorry for the noise.
> Keep up the good work.
> Best,
> Raphaël
> Here are shrinked outputs concerning this problem:
> {quote}
> gfsh> start locator --name=happylocator
> gfsh> start server --name=happyserver1
> gfsh>create gateway-sender --id=sender --remote-distributed-system-id=2
>Member| Status
> |
> happyserver1 | GatewaySender "sender" created on "happyserver1"
> gfsh>list gateways
> Gateways
> GatewaySender
> GatewaySender Id | Member | Remote Cluster
> Id | Type | Status | Queued Events | Receiver Location
> | --- |
> - | -- | --- | - | -
> sender | 192.168.0.6(happyserver1:1689):1025 | 2
> | Serial | Running | 0 | null
> gfsh>destroy gateway-sender --id sender
>Member| Status
> | --
> happyserver1 | GatewaySender "sender" destroyed on "happyserver1"
> gfsh>list gateways
> Gateways
> GatewaySender
> GatewaySender Id | Member | Remote Cluster
> Id | Type | Status| Queued Events | Receiver Location
> | --- |
> - | -- | --- | - | -
> sender | 192.168.0.6(happyserver1:1689):1025 | 2
> | Serial | Not Running | 0 | null
> gfsh>destroy gateway-sender --id sender
>Member| Status
> | --
> happyserver1 | ERROR: GateWaySender with Id sender not found
> gfsh>start gateway-sender --id sender
> Member | Result | Message
> --- | -- |
> -
> 192.168.0.6(happyserver1:1689):1025 | OK | GatewaySender sender is
> started on member 192.168.0.6(happyserv..
> {quote}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (GEODE-3540) unable to gfsh destroy gateway-sender
[
https://issues.apache.org/jira/browse/GEODE-3540?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16322793#comment-16322793
]
Rebecca P commented on GEODE-3540:
--
Hello, we have also observed the same:
{code:java}
Cluster-1 gfsh>list gateways
Gateways
GatewaySender
GatewaySender Id | Member
| Remote Cluster Id | Type | Status| Queued Events |
Receiver Location
|
|
- | -- | --- | - | -
ernie|
10.0.8.10(cacheserver-b7deac02-f1c6-4621-9e91-fca4bd5062e4:1):49152 | 2
| Serial | Not Running | 0 | null
ernie|
10.0.8.11(cacheserver-cda25ca9-c122-44bd-9604-06bbbf59e63d:1):49152 | 2
| Serial | Not Running | 0 | null
ernie|
10.0.8.8(cacheserver-887c724b-2eaf-42a0-9ce8-fd4cfaf45b4a:1):49152 | 2
| Serial | Not Running | 0 | null
ernie|
10.0.8.9(cacheserver-14b2bbb8-713b-4b8d-91c2-d365482c9163:1):49152 | 2
| Serial | Not Running | 0 | null
GatewayReceiver
Member | Port
| Sender Count | Sender's Connected
|
| |
10.0.8.10(cacheserver-b7deac02-f1c6-4621-9e91-fca4bd5062e4:1):49152 | 5165
| 0| [Ljava.lang.String;@4e8fbdf5
10.0.8.11(cacheserver-cda25ca9-c122-44bd-9604-06bbbf59e63d:1):49152 | 5357
| 0| [Ljava.lang.String;@375d396a
10.0.8.8(cacheserver-887c724b-2eaf-42a0-9ce8-fd4cfaf45b4a:1):49152 | 5304
| 0| [Ljava.lang.String;@717a28a4
10.0.8.9(cacheserver-14b2bbb8-713b-4b8d-91c2-d365482c9163:1):49152 | 5474
| 0| [Ljava.lang.String;@18ef07ad
Cluster-1 gfsh>destroy gateway-sender --id ernie
Member | Status
|
-
cacheserver-887c724b-2eaf-42a0-9ce8-fd4cfaf45b4a | ERROR: GateWaySender with Id
ernie not found
cacheserver-14b2bbb8-713b-4b8d-91c2-d365482c9163 | ERROR: GateWaySender with Id
ernie not found
cacheserver-b7deac02-f1c6-4621-9e91-fca4bd5062e4 | ERROR: GateWaySender with Id
ernie not found
cacheserver-cda25ca9-c122-44bd-9604-06bbbf59e63d | ERROR: GateWaySender with Id
ernie not found
{code}
we also noted that the state of a gateway sender without a region associated
looks the same as a destroyed gateway sender. This makes it misleading in terms
of determining what state a gateway sender is in.
> unable to gfsh destroy gateway-sender
> -
>
> Key: GEODE-3540
> URL: https://issues.apache.org/jira/browse/GEODE-3540
> Project: Geode
> Issue Type: Bug
> Components: gfsh
>Reporter: Raphaël Enrici
>
> Dear all,
> while playing with wan setup we found that we are unable to destroy a
> declared sender configuration.
> You can reproduce this in a simple one node setup with apache geode 1.2.0:
> * start a locator
> * start a server
> * create a gateway-sender
> * destroy the gateway-sender => messages are ok
> * list gateways, the gateway-sender is still here although we just destroyed
> it
> * if you try to destroy it again, you get "ERROR: GateWaySender with Id
> sender not found"
> * if you list gateways again, the gateway is still here, you can even start
> and stop it although it is not functional anymore.
> * restarting the whole cluster does not change anything.
> Maybe we missed something concerning this, if the answer to this is a RTFM
> one, sorry for the noise.
> Keep up the good work.
> Best,
> Raphaël
> Here are shrinked outputs concerning this problem:
> {quote}
> gfsh> start locator --name=happylocator
> gfsh> start server --name=happyserver1
> gfsh>create gateway-sender --id=sender --remote-distributed-system-id=2
>Member| Status
> |
> happyserver1 | GatewaySender "sender" created on "happyserver1"
> gfsh>list gateways
> Gateways
> GatewaySender
> GatewaySender Id | Member | Remote Cluster
> Id | Type | Status | Queued Events | Receiver Location
> | --- |
> - | -- | --- | - | -
> sender | 192.168.0.6(happyserver1:1689):1025 | 2
> | Serial | Running | 0 | null
> gfsh>destroy gateway-sender --id sender
>Member| Status
> | --
> happyserver1 |
