Details
-
Bug
-
Status: Closed
-
Major - P3
-
Resolution: Duplicate
-
2.5.4
-
None
-
None
-
ALL
Description
I have a version 1 FTS index on 2.4.8. I then added new 2.5.4 replica set member. The initial sync fails with FTS index creation errors.
The same happens if I upgrade the primary to 2.5.4 with `--upgrade` and proceed to add a new 2.5.4 member.
Index in 2.4.8:
> db.xyz.getIndexSpecs()
|
[
|
{
|
"v" : 1,
|
"key" : {
|
"_id" : 1
|
},
|
"ns" : "test.xyz",
|
"name" : "_id_"
|
},
|
{
|
"v" : 1,
|
"key" : {
|
"_fts" : "text",
|
"_ftsx" : 1
|
},
|
"ns" : "test.xyz",
|
"name" : "field_text",
|
"weights" : {
|
"field" : 1
|
},
|
"default_language" : "english",
|
"language_override" : "language",
|
"textIndexVersion" : 1
|
}
|
]
|
>
|
Added a 2.5.4 member into the replica set:
2014-01-21T10:01:20.786-0500 [rsSync] build index on: test.xyz properties: { v: 1, key: { _id: 1 }, name: "_id_", ns: "test.xyz" }
|
2014-01-21T10:01:20.787-0500 [rsSync] build index done. scanned 0 total records. 0 secs
|
2014-01-21T10:01:20.794-0500 [rsSync] replSet initial sync data copy, starting syncup
|
2014-01-21T10:01:20.794-0500 [rsSync] oplog sync 1 of 3
|
2014-01-21T10:01:20.794-0500 [rsSync] replication oplog stream went back in time. previous timestamp: 52de8a93:1 newest timestamp: 52de8a93:1. attempting to sync directly from primary.
|
2014-01-21T10:01:20.794-0500 [rsSync] oplog sync 2 of 3
|
2014-01-21T10:01:20.794-0500 [rsSync] replSet initial sync building indexes
|
2014-01-21T10:01:20.794-0500 [rsSync] replSet initial sync cloning indexes for : test
|
2014-01-21T10:01:20.795-0500 [rsSync] ERROR: error: exception cloning object in test.system.indexes bad textIndexVersion: 1 obj:{ key: { _fts: "text", _ftsx: 1 }, ns: "test.xyz", name: "field_text", weights: { field: 1 }, default_language: "english", language_override: "language", textIndexVersion: 1 }
|
2014-01-21T10:01:20.795-0500 [rsSync] replSet initial sync exception: 16730 bad textIndexVersion: 1 0 attempts remaining
|
2014-01-21T10:01:21.050-0500 [rsBackgroundSync] replSet syncing to: boxster:27555 by request
|
2014-01-21T10:01:21.051-0500 [rsBackgroundSync] upstream updater is unsupported on this version
|
^C2014-01-21T10:01:31.762-0500 [signalProcessingThread] got signal 2 (Interrupt), will terminate after current cmd ends
|
2014-01-21T10:01:31.762-0500 [signalProcessingThread] now exiting
|
dbexit: 2014-01-21T10:01:31.762-0500 [signalProcessingThread] shutdown: going to close listening sockets...
|
2014-01-21T10:01:31.762-0500 [signalProcessingThread] closing listening socket: 7
|
2014-01-21T10:01:31.762-0500 [signalProcessingThread] closing listening socket: 8
|
2014-01-21T10:01:31.762-0500 [signalProcessingThread] removing socket file: /tmp/mongodb-27556.sock
|
2014-01-21T10:01:31.762-0500 [signalProcessingThread] shutdown: going to flush diaglog...
|
2014-01-21T10:01:31.762-0500 [signalProcessingThread] shutdown: going to close sockets...
|
2014-01-21T10:01:31.762-0500 [signalProcessingThread] shutdown: waiting for fs preallocator...
|
2014-01-21T10:01:31.762-0500 [signalProcessingThread] shutdown: lock for final commit...
|
2014-01-21T10:01:31.762-0500 [signalProcessingThread] shutdown: final commit...
|
2014-01-21T10:01:31.762-0500 [conn11] end connection 127.0.0.1:45603 (0 connections now open)
|
2014-01-21T10:01:31.762-0500 [rsBackgroundSync] replSet sync source problem: 10278 dbclient error communicating with server: boxster:27555
|
2014-01-21T10:01:31.776-0500 [signalProcessingThread] shutdown: closing all files...
|
2014-01-21T10:01:31.776-0500 [signalProcessingThread] closeAllFiles() finished
|
2014-01-21T10:01:31.776-0500 [signalProcessingThread] journalCleanup...
|
2014-01-21T10:01:31.776-0500 [signalProcessingThread] removeJournalFiles
|
2014-01-21T10:01:31.777-0500 [signalProcessingThread] shutdown: removing fs lock...
|
Attachments
Issue Links
- duplicates
-
SERVER-10906 Support for legacy text index format textIndexVersion:1
-
- Closed
-