Home/ Questions/Q 8829439
In Process

The Archive Base Latest Questions

Editorial Team
  • 0
Asked: 2026-06-14T07:50:03+00:00

I’m using MongoDB as denormalized storage which state is completely rebuilds every 15 minutes.

  • 0

I’m using MongoDB as denormalized storage which state is completely rebuilds every 15 minutes. Rebuild process takes many time and resources. Is there any way to organize table “hotswap” process, to avoid db locks and perfomance down during rebuild. Lets suppose that I’m building new version of DB on another server, make all needed indexes etc, then copy db file on main server and “swap” tables so users getting refreshed data immediately after swapping?

Share

Leave an answer

You must login to add an answer.

Need An Account,

1 Answer

  1. Editorial Team

    MongoDB uses pre-allocated data files so if you are frequently dropping and rebuilding databases you’re probably going to be churning the disk. The data files are opened using memory-mapped I/O and there is no provision to “hot swap” or rename databases.

    The space from deleted collections can be re-used, so a better approach might be to generate temporary collection names based on your 15 minute intervals so your program can predictably “swap” to the next collection and older collections can be dropped.

    If you are using MongoDB 2.2 or newer, you have some additional options:

    • use the new usePowerOf2Sizes collection option to improve re-use of deleted space

    • use the Time-To-Live (TTL) function to automatically expire documents after 15 minutes.

    • 0