Spot fleet specifies that the interrupting behavior is stopped and does not persist, but still loses data

We followed the AWS documentation at https://docs.aws.amazon.com/AWSEC2/latest/UserGuide/interruption-behavior.htm and https://docs.aws.amazon.com/AWSEC2/latest /UserGuide/stop-spot-instances.html and set the terminate behavior of Spot in the template of Spot fleet to stop. According to the explanation of AWS documentation, it should keep the data persistence and private IP of the root directory unchanged. However, in the model replacement that happened on 2023.1.15, we found that not only has the previous data not persisted, but the private IP has also changed. Please help us to find out the reason.

Our Spot-Fleet request id ：sfr-b3e1521c-786e-4372-a15a-e06445a93cee

Themen

Kalkulation

Relevanter Inhalt

Wie kann ich den Fehler „FAILED: SemanticException table is not partitioned but partition spec exists" in Athena beheben?
AWS OFFICIALAktualisiert vor einem Jahr
Wie behebe ich den Fehler „The specified queue does not exist or you do not have access to it.“, wenn ich einen AWS Glue Job ausführe, um Nachrichten an Amazon SQS in einer anderen Region zu senden?
AWS OFFICIALAktualisiert vor 3 Jahren
Wie behebe ich den Fehler „The new key policy will not allow you to update the key policy in the future“, wenn ich versuche, mit AWS CloudFormation einen AWS-KMS-Schlüssel zu erstellen?
AWS OFFICIALAktualisiert vor 2 Jahren
Wie kann ich den Fehler „The security token included in the request is expired“ bei der Ausführung von Java-Anwendungen auf Amazon EC2 beheben?
AWS OFFICIALAktualisiert vor 2 Jahren