Currently the update and delete commands are disabled in jstests/sharding/read_write_concern_defaults_application.js. This is because SERVER-23266 means that the bulk commands aren't profiled. Using logging instead of profiling isn't possible because when sharded the log lines are much longer than the RamLog's maximum log line length.

Possible solutions include:

1. Scope, design, and implement SERVER-23266.
2. Implement the functionality of SERVER-23266 on this ticket, but gated behind a failpoint (to avoid the effort of scoping/designing a user-facing change).
3. Increase the RamLog maximum log line length (SERVER-45694).