You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
So it's usual to close one EC2 instance and wait for the new one come to serve in the upgrade procedure.
In this situation, it's useful to upload the temp files to s3 when the s3 plugin is shutting down to avoid some log data missing after EC2 stop and terminate.
So it's nice to have a flag to enable this kind of "graceful shutdown" for this plugin.
The text was updated successfully, but these errors were encountered:
I don't think this issue (and #68, and any other dupes) are valid anymore? The code was significantly refactored after this issue was reported and now the close method has this comment:
# The plugin has stopped receiving new events, but we still have
# data on disk, lets make sure it get to S3.
These issues and the related PRs can probably be closed.
In AWS environment, there's a way to make zero-download time upgrade, using the AWS auto scaling feature.
Details in here.
http://serverfault.com/questions/389301/amazon-ec2-elastic-load-balancing-strategy-for-zero-downtime-server-restart/679502#679502
So it's usual to close one EC2 instance and wait for the new one come to serve in the upgrade procedure.
In this situation, it's useful to upload the temp files to s3 when the s3 plugin is shutting down to avoid some log data missing after EC2 stop and terminate.
So it's nice to have a flag to enable this kind of "graceful shutdown" for this plugin.
The text was updated successfully, but these errors were encountered: