flush_all doesn't work on the latest 2.0 builds

Farshid Ghods added a comment - 13/Mar/12 10:18 PM flush_all is not handled correctly in 2.0 dp4 builds if there are views defined in the node/cluster or if flush is invoked when view or database compaction is running. users should use bucket_deletion for deleting and recreating the bucket.

Filipe Manana added a comment - 02/May/12 6:37 AM Farshid, from what I understand the flush command is no longer supported for DP5. If true, shall this issue be closed?

Farshid Ghods added a comment - 03/Jun/12 3:16 PM flush_all is disabled by default but the user can enable it and use it for testing

Matt Ingenthron added a comment - 03/Jun/12 3:22 PM For 2.0, the plan is to make the REST flush work correctly (though off by default) and leave this flush disabled. I don't know of an issue tracking this currently.

Matt Ingenthron added a comment - 03/Jun/12 3:24 PM Farshid: could you clarify the description here? Are you talking about 'failures in couch' or users seeing their data lost due to inadvertently issuing a flush_all command?

Farshid Ghods added a comment - 03/Jun/12 3:33 PM this is failure in couch and compaction daemons after calling flush_all. ( so the user won't be able to use the bucket after flush )

Matt Ingenthron added a comment - 07/Jun/12 7:29 PM MB-5170 is tracking the implementation of a REST level flush feature.

Peter Wansch added a comment - 28/Jun/12 12:34 PM Can you update the affects and fixed version and if you know this is a current or next sprint item, the sprint status as well? Thank you.

Filipe Manana added a comment - 28/Jun/12 12:53 PM 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.

Farshid Ghods added a comment - 24/Jul/12 10:34 PM assigning this to Dipti. do we plan to support flush in 2.0 ?

Matt Ingenthron added a comment - 24/Jul/12 10:53 PM 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

Trond Norbye added a comment - 30/Jul/12 2:57 PM this isn't a bucket_engine thing (works as expected for memcached buckets), but a problem with the couchdb buckets

Dipti Borkar added a comment - 03/Aug/12 6:44 PM MB-5170