mongo3.4 "Cannot truncate a live oplog while replicating:"

Bug #1749078 reported by John A Meinel on 2018-02-13
This bug affects 1 person
Affects Status Importance Assigned to Milestone
John A Meinel

Bug Description

Part of our mongo 3.4 compatibility. Part of our test suite cleans up the databases, and seems to be trying to truncate the oplog. Which apparently was ok in Mongo 3.2 but is not ok in Mongo 3.4.

You can see this failure by having mongodb 3.4 available, and doing something like:

export JUJU_MONGOD=$PATH/TO/3.4/bin/mongod
go test --check.v --check.f debugLogDb

(one of the first tests that seems to trigger this, I need to investigate why.)

John A Meinel (jameinel) on 2018-02-13
Changed in juju:
assignee: Eric Claude Jones (ecjones) → John A Meinel (jameinel)
John A Meinel (jameinel) on 2018-02-13
Changed in juju:
milestone: none → 2.4-beta1
Anastasia (anastasia-macmood) wrote :

Forward port to develop, 2.4:

Changed in juju:
status: Triaged → In Progress
assignee: John A Meinel (jameinel) → Anastasia (anastasia-macmood)
Changed in juju:
status: In Progress → Fix Committed
Changed in juju:
status: Fix Committed → Fix Released
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers