[SERVER-16806] After 1 hour timeout, rangeDeleter incorrectly reports "timed out after 0 seconds" Created: 12/Jan/15 Updated: 23/Jan/15 Resolved: 21/Jan/15 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Logging |
| Affects Version/s: | 2.8.0-rc4 |
| Fix Version/s: | 3.0.0-rc6 |
| Type: | Bug | Priority: | Minor - P4 |
| Reporter: | Kevin Pulo | Assignee: | Andy Schwerin |
| 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 | |||||||||
| Steps To Reproduce: | Repro is basically identical to that in
|
|||||||||
| Participants: |
| Description |
Note the timestamps — clearly exactly 1 hr has passed (kWTimeoutMillis in db/range_deleter.cpp:271), yet the message says "timed out after 0 seconds". |
| Comments |
| Comment by Githook User [ 21/Jan/15 ] |
|
Author: {u'username': u'andy10gen', u'name': u'Andy Schwerin', u'email': u'schwerin@mongodb.com'}Message: |
| Comment by Kevin Pulo [ 12/Jan/15 ] |
|
schwerin, this w:majority (with 1hr timeout) for rangeDeleter seems to be new behaviour that wasn't present in 2.6. The base commit was 017fc448ba39e0ee731b84b21991c7a3646a8724 for |
| Comment by Andy Schwerin [ 12/Jan/15 ] |
|
kevin.pulo@10gen.com, can you check to see if this is a regression from 2.6? |