[SERVER-11970] While fsyncLock() to secondary stoping write operations also Created: 05/Dec/13  Updated: 06/Dec/13  Resolved: 05/Dec/13

Status: Closed
Project: Core Server
Component/s: Replication
Affects Version/s: 2.4.7
Fix Version/s: None

Type: Bug Priority: Blocker - P1
Reporter: Appnique OMS Assignee: Unassigned
Resolution: Duplicate Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified
Environment:

Unix


Issue Links:
Duplicate
duplicates SERVER-1423 reads often aren't possible while in ... Closed
Operating System: ALL
Participants:

 Comments   
Comment by Appnique OMS [ 06/Dec/13 ]

thanks..

Comment by Scott Hernandez (Inactive) [ 06/Dec/13 ]

SERVER-1423 is still open and requires more work for the improvement needed. When you look at the Status and Resolution on the page you can see it is still in progress and unresolved. I also suggest that you read the related issues since what you expect may not be how things work – reading the documentation is good as well (http://docs.mongodb.org/manual/reference/command/fsync/#dbcmd.fsync). I think what you may be interested in is a read-only mode, which fsyncLock is not designed to do.

Comment by Appnique OMS [ 06/Dec/13 ]

Hi Scott, any comments.....

Comment by Appnique OMS [ 05/Dec/13 ]

Hi Scott,
thanks for reply..
so this is still bug in mongodb?

-Ashraf

Comment by Scott Hernandez (Inactive) [ 05/Dec/13 ]

Duplicate of SERVER-1423 – please follow/vote on that issue.

Comment by Appnique OMS [ 05/Dec/13 ]

Hi,
When i fsyncLock() to secondary ,it was locking read operations also.is this bug in 2.4.7

-Ashraf

Generated at Thu Feb 08 03:27:15 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.