I plan to use the MongoDB Atlas Live-Migration to move a local ReplSet to Atlas. There should be no downtime. So the Live-Migration comes in handy. But I have only a small line of 100MB/s available which is used by ~30% constantly. I fear when I live-migrate that I will have a major impact on current processes which need bandwidth. The DB is > 500GB so even when would use 100% of the line this is > 12h
So in case I would impact my current processes for > 12h I would better go for mongorestore, which uses compressed data but this would still be quite a big downtime. This currently not an option. I would like to have the smallest downtime window possible, I do not care how long the Live-Migration takes so even 24h would be ok.
How can I limit the traffic of the MongoDB Live-Migration (monogmirror) to max 50% of my available network bandwidth capacity? I did some investigation with tc and trickle but both seem not to be the correct tools, or I misunderstood how to use them.