-
Type: New Feature
-
Resolution: Done
-
Priority: Blocker - P1
-
Affects Version/s: None
-
Component/s: mongoreplay
-
None
-
1
-
Platforms 2017-01-23, Platforms 2017-03-06
-
v3.4
Use cases:
We are using mongoreplay to replay data in sys-perf. The data is collected against one shard, but we need replay it against a non-shard replset (to reduce test complexity). Shard meta data failed all writes. Would like to have a way to let mongoreply ignore shard meta data.
Example:
2/17 17:34:17.679 (Connection: 9:83898371) +152µs op_command insert buildlogs Request:{"command_args":{"documents":{"_id":{"$oid":"5804f9219041307e0d06cc46"},"build_id":"f4e1c4e166ae1b1d5165fc069df0d32c","build_name":"MCI_enterprise-rhel-62-64-bit_job2 #4442...0000000000000"},"writeConcern":{"getLastError":1}},"input_docs":[],"metadata":{"configsvr":{"opTime":{"t":{"$numberLong":"9"},"ts":{"$timestamp":{"t":1476720928,"i":2}}}}}} Response:{"command_reply":{"code":193,"codeName":"NoShardingEnabled","errmsg":"Cannot accept sharding commands if not started with --shardsvr","ok":0.0},"metadata":{},"output_docs":null}
- is duplicated by
-
TOOLS-1708 allow mongoreplay to filter out shardVersion from commands when doing playback against a cluster without sharding
- Closed