Why is "stateStr": "ROLLBACK" not completing?

Question

MongoDB

Good afternoon. Please help me with this problem. There is Mongo replication. master 3.0.10 slave 3.0.1 version. Bases weigh 750 GB. Before starting, the databases were copied via rsync. This status has been hanging for over a week.

mongo-master ~ # mongo
MongoDB shell version: 3.0.10
connecting to: test
actr:PRIMARY> rs.status()
{
  "set" : "actr",
  "date" : ISODate("2016-05-04T13:45:03.798Z"),
  "myState" : 1,
  "members" : [
    {
      "_id" : 0,
      "name" : "1.2.3.4:27017",
      "health" : 1,
      "state" : 1,
      "stateStr" : "PRIMARY",
      "uptime" : 1124613,
      "optime" : Timestamp(1462369502, 3),
      "optimeDate" : ISODate("2016-05-04T13:45:02Z"),
      "electionTime" : Timestamp(1461245375, 1),
      "electionDate" : ISODate("2016-04-21T13:29:35Z"),
      "configVersion" : 47573,
      "self" : true
    },
    {
      "_id" : 1,
      "name" : "1.2.3.5:27017",
      "health" : 1,
      "state" : 9,
      "stateStr" : "ROLLBACK",
      "uptime" : 143156,
      "optime" : Timestamp(1461243514, 7),
      "optimeDate" : ISODate("2016-04-21T12:58:34Z"),
      "lastHeartbeat" : ISODate("2016-05-04T13:45:02.126Z"),
      "lastHeartbeatRecv" : ISODate("2016-05-04T13:45:03.306Z"),
      "pingMs" : 0,
      "syncingTo" : "1.2.3.4:27017",
      "configVersion" : 47573
    },
    {
      "_id" : 2,
      "name" : "1.2.3.6:27017",
      "health" : 1,
      "state" : 7,
      "stateStr" : "ARBITER",
      "uptime" : 1123842,
      "lastHeartbeat" : ISODate("2016-05-04T13:45:02.809Z"),
      "lastHeartbeatRecv" : ISODate("2016-05-04T13:45:03.146Z"),
      "pingMs" : 0,
      "configVersion" : 47573
    }
  ],
  "ok" : 1
}

Answer 1

Why is "stateStr": "ROLLBACK" not completing?

Apparently because:
Monga must fill the slave itself, it's not just copying.