Mongo crash beyond 2038 on 64 bit

[choco_lap]

I’m getting the 2038 problem even though I have the 64 bit mongoDb 4.4.13 version installed.
I see the following error message:
“cluster time cannot be advanced beyond its maximum value”

so it seems related to Mongodb replicaset cluster maximum logicalTime => 2038 year max.

Should this error still be happening even though I’m on 64 bit or is there a config I’m missing?

[chris (Chris Dellaway)]

Looks like there are some JIRAs still to shake out with regard to 2038 / 32bit time.

Linked to the JIRA I found when looking at this Wall field question a couple of years back is another related SERVER-18557, this would be a good one to watch.

Wall field in oplog collection

Hi @Tamar_Nirenberg The ts field in the oplog is seconds since epoch and then order of inserts in that second. Wall time is added in https://jira.mongodb.org/browse/SERVER-27769 Change oplog OpTime format to raw 64bit values So it is likely a part of that transition as the seconds since epoch is a 32bit integer that will max out in 2038 Sure I don’t see why not. I still use the ts field at the moment.