Killing process - db.t_my_coll.deleteMany( {"MainDate": /^2019/} )

Ops and Admin
1

Hi,

Environment:
MongoDB Version 4.2.7
No Replica-Set, etc … normal single Instance.

I was try to delete data of a very big table with “db.t_my_coll.deleteMany( {“MainDate”: /^2019/} )” by mongo cmd line at 2020-08-18 11:21. The operation takes to long, so I’ve killed the process 2020-08-19 10:34 with MongoDB Compass UI. I was think that the changes will be rolled back. But they don’t.

if I call db.currentOp(), Mongo shows me that operation:

 {
                        "type" : "op",
                        "host" : "privateXdataXXX:27017",
                        "desc" : "waitForMajority",
                        "active" : true,
                        "currentOpTime" : "2020-08-24T19:17:11.756+0200",
                        "opid" : 2,
                        "op" : "none",
                        "ns" : "",
                        "command" : {

                        },
                        "numYields" : 0,
                        "waitingForLatch" : {
                                "timestamp" : ISODate("2020-08-19T10:34:58.324Z"),
                                "captureName" : "WaitForMaorityService::_mutex"
                        },
                        "locks" : {

                        },
                        "waitingForLock" : false,
                        "lockStats" : {

                        },
                        "waitingForFlowControl" : false,
                        "flowControlStats" : {

                        }
                }

What means this op “waitForMajority” what means “waitingForLatch”. Can’t find good documentation on these topics! Can I start the rollback manually or I have to restore the missing datasets from a backup of DB?

Thanks in advance for competent help!