Uploaded image for project: 'Core Server'
  1. Core Server
  2. SERVER-3767

Keep Indexes in Memory on Secondary Nodes

    XMLWordPrintableJSON

Details

    • Replication

    Description

      Replica sets provide great automatic failover and redundancy, but the failover in any relatively high traffic database is almost useless since the secondaries don't seem to keep indexes or recently queried data in memory. We've solved this in the interim by writing a script with slaveok to query in the indexes and "warm the cache." I consider the fact this is necessary is ridiculous in a production server.

      Could MongoDB secondaries please keep hot-data in memory so that in the case of a failover, page faults don't skyrocket. At the very least, indexes should always be kept in RAM.

      Attachments

        Activity

          People

            backlog-server-repl Backlog - Replication Team
            mitchellh Mitchell Hashimoto
            Votes:
            4 Vote for this issue
            Watchers:
            10 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: