2 Antworten
- Neueste
- Die meisten Stimmen
- Die meisten Kommentare
0
Through AWS support, I learned the "archive command failed with exit code 1" log entry is a symptom of failing to have enough IOPS to write the WAL to S3. As the filename is advancing each time, it is not an issue, per se, but does indicate back-pressure within the storage subsystem. If the filename were to stay the same, that means the WAL is not being written to S3 and would start to affect the last restorable time.
In short, the RDS instance needs more IOPs.
beantwortet vor einem Jahr
0
Hi there,
These logs are generally not something to be concerned about. They tend to be seen when there are transient network issues reported with multi-AZ between primary and secondary instances of database instances. They should resolve if they haven't already :)
Relevanter Inhalt
- AWS OFFICIALAktualisiert vor einem Jahr
- AWS OFFICIALAktualisiert vor 2 Jahren
- AWS OFFICIALAktualisiert vor einem Jahr
- AWS OFFICIALAktualisiert vor einem Jahr
Thanks for the follow up. I had forgotten about this post and added an accepted answer based on my interaction with AWS support.