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

Long running index builds don't seem to update stats until complete

    XMLWordPrintable

Details

    • Bug
    • Resolution: Fixed
    • Major
    • 4.0.0
    • 4.0.0
    • secondary-index
    • Security Level: Public
    • None
    • Untriaged
    • Unknown

    Description

      On the latest build (1844) I loaded 5M items into the default bucket before creating any index and then ran "create primary index on default using GSI".

      I noticed in the UI that the statistics around index and disk size (among others) didn't update until quite a while into the initial build and then after the "items remaining" had reached 0, the disk and index sizes were still not correct.

      In general, it's hard to tell what the indexer is doing and when it is considered "done" via the UI.

      Let me know if screenshots and/or logs are most useful, this should be fairly straightforward to reproduce. We might need a bit of PM guidance in terms of what we want the behavior to be.

      Attachments

        Issue Links

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

          Activity

            People

              deepkaran.salooja Deepkaran Salooja
              perry Perry Krug
              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