[ https://issues.apache.org/jira/browse/GEODE-8329?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Jakov Varenina updated GEODE-8329: ---------------------------------- Description: {color:#172b4d}It seems that aftter server failover the java client is wrongly re-registering CQ on new server as not durable. Command *list durable-cq* prints that there are no durable CQ which is correct, since CQ is wrongly registered by client as not durable and therefore following printout:{color} {code:java} gfsh>list durable-cqs --durable-client-id=AppCounters Member | Status | CQ Name ------- | ------- | -------------------------------------------- server1 | OK | randomTracker server2 | IGNORED | No client found with client-id : AppCounters server3 | IGNORED | No client found with client-id : AppCounters after shutdown of server1: gfsh>list durable-cqs --durable-client-id=AppCounters Member | Status | CQ Name ------- | ------- | ----------------------------------------------------------- server2 | IGNORED | No durable cqs found for durable-client-id : "AppCounters". --> server2 is hosting CQ, but it is not flagged as durable server3 | IGNORED | No client found with client-id : AppCounters{code} > Durable CQ not registered as durable after server failover > ---------------------------------------------------------- > > Key: GEODE-8329 > URL: https://issues.apache.org/jira/browse/GEODE-8329 > Project: Geode > Issue Type: Bug > Reporter: Jakov Varenina > Assignee: Jakov Varenina > Priority: Major > > {color:#172b4d}It seems that aftter server failover the java client is > wrongly re-registering CQ on new server as not durable. Command *list > durable-cq* prints that there are no durable CQ which is correct, since CQ is > wrongly registered by client as not durable and therefore following > printout:{color} > {code:java} > gfsh>list durable-cqs --durable-client-id=AppCounters > Member | Status | CQ Name > ------- | ------- | -------------------------------------------- > server1 | OK | randomTracker > server2 | IGNORED | No client found with client-id : AppCounters > server3 | IGNORED | No client found with client-id : AppCounters > > after shutdown of server1: > > gfsh>list durable-cqs --durable-client-id=AppCounters > Member | Status | CQ Name > ------- | ------- | > ----------------------------------------------------------- > server2 | IGNORED | No durable cqs found for durable-client-id : > "AppCounters". --> server2 is hosting CQ, but it is not flagged as durable > server3 | IGNORED | No client found with client-id : AppCounters{code} -- This message was sent by Atlassian Jira (v8.3.4#803005)