Tetap teratur dengan koleksi
Simpan dan kategorikan konten berdasarkan preferensi Anda.
Halaman ini menjelaskan masa pemeliharaan, yang memberikan kontrol atas kapan pemeliharaan layanan yang mengganggu seperti patch keamanan dapat terjadi di layanan Dataproc Metastore Anda.
Ringkasan
Masa pemeliharaan memberi Anda kontrol terperinci terkait kapan pemeliharaan dapat terjadi untuk memitigasi potensi gangguan sementara pada workload Anda.
Pemeliharaan yang mengganggu ini tidak sering terjadi, tetapi dalam beberapa kasus, mungkin memerlukan mulai ulang server untuk menerapkan perbaikan mendesak.
Periode pemeliharaan berguna untuk jenis skenario berikut, antara lain:
Di luar jam sibuk: Anda ingin meminimalkan peluang periode nonaktif dengan menjadwalkan upgrade otomatis di luar jam sibuk saat traffic sedang turun.
Jam kerja: Anda ingin memastikan bahwa upgrade terjadi selama jam kerja agar ada orang yang dapat memantau upgrade dan mengelola masalah yang tidak terduga.
Upgrade multi-cluster: Anda ingin meluncurkan upgrade di beberapa layanan di berbagai region satu per satu pada interval yang ditentukan.
Masa pemeliharaan dijadwalkan berlangsung paling lama dua jam. Jika tugas berjalan di luar periode, Dataproc Metastore akan mencoba menjeda operasi dan melanjutkannya selama periode pemeliharaan berikutnya.
Dataproc Metastore berhak meluncurkan upgrade darurat
di luar periode pemeliharaan.
Mengonfigurasi masa pemeliharaan
Anda dapat mengonfigurasi masa pemeliharaan berulang yang terpisah untuk setiap layanan Dataproc Metastore.
Untuk mengonfigurasi masa pemeliharaan, Anda mengonfigurasi hari dalam seminggu dan jam
dalam sehari saat pemeliharaan dimulai. Misalnya, Anda dapat mengonfigurasi masa pemeliharaan yang diulang setiap hari Jumat pukul 06.00.
Anda dapat mengonfigurasi masa pemeliharaan menggunakan konsol Google Cloud .
Membuat layanan dengan masa pemeliharaan
Untuk membuat masa pemeliharaan untuk layanan baru:
Konsol
Di konsol Google Cloud , buka halaman Dataproc Metastore:
[[["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-08-27 UTC."],[[["\u003cp\u003eMaintenance windows allow users to control when disruptive service maintenance, such as security patches, occurs on Dataproc Metastore services, potentially causing service unavailability.\u003c/p\u003e\n"],["\u003cp\u003eThese windows are useful for scheduling upgrades during off-peak hours, ensuring on-call personnel are available, or coordinating multi-cluster upgrades.\u003c/p\u003e\n"],["\u003cp\u003eMaintenance windows are scheduled to last up to two hours, and any tasks that run longer are paused and resumed in the next window, but service-disruptive updates are always attempted to be scheduled during this time.\u003c/p\u003e\n"],["\u003cp\u003eUsers can configure recurring maintenance windows for each service by specifying the day of the week and hour of the day, using the Google Cloud console.\u003c/p\u003e\n"],["\u003cp\u003eWhile normal maintenance may occur outside the maintenance window, Dataproc Metastore reserves the right to roll out emergency updates outside of these windows.\u003c/p\u003e\n"]]],[],null,["# Maintenance windows\n\nThis page explains maintenance windows, which provide control over when\ndisruptive service maintenance such as security patches can occur on your\nDataproc Metastore services.\n| **Note:** During maintenance, the Dataproc Metastore services may become unavailable.\n\nOverview\n--------\n\nMaintenance windows give you fine-grained control over when maintenance can\noccur in order to mitigate potential transient disruptions to your workloads.\nThese disrupting maintenance do not happen very often, but in some cases, may\nrequire server restart to apply urgent fixes.\n| **Note:** Normal maintenance that doesn't cause service downtime can still occur outside of the maintenance window. We always try to honor a service's maintenance window for potentially disruptive updates when possible.\n\nMaintenance windows are useful for the following types of scenarios, among\nothers:\n\n- **Off-peak hours:** You want to minimize the chance of downtime by scheduling automatic upgrades during off-peak hours when traffic is reduced.\n- **On-call:** You want to ensure that upgrades happen during working hours so that someone can monitor the upgrades and manage any unanticipated issues.\n- **Multi-cluster upgrades:** You want to roll out upgrades across multiple services in different regions one at a time at specified intervals.\n\nMaintenance windows are scheduled to last up to two hours at most. If tasks run\nbeyond the window, Dataproc Metastore attempts to pause the operation and\nresume it during the next maintenance window.\n\nDataproc Metastore reserves the right to roll out emergency upgrades\noutside of maintenance windows.\n\nConfigure a maintenance window\n------------------------------\n\nYou can configure separate, repeating maintenance windows for each of your\nDataproc Metastore services.\n\nTo configure a maintenance window, you configure the day of the week and hour of\nthe day when it starts. For example, you can configure a maintenance\nwindow that recurs every Friday at 6:00 AM.\n| **Note:** The day and hour are defined in UTC IIUC. When using the Google Cloud console, times are always displayed using your local timezone.\n\nYou can configure a maintenance window using the Google Cloud console.\n\n### Create a service with a maintenance window\n\nTo create a maintenance window for a new service: \n\n### Console\n\n1. In the Google Cloud console, open the Dataproc Metastore page:\n\n [Open Dataproc Metastore in the\n Google Cloud console](https://console.cloud.google.com/dataproc/metastore/services)\n2. At the top of the **Dataproc Metastore** page, click the **Create**\n button. The **Create service** page opens.\n\n3. Configure your service as desired.\n\n4. Under **Maintenance window** , select the **Day of week**.\n\n5. Then select the **Hour of day**.\n\n6. Click **Submit**.\n\n### Configure a maintenance window for an existing service\n\nTo create or modify a maintenance window for an existing service: \n\n### Console\n\n1. In the Google Cloud console, open the Dataproc Metastore page:\n\n [Open Dataproc Metastore in the\n Google Cloud console](https://console.cloud.google.com/dataproc/metastore/services)\n2. On the **Dataproc Metastore** page, click the service name of the\n service you'd like to update. The **Service detail** page for that service opens.\n\n3. Under the **Configuration** tab, click the **Edit** button. The\n **Edit service** page opens.\n\n4. In the **Maintenance Window** section, select the **Day of week**.\n\n5. Then select the **Hour of day**.\n\n6. Click the **Submit** button to update the service.\n\nWhat's next\n-----------\n\n- [Service access](/dataproc-metastore/docs/access-service)\n- [Update and delete a service](/dataproc-metastore/docs/manage-service)\n- [Version policy](/dataproc-metastore/docs/version-policy)"]]
