Uploaded image for project: 'Couchbase Elasticsearch Connector'
  1. Couchbase Elasticsearch Connector
  2. CBES-65 Autonomous Operations Mode with Consul
  3. CBES-115

When Consul agent dies, leader still expects broadcast response

    XMLWordPrintable

Details

    • Sub-task
    • Resolution: Fixed
    • Major
    • 4.0.0-dp.1
    • None
    • None
    • SDK40: Coll. Plumb./SDK3 Refac, SDK3: SDK 3 Core/Comp./ES/Txn, SDK6: Durab., Hello, KV Doc, SDK8: SDK3, Pkg/CI, DOC KV, SDK14: α pub, blogs, svcs resp, SDK16: αS, error hnd, lookupin, SDK18: SYNC, err hand upd, sub, SDK20: PrepStmt, Doc ErrorH, SDK22: PrepStmt, Doc ErrorH, SDK24: PS, D-EH, D-A, MAPI, SDK30: MAPI, D-Async

    Description

      A Consul session does not automatically expire when the agent dies.

      As a result, the leader notices the worker is gone (since it gets a service health update) but tries to broadcast the "stop" request to it anyway since the endpoint document still exists (and doesn't go away after the session would expire naturally). The leader continually fails to quiesce the cluster (since it never gets a response from the dead node) and the connector gets stuck.

      Attachments

        Issue Links

          Activity

            People

              david.nault David Nault
              david.nault David Nault
              Votes:
              0 Vote for this issue
              Watchers:
              1 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved:

                PagerDuty