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

Updating pre-existing numeric fields (intermittently) causes documents to be moved?

    • Type: Icon: Question Question
    • Resolution: Done
    • Priority: Icon: Minor - P4 Minor - P4
    • None
    • Affects Version/s: 2.2.3
    • Component/s: Write Ops
    • None
    • Environment:
      Centos 5.5/6.3, driver 2.7.3

      Originally posted here: https://groups.google.com/forum/?hl=en&fromgroups=#!topic/mongodb-user/T-NpDM6G0aM

      Sun Feb 17 04:11:31 [conn218] update doc_metadata.metadata query:

      { entities.index: "philip morris/company", communityId: ObjectId('4c927585d591d31d7b37097a')) }

      update: { $set:

      { entities.$.totalfrequency: 117, entities.$.doccount: 72 }

      } nscanned:107 nmoved:55 nupdated:72 numYields: 32 locks(micros) w:59851387 30783ms

      I'm trying to understand why nmoved>0 when my objects are all pre-populated as numeric (longs, via the Java driver)

      The thread includes some relevant gists:
      https://gist.github.com/Alex-Ikanow/4979336 - collection stats
      https://gist.github.com/Alex-Ikanow/4979375 - example object

      One thing I noticed in the example object is that some of the numbers are wrapped in NumberLong and some aren't - what determines this?

            Assignee:
            Unassigned Unassigned
            Reporter:
            apiggott@ikanow.com Alex Piggott
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

              Created:
              Updated:
              Resolved: