[jira] [Commented] (GEODE-8329) Durable CQ not registered as durable after server failover

["ASF GitHub Bot (Jira)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/GEODE-8329?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17154201#comment-17154201 ] 

ASF GitHub Bot commented on GEODE-8329:
---------------------------------------

jvarenina opened a new pull request #5360:
URL: https://github.com/apache/geode/pull/5360


   This change solves the issue when the client without configured HA is
   wrongly re-registering durable CQs as non durable during the server
   failover.
   
   Thank you for submitting a contribution to Apache Geode.
   
   In order to streamline the review of the contribution we ask you
   to ensure the following steps have been taken:
   
   ### For all changes:
   - [x] Is there a JIRA ticket associated with this PR? Is it referenced in the commit message?
   
   - [x] Has your PR been rebased against the latest commit within the target branch (typically `develop`)?
   
   - [x] Is your initial contribution a single, squashed commit?
   
   - [x] Does `gradlew build` run cleanly?
   
   - [x] Have you written or updated unit tests to verify your changes?
   
   - [ ] If adding new dependencies to the code, are these dependencies licensed in a way that is compatible for inclusion under [ASF 2.0](http://www.apache.org/legal/resolved.html#category-a)?
   
   ### Note:
   Please ensure that once the PR is submitted, check Concourse for build issues and
   submit an update to your PR as soon as possible. If you need help, please send an
   email to dev@geode.apache.org.
   


----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

For queries about this service, please contact Infrastructure at:
users@infra.apache.org


> 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)