Atlantis was not designed for this

so you will have some work to do

do you have Redis locking enabled?

what is that for ?

oh got it. https://www.runatlantis.io/docs/server-configuration.html#locking-db-type atlantis will write to an external db for locks on MR, cmiiw,

and then we can connect to same db from another atlantis node, this way i guess we can achieve what we want,

Hi Pepe so we went ahead with using redis and helped us at one point where mutiple MR try to refer the same file path in them, that is getting blocked and we are getting error

Plan Failed: This project is currently locked by an unapplied plan from pull !XX. To continue, delete the lock from !XX or apply that plan and merge the pull request.
Once the lock is released, comment atlantis plan here to re-plan.

so this is fine, but the when on the same MR multiple plan/apply requests are fired irrespective of waiting for the response of first request to came, there are two scaneris which are possible 1. if all requests landed on same node 2. if all requests landed on different node for case 1) it is expected that we will get workspace lock error i.e.

Plan Error
The default workspace at path . is currently locked by another command that is running for this pull request.
Wait until the previous command is complete and try again.

and this is happening as expected, but in case 2) this is not happening, because what we find from code that this information is stored in the application memory and not in any database, so in order to make this info available to other nodes, this info needs to stored in some common shared storage location, like redis can be used again here, but now this comes with 2 I/O operations in a single plan/apply request, because first data will be written in redis that a plan for this path is going to start, like we are doing here but instead of writing it to application memory this time it will be written to redis and similarly this info will be removed from redis once the plan/apply operation is performed, like inside unlock fn, the data will be removed from redis. what do you think of this approach or if you have something else in mind please let me know. we have hard requirement of running atlantis on multi node, because the traffic which we have it can’t be handled by a single node, we need multi node architecture.

that could work but I’m not an expert on that part of the code. Lyft forked atlantis and added Temporal as a backend to manage it workers queue to solve some related issues of what you are talking about