In a recent investigation of something unrelated, I found that the server will send not-my-vbucket replies during warmup.
Note that in a discussion with Trond, both he and I expected warmup (as currently designed) would send a tmpfail.
I've actually observed that the server sends not-my-vbucket responses. This is bad, as many clients will retry (possibly as fast as they can) and moxi will hit every server twice and give up.
What is the intended behavior of the server on the memcached port number during warmup? Is that behavior defined anywhere? We need to verify that client reactions are appropriate during warmup.
Note that Aliaksey said a related issue is document editing from the UI in this state.
|For Gerrit Dashboard: &For+MB-5201=message:MB-5201|
|16357,1||MB-5201 Convert NOT_MY_VBUCKET to TMP_FAIL response during warmup||ep-engine||Status: MERGED||+2||+1|
|16383,1||MB-5201 Convert NOT_MY_VBUCKET to TMP_FAIL response during warmup||ep-engine||Status: MERGED||+2||+1|
|16387,1||Merge branch 'branch-18'||ep-engine||Status: MERGED||+2||+1|