Loading...

XML

Word

Printable

JSON

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

Operating System:
ALL
Linked BF Score:
0
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

Currently if a getMore fails with an ExceededTimeLimit error, such as if there is no data to return, the fetcher will shutdown, and the fetcher will then look for a new sync source.

We should fix this so that if a getMore in the fetcher fails with this error, we issue a new getMore instead. We need to make sure we get and process the metadata as well. So further work will need to be done to return the metadata with the QueryResponseStatus, and then update the server with that metadata as we do on successful getMores.

depends on

SERVER-24113 OplogFetcher getMore callback QueryResponseStatus should include metadata on error

Closed

related to

SERVER-23222 Replset metadata is not attached to command response on the exception path

Closed

SERVER-25702 add support to OplogFetcher for restarting oplog query

Closed

Assignee:: Judah Schvimer
Reporter:: Judah Schvimer
Participants:: Eric Milkie, Judah Schvimer
Votes:: 0 Vote for this issue
Watchers:: 4 Start watching this issue

Created:: May 06 2016 09:48:57 PM UTC
Updated:: Mar 22 2018 04:42:35 PM UTC
Resolved:: May 23 2016 02:22:32 PM UTC

Details

Description

Attachments

Issue Links

Forms

Activity

People

Dates