[DOCS-12978] Improve nuance around Jumbo chunks Created: 22/Aug/19  Updated: 30/Oct/23

Status: Closed
Project: Documentation
Component/s: manual
Affects Version/s: None
Fix Version/s: Server_Docs_20231030

Type: Improvement Priority: Major - P3
Reporter: Kevin Pulo Assignee: Unassigned
Resolution: Won't Do Votes: 0
Labels: docs-onboarding-candidate
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Related
related to DOCS-12704 Update jumbo chunk definition Closed
related to SERVER-40881 Jumbo chunk not marked as jumbo Closed
Participants:
Days since reply: 1 year, 14 weeks, 2 days ago
Epic Link: DOCSP-1769

 Description   

Description

The docs could be clearer when handling the phrase "jumbo chunks". This is used interchangably to refer to each of:

  1. chunk that has been marked with the jumbo: true flag
  2. chunk that is indivisible, and will be marked as jumbo: true if the balancer attempts to move it (but currently doesn't have jumbo: true)
  3. chunk that is divisible, but has been marked as jumbo: true for some other reason (eg. SERVER-19919, SERVER-21931).
  4. chunk that is informally very large and difficult to migrate or work with (but may in fact be divisible)

I'm not sure if #3 and #4 are actually a problem in the docs — it might be more in discussions elsewhere about jumbo chunks.

In any case, the docs would benefit from some discussion around "jumbo as in jumbo: true" vs "jumbo as in indivisible and large".

Examples:

Scope of changes

Impact to Other Docs

MVP (Work and Date)

Resources (Scope or Design Docs, Invision, etc.)



 Comments   
Comment by Education Bot [ 31/Oct/22 ]

Hello! This ticket has been closed due to inactivity. If you believe this ticket is still important, please reopen it and leave a comment to explain why. Thank you!

Generated at Thu Feb 08 08:06:38 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.