Uploaded image for project: 'Couchbase Server'
  1. Couchbase Server
  2. MB-26664

close tcp connection first and do not close dcp streams when dcp nozzle stops

    XMLWordPrintable

Details

    • Bug
    • Resolution: Fixed
    • Major
    • 5.5.0
    • 5.5.0
    • XDCR
    • None
    • Triaged
    • Unknown

    Description

      As of now, when dcp nozzle stops, it closes dcp streams, then closes gomemcached feed, then closed tcp connection for dcp. If the first two operations hang, the tcp connection may not get closed.

      The new plan is to close tcp connection first, then close gomemcached feed. There is no need to close dcp streams since tcp connection will cause the dcp streams to be closed by dcp shortly.

      Attachments

        Issue Links

          blocks

          Bug - A problem which impairs or prevents the functions of the product. MB-26818 [5.1.0 CLONE MB-26664]- close tcp connection first and do not close dcp streams when dcp nozzle stops

          • Major - Major loss of function.
          • Closed
          relates to

          Bug - A problem which impairs or prevents the functions of the product. MB-25979 dcp nozzle needs to close tcp connection when stopping

          • Major - Major loss of function.
          • Closed

          Bug - A problem which impairs or prevents the functions of the product. MB-27277 [5.0 CLONE] old dcp connection is not closed when replication restarts

          • Major - Major loss of function.
          • Closed

          Bug - A problem which impairs or prevents the functions of the product. MB-26808 [4.6.5 CLONE MB-26664]- close tcp connection first and do not close dcp streams when dcp nozzle stops

          • Major - Major loss of function.
          • Closed

          Activity

            People

              yu Yu Sui (Inactive)
              yu Yu Sui (Inactive)
              Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved:

                PagerDuty