Database: SetSafe() necessary? #8

Closed
opened 2014-04-26 09:47:15 +00:00 by thorsten · 4 comments
thorsten commented 2014-04-26 09:47:15 +00:00 (Migrated from devops.tsommer.org)

Check the default behavior of mgo's safe setting and afterwards may use SetSafe() for the session, to provide a propper mode.

Check the default behavior of mgo's safe setting and afterwards may use SetSafe() for the session, to provide a propper mode.
thorsten commented 2014-06-04 12:57:02 +00:00 (Migrated from devops.tsommer.org)

There is also a EnsureSafe() function! Check the whole behavior behind this.

There is also a EnsureSafe() function! Check the whole behavior behind this.
thorsten commented 2014-06-04 14:55:29 +00:00 (Migrated from devops.tsommer.org)

Done. The safe mode is set to "majority" to ensure, that the majority of all servers has acknowledged. The mode is set to "eventual" which allows to read from any secondary but write to master server.

Done. The safe mode is set to "majority" to ensure, that the majority of all servers has acknowledged. The mode is set to "eventual" which allows to read from any secondary but write to master server.
thorsten commented 2014-06-04 19:36:45 +00:00 (Migrated from devops.tsommer.org)

Todo: Specify both also for the ConfigurationDB!

**Todo**: Specify both also for the ConfigurationDB!
thorsten commented 2014-06-05 09:56:38 +00:00 (Migrated from devops.tsommer.org)

Done and all tests passed :)

Done and all tests passed :)
Sign in to join this conversation.
No Milestone
No project
No Assignees
1 Participants
Notifications
Due Date
The due date is invalid or out of range. Please use the format 'yyyy-mm-dd'.

No due date set.

Dependencies

No dependencies set.

Reference: Go/Ocean#8
No description provided.