1 réponse
- Le plus récent
- Le plus de votes
- La plupart des commentaires
0
The following documentation seems to be consistent with the file system.
However, they lose consistency if a failure occurs when operating in a single AZ.
https://docs.aws.amazon.com/fsx/latest/WindowsGuide/what-is.html
https://docs.aws.amazon.com/fsx/latest/WindowsGuide/high-availability-multiAZ.html
Contenus pertinents
- demandé il y a un an
- demandé il y a un mois
- demandé il y a 7 mois
- demandé il y a 2 ans
AWS OFFICIELA mis à jour il y a un an- AWS OFFICIELA mis à jour il y a un an
- AWS OFFICIELA mis à jour il y a 9 mois
- AWS OFFICIELA mis à jour il y a 3 ans
Thank you for your answer. What I mean by read-after-write consistency is that if a user A writes to a file A, and user B is reading from file A immediately after that, user B will see user A's change. I can't find in the documentation whether FSx for Windows File Server delivers that or not. For example, S3 does provide it: https://aws.amazon.com/blogs/aws/amazon-s3-update-strong-read-after-write-consistency/