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