[SERVER-10033] Add a global flag to turn off the TTLMonitor thread Created: 26/Jun/13 Updated: 27/Oct/15 Resolved: 03/Jul/13 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Usability |
| Affects Version/s: | None |
| Fix Version/s: | 2.4.6, 2.5.1 |
| Type: | New Feature | Priority: | Major - P3 |
| Reporter: | Steve Briskin (Inactive) | Assignee: | Daniel Pasette (Inactive) |
| Resolution: | Done | Votes: | 2 |
| Labels: | brs | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||
| Participants: | |||||||||
| Description |
|
Via a command-line parameter and/or server command. May be used to stop TTL deletes if the system is under extreme load or during an outage/corruption investigation. A single global (or per-DB) setting would be easier than having to update or drop all TTL indexes. By default, the TTLMonitor thread is enabled. To disable at startup:
To disable at runtime:
|
| Comments |
| Comment by Asya Kamsky [ 14/Jan/14 ] |
|
Opened DOC ticket to document option. |
| Comment by auto [ 05/Jul/13 ] |
|
Author: {u'username': u'monkey101', u'name': u'Dan Pasette', u'email': u'dan@10gen.com'}Message: |
| Comment by auto [ 05/Jul/13 ] |
|
Author: {u'username': u'monkey101', u'name': u'Dan Pasette', u'email': u'dan@10gen.com'}Message: Conflicts: |
| Comment by auto [ 03/Jul/13 ] |
|
Author: {u'username': u'monkey101', u'name': u'Dan Pasette', u'email': u'dan@10gen.com'}Message: |
| Comment by auto [ 03/Jul/13 ] |
|
Author: {u'username': u'monkey101', u'name': u'Dan Pasette', u'email': u'dan@10gen.com'}Message: |