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

Indexes don't always get carried over to all shards

    XMLWordPrintableJSON

Details

    • Icon: Bug Bug
    • Resolution: Cannot Reproduce
    • Icon: Major - P3 Major - P3
    • None
    • 1.6.2
    • None
    • None
    • Centos 64 bit, Amazon EC2
    • Linux

    Description

      In a sharded configuration, we have noticed that indexes don't always get carried over to all the shards. This seems to happen more frequently when we do a remove on a collection that has chunks on multiple shards and then start filling up the collection again. When the chunk size gets larger than what the primary shard can handle, the data gets sent to the secondary shard but it doesn't seem to have the index.

      Workaround is to manually build the indexes on all shards upon discovery excessive CPU usage.

      Attachments

        Activity

          People

            Unassigned Unassigned
            giri.iyengar Giri Iyengar
            Votes:
            0 Vote for this issue
            Watchers:
            0 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: