The analyzeShardKey command by default uses readConcern: "secondaryPreferred". Currently, the analyzeShardKey tests all don't specify writeConcern so they just use the default w: "majority". This covers the two nodes that each shard in those tests have. However, SPM-3489 changed w: majority to only wait for the opTime of that write to be persisted. To wait for the opTime of that write to be applied, w: <n> must be used. For this reason, all of the analyzeShardKey tests should use w: all for every write that they do.