https://www.runatlantis.io/ logo
Join Slack
Powered by
This message was deleted.
# atlantis-community
s
This message was deleted.
p
have you checked CPU and Memory saturations?
it could be it takes that long because it does not have enough CPU or memory
n
CPU and Memory are nowhere near its limits (neither at deploy time nor during regular operation), it is absolutely overprovisioned when it comes to resources right now.
p
there is no reason to be slow on start
90% of the people use the default which will use the localdb (boltdb)
what about data volume? is it attached or nfs?
n
To clarify, we've been running with more or less this setup for over a year. So I wasn't intending to call out the localdb. All of the volumes are EBS devices in AWS. There is no nfs or anything like that.We also don't have any persistent volumes associated with Atlantis.
p
no issues , I'm just curious that it takes time to start
my setup starts righ away
n
Ours used to as well :)
p
do you know if there are old PRs in the data dir ?
maybe PRs that were never removed ?
n
We don't preserve the data directory across deploys, so it is empty.
Circling back to this, I believe we have a lead regarding why this was occurring. We had Atlantis sitting behind an AWS Classic ELB. When Atlantis would go down as part of the deploy process, the 
Surge Queue
on the load balancer would grow. The theory is that when Atlantis would come back up, it would get stuck waiting for the Surge Queue to process before being able to handle planning new changes. We swapped out the Classic ELB and are no longer seeing this issue.
p
interesting, thanks for getting back
Open in Slack
PreviousNext
Powered by