-
Type:
Improvement
-
Resolution: Unresolved
-
Priority:
Major - P3
-
None
-
Affects Version/s: None
-
Component/s: None
-
Cluster Scalability
-
None
-
None
-
None
-
None
-
None
-
None
-
None
Today the migration destination manager save in the changelog the reason why a movechunk aborted but the migration source manager does not.
Can we add the same "errmsg" to the moveChunk.from event?
Example from recipient:
{
_id: 'xxxx',
server: 'xxxx',
shard: 'xxx',
clientAddr: '',
time: ISODate('2025-10-01T23:17:34.016Z'),
what: 'moveChunk.to',
ns: 'test.foo',
details: {
'step 1 of 8': 1,
'step 2 of 8': 0,
'step 3 of 8': 1,
'step 4 of 8': 50000,
'step 5 of 8': 10,
min: { id: 'AAAA' },
max: { id 'BBBB' },
to: 'xxxx,
from: 'xxxx',
note: 'aborted',
errmsg: 'timed out waiting for commit'
}
}
- is related to
-
-
- Backlog
-