Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

chore: [release-3.1.x] docs: Fix link bracket for query-acceleration-blooms #14264

Merged
merged 1 commit into from
Sep 25, 2024
Merged

chore: [release-3.1.x] docs: Fix link bracket for query-acceleration-blooms #14264

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 1 addition & 1 deletion docs/sources/operations/query-acceleration-blooms.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -139,7 +139,7 @@ Example calculation for storage requirements of blooms for a single tenant.

Since reading blooms depends heavily on disk IOPS, Bloom Gateways should make use of multiple,
locally attached SSD disks (NVMe) to increase i/o throughput.
Multiple directories on different disk mounts can be specified using the `-bloom.shipper.working-directory` [setting]storage-config-cfg]
Multiple directories on different disk mounts can be specified using the `-bloom.shipper.working-directory` [setting][storage-config-cfg]
when using a comma separated list of mount points, for example:
```
-bloom.shipper.working-directory="/mnt/data0,/mnt/data1,/mnt/data2,/mnt/data3"
Expand Down
Loading