Details
Description
Created an attachment (id=590)
diag
1.6.0beta3.2b-22
centos 5.4 32bit
4 nodes
1) cluster 4 nodes
2) create 3 new buckets
* 1 with replication count 1
* 1 with replication count 2
* 1 with replication count 3
3) load some data in to the buckets
Port server vbucketmigrator on node 'ns_1@10.1.4.199' exited with status 78. Restarting. Messages: Authenticating towards: {Sock 10.1.4.207:11210}
Authenticated towards: {Sock 10.1.4.207:11210}
Connecting to source: 10.1.4.199:11210
Authenticating towards: {Sock 10.1.4.199:11210}
Failed to authenticate: Authentication failed: Auth failure
diag
1.6.0beta3.2b-22
centos 5.4 32bit
4 nodes
1) cluster 4 nodes
2) create 3 new buckets
* 1 with replication count 1
* 1 with replication count 2
* 1 with replication count 3
3) load some data in to the buckets
Port server vbucketmigrator on node 'ns_1@10.1.4.199' exited with status 78. Restarting. Messages: Authenticating towards: {Sock 10.1.4.207:11210}
Authenticated towards: {Sock 10.1.4.207:11210}
Connecting to source: 10.1.4.199:11210
Authenticating towards: {Sock 10.1.4.199:11210}
Failed to authenticate: Authentication failed: Auth failure
Activity
Matt Ingenthron
made changes -
| Field | Original Value | New Value |
|---|---|---|
| issue.field.bugzillaimportkey | 2396 | 12166 |
Frank Weigel
made changes -
| Affects Version/s | 1.6.0 beta4 [ 10055 ] | |
| Affects Version/s | 1.6.0beta4 [ 10045 ] |
Sean Lynch
made changes -
| Fix Version/s | 1.6.1 [ 10059 ] |
Sean Lynch
made changes -
| Fix Version/s | Backlog [ 10090 ] |
Aleksey Kondratenko
made changes -
| Assignee | Sean Lynch [ sean@northscale.com ] | Keith Batten [ keith ] |
Aleksey Kondratenko
made changes -
| Priority | Critical [ 2 ] |
Aleksey Kondratenko
made changes -
| Labels | need_info | |
| Priority | Critical [ 2 ] | Blocker [ 1 ] |
Aleksey Kondratenko
made changes -
Benjamin Young
made changes -
| Status | Open [ 1 ] | Resolved [ 5 ] |
| Resolution | Incomplete [ 4 ] |
Benjamin Young
made changes -
It appears that the final bucket was created an extremely short period before the rebalance started - was this an automated test? Did retrying the rebalance succeed?
Memcached only checks the password file once per second, so if you create a bucket and then try to do something to it within a short period of time, you can get auth failures. It's difficult to make this synchronous, so for beta4, assuming the failure was transient, I'm inclined to say "don't do that."