-
Type:
Bug
-
Resolution: Done
-
Priority:
Major - P3
-
None
-
Affects Version/s: 2.2.3
-
Component/s: Stability
-
Labels:
-
Environment:Unix Distribution: CentOS release 5.8 (Final),
Driver: mongo-java-driver:2.9.1
Build: Compiled from source, with this command line:
# scons install -j 9 --64 --ssl --prefix=/tmp/mongodb-linux-2.2.3-x86_64
OpenSSL version: 0.9.8e-22.el5_8.4
Deployment: one primary instance, one secondary, one arbiter.
build info: Linux 12.servername.com 2.6.18-194.3.1.el5.028stab069.6 #1 SMP Tue Aug 10 21:28:51 GMT 2010 x86_64 BOOST_LIB_VERSION=1_49Unix Distribution: CentOS release 5.8 (Final), Driver: mongo-java-driver:2.9.1 Build: Compiled from source, with this command line: # scons install -j 9 --64 --ssl --prefix=/tmp/mongodb-linux-2.2.3-x86_64 OpenSSL version: 0.9.8e-22.el5_8.4 Deployment: one primary instance, one secondary, one arbiter. build info: Linux 12.servername.com 2.6.18-194.3.1.el5.028stab069.6 #1 SMP Tue Aug 10 21:28:51 GMT 2010 x86_64 BOOST_LIB_VERSION=1_49
-
Linux
-
We recently upgraded Mongo from 2.2.2 to 2.2.3. After a couple days of running, the primary couldn't be contacted by the arbiter and the secondary was elected to take over... however, at that point, MongoDB just stopped responding and put tons of errors in the log.
(See attachments for the logs)
The primary has these types of errors:
problem detected during query over (DBNAME).(COLLECTION_NAME) :
{ $err: "not master and slaveOk=false", code: 13435 }[rsMgr] replSet can't see a majority, will not try to elect self
recv(): message len XXX is too largeXX
Assertion: 16141:cannot translate opcode 26975
... but see the log for more details.
The Java application server running the same box as the primary MongoDB instance (o16.servername.com) uses ReadPreference.primaryPreferred() when it does queries.
The Java application server running the same box as the secondary MongoDB instance (o15.servername.com) uses ReadPreference.nearest() when it does queries, since it's physically across the country from the primary.
P.S. after this happened, I updated my Java driver to mongo-java-driver:2.10.1 and am considering rebuilding using the latest openssl build (0.9.8e-26.el5_9.1).