[SERVER-15873] massert trace not needed when splitAndMove fails Created: 30/Oct/14 Updated: 19/Nov/14 Resolved: 30/Oct/14 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Sharding |
| Affects Version/s: | None |
| Fix Version/s: | 2.8.0-rc0 |
| Type: | Bug | Priority: | Minor - P4 |
| Reporter: | Greg Studer | Assignee: | Matt Kangas |
| 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 |
| Participants: |
| Description |
|
There's no benefit to a scary stack trace here: m30999| 2014-10-30T07:01:34.912 0000 I - [conn1] Assertion: 10412:moveAndCommit failed: { cause: { ok: 0.0, errmsg: "can't accept new chunks because there are still 1 deletes from previous migration" }, ok: 0.0, errmsg: "moveChunk failed to engage TO-shard in the data transfer: can't accept new chunks because there are still 1 deletes from previous migration" } |
| Comments |
| Comment by Githook User [ 30/Oct/14 ] |
|
Author: {u'username': u'kangas', u'name': u'Matt Kangas', u'email': u'matt.kangas@mongodb.com'}Message: |
| Comment by Githook User [ 30/Oct/14 ] |
|
Author: {u'username': u'kangas', u'name': u'Matt Kangas', u'email': u'matt.kangas@mongodb.com'}Message: |
| Comment by Greg Studer [ 30/Oct/14 ] |
|
Yeah pretty much. Just didn't want to lose it. |
| Comment by Matt Kangas [ 30/Oct/14 ] |
|
Change needed here? Recommend using msgassertedNoTrace |