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

flush_all doesn't work on the latest 2.0 builds

    Details

      Description

      some of the failures we saw recently in couch were caused by flush _alll

      will add more info later

        Issue Links

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

          Activity

          Hide
          FilipeManana Filipe Manana (Inactive) added a comment -

          No idea what this is about neither how the view engine could solve anything here.
          This seems like some component (mccouch?) is not doing the necessary view engine interaction.

          Show
          FilipeManana Filipe Manana (Inactive) added a comment - No idea what this is about neither how the view engine could solve anything here. This seems like some component (mccouch?) is not doing the necessary view engine interaction.
          Hide
          farshid Farshid Ghods (Inactive) added a comment -

          assigning this to Dipti.

          do we plan to support flush in 2.0 ?

          Show
          farshid Farshid Ghods (Inactive) added a comment - assigning this to Dipti. do we plan to support flush in 2.0 ?
          Hide
          ingenthr Matt Ingenthron added a comment -

          To my knowledge, plan is the same as described in my comment on June 3. In more detail, plan is to:
          1) disable flush_all by default, with a method to enable it with known drawbacks on it not being synchronous (but not broken) until...
          2) RESTful flush is fixed to be correct to its interface and at least reasonable latency (and still have it off by default) and then
          3) Migrate all tests to use the now reliable RESTful flush
          4) Take away the method to disable flush_all on a per-node basis

          Show
          ingenthr Matt Ingenthron added a comment - To my knowledge, plan is the same as described in my comment on June 3. In more detail, plan is to: 1) disable flush_all by default, with a method to enable it with known drawbacks on it not being synchronous (but not broken) until... 2) RESTful flush is fixed to be correct to its interface and at least reasonable latency (and still have it off by default) and then 3) Migrate all tests to use the now reliable RESTful flush 4) Take away the method to disable flush_all on a per-node basis
          Hide
          trond Trond Norbye added a comment -

          this isn't a bucket_engine thing (works as expected for memcached buckets), but a problem with the couchdb buckets

          Show
          trond Trond Norbye added a comment - this isn't a bucket_engine thing (works as expected for memcached buckets), but a problem with the couchdb buckets
          Hide
          dipti Dipti Borkar added a comment -
          Show
          dipti Dipti Borkar added a comment - MB-5170

            People

            • Assignee:
              dipti Dipti Borkar
              Reporter:
              farshid Farshid Ghods (Inactive)
            • Votes:
              0 Vote for this issue
              Watchers:
              1 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved:

                Gerrit Reviews

                There are no open Gerrit changes