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

After re-starting mongod, logs gets filled with messages during IndexRebuild

    • Type: Icon: Bug Bug
    • Resolution: Done
    • Priority: Icon: Major - P3 Major - P3
    • 2.4.0-rc1
    • Affects Version/s: 2.3.2
    • Component/s: Index Maintenance
    • None
    • ALL
    • Hide

      1. Create a text index
      2. During the creation, kill the mongod process
      3. Re-start the mongod process
      4. Observe the messages

      Show
      1. Create a text index 2. During the creation, kill the mongod process 3. Re-start the mongod process 4. Observe the messages

      Problem:
      After a restart of mongod the logs gets filled with the following messages

      5.510 [IndexRebuilder] warning Listener::getElapsedTimeMillis returning 0ms
      Tue Jan 22 22:51:55.864 [IndexRebuilder] warning Listener::getElapsedTimeMillis returning 0ms
      Tue Jan 22 22:51:56.218 [IndexRebuilder] warning Listener::getElapsedTimeMillis returning 0ms
      Tue Jan 22 22:51:56.571 [IndexRebuilder] warning Listener::getElapsedTimeMillis returning 0ms
      Tue Jan 22 22:51:59.743 [IndexRebuilder] warning Listener::getElapsedTimeMillis returning 0ms
      Tue Jan 22 22:52:00.003 [IndexRebuilder] 		Index: (1/3) External Sort Progress: 1143000/21633992	5%
      Tue Jan 22 22:52:00.092 [IndexRebuilder] warning Listener::getElapsedTimeMillis returning 0ms
      Tue Jan 22 22:52:00.419 [IndexRebuilder] warning Listener::getElapsedTimeMillis returning 0ms
      Tue Jan 22 22:52:00.779 [IndexRebuilder] warning Listener::getElapsedTimeMillis returning 0ms
      Tue Jan 22 22:52:01.141 [IndexRebuilder] warning Listener::getElapsedTimeMillis returning 0ms
      Tue Jan 22 22:52:0
      

      Workaround:
      None

            Assignee:
            kristina Kristina Chodorow (Inactive)
            Reporter:
            alvin Alvin Richards (Inactive)
            Votes:
            0 Vote for this issue
            Watchers:
            4 Start watching this issue

              Created:
              Updated:
              Resolved: