Comment 2 for bug 1727679

That query moves the TXN from prepared (all docs should be ready to apply)
to preparing (create what needs to exist).

If we caught it earlier we probably wouldn't need the mgopurge

John
=:->

On Oct 27, 2017 11:21, "Junien Fridrick" <email address hidden> wrote:

> This got worked around by applying this change :
> db.txns.update({_id: ObjectId("59ef3f595f5ce87b42d1e774")}, {$unset:
> {"n": 1}, $set: {"s": 1}})
>
> And the, running a full mgopurge (with controllers stopped) to handle
> the big txn-queues.
>
> --
> You received this bug notification because you are subscribed to juju.
> Matching subscriptions: juju bugs
> https://bugs.launchpad.net/bugs/1727679
>
> Title:
> mgo-txn-resumer cannot resume transaction because missing document
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/juju/+bug/1727679/+subscriptions
>