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

Fix Badger doc #825

Merged
merged 1 commit into from
Dec 28, 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
3 changes: 1 addition & 2 deletions content/docs/next-release-v2/badger.md
Original file line number Diff line number Diff line change
Expand Up @@ -11,8 +11,7 @@ hasparent: true

**Cons**:
* It is only suitable for a _single-node deployment_, so it cannot scale horizontally for higher data volumes.
* It is not possible to share a single Badger instance between multiple Jaeger processes, such as **jaeger-collector** and **jaeger-query**, therefore it is usually only used in the **all-in-one** configuration.
* NB: it is possible to share a single Badger instance between multiple processes if you use Badger with the [remote storage](../tools/#remote-storage-component) component.
* If Badger backend is enabled in **jaeger-collector**, it cannot be accessed from **jaeger-query**, and vice versa. Therefore, Badger can only used either in the **all-in-one** configuration or with the [remote storage](../tools/#remote-storage-component) component.

## Configuration

Expand Down
Loading