[SERVER-48061] A streaming isMaster that fails via failCommand still includes the OP_MSG moreToCome flag Created: 08/May/20  Updated: 08/Jan/24  Resolved: 08/Oct/20

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

Type: Bug Priority: Major - P3
Reporter: Shane Harvey Assignee: Amirsaman Memaripour
Resolution: Cannot Reproduce Votes: 0
Labels: servicearch-wfbf-day
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Backports
Operating System: ALL
Backport Requested:
v4.4
Sprint: Service arch 2020-10-19
Participants:

 Description   

When the failCommand failpoint is configured to fail a streaming isMaster, the server's ok:0 response mistakenly includes the OP_MSG moreToCome flag. Can we also confirm that the server will never set moreToCome on a ok:0 response in practice?

Note that wether the server includes moreToCome or not on a ok:0 response shouldn't matter because the client will close the connection after reading the ok:0 response (See SDAM's network or command error during server check).

CC: jeff.yemin



 Comments   
Comment by Shane Harvey [ 08/Oct/20 ]

I also don't see this behavior on 4.4.0 or 4.4.1. Feel free to resolve.

Generated at Thu Feb 08 05:16:01 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.