[SERVER-7913] Invalid BSON in db.system.profile Created: 12/Dec/12 Updated: 10/Dec/14 Resolved: 15/Mar/13 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Logging |
| Affects Version/s: | 2.2.1 |
| Fix Version/s: | None |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | Michael Henson | Assignee: | Tad Marshall |
| Resolution: | Done | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Environment: |
Linux - Ubuntu Lucid |
||
| Attachments: |
|
||||||||
| Issue Links: |
|
||||||||
| Operating System: | ALL | ||||||||
| Participants: | |||||||||
| Description |
|
We are getting what appear to be invalid bson documents in the system profile collection, which is making it rather difficult to analyze the results. After enabling the profiler, these invalid documents will appear after a few minutes of run time. Dropping the capped collection and recreating it seems to have no effect as the invalid documents will be reinserted after a few minutes time. So far we have only seen this issue on our primary node. The secondary machines in our replica set do not appear to be affected. I don't recall ever getting this sort of error when we were running mongo 2.0. This is the first time since our upgrade to 2.2.1 that we have turned on the profiler. Attempts to iterate through db.system.profile in the mongo shell result in the following assertion:
Running db.system.profile.validate( {full: true}) results in the following output:
During the validation the following log lines are emitted:
I've also attached a copy of the affected collection to this jira. |
| Comments |
| Comment by Tad Marshall [ 15/Mar/13 ] |
|
Hi Michael, Thanks for letting us know! Tad |
| Comment by Michael Henson [ 14/Mar/13 ] |
|
Following up here ... We upgraded to 2.2.2 and this issue looks to be resolved. You can close this one out. |
| Comment by Michael Henson [ 12/Dec/12 ] |
|
Sure. We'll start the upgrade process within the next week. I'll follow back up after that process has been completed. |
| Comment by Tad Marshall [ 12/Dec/12 ] |
|
Hi Michael, This sounds a bit like Can you try version 2.2.2 and let us know if the problem goes away? Thanks! Tad |