Details

    • Type: Improvement
    • Status: Resolved
    • Priority: Critical
    • Resolution: Fixed
    • Affects Version/s: None
    • Fix Version/s: 2.0
    • Component/s: ns_server
    • Security Level: Public
    • Labels:
      None

      Description

      With the memcached protocol level flush_all command disabled as of 1.8.1, we need a feature to achieve a similar kind of flush.

      From earlier discussions, this would be available through the REST interface (disabled by default, with some bucket-level configuration option to enable). In previous discussions, we said it should similar semantics to flush_all from a client. By this I mean a request to REST to 'flush the bucket' would not remove the definition of the bucket like a delete, and clients would not be dropped or receive any errors while the cluster does whatever needs to be done to remove the data from the cluster.

      The full specification is TBD.

      # Subject Project Status CR V
      For Gerrit Dashboard: &For+MB-5170=message:MB-5170

        Activity

        Hide
        alkondratenko Aleksey Kondratenko (Inactive) added a comment -

        Noted. Thanks a lot.

        Show
        alkondratenko Aleksey Kondratenko (Inactive) added a comment - Noted. Thanks a lot.
        Hide
        alkondratenko Aleksey Kondratenko (Inactive) added a comment -

        merged at last

        Show
        alkondratenko Aleksey Kondratenko (Inactive) added a comment - merged at last
        Hide
        ingenthr Matt Ingenthron added a comment -

        Is it possible to update this with:
        1) A description of the specification in the description, it currently says TBD
        2) Any notes on what was implemented and merged on 26-Sept. I'm of course interested interested in how things ended up with the client.

        Show
        ingenthr Matt Ingenthron added a comment - Is it possible to update this with: 1) A description of the specification in the description, it currently says TBD 2) Any notes on what was implemented and merged on 26-Sept. I'm of course interested interested in how things ended up with the client.
        Hide
        alkondratenko Aleksey Kondratenko (Inactive) added a comment -

        server will first use new command - disable_traffic on all nodes. ep-engine will then start returning temp errors back to clients. Then we remove and recreate all vbuckets, and then we enable traffic back.

        From perspective of client it loooks like period of temp errors after which all data is gone

        Show
        alkondratenko Aleksey Kondratenko (Inactive) added a comment - server will first use new command - disable_traffic on all nodes . ep-engine will then start returning temp errors back to clients. Then we remove and recreate all vbuckets, and then we enable traffic back. From perspective of client it loooks like period of temp errors after which all data is gone
        Hide
        alkondratenko Aleksey Kondratenko (Inactive) added a comment -

        REST call is synchronous

        Show
        alkondratenko Aleksey Kondratenko (Inactive) added a comment - REST call is synchronous

          People

          • Assignee:
            alkondratenko Aleksey Kondratenko (Inactive)
            Reporter:
            ingenthr Matt Ingenthron
          • Votes:
            1 Vote for this issue
            Watchers:
            5 Start watching this issue

            Dates

            • Created:
              Updated:
              Resolved:

              Gerrit Reviews

              There are no open Gerrit changes