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

Cannot change priority of dcp connection

    XMLWordPrintable

Details

    • Bug
    • Status: Closed
    • Major
    • Resolution: User Error
    • 6.5.0
    • 6.5.0
    • DCP
    • None
    • Untriaged
    • Unknown

    Description

      I tried changing priority of DCP connection as follows:
      1. Set priority when DCP connection was set up. – no error here.
      2. Set/change priority after DCP connection was set up.

      The following error was seen in memcached log at step 2.

      2018-12-04T10:55:00.239768Z WARNING 512096080: cookie_get_priority: priority (which is 16) is not a valid CONN_PRIORITY - closing connection (<86>^^A@@@@<86>^^A@@<86>^^A@@@<80>,<86>^^A@@@Ð-<86>^^A@@@@/<86>^^A@@@p

      I tried setting different priorities at step 1 and step 2, and the same error message about invalid value of 16 was returned regardless. There seems to be issues with the way the dcp connection maintains priority.

      cbcollect attached.

      Attachments

        No reviews matched the request. Check your Options in the drop-down menu of this sections header.

        Activity

          jwalker Jim Walker added a comment -

          Yu Sui can I ask you to update your repo and try again.

          Checking the git history shows that the logging with "cookie_get_priority" dates your kv-engine from before July 2018, you're basically using a very old KV here and I've no idea how old your version is.

          Note: It may not fix the issue, but if this is a mad-hatter MB, you should be using something representative of the mad-hatter KV!

          jwalker Jim Walker added a comment - Yu Sui can I ask you to update your repo and try again. Checking the git history shows that the logging with "cookie_get_priority" dates your kv-engine from before July 2018 , you're basically using a very old KV here and I've no idea how old your version is. Note: It may not fix the issue, but if this is a mad-hatter MB, you should be using something representative of the mad-hatter KV!

          stats.log has the KV sha as 4b0cd5566baedf1a146b8a61b08010d959b19b6c from Jun 27

          dhaikney David Haikney added a comment - stats.log has the KV sha as 4b0cd5566baedf1a146b8a61b08010d959b19b6c from Jun 27

          Every time I updated my repo, I ran into some issues, probably because my Mac OS is old. That is why I had refrained from updates as long as things do not break.

          I will upgrade my OS and my repo.

          yu Yu Sui (Inactive) added a comment - Every time I updated my repo, I ran into some issues, probably because my Mac OS is old. That is why I had refrained from updates as long as things do not break. I will upgrade my OS and my repo.

          Things worked fine after I synced to latest madhatter.

          yu Yu Sui (Inactive) added a comment - Things worked fine after I synced to latest madhatter.

          Closing all invalid, won-t fix, duplicate bugs

          raju Raju Suravarjjala added a comment - Closing all invalid, won-t fix, duplicate bugs

          People

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

            Dates

              Created:
              Updated:
              Resolved:

              Gerrit Reviews

                There are no open Gerrit changes

                PagerDuty