slave '' is not initialized or invalid - NoSQL Databases

The old Google Groups will be going away soon, but your browser is incompatible with the new version.
Message from discussion slave '' is not initialized or invalid
Received-SPF: pass (google.com: domain of the.mindstorm.mailinglist+caf_=nosql-databases=googlegroups....@gmail.com designates 209.85.215.173 as permitted sender) client-ip=209.85.215.173;
Received-SPF: pass (google.com: domain of mongodb-user+bncCNzm5pKBCBDh5dn2BBoE8aZIPw@googlegroups.com designates 10.236.161.165 as permitted sender) client-ip=10.236.161.165;
Received-SPF: pass (google.com: domain of dchenbec...@gmail.com designates 209.85.216.56 as permitted sender) client-ip=209.85.216.56;
Date: Wed, 30 Nov 2011 10:16:00 -0800 (PST)
From: Derek Chen-Becker <dchenbec...@gmail.com>
Reply-To: mongodb-user@googlegroups.com
To: mongodb-user@googlegroups.com
Message-ID: <16546394.869.1322676960708.JavaMail.geo-discussion-forums@vbwb6>
In-Reply-To: <056ac208-8a6d-4b86-9258-0c1704d44...@u6g2000vbg.googlegroups.com>
References: <32236370.177.1322513750294.JavaMail.geo-discussion-forums@yqmm19> <29c2bbb0-3566-4633-8832-9a3adaac9...@o37g2000prn.googlegroups.com>
 <056ac208-8a6d-4b86-9258-0c1704d44...@u6g2000vbg.googlegroups.com>
Subject: [mongodb-user] Re: slave '' is not initialized or invalid
MIME-Version: 1.0
Precedence: list
Mailing-list: list mongodb-user@googlegroups.com; contact mongodb-user+owners@googlegroups.com
Sender: mongodb-user@googlegroups.com
Content-Type: multipart/alternative; 
	boundary="----=_Part_868_28933621.1322676960706"

------=_Part_868_28933621.1322676960706
Content-Type: text/plain; charset=ISO-8859-1

Well, this is looking very serious. I ended up having to restart all three 
config servers as well as mongos processes on all app servers to get things 
to the point where the app servers would all report queries consistently. 
Further investigation shows that during the period between where one of our 
shard servers (the primary for its replset) started reporting

Assertion: 10422:write with bad shard config and no server id!

and when I restarted configs/mongos, we are definitely missing data and 
lots of it. Fortunately, we have raw data sent to a completely separate, 
non-sharded replset, so we can reconstruct, but it's going to take days to 
do that with no guarantee that this won't happen again. What can we do to 
help diagnose the issues leading up to this state and prevent it from 
happening in the first place. FYI, everything in the system is Mongo 2.0.1.

Derek

-- 
You received this message because you are subscribed to the Google Groups "mongodb-user" group.
To view this discussion on the web visit https://groups.google.com/d/msg/mongodb-user/-/upajgYqL_QMJ.
To post to this group, send email to mongodb-user@googlegroups.com.
To unsubscribe from this group, send email to mongodb-user+unsubscribe@googlegroups.com.
For more options, visit this group at http://groups.google.com/group/mongodb-user?hl=en.


------=_Part_868_28933621.1322676960706
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

Well, this is looking very serious. I ended up having to restart all three =
config servers as well as mongos processes on all app servers to get things=
 to the point where the app servers would all report queries consistently. =
Further investigation shows that during the period between where one of our=
 shard servers (the primary for its replset) started reporting<div><br></di=
v><div>Assertion: 10422:write with bad shard config and no server id!<br></=
div><div><br></div><div>and when I restarted configs/mongos, we are definit=
ely missing data and lots of it. Fortunately, we have raw data sent to a co=
mpletely separate, non-sharded replset, so we can reconstruct, but it's goi=
ng to take days to do that with no guarantee that this won't happen again. =
What can we do to help diagnose the issues leading up to this state and pre=
vent it from happening in the first place. FYI, everything in the system is=
 Mongo 2.0.1.</div><div><br></div><div>Derek</div>

<p></p>

-- <br />
You received this message because you are subscribed to the Google Groups "=
mongodb-user" group.<br />
To view this discussion on the web visit <a href=3D"https://groups.google.c=
om/d/msg/mongodb-user/-/upajgYqL_QMJ">https://groups.google.com/d/msg/mongo=
db-user/-/upajgYqL_QMJ</a>.<br />=20
To post to this group, send email to mongodb-user@googlegroups.com.<br />
To unsubscribe from this group, send email to mongodb-user+unsubscribe@goog=
legroups.com.<br />

For more options, visit this group at http://groups.google.com/group/mongod=
b-user?hl=3Den.<br />



------=_Part_868_28933621.1322676960706--
Create a group - Google Groups - Google Home - Terms of Service - Privacy Policy
Account Options
