replica set sync

52 views
Skip to first unread message

tetlika

unread,
Feb 24, 2011, 5:45:49 AM2/24/11
to mongodb-user
Hi!

while executing db.currentOp() on primary in replica set, i see next:


{
"opid" : 61329,
"active" : true,
"lockType" : "read",
"waitingForLock" : false,
"secs_running" : 5967,
"op" : "none",
"ns" : "local.replset.minvalid",
"query" : {

},
"client" : "(NONE)",
"desc" : "replica set sync"
},


from the point of view the app is working ok, replica set status is
ok, all looks ok - but this operation is still pending, is that ok?

P.S.

we just upgraded our replica set from 1.6.5 to 1.7.6

Kristina Chodorow

unread,
Feb 24, 2011, 9:08:59 AM2/24/11
to mongod...@googlegroups.com, tetlika
This is a bug, see http://jira.mongodb.org/browse/SERVER-2578.  However, it shouldn't affect anything.  If it really annoys you, you can restart the server and it should disappear.



--
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.


tetlika

unread,
Feb 24, 2011, 9:28:44 AM2/24/11
to mongodb-user
Ok, thanks for reply!

Well, If it does not affect anything, I won't touch it.


On 24 фев, 16:08, Kristina Chodorow <krist...@10gen.com> wrote:
> This is a bug, seehttp://jira.mongodb.org/browse/SERVER-2578.  However, it
> shouldn't affect anything.  If it really annoys you, you can restart the
> server and it should disappear.
>
Reply all
Reply to author
Forward
0 new messages