[
https://issues.apache.org/jira/browse/GEODE-3906?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Dave Barnes updated GEODE-3906:
-------------------------------
Description:
This feature request is to enhance the 'describe connection' and 'disconnect'
commands to provide the actual string that will work for a subsequent 'connect'
command. I know this is available to gfsh, as it is provided when you issue a
'describe member' command.
Current behavior:
The gfsh 'describe connection' command currently shows host and JMX port:
```
gfsh>describe connection
Connection Endpoints
--------------------
172.16.71.1[1099]
```
The 'disconnect' command gives the same info:
```
gfsh>disconnect
Disconnecting from: 172.16.71.1[1099]
Disconnected from : 172.16.71.1[1099]
```
While the information is accurate, it cannot be used to reconnect. Instead,
gfsh wants the locator port (default 10334), not the JMX port. As a user, I
find this un-intuitive.
Consider this use case:
- I know I am going to disconnect and then reconnect (during an upgrade, for
example).
- I issue the 'describe connection' command and note the result, so I can use
it when I reconnect.
- I disconnect and exit gfsh.
- Later, I fire up gfsh and try to reconnect using 'connect
--locator=localhost[1099]'. The connection fails, because gfsh wants the
locator port (10334 by default, but could be something else).
was:
The gfsh 'describe connection' command currently shows host and JMX port:
```
gfsh>describe connection
Connection Endpoints
--------------------
172.16.71.1[1099]
```
The 'disconnect' command gives the same info:
```
gfsh>disconnect
Disconnecting from: 172.16.71.1[1099]
Disconnected from : 172.16.71.1[1099]
```
While the information is accurate, it cannot be used to reconnect. Instead,
gfsh wants the locator port (default 10334), not the JMX port. As a user, I
find this un-intuitive.
Consider this use case:
- I know I am going to disconnect and then reconnect (during an upgrade, for
example).
- I issue the 'describe connection' command and note the result, so I can use
it when I reconnect.
- I disconnect and exit gfsh.
- Later, I fire up gfsh and try to reconnect using 'connect
--locator=localhost[1099]. The connection fails, because gfsh wants the locator
port (10334 by default, but could be something else).
This feature request is enhance the 'describe connection' and 'disconnect'
commands to provide the actual string that will work for a subsequent 'connect'
command. I know this is available to gfsh, as it is provided when you issue a
'describe member' command.
> Improve gfsh 'describe connection' and 'disconnect' command info
> -----------------------------------------------------------------
>
> Key: GEODE-3906
> URL: https://issues.apache.org/jira/browse/GEODE-3906
> Project: Geode
> Issue Type: New Feature
> Components: gfsh
> Reporter: Dave Barnes
>
> This feature request is to enhance the 'describe connection' and 'disconnect'
> commands to provide the actual string that will work for a subsequent
> 'connect' command. I know this is available to gfsh, as it is provided when
> you issue a 'describe member' command.
> Current behavior:
> The gfsh 'describe connection' command currently shows host and JMX port:
> ```
> gfsh>describe connection
> Connection Endpoints
> --------------------
> 172.16.71.1[1099]
> ```
> The 'disconnect' command gives the same info:
> ```
> gfsh>disconnect
> Disconnecting from: 172.16.71.1[1099]
> Disconnected from : 172.16.71.1[1099]
> ```
> While the information is accurate, it cannot be used to reconnect. Instead,
> gfsh wants the locator port (default 10334), not the JMX port. As a user, I
> find this un-intuitive.
> Consider this use case:
> - I know I am going to disconnect and then reconnect (during an upgrade, for
> example).
> - I issue the 'describe connection' command and note the result, so I can use
> it when I reconnect.
> - I disconnect and exit gfsh.
> - Later, I fire up gfsh and try to reconnect using 'connect
> --locator=localhost[1099]'. The connection fails, because gfsh wants the
> locator port (10334 by default, but could be something else).
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
