[SERVER-36551] Collection UUID differs from UUID on change stream operations Created: 09/Aug/18 Updated: 08/Mar/19 Resolved: 31/Jan/19 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | None |
| Affects Version/s: | 3.6.1, 3.6.6 |
| Fix Version/s: | None |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | Artem | Assignee: | Kelsey Schubert |
| Resolution: | Incomplete | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Operating System: | ALL |
| Participants: |
| Description |
|
I try to migrate from oplog fetching to change stream and got error:
After googling I found issue
But it was unsuccessfully:
The user.users collection was created half-year ago and servers was some times rebooted and upgraded. |
| Comments |
| Comment by Kelsey Schubert [ 31/Jan/19 ] | ||
|
Hi bozaro, We haven’t heard back from you for some time, so I’m going to mark this ticket as resolved. If this is still an issue for you, please provide additional information and we will reopen the ticket. Regards, | ||
| Comment by Kelsey Schubert [ 30/Nov/18 ] | ||
|
Hi bozaro, We still need additional information to diagnose the problem. If this is still an issue for you, would you please answer my questions above? Thank you, | ||
| Comment by Kelsey Schubert [ 12/Oct/18 ] | ||
|
Hi bozaro, Thanks for the additional information and sorry for the delay getting back to you. Would you please clarify whether you are able to reproduce this issue with fresh data directly inserted into MongoDB 3.6? If not, I have a few follow up questions:
Thank you, | ||
| Comment by Artem [ 16/Aug/18 ] | ||
|
I can reproduce and fix this issue. Reproducing:
Solution:
If I remove uuid value from cache.collection back, I can reproduce this issue again. | ||
| Comment by Nick Brewer [ 15/Aug/18 ] | ||
|
I did some testing (a 3.4 --> 3.6 upgrade) on this as well and I wasn't able to reproduce it either. I'll close this ticket for now, but if you run into this again feel free to comment here and we can reopen it. -Nick | ||
| Comment by Artem [ 13/Aug/18 ] | ||
|
I installed mongo servers (3.6.6) with data from production snapshot: this error was not reproduced. I have no thoughts how to fix (on production) or reproduce (on test environment) the problem | ||
| Comment by Artem [ 12/Aug/18 ] | ||
|
I already did it. I run forceRoutingTableRefresh with and without syncFromConfig flag on version 3.6.1 and 3.6.6. Next week I would to create copy of production cluster and try to add UUID to config.cache.collections manually. | ||
| Comment by Nick Brewer [ 10/Aug/18 ] | ||
|
bozaro Please try running the forceRoutingTableRefresh command without the syncFromConfig: true option specified. Thanks, | ||
| Comment by Artem [ 10/Aug/18 ] | ||
|
Yes. All servers was rebooted after forceRoutingTableRefresh command on the primary. Also I can see "Collection user.users UUID differs from UUID on change stream operations" error even I try to create changeStream directory on primary (without using mongos). | ||
| Comment by Nick Brewer [ 09/Aug/18 ] | ||
|
bozaro Per the instructions in the linked ticket, did you reboot the secondaries after running the forceRoutingTableRefresh command on the primary? -Nick |