Tetap teratur dengan koleksi
Simpan dan kategorikan konten berdasarkan preferensi Anda.
Halaman ini menjelaskan perilaku instance Memorystore for Memcached selama operasi upgrade versi, pengaruh operasi upgrade terhadap aplikasi Anda, dan waktu yang tepat untuk menjalankan operasi upgrade. Untuk mempelajari cara mengupgrade versi Memcached instance, lihat Mengupgrade versi Memcached instance.
Mengupgrade instance memiliki implikasi performa dan penyimpanan untuk aplikasi
Anda.
Praktik terbaik untuk mengupgrade versi Memcached instance
Upgrade instance Anda selama periode traffic instance yang rendah untuk meminimalkan dampak pengosongan cache penuh yang disebabkan oleh operasi upgrade. Untuk mempelajari cara memantau traffic instance, lihat Memantau instance Memcached.
Perilaku upgrade versi
Instance Memcached mengalami pengosongan cache sepenuhnya selama operasi upgrade versi. Instance multi-node
tersedia sebagian selama operasi upgrade. Anda tidak dapat mendowngrade instance ke versi sebelumnya setelah diupgrade.
Operasi upgrade juga menyebabkan node mengalami reset koneksi singkat selama beberapa menit, atau kurang. Aplikasi harus menyertakan logika percobaan ulang dalam kode agar dapat terhubung kembali ke node. Endpoint penemuan dan endpoint node memcached tetap sama.
Karena pemutusan koneksi jangka pendek, mungkin ada sejumlah kecil data yang sudah tidak berlaku atau tidak konsisten yang tidak ditulis atau diperbarui ke cache selama waktu singkat saat node Memcached tidak tersedia.
[[["Mudah dipahami","easyToUnderstand","thumb-up"],["Memecahkan masalah saya","solvedMyProblem","thumb-up"],["Lainnya","otherUp","thumb-up"]],[["Sulit dipahami","hardToUnderstand","thumb-down"],["Informasi atau kode contoh salah","incorrectInformationOrSampleCode","thumb-down"],["Informasi/contoh yang saya butuhkan tidak ada","missingTheInformationSamplesINeed","thumb-down"],["Masalah terjemahan","translationIssue","thumb-down"],["Lainnya","otherDown","thumb-down"]],["Terakhir diperbarui pada 2025-09-05 UTC."],[],[],null,["# About upgrading the Memcached version of an instance\n\nThis page describes how your Memorystore for Memcached instance behaves during a version\nupgrade operation, how an upgrade operation can affect your application, and\nwhen you should run an upgrade operation. To learn how to upgrade an instance's\nMemcached version, see [Upgrade the Memcached version of an instance](/memorystore/docs/memcached/upgrade-memcached-version).\n\nUpgrading an instance has performance and storage implications for your\napplication.\n\nBest practices for upgrading an instance's Memcached version\n------------------------------------------------------------\n\nUpgrade your instance during periods of low instance traffic to minimize the impact of the full cache flush caused by the upgrade operation. To learn how to monitor instance traffic, see [Monitor Memcached instances](/memorystore/docs/memcached/monitor-instances).\n\nVersion upgrade behavior\n------------------------\n\nThe Memcached instance undergoes a complete cache flush during a version upgrade operation. Multi-node\ninstances are partially available during the upgrade operation. You cannot downgrade the instance to an earlier version once it has been upgraded.\n\nAn upgrade operation also causes the nodes to undergo a short connection reset of a couple minutes, or less. Applications should incorporate retry logic in the code to be able to reconnect to the nodes. The discovery endpoint and memcached node endpoints remain the same.\n\nBecause of the short term connection break, there may be a small amount of stale or inconsistent data that didn't write or update to the cache for the short amount of time the Memcached node was unavailable."]]
