-
Type:
Task
-
Resolution: Unresolved
-
Priority:
Major - P3
-
None
-
Affects Version/s: None
-
Component/s: None
-
Query Integration
-
None
-
3
-
TBD
-
None
-
None
-
None
-
None
-
None
-
None
-
None
Right now this FSM workload performs migrations on a namespace unrelated to the map reduce operation (fsmdb.undefined) due to this not being the correct way to override this parameter in these tests.
[j1:s1:prim] | 2025-07-28T13:21:00.842+00:00 I MIGRATE 22016 [S] [MoveChunk] "Starting chunk migration donation","attr":{"requestParameters":{"_shardsvrMoveRange":"test9_fsmdb0.undefined","toShard":"shard-rs0","min":{"_id":50},"max":{"_id":{"$maxKey":1}},"waitForDelete":false,"collectionTimestamp":{"$timestamp":{"t":1753708858,"i":97}},"fromShard":"shard-rs1","maxChunkSizeBytes":134217728,"forceJumbo":0,"secondaryThrottle":false,"writeConcern":{"w":1,"wtimeout":0},"$clusterTime":{"clusterTime":{"$timestamp":{"t":1753708860,"i":269}}},"$configTime":{"$timestamp":{"t":1753708860,"i":260}},"$topologyTime":{"$timestamp":{"t":1753708713,"i":18}},"mayBypassWriteBlocking":false}}
From a comment in the test, though, it seems that map reduce is not compatible with concurrent chunk migrations anyways.
We should reconsider whether this test makes sense and, if it is deemed valuable to keep, update the test so that the migrations are being done on a meaningful collection.
- is related to
-
-
- Closed
-