Error with Temporary File Storage in Multi-Instance Auto-Scaling Environment and Inquiry on Using Cloud Storage for Temporary Files #4233
Unanswered
noor1yasser9
asked this question in
Q&A
Replies: 1 comment
-
https://docs.laravel-excel.com/3.1/exports/queued.html#multi-server-setup |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
I'm encountering an issue when using auto-scaling, particularly when my application scales to more than one instance. After auto-scaling, I start seeing the following error when trying to export files:
When I have only one instance running, everything works as expected, and there are no errors. However, my architecture relies on auto-scaling and will typically use multiple instances to handle load. It appears this error may be related to the file being cached or stored locally on each instance, which isn’t shared across instances in the auto-scaling setup.
Is there a recommended approach to handle storage for temporary or cache files in a multi-instance environment?
Additionally, is there a way to configure the temporary file local_path to a cloud-based storage solution like Amazon S3? I see that local_path is used to define where temporary files are stored during export/import processes:
Since we are running in a multi-instance environment, storing these temporary files locally on each instance creates issues with consistency across instances. If we could use a shared location, such as an S3 bucket, it might help avoid this issue. Any guidance on this would be greatly appreciated!
Beta Was this translation helpful? Give feedback.
All reactions