Good suggestion heard at MongoDay yesterday as used in a different (non Drupal) production environment: vary the write safety ("w" factor in getLastError(): fire&forget, safe, cluster ratio safe..) depending on the event criticity.

In our cae, this would likely have to be a setting with a sane default (probably confirmed by master).


fgm’s picture

Version: 7.x-1.x-dev » 8.x-1.x-dev
Issue summary: View changes

Features only go in the current dev version.

fgm’s picture

Version: 8.x-1.x-dev » 8.x-2.x-dev

Bumping to current dev version.

fgm’s picture

For the record, write safety is currently defined globally in the Client options. Not sure there could be a generic strategy to derive a specific write safety setting from default options, so that would have to be specified entirely manually.