Tetap teratur dengan koleksi
Simpan dan kategorikan konten berdasarkan preferensi Anda.
Halaman ini menjelaskan perilaku instance Memorystore Anda selama operasi upgrade versi, pengaruh operasi upgrade terhadap aplikasi Anda, dan waktu yang tepat untuk menjalankan operasi upgrade. Untuk mempelajari cara mengupgrade versi Redis instance, lihat Mengupgrade versi Redis instance.
Bergantung pada tingkatan instance,
menjalankan operasi upgrade versi dapat berdampak pada performa dan penyimpanan
aplikasi Anda. Ada juga beberapa batasan untuk mengupgrade instance berdasarkan jumlah memori yang sedang digunakan.
Praktik terbaik untuk mengupgrade versi Redis instance
Sebaiknya Anda mengupgrade ke versi 7.0 dan yang lebih baru karena rotasi Otoritas Sertifikat tidak lagi menghentikan koneksi.
Sebaiknya ekspor
data instance Anda sebelum menjalankan operasi upgrade versi.
Untuk instance Paket Standar, guna meningkatkan kecepatan dan keandalan
operasi upgrade versi, upgrade instance Anda selama periode traffic instance rendah. Untuk mempelajari cara memantau traffic instance, lihat
Memantau instance Redis.
Saat mengupgrade instance Paket Standar, jaga beban penulisan instance seminimal
mungkin. Beban tulis yang tinggi dapat menyebabkan operasi upgrade memerlukan waktu yang jauh lebih lama, dan dapat menyebabkan upgrade gagal.
Perilaku upgrade versi
Data dipertahankan selama operasi upgrade versi untuk instance Paket Dasar dan Standar. Selama operasi upgrade, instance mengalami reset koneksi singkat selama beberapa menit, atau kurang. Aplikasi harus menyertakan logika percobaan ulang dalam kode agar dapat terhubung kembali ke instance. Alamat IP dan string koneksi tetap sama.
Karena gangguan koneksi jangka pendek, mungkin ada sejumlah kecil data usang atau tidak konsisten yang tidak ditulis atau diperbarui ke cache selama instance tidak tersedia dalam jangka waktu singkat.
Beban tulis selama upgrade
Anda harus mengupgrade instance selama periode traffic instance rendah untuk meminimalkan dampak performa pada aplikasi Anda. Beban tulis yang tinggi, atau tekanan memori yang tinggi, dapat menyebabkan operasi upgrade memerlukan waktu yang lebih lama dan dapat menyebabkan upgrade gagal. Untuk mengetahui informasi selengkapnya, lihat Operasi penskalaan dan upgrade versi.
Kunci yang sudah berakhir
Saat Anda mengupgrade instance Paket Standar, kunci yang sudah habis masa berlakunya tidak akan disinkronkan. Jika Anda memiliki kunci yang sudah tidak berlaku di instance Redis sebelum melakukan upgrade, Anda akan memiliki lebih sedikit kunci setelah instance diupgrade.
[[["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 Redis version of an instance\n\nThis page describes how your Memorystore 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\nRedis version, see [Upgrading an instance's Redis version](/memorystore/docs/redis/upgrading-instance-version).\n\nDepending on the instance's [tier](/memorystore/docs/redis/redis-tiers),\nrunning a version upgrade operation can have performance and storage\nimplications for your application. There are also some limitations to upgrading\ninstances based on the amount of memory that is currently in use.\n\nBest practices for upgrading an instance's Redis version\n--------------------------------------------------------\n\n- We recommend that you upgrade to version 7.0 and later because [Certificate Authority rotation](/memorystore/docs/redis/about-in-transit-encryption#certificate_authority_rotation) no longer drops connections.\n\n- We recommend [exporting](/memorystore/docs/redis/export-data)\n your instance data before running a version upgrade operation.\n\n- For Standard Tier instances, to increase the speed and reliability of\n your version upgrade operation, upgrade your instance during periods of low\n instance traffic. To learn how to monitor instance traffic, see\n [Monitoring Redis instances](/memorystore/docs/redis/monitoring-instances).\n\n- When upgrading a Standard Tier instance, keep the instance write load to a\n minimum. A high write load can cause upgrade operations to take significantly\n longer, and can cause upgrades to fail.\n\nVersion upgrade behavior\n------------------------\n\nData is preserved during a version upgrade operation for both Basic and Standard Tier instances. During an upgrade operation the instance undergoes 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 instance. The IP address and connection string 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 instance was unavailable.\n\n### Write load during an upgrade\n\nYou should upgrade an instance during a period of low instance traffic to minimize the performance impact on your application. A high write load, or high memory pressure, can cause an upgrade operation to take significantly longer and can cause the upgrade to fail. For more information see [Scaling and version upgrade operations](/memorystore/docs/redis/memory-management-best-practices#scaling_and_version_upgrade_operations).\n\n### Expired keys\n\nWhen you upgrade a Standard Tier instance, expired keys are not synced. If you have expired keys in your Redis instance before you upgrade, you will have fewer keys after the instance is upgraded."]]
