[SERVER-20659] balancer ignores collection storage engine options on moveChunk Created: 28/Sep/15 Updated: 06/Dec/22 Resolved: 02/Dec/21 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Sharding |
| Affects Version/s: | 3.0.6 |
| Fix Version/s: | None |
| Type: | Bug | Priority: | Minor - P4 |
| Reporter: | Clement R | Assignee: | [DO NOT USE] Backlog - Sharding Team |
| Resolution: | Duplicate | Votes: | 0 |
| Labels: | pm-1051-legacy-tickets | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Environment: |
OS : debian 7.8 64 |
||
| Issue Links: |
|
||||||||||||||||||||
| Assigned Teams: |
Sharding
|
||||||||||||||||||||
| Operating System: | ALL | ||||||||||||||||||||
| Steps To Reproduce: | Apply the following patch to the sharding_system_namespaces.js test:
|
||||||||||||||||||||
| Sprint: | QuInt A (10/12/15), QuInt B (11/02/15), QuInt C (11/23/15) | ||||||||||||||||||||
| Participants: | |||||||||||||||||||||
| Description |
| Comments |
| Comment by Jack Mulrow [ 02/Dec/21 ] | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
This issue was fixed in | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| Comment by Ramon Fernandez Marina [ 01/Apr/16 ] | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
clement@compilatio, unfortunately this ticket is not part of the current development cycle at the moment, but will be considered in the next round of planning. A fix for 3.2/3.4 is not scheduled right now, but if that changes will update this ticket accordingly. Regards, | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| Comment by Clement R [ 01/Apr/16 ] | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
Hello, Any update on this issue ? Thanks, | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| Comment by Max Hirschhorn [ 13/Dec/15 ] | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
The reason that the storage engine options are not propagated during the moveChunk operation is because the .chunks collection does in fact already exist on the other shard. The GridFS specification requires that the driver create the index {files_id: 1, n: 1} on the .chunks collection before the first write operation if the index doesn't already exist. mongos forwards the createIndexes command to all shards in the cluster, even if they don't store any chunks of the sharded collection. The createIndexes command is what causes the .chunks collection to be implicitly created without any storage engine options on the other shard. This issue isn't really GridFS-specific and can easily be observed by applying the following patch to the sharding_system_namespaces.js test:
| ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| Comment by Clement R [ 24/Nov/15 ] | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
No. I dont think so.
=> So this bug seems "GridFS" related... Regards, | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| Comment by Max Hirschhorn [ 21/Nov/15 ] | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
Hi Clement, Sorry about the delayed response. Dan answered your question regarding a possible workaround by creating an empty collection on each of the shards with the block_compressor option you wanted.
Thanks, | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| Comment by Daniel Pasette (Inactive) [ 28/Sep/15 ] | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
Thanks for the detailed report Clement. The intention is that the expressly defined storageEngine options for a collection will override the server defaults and that moveChunk will honor those options. As a workaround, it should be safe to create an empty collection with the blockCompressor options you want on the empty shard. We'll investigate what needs to happen in the server. |