Couchbase Server

moxi: ascii noreply mutation cmds don't handle not-my-vbucket errors

Details

  • Type: Bug Bug
  • Status: Closed Closed
  • Resolution: Won't Fix
  • Affects Version/s: 1.6.0 beta4
  • Fix Version/s: None
  • Component/s: moxi
  • Labels:
    None
  • Environment:
    Operating System: All
    Platform: All

Description

During a vbucket migration / rebalance, when a moxi has an outdated vBucketServerMap, and a user tries an ascii key-based mutation cmd (SET/DELETE/ADD/...) ...

moxi will forward an equivalent quiet binary mutation request to a downstream binary server and then start processing the next client ascii request.

meanwhile, the downstream binary server will return a not-my-vbucket error, which moxi will ignore.

an alternative behavior is moxi should instead retry the quiet binary command on a different server.

Activity

Ascending order - Click to sort in descending order
Hide
Permalink
Matt(old) Ingenthron (Inactive) added a comment -
These are believed to be fixed. Please reopen if incorrect.
Show
Matt(old) Ingenthron (Inactive) added a comment - These are believed to be fixed. Please reopen if incorrect.
Hide
Permalink
Steve Yen added a comment -
Not fixed - while vocal ascii commands work fine (even through the NOT_MY_VBUCKET error response algorithm), noreply ascii cmds won't go through the retry-another-server algorithm.

Since the command was "noreply", perhaps the client doesn't care, but it'd still be good to retry at best-effort anyways.
Show
Steve Yen added a comment - Not fixed - while vocal ascii commands work fine (even through the NOT_MY_VBUCKET error response algorithm), noreply ascii cmds won't go through the retry-another-server algorithm. Since the command was "noreply", perhaps the client doesn't care, but it'd still be good to retry at best-effort anyways.
Hide
Permalink
Sean Lynch (Inactive) added a comment -
What's the user impact of this?
Show
Sean Lynch (Inactive) added a comment - What's the user impact of this?
Hide
Permalink
Steve Yen added a comment -
A client application requesting noreply ascii mutations during a rebalance could have their mutations disappear, without any feedback (e,g, they don't get any reply that their mutations went missing).
Show
Steve Yen added a comment - A client application requesting noreply ascii mutations during a rebalance could have their mutations disappear, without any feedback (e,g, they don't get any reply that their mutations went missing).
Hide
Permalink
Pivotal Integration added a comment -
A Pivotal Tracker story has been created for this Issue: http://www.pivotaltracker.com/story/show/27629741
Show
Pivotal Integration added a comment - A Pivotal Tracker story has been created for this Issue: http://www.pivotaltracker.com/story/show/27629741
Hide
Permalink
Pivotal Integration added a comment -
Steve Yen deleted the linked story in Pivotal Tracker
Show
Pivotal Integration added a comment - Steve Yen deleted the linked story in Pivotal Tracker

People

  • Assignee:
    Unassigned
    Reporter:
    Steve Yen
Vote (0)
Watch (1)

Dates

  • Created:
    Updated:
    Resolved: