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

Can't set replica count higher than 1 #412

Closed
paymog opened this issue Aug 9, 2024 · 5 comments
Closed

Can't set replica count higher than 1 #412

paymog opened this issue Aug 9, 2024 · 5 comments
Labels
Stale waiting-on-response Waiting for a response from the user

Comments

@paymog
Copy link

paymog commented Aug 9, 2024

When I set the replica count higher than 1, I get the following error in a crash loop

Error: initializing server: starting BoltDB: timeout (a possible cause is another Atlantis instance already running)
@GMartinez-Sisti
Copy link
Member

Hi @paymog, to increase replicas you need to have a shared database. Atlantis allows using redis instead of boltdb for this, but it will not set it up for you. Please take a look here:

# -- Set the desired Locking DB type
# Accepts boltdb or redis.
lockingDbType: ""
# -- Configure Redis Locking DB.
# lockingDbType value must be redis for the config to take effect.
# Check values.yaml for examples.
redis: {}
# redis:
# host: redis.host.name
# password: myRedisPassword
# port: 6379
# db: 0
# tlsEnabled: false
# insecureSkipVerify: false

@GMartinez-Sisti GMartinez-Sisti added the waiting-on-response Waiting for a response from the user label Aug 9, 2024
@paymog
Copy link
Author

paymog commented Aug 9, 2024

aaah gotcha. It would be nice if that was documented for the replicaCount value in the helm chart

@GMartinez-Sisti
Copy link
Member

aaah gotcha. It would be nice if that was documented for the replicaCount value in the helm chart

Maybe we can do a check and fail when replica > 1 && lockingDbType != redis. Feel free to send a PR 😃

@paymog
Copy link
Author

paymog commented Aug 9, 2024

That would be great, I think just one line of doc would also be useful 🙂

Copy link

This issue is stale because it has been open for 1 month with no activity. Remove stale label or comment or this will be closed in 1 month.'

@github-actions github-actions bot added the Stale label Sep 10, 2024
@github-actions github-actions bot closed this as not planned Won't fix, can't repro, duplicate, stale Oct 11, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Stale waiting-on-response Waiting for a response from the user
Projects
None yet
Development

No branches or pull requests

2 participants