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
Right now sns supports two release methods for pods: hard (default) and soft.
The hard release is focused on a quick release process from the Ops perspective. It will stop the old pod version and run the new version in the same transaction, which likely gives a small glitch in uptime.
The soft process takes longer time as as it has both versions running with overlap before retiring the old version.
We would want a safe method which guarantees that there is no overlap between version. Which is desirable when
running processes which should never concurrently access the same file. For example a database.
The text was updated successfully, but these errors were encountered:
Right now sns supports two release methods for pods:
hard
(default) andsoft
.The
hard
release is focused on a quick release process from the Ops perspective. It will stop the old pod version and run the new version in the same transaction, which likely gives a small glitch in uptime.The
soft
process takes longer time as as it has both versions running with overlap before retiring the old version.We would want a
safe
method which guarantees that there is no overlap between version. Which is desirable whenrunning processes which should never concurrently access the same file. For example a database.
The text was updated successfully, but these errors were encountered: