[SERVER-61151] batch->getResult().getStatus() == ErrorCodes::TimeseriesBucketCleared Created: 31/Oct/21  Updated: 14/Dec/21  Resolved: 14/Dec/21

Status: Closed
Project: Core Server
Component/s: None
Affects Version/s: None
Fix Version/s: None

Type: Bug Priority: Major - P3
Reporter: hung hoang Assignee: Dan Larkin-York
Resolution: Duplicate Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Duplicate
duplicates SERVER-58464 Invariant failure during time-series ... Closed
duplicates SERVER-61194 Prevent time-series bucket OID reuse ... Closed
Operating System: ALL
Sprint: Execution Team 2021-12-27
Participants:

 Description   

Server cashes with this error

{"t":{"$date":"2021-10-30T16:40:21.605+07:00"},"s":"F",  "c":"-",        "id":23081,   "ctx":"conn54","msg":"Invariant failure","attr":{"expr":"batch->getResult().getStatus() == ErrorCodes::TimeseriesBucketCleared","msg":"Got unexpected error (DuplicateKey{ keyPattern: { _id: 1 }, keyValue: { _id: ObjectId('617c60d0980af88b77a3179b') } }: E11000 duplicate key error collection: adstats.system.buckets.AdStatsViewTimeSeries dup key: { _id: ObjectId('617c60d0980af88b77a3179b') }) preparing time-series bucket to be committed for adstats.AdStatsViewTimeSeries:....



 Comments   
Comment by Dan Larkin-York [ 14/Dec/21 ]

It looks like this duplicates two different issues we have fixed in versions 5.0.3 and 5.0.6 respectively. If the issue persists in a server >= 5.0.6, please feel free to re-open this ticket or file a new one.

Comment by Edwin Zhou [ 16/Nov/21 ]

Hi hunghoang@chotot.vn,

We still need additional information to diagnose the problem. If this is still an issue for you, would you please attach logs from 2021-10-30 or which cover a repeat incident?

Best,
Edwin

Comment by Edwin Zhou [ 03/Nov/21 ]

Hi hunghoang@chotot.vn,

Thanks for reporting this issue. Can you let us know of the steps you took leading up to this issue? Is this reproducible in the same steps you provided in SERVER-60959?

We also suspect this may be related to corruption issues that we saw in SERVER-58936 which affects 5.0.0 and 5.0.1. Did you previously work on this time series collection on those affected versions prior to using 5.0.3?

Would you please archive (tar or zip) the mongod.log files and the $dbpath/diagnostic.data directory (the contents are described here) and upload them to this support uploader location?

Files uploaded to this portal are visible only to MongoDB employees and are routinely deleted after some time.

Best,
Edwin

Generated at Thu Feb 08 05:51:41 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.