Loading...

XML

Word

Printable

JSON

Type: Bug
Resolution: Done
Priority: Major - P3
Fix Version/s: 2.2.1
Affects Version/s: 2.2.0
Component/s: Replication
Labels:
None

Operating System:
ALL
Confidence Status:
None
Work Order:
3
CAR Domain/s:
None

Aha! Reference:
None
Tracking Level:
None
Risk Status:
None
Exec Notes:
None
Goal Name(s):
None
Goal Link:
None

A node that is initial syncing is in state STARTUP2. If all goes well, it transitions to state SECONDARY, then RECOVERING, then back to SECONDARY. The first SECONDARY state is a mistake; it should go straight to RECOVERING.

is related to

SERVER-7186 Batched oplog application increases frequency of idempotency violations

Closed

related to

SERVER-3251 Overflowed replica set members briefly re-initialize as SECONDARY

Closed

Assignee:: Kristina Chodorow (Inactive)
Reporter:: Eric Milkie
Participants:: auto, Eric Milkie, Kristina Chodorow
Votes:: 0 Vote for this issue
Watchers:: 5 Start watching this issue

Created:: Sep 26 2012 06:46:07 PM UTC
Updated:: Jul 11 2016 05:57:41 PM UTC
Resolved:: Oct 10 2012 06:57:10 PM UTC

Details

Description

Attachments

Issue Links

Forms

Activity

People

Dates