[jira] [Updated] (GEODE-9314) Redis CLUSTER NODES incorrect when primary buckets are moving
[ https://issues.apache.org/jira/browse/GEODE-9314?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Anthony Baker updated GEODE-9314: - Labels: pull-request-available unreleased (was: pull-request-available) > Redis CLUSTER NODES incorrect when primary buckets are moving > - > > Key: GEODE-9314 > URL: https://issues.apache.org/jira/browse/GEODE-9314 > Project: Geode > Issue Type: Bug > Components: redis >Reporter: Jens Deppe >Priority: Major > Labels: pull-request-available, unreleased > Fix For: 1.15.0 > > > When buckets are moving the CLUSTER NODES command may produce incorrect > results - specifically the node host/port information may be > duplicated/incorrect. -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Updated] (GEODE-9314) Redis CLUSTER NODES incorrect when primary buckets are moving
[ https://issues.apache.org/jira/browse/GEODE-9314?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] ASF GitHub Bot updated GEODE-9314: -- Labels: pull-request-available (was: ) > Redis CLUSTER NODES incorrect when primary buckets are moving > - > > Key: GEODE-9314 > URL: https://issues.apache.org/jira/browse/GEODE-9314 > Project: Geode > Issue Type: Bug > Components: redis >Reporter: Jens Deppe >Priority: Major > Labels: pull-request-available > > When buckets are moving the CLUSTER NODES command may produce incorrect > results - specifically the node host/port information may be > duplicated/incorrect. -- This message was sent by Atlassian Jira (v8.3.4#803005)