Files
lancedb/docs/web/enterprise/distributed-compaction.mdx
T
Jack YeandClaude Sonnet 5 dfbf682cb5 style: re-theme Mermaid diagrams to the brand palette, light and dark (#4822)
## Summary

Every Mermaid diagram now renders in the brand palette, with separate
light and dark variants that switch with the site's theme toggle.
Default node styling stays neutral; one accent color marks each
diagram's actual subject, chosen per diagram. A couple of diagrams
changed orientation where their old layout was too wide to read
comfortably.

Companion change in lancedb/sophon uses the same colors and pattern.

🤖 Generated with [Claude Code](https://claude.com/claude-code)

https://claude.ai/code/session_018PXMCbRH6i5w47TsjeEUMT

Co-authored-by: Claude Sonnet 5 <noreply@anthropic.com>
2026-11-03 21:02:24 -08:00

84 lines
3.6 KiB
Plaintext

---
title: "Distributed compaction"
sidebarTitle: "Distributed compaction"
description: "How LanceDB Enterprise distributes compaction across a fleet of job workers."
icon: "compress"
availability:
embedded: unavailable
enterprise: available
---
Distributed compaction splits a table's fragments into independent,
fragment-disjoint tasks and fans them out across job workers in LanceDB
Enterprise. Unlike an index build, a compaction plan needs no bin-packing:
Lance's own planner already produces disjoint tasks, so workers claim and
execute them directly through the job registry, with no coordination
needed to decide who does what. See [Architecture](/index#architecture).
<div className="hidden dark:block">
```mermaid
%%{init: {"theme": "base", "themeVariables": {
"background": "#171513", "primaryColor": "#1e1b19", "primaryTextColor": "#f4ebe8",
"primaryBorderColor": "#4c443f", "lineColor": "#847770", "textColor": "#f4ebe8",
"edgeLabelBackground": "#171513", "fontFamily": "Inter, sans-serif", "fontSize": "15px"
}}}%%
flowchart LR
L["Lance's planner<br/>splits fragments into<br/>disjoint tasks"] --> R[("Job registry")]
R --> W1["Worker<br/>claims fragments 1-2"]
R --> W2["Worker<br/>claims fragments 3-4"]
R --> W3["Worker<br/>claims fragments 5-6"]
W1 --> C["Fleet-wide eligibility gate:<br/>one worker claims the commit"]
W2 --> C
W3 --> C
classDef default fill:#1e1b19,stroke:#4c443f,stroke-width:1px,color:#f4ebe8
classDef accent fill:#2a1810,stroke:#ff734a,stroke-width:1.5px,color:#f4ebe8
class R,C accent
```
</div>
<div className="block dark:hidden">
```mermaid
%%{init: {"theme": "base", "themeVariables": {
"background": "#ffffff", "primaryColor": "#ffffff", "primaryTextColor": "#221d19",
"primaryBorderColor": "#ad9e95", "lineColor": "#6b625c", "textColor": "#221d19",
"edgeLabelBackground": "#ffffff", "fontFamily": "Inter, sans-serif", "fontSize": "15px"
}}}%%
flowchart LR
L["Lance's planner<br/>splits fragments into<br/>disjoint tasks"] --> R[("Job registry")]
R --> W1["Worker<br/>claims fragments 1-2"]
R --> W2["Worker<br/>claims fragments 3-4"]
R --> W3["Worker<br/>claims fragments 5-6"]
W1 --> C["Fleet-wide eligibility gate:<br/>one worker claims the commit"]
W2 --> C
W3 --> C
classDef default fill:#ffffff,stroke:#ad9e95,stroke-width:1px,color:#221d19
classDef accent fill:#fff1ec,stroke:#e8582d,stroke-width:1.5px,color:#221d19
class R,C accent
```
</div>
No task depends on another's result, so a worker that finishes early
simply claims another task rather than waiting on its peers. Committing is
where the fleet does coordinate: finished tasks go through a shared
eligibility gate, and only the one worker that claims the commit actually
writes it, rather than each worker committing its own task independently.
Whether a failed task can still let the rest commit depends on the remap
mode. Inline remap is all-or-nothing: one failed task fails the whole job,
since the commit updates every affected index inline and can't skip a
task's share of that. Deferred remap can commit a subset -- a failed
task's fragments are abandoned and replanned in a later round, while the
rest of the job's tasks commit without waiting on it. See
[Advanced Conflict Resolution](/enterprise/advanced-conflict-resolution)
for when compaction defers a remap at all.
## Compaction interfaces {#compaction-interfaces}
- [Compaction](/maintenance/compaction) for triggering and configuring a compaction.
- [Garbage Collection](/maintenance/cleanup) for removing files compaction and other operations leave behind.
- [Job Framework](/basics/jobs) for the job types a deployment runs on its own schedule.