Account Options

  1. Sign in
The old Google Groups will be going away soon, but your browser is incompatible with the new version.
Google Groups Home
« Groups Home
Message from discussion warnings in log after master failover
The group you are posting to is a Usenet group. Messages posted to this group will make your email address visible to anyone on the Internet.
Your reply message has not been sent.
Your post was successful
 
From:
To:
Cc:
Followup To:
Add Cc | Add Followup-to | Edit Subject
Subject:
Validation:
For verification purposes please type the characters you see in the picture below or the numbers you hear by clicking the accessibility icon. Listen and type the numbers you hear
 
Jason Rassi  
View profile  
 More options Sep 24 2012, 10:49 am
From: Jason Rassi <ra...@10gen.com>
Date: Mon, 24 Sep 2012 07:49:57 -0700 (PDT)
Local: Mon, Sep 24 2012 10:49 am
Subject: Re: warnings in log after master failover

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 !


 
You must Sign in before you can post messages.
To post a message you must first join this group.
Please update your nickname on the subscription settings page before posting.
You do not have the permission required to post.