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.

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

docs: support clarification for filesystem (backport release-3.2.x) #14562

Merged
merged 1 commit into from
Oct 21, 2024
Merged
Changes from all commits
Commits
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
10 changes: 6 additions & 4 deletions docs/sources/operations/storage/filesystem.md
Original file line number Diff line number Diff line change
@@ -1,8 +1,8 @@
---
title: Filesystem object store
menuTitle: Filesystem object store
menuTitle: Filesystem object store
description: Describes the features and limitations of using a filesystem object store with Loki.
weight: 300
weight: 300
---
# Filesystem object store

Expand All @@ -20,7 +20,7 @@ A folder is created for every tenant all the chunks for one tenant are stored in

If Loki is run in single-tenant mode, all the chunks are put in a folder named `fake` which is the synthesized tenant name used for single tenant mode.

See [multi-tenancy]({{< relref "../multi-tenancy" >}}) for more information.
See [multi-tenancy](https://grafana.com/docs/loki/<LOKI_VERSION>/operations/multi-tenancy/) for more information.

## Pros

Expand All @@ -30,6 +30,8 @@ Great for low volume applications, proof of concepts, and just playing around wi

## Cons

The filesystem is not supported by Grafana Labs for production environments (for those customers who have purchased a support contract).

### Scaling

At some point there is a limit to how many chunks can be stored in a single directory, for example see [issue #1502](https://github.com/grafana/loki/issues/1502) which explains how a Loki user ran into a strange error with about **5.5 million chunk files** in their file store (and also a workaround for the problem).
Expand All @@ -44,4 +46,4 @@ The durability of the objects is at the mercy of the filesystem itself where oth

### High Availability

Running Loki clustered is not possible with the filesystem store unless the filesystem is shared in some fashion (NFS for example). However using shared filesystems is likely going to be a bad experience with Loki just as it is for almost every other application.
Running Loki clustered is not possible with the filesystem store unless the filesystem is shared in some fashion (NFS for example). However using shared filesystems is likely going to be a bad experience with Loki just as it is for almost every other application.
Loading