validate command returns valid false but no errors
12 views
Skip to first unread message
Mac Gillon
Feb 9, 2012, 6:04:33 PM2/9/12
to mongodb-user
Replica set with 4 members, one hidden. Master is currently 1.8.4, no
journal. All secondaries are 2.0.2 with journal. I'm still going back
through logs looking for interesting entries but nothing yet. Clear
that no errors are reported in logs when the validate was run on the
replica collections.
What condition would cause validate to return valid false but not have
any errors?
journal. All secondaries are 2.0.2 with journal. I'm still going back
through logs looking for interesting entries but nothing yet. Clear
that no errors are reported in logs when the validate was run on the
replica collections.
What condition would cause validate to return valid false but not have
any errors?
Mac Gillon
Feb 9, 2012, 10:18:40 PM2/9/12
to mongodb-user
This node was updating from 1.8.1 to 2.0.2. So the Master is 1.8.1 if
that makes a difference.
that makes a difference.
Scott Hernandez
Feb 9, 2012, 10:32:09 PM2/9/12
to mongod...@googlegroups.com
Please provide the full output of validate(true) from one of the 2.0.2
instances.
instances.
> --
> You received this message because you are subscribed to the Google Groups "mongodb-user" group.
> To post to this group, send email to mongod...@googlegroups.com.
> To unsubscribe from this group, send email to mongodb-user...@googlegroups.com.
> For more options, visit this group at http://groups.google.com/group/mongodb-user?hl=en.
>
Mac Gillon
Feb 10, 2012, 1:17:26 PM2/10/12
to mongodb-user
Turns out the cause is pretty simple. The 1.8.1 shell is getting used
to issue the command. Because one node member is 1.8.1, the path used
to find the mongo shell didn't get updated yet. So using the true
option still returns the short output and valid false but no errors.
Using the 2.0.2 version of the shell valid is true and no errors.
to issue the command. Because one node member is 1.8.1, the path used
to find the mongo shell didn't get updated yet. So using the true
option still returns the short output and valid false but no errors.
Using the 2.0.2 version of the shell valid is true and no errors.
Scott Hernandez
Feb 10, 2012, 3:26:00 PM2/10/12
to mongod...@googlegroups.com
Can you please post the output and db.serverStatus() also? Posting to
gist/pastebin/etc. would be helpful.
gist/pastebin/etc. would be helpful.
Mac Gillon
Feb 10, 2012, 7:05:29 PM2/10/12
to mongodb-user
Sure.
http://pastebin.com/q5qrJ6RL
On Feb 10, 12:26 pm, Scott Hernandez <scotthernan...@gmail.com> wrote:
> Can you please post the output and db.serverStatus() also? Posting to
> gist/pastebin/etc. would be helpful.
>
>
>
>
>
>
>
> On Fri, Feb 10, 2012 at 1:17 PM, Mac Gillon <wmgil...@pacbell.net> wrote:
> > Turns out the cause is pretty simple. The 1.8.1 shell is getting used
> > to issue the command. Because one node member is 1.8.1, the path used
> > to find the mongo shell didn't get updated yet. So using the true
> > option still returns the short output and valid false but no errors.
> > Using the 2.0.2 version of the shell valid is true and no errors.
>
> > Scott Hernandez wrote:
> >> Please provide the full output of validate(true) from one of the 2.0.2
> >> instances.
>
http://pastebin.com/q5qrJ6RL
On Feb 10, 12:26 pm, Scott Hernandez <scotthernan...@gmail.com> wrote:
> Can you please post the output and db.serverStatus() also? Posting to
> gist/pastebin/etc. would be helpful.
>
>
>
>
>
>
>
> On Fri, Feb 10, 2012 at 1:17 PM, Mac Gillon <wmgil...@pacbell.net> wrote:
> > Turns out the cause is pretty simple. The 1.8.1 shell is getting used
> > to issue the command. Because one node member is 1.8.1, the path used
> > to find the mongo shell didn't get updated yet. So using the true
> > option still returns the short output and valid false but no errors.
> > Using the 2.0.2 version of the shell valid is true and no errors.
>
> > Scott Hernandez wrote:
> >> Please provide the full output of validate(true) from one of the 2.0.2
> >> instances.
>
> >> On Thu, Feb 9, 2012 at 10:18 PM, Mac Gillon <wmgil...@pacbell.net> wrote:
> >> > This node was updating from 1.8.1 to 2.0.2. So the Master is 1.8.1 if
> >> > that makes a difference.
>
> >> > On Feb 9, 3:04 pm, Mac Gillon <wmgil...@pacbell.net> wrote:
> >> >> Replica set with 4 members, one hidden. Master is currently 1.8.4, no
> >> >> journal. All secondaries are 2.0.2 with journal. I'm still going back
> >> >> through logs looking for interesting entries but nothing yet. Clear
> >> >> that no errors are reported in logs when the validate was run on the
> >> >> replica collections.
>
> >> >> What condition would cause validate to return valid false but not have
> >> >> any errors?
>
> >> > --
> >> > You received this message because you are subscribed to the Google Groups "mongodb-user" group.
> >> > To post to this group, send email to mongod...@googlegroups.com.
> >> > To unsubscribe from this group, send email to mongodb-user...@googlegroups.com.
> >> > For more options, visit this group athttp://groups.google.com/group/mongodb-user?hl=en.
> >> > This node was updating from 1.8.1 to 2.0.2. So the Master is 1.8.1 if
> >> > that makes a difference.
>
> >> > On Feb 9, 3:04 pm, Mac Gillon <wmgil...@pacbell.net> wrote:
> >> >> Replica set with 4 members, one hidden. Master is currently 1.8.4, no
> >> >> journal. All secondaries are 2.0.2 with journal. I'm still going back
> >> >> through logs looking for interesting entries but nothing yet. Clear
> >> >> that no errors are reported in logs when the validate was run on the
> >> >> replica collections.
>
> >> >> What condition would cause validate to return valid false but not have
> >> >> any errors?
>
> >> > --
> >> > You received this message because you are subscribed to the Google Groups "mongodb-user" group.
> >> > To post to this group, send email to mongod...@googlegroups.com.
> >> > To unsubscribe from this group, send email to mongodb-user...@googlegroups.com.
Eliot Horowitz
Feb 11, 2012, 10:29:51 PM2/11/12
to mongod...@googlegroups.com
This has ok and valid as true.
Seems ok?
Seems ok?
Mac Gillon
Feb 12, 2012, 12:36:57 PM2/12/12
to mongodb-user
Looks like it. I think the only issue is our tools using the 1.8.1
shell to issue commands to a 2.0.2 server. Once the node upgrade is
complete, it should not be an issue.
shell to issue commands to a 2.0.2 server. Once the node upgrade is
complete, it should not be an issue.
Reply all
Reply to author
Forward
0 new messages