Re: warnings in log after master failover
35 views
Skip to first unread message
Message has been deleted
Jason Rassi
Sep 24, 2012, 10:49:57 AM9/24/12
to mongod...@googlegroups.com
The warning is harmless.
On Monday, September 24, 2012 9:11:27 AM UTC-4, gowabash wrote:
We have 3 servers in out replica set (a,b,c). a is normally the master. This weekend I needed to perform compaction on a, so I switched over primary to b and performed our normal compaction. On completion, I switched primary back to a. Before the switchover occurred, there were a bunch of warnings in the log file of the related to cursor loc null. Below is a sample. The database switched back to primary and appears to be running smoothly, but I want to make sure that the warning / error is not something I need to worry about. We have multiple repica sets and this message appeared in more than one of the logs after switchover.Mon Sep 24 11:23:09 [conn26580] DB_NAME.COLLECTION_NAME warning: cursor loc null does not match byLoc position 1c:70a4bb5c !
Jason Rassi
Sep 26, 2012, 12:28:02 PM9/26/12
to mongodb-user
The warning indicates there were active cursors pointing to data that
was moved during compaction. These cursors were cleaned up by the
compaction code.
On Sep 24, 2:36 pm, gowabash <mbr...@igodigital.com> wrote:
> Any context behind that comment.
>
> Can you explain why the warning is there and what it means?
was moved during compaction. These cursors were cleaned up by the
compaction code.
On Sep 24, 2:36 pm, gowabash <mbr...@igodigital.com> wrote:
> Any context behind that comment.
>
> Can you explain why the warning is there and what it means?
Reply all
Reply to author
Forward
0 new messages