Details

    • Type: Bug
    • Status: Closed
    • Priority: Major
    • Resolution: Fixed
    • Affects Version/s: None
    • Fix Version/s: 0.7
    • Component/s: library
    • Security Level: Public
    • Labels:
      None

      Description

      The current Python client cannot handle topology changes dynamically. It should learn to do so in one of two ways.

      1) Implement handling of fast-forward map.
      2) Implement retry of nodes.

      When a node is added to the cluster and rebalance is started, a new map is published with a fast-forward section and an updated node list with the new node listed.

      The python client should handle not-my-vbucket errors by trying the fast forward map, or should retry each node (maybe twice?) until some node takes the item.

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

        Activity

          People

          • Assignee:
            farshid Farshid Ghods (Inactive)
            Reporter:
            ingenthr Matt Ingenthron
          • Votes:
            0 Vote for this issue
            Watchers:
            0 Start watching this issue

            Dates

            • Created:
              Updated:
              Resolved:

              Gerrit Reviews

              There are no open Gerrit changes