Skip to content

Update default number of primary shards for assets index #325

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

Merged
CiprianAnton merged 1 commit into from
Mar 17, 2026
Merged

Update default number of primary shards for assets index #325

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
18 changes: 1 addition & 17 deletions getting-started/templates/systemlink-values.yaml
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -517,14 +517,6 @@ assetservicecdc:
##
host: "elasticsearch-release-master-hl.default.svc.cluster.local"

## High Availability configuration
##
highAvailability:
## Enables high availability, which is recommended for production environments.
## To use this feature, your system must be able to access a durable shared storage.
## For example, the shared storage can be S3, Azure Storage, or a ReadWriteMany volume.
enabled: true

## Job configuration.
##
job:
Expand All @@ -539,7 +531,7 @@ assetservicecdc:
index:
## The number of primary shards that SystemLink allocates for the assets elastic index.
## You can only configure this value for the first deployment. Subsequent deployments ignore this variable.
primaryShardsCount: 2
primaryShardsCount: 1

## Configuration for the Grafana dashboard provider.
##
Expand Down Expand Up @@ -1051,14 +1043,6 @@ fileingestioncdc:
## <ATTENTION> The Elasticsearch host depends on the release name. Ensure that you are using the correct host.
host: "elasticsearch-release-master-hl.default.svc.cluster.local"

## High Availability configuration
##
highAvailability:
## Enables high availability, which is recommended for production environments.
## To use this feature, your system must be able to access a durable shared storage.
## For example, the shared storage can be S3, Azure Storage, or a ReadWriteMany volume.
enabled: true

## Job configuration.
##
job:
Expand Down
Loading