Details

    • Type: Bug
    • Status: Resolved
    • Priority: Major
    • Resolution: Won't Fix
    • Affects Version/s: 1.5 z
    • Fix Version/s: None
    • Component/s: couchbase-bucket
    • Labels:
      None
    • Environment:
      Operating System: All
      Platform: All

      Description

      In performing testing with dbmaint for vacuum, there are times the vacuum takes too long.

      For example:
      Issuing stop command
      Issuing start command
      Pausing persistence... paused.
      Vacuuming /ebs/zstore/test.db
      Vacuuming /ebs/zstore/test.db-0.sqlite
      Vacuuming /ebs/zstore/test.db-1.sqlite
      Vacuuming /ebs/zstore/test.db-2.sqlite
      Vacuuming /ebs/zstore/test.db-3.sqlite
      Unpausing persistence.
      time taken for vacuum process: 666

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

        Activity

        Hide
        farshid Farshid Ghods (Inactive) added a comment -

        verify this as part of 1.7.0 testing of mbbackup

        Show
        farshid Farshid Ghods (Inactive) added a comment - verify this as part of 1.7.0 testing of mbbackup
        Hide
        farshid Farshid Ghods (Inactive) added a comment -

        ran mbbackup to backup a huge database and the time it took was reasonable

        please reopen the bug if this bug is still relevant and i should try to reproduce this using dbmaint instead of mbbackup.

        Show
        farshid Farshid Ghods (Inactive) added a comment - ran mbbackup to backup a huge database and the time it took was reasonable please reopen the bug if this bug is still relevant and i should try to reproduce this using dbmaint instead of mbbackup.
        Hide
        ingenthr Matt Ingenthron added a comment -

        Reopening as there was nothing said about the age of the db files. A vacuum of a DB which is already in optimal shape would be rather quick. I know of nothing that should have made this any better, so I see no argument for closing it as fixed.

        There may be an argument someday for closing it will not fix, but it should remain for now.

        Show
        ingenthr Matt Ingenthron added a comment - Reopening as there was nothing said about the age of the db files. A vacuum of a DB which is already in optimal shape would be rather quick. I know of nothing that should have made this any better, so I see no argument for closing it as fixed. There may be an argument someday for closing it will not fix, but it should remain for now.

          People

          • Assignee:
            farshid Farshid Ghods (Inactive)
            Reporter:
            matt@northscale.com Matt(old) Ingenthron (Inactive)
          • Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

            Dates

            • Created:
              Updated:
              Resolved:

              Gerrit Reviews

              There are no open Gerrit changes