[SERVER-6523] RO auth doesn't work right after user is created Created: 19/Jul/12 Updated: 11/Jul/16 Resolved: 20/Jul/12 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Sharding |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | Kristina Chodorow (Inactive) | Assignee: | Spencer Brody (Inactive) |
| Resolution: | Done | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Attachments: |
|
| Operating System: | ALL |
| Participants: |
| Description |
|
Seems like a caching issue? Happens intermittently. Andy thought that changing the Scoped connection in s/security.cpp to a ScopedInternal connection would fix it, not sure if it does or not. I attached a file that reproduces it but the file has a ton of cruft that I couldn't get rid of without it not reproducing it anymore (stupid stuff like code that isn't even called before the exception). The important part that isn't working is basically in the getUser function: it does an addUser and then and auth on the user that was just added and it doesn't work. |
| Comments |
| Comment by Spencer Brody (Inactive) [ 20/Jul/12 ] |
|
Kristina already confirmed that waiting for replication fixed the problem. |
| Comment by Spencer Brody (Inactive) [ 20/Jul/12 ] |
|
This sounds like |
| Comment by Andy Schwerin [ 20/Jul/12 ] |
|
@spencer, is this a regression? |