You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@geode.apache.org by "Sai Boorlagadda (JIRA)" <ji...@apache.org> on 2018/04/27 00:06:00 UTC

[jira] [Updated] (GEODE-5146) WAN Information view in Pulse shows wrong status for remote clusters

     [ https://issues.apache.org/jira/browse/GEODE-5146?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Sai Boorlagadda updated GEODE-5146:
-----------------------------------
    Description: 
GEODE-2186 fixed to address that the status should be cumulative and not just the last sender's status, but introduced *connection status* of remote cluster based on gateway sender being running rather than being connected.

This ticket is to fix the connection status to infer from GatewaySenderMXBean.isConnected while considering whether sender is a serial or parallel.
 * serial - primary connected -> true
 * serial - primary not connected -> false
 * parallel - all members connected - true
 * parallel - not all members connected - false

  was:
GEODE-2186 fixed to address that the status should be cumulative and not to consider just the last sender's status, but introduced *connection status* of remote cluster based on gateway sender being running rather than being connected.

This ticket is to fix the connection status to infer from GatewaySenderMXBean.isConnected while considering whether sender is a serial or parallel.
 * serial - primary connected -> true
 * serial - primary not connected -> false
 * parallel - all members connected - true
 * parallel - not all members connected - false


> WAN Information view in Pulse shows wrong status for remote clusters
> --------------------------------------------------------------------
>
>                 Key: GEODE-5146
>                 URL: https://issues.apache.org/jira/browse/GEODE-5146
>             Project: Geode
>          Issue Type: Bug
>          Components: pulse
>            Reporter: Sai Boorlagadda
>            Priority: Major
>
> GEODE-2186 fixed to address that the status should be cumulative and not just the last sender's status, but introduced *connection status* of remote cluster based on gateway sender being running rather than being connected.
> This ticket is to fix the connection status to infer from GatewaySenderMXBean.isConnected while considering whether sender is a serial or parallel.
>  * serial - primary connected -> true
>  * serial - primary not connected -> false
>  * parallel - all members connected - true
>  * parallel - not all members connected - false



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