1 Respuesta
- Más nuevo
- Más votos
- Más comentarios
2
Simply attaching the volume to multiple instances doesn’t mean your filesystem would support multiple writers/readers. Multi attach use cases are explained in this blog https://aws.amazon.com/blogs/storage/delivering-instant-data-sharing-with-multi-attach-enabled-amazon-ebs/
Contenido relevante
- OFICIAL DE AWSActualizada hace un año
- OFICIAL DE AWSActualizada hace un año
- OFICIAL DE AWSActualizada hace un año
- OFICIAL DE AWSActualizada hace un año
Thanks @Kallu for the link explaining the issue. So that means that by default the multi-attach volume can't be used as a shared storage on multiple ec2 instances without setting them up using the CVM for taking instant snapshots. I guess that would also create significant cost increases for running such a setup.
Ideally using EFS would have worked for our use case, but since there are substantial latency issues for hundreds of read/write operations on different files on it, unfortunately in our load tests the lags became too large to work with it. Hence this was being tried out as an auto-scaling option with the nodejs application with a shared storage. Thanks again for the help.