[SERVER-17247] traceWriteConflictException should be settable at startup Created: 10/Feb/15  Updated: 18/Sep/15  Resolved: 13/Feb/15

Status: Closed
Project: Core Server
Component/s: Internal Code
Affects Version/s: None
Fix Version/s: 3.0.0-rc9, 3.1.0

Type: Bug Priority: Major - P3
Reporter: Mathias Stearn Assignee: Mathias Stearn
Resolution: Done Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Backwards Compatibility: Fully Compatible
Operating System: ALL
Backport Completed:
Participants:

 Comments   
Comment by Githook User [ 15/Feb/15 ]

Author:

{u'username': u'RedBeard0531', u'name': u'Mathias Stearn', u'email': u'mathias@10gen.com'}

Message: SERVER-17247 allow traceWriteConflictException to be set on startup

This makes it usable with smoke.py

(cherry picked from commit 1438dfd8fb21ea29ea2de273470b934f599269e5)
Branch: v3.0
https://github.com/mongodb/mongo/commit/5635d23c6749e73b8c367070fe8474884dcb0207

Comment by Githook User [ 13/Feb/15 ]

Author:

{u'username': u'RedBeard0531', u'name': u'Mathias Stearn', u'email': u'mathias@10gen.com'}

Message: SERVER-17247 allow traceWriteConflictException to be set on startup

This makes it usable with smoke.py
Branch: master
https://github.com/mongodb/mongo/commit/1438dfd8fb21ea29ea2de273470b934f599269e5

Generated at Thu Feb 08 03:43:46 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.