|
Hi fengjing@vastdata.com.cn,
The best approach to SERVER-45119 at this point is to upgrade to 4.2.6 to avoid the issue altogether. That is what we recommend.
Beyond that, if it is truly necessary for you to explore this, we'd like to encourage you to start by asking our community for help by posting on the MongoDB Developer Community Forums.
There, you can get clarifications on how MongoDB works and suggestions for how to approach particular problems. If you post there explaining some context about why you need to reproduce SERVER-45119, they should be able to provide insight.
If the discussion there leads you to suspect a bug in the MongoDB server, or an inaccuracy in what we've documented at SERVER-45119, then we'd be able to address this here in the SERVER project (which is for reporting bugs and feature suggestions for the MongoDB server).
Hopefully this helps,
Eric
|