ask sth about mongodb rollback limitation

[超 王]

why have this limitation? is it will be improve ? ^_^

Rollback Limitations

MongoDB will not rollback more than 300MB of data. In this situation,
the rollback will halt with the log message: [replica set sync]
replSet syncThread: 13410 replSet too much data to roll back

To recover data from the member that has failed to rollback, you will
need to manually intervene. If you do not care about this data, remove
the data directory and fully resync (or restore from a backup) to
resume normal operation.

[A. Jesse Jiryu Davis]

A large rollback file indicates a prior problem with your replica set: your secondaries were very far behind the primary when the primary crashed. The primary stores in the rollback file the operations that hadn't been replicated before it crashed. We limit the size of the rollback file because a large rollback indicates that you must do manual intervention to bring your cluster into a consistent state. In general, you should ensure you have sufficient hardware to keep your replica set synced at all times. If your primary has more than 300MB of unsynced data at any time, the proper fix is to upgrade your hardware or your network so that replication is able to stay in sync, rather than raising the cap on rollback size.