Uploaded image for project: 'Couchbase Documentation'
  1. Couchbase Documentation
  2. DOC-9599

Release note MB-43232 makes no sense

    XMLWordPrintable

Details

    • Bug
    • Resolution: Unresolved
    • None
    • None
    • None

    Description

      Problem
      A end user is not going to understand this release note

      MB-43232

      Summary: Starting with version 6.5.0, VbSeqnosReader has been updated to process two types of requests: VbSeqnosRequest and VbMinSeqnosRequest. When processing VbSeqnosRequest, if there are any VbMinSeqnosRequest’s, then the VbMinSeqnosRequest’s will be queued back into the requestCh of VbSeqnosReader. However, if the VbSeqnosReader closed by this time, then enqueue would fail and the caller would be waiting for a response indefinitely. This has been fixed to respond to outstanding requests upon exit of VbSeqnosReader.

      A user does not know what VbMinSeqnosRequest’s and VbSeqnosReader.

      Expectation

      For the release notes to be in plain English that an end user can understand. It should say what is the problem in terms of affecting the end user and how that is triggered.

      For example:

      • Index Services crashes when X happens
      • Index Service is slow at processing mutations under Y situation
      • Index Service does create disk snapshot when Z happens causing recovery to be slow if the process restarts
      • Index Service has a memory leak when A happens.

      The X, Y, Z and A should be easily understandable to the user.

      I suspect you will need help from the the GSI team.

      Attachments

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

        Activity

          People

            simon.dew Simon Dew
            pvarley Patrick Varley (Inactive)
            Votes:
            0 Vote for this issue
            Watchers:
            8 Start watching this issue

            Dates

              Created:
              Updated:

              Gerrit Reviews

                There are no open Gerrit changes

                PagerDuty