[SERVER-71661] Inconsistency between nodes Created: 22/Nov/22 Updated: 19/Jan/23 Resolved: 19/Jan/23 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | None |
| Affects Version/s: | 4.2.14 |
| Fix Version/s: | None |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | Li xin | Assignee: | Eric Sedor |
| Resolution: | Done | Votes: | 0 |
| Labels: | Bug | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Environment: |
ubuntu mongodb 4.2.14 |
||
| Attachments: |
|
| Participants: |
| Description |
|
I found that part of the data read from the primary is different from the one written . The data of the same _id is inconsistent in primary and secondary |
| Comments |
| Comment by Eric Sedor [ 27/Dec/22 ] | ||||
|
Hi bingfeng198878@163.com, I wanted to see if you'd be able to provide any of the above information. If not, I will close this as you requested. | ||||
| Comment by Eric Sedor [ 28/Nov/22 ] | ||||
|
Hi bingfeng198878@163.com, I am treating this as a SERVER ticket rather than a WT ticket initially, as this seems part of your use of MongoDB. To start with, please make a complete copy of the node's $dbpath directory to safeguard so that you can work off of the current $dbpath. Our ability to determine the source of this issue depends greatly on your ability to provide:
The ideal resolution is to perform a clean resync from an unaffected node. If you can provide us with the answers above, we can investigate further. | ||||
| Comment by Li xin [ 24/Nov/22 ] | ||||
|
I think this issue can be closed, the probability is “bit flip” | ||||
| Comment by Li xin [ 22/Nov/22 ] | ||||
|
I query on primary
I query on other 3 secondarys
offset field is different.
I write majory, and no delay between primary and secondary. The hexadecimal format of the offset field of primary is 0x190000424f1d,the hexadecimal format of the offset field of secondary is 0x424f1d (is NumberLong(4345629) ). So I think the data on primary highest bit has jumped from 0x00 to0x19(other cases 0x00 to 0x12 ) . At least 32 wrong data
|