[SERVER-15729] fix startup message when illegal indexes encountered Created: 20/Oct/14  Updated: 11/Jul/16  Resolved: 27/Oct/14

Status: Closed
Project: Core Server
Component/s: Index Maintenance
Affects Version/s: 2.7.6
Fix Version/s: 2.8.0-rc0

Type: Bug Priority: Major - P3
Reporter: Asya Kamsky Assignee: Eric Milkie
Resolution: Done Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Operating System: ALL
Participants:

 Description   

Started mongod with noIndexBuildRetry (because I have some illegal indexes 2.7.x fasserts on):

~/bins/mongodb-osx-x86_64-2.7.6/bin/mongod --noIndexBuildRetry -v
2014-10-20T07:43:17.329-0700 D COMMANDS [DataFileSync] BackgroundJob starting: DataFileSync
2014-10-20T07:43:17.329-0700 D SHARDING shardObjTest passed
2014-10-20T07:43:17.329-0700 D SHARDING isInRangeTest passed
2014-10-20T07:43:17.329-0700 D SHARDING shardKeyTest passed
2014-10-20T07:43:17.329-0700 I -        [initandlisten] MongoDB starting : pid=2212 port=27017 dbpath=/data/db 64-bit host=Asyas-MacBook-Pro.local
2014-10-20T07:43:17.329-0700 I -        [initandlisten]
2014-10-20T07:43:17.329-0700 I -        [initandlisten] ** NOTE: This is a development version (2.7.6) of MongoDB.
2014-10-20T07:43:17.329-0700 I -        [initandlisten] **       Not recommended for production.
2014-10-20T07:43:17.329-0700 I -        [initandlisten]
2014-10-20T07:43:17.329-0700 I -        [initandlisten] db version v2.7.6
2014-10-20T07:43:17.329-0700 I -        [initandlisten] git version: a8828ca2f6d50eb9f183e3bc5d317a7e356083c7
2014-10-20T07:43:17.329-0700 I -        [initandlisten] build info: Darwin mci-osx108-4.build.10gen.cc 12.3.0 Darwin Kernel Version 12.3.0: Sun Jan  6 22:37:10 PST 2013; root:xnu-2050.22.13~1/RELEASE_X86_64 x86_64 BOOST_LIB_VERSION=1_56
2014-10-20T07:43:17.329-0700 I -        [initandlisten] allocator: system
2014-10-20T07:43:17.329-0700 I -        [initandlisten] options: { storage: { indexBuildRetry: false }, systemLog: { verbosity: 1 } }

and still:

2014-10-20T07:43:21.209-0700 D -        [initandlisten] User Assertion: 72:wrong type for 'max' field, expected number, found max: new Date(32503701600000)
2014-10-20T07:43:21.209-0700 E INDEXING [initandlisten] Index rebuilding did not complete: 72 wrong type for 'max' field, expected number, found max: new Date(32503701600000)
2014-10-20T07:43:21.209-0700 I INDEXING [initandlisten] note: restart the server with --noIndexBuildRetry to skip index rebuilds
2014-10-20T07:43:21.209-0700 I -        [initandlisten] Fatal Assertion 18643
2014-10-20T07:43:21.209-0700 I -        [initandlisten]
 
***aborting after fassert() failure
 



 Comments   
Comment by Githook User [ 27/Oct/14 ]

Author:

{u'username': u'milkie', u'name': u'Eric Milkie', u'email': u'milkie@10gen.com'}

Message: SERVER-15729 make index rebuilder error message more clear
Branch: master
https://github.com/mongodb/mongo/commit/52bef37842c1b78e3378a5a931ba8c428aad8e6a

Comment by Eric Milkie [ 20/Oct/14 ]

We should fix the exception message to be more accurate, however.

Comment by Eric Milkie [ 20/Oct/14 ]

Unfortunately, that option won't do what you want. It only prevents the rebuilding of interrupted indexes; the system still always checks all indexes for validity on startup.

Generated at Thu Feb 08 03:38:48 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.