Tetap teratur dengan koleksi
Simpan dan kategorikan konten berdasarkan preferensi Anda.
Dokumen ini menjelaskan siklus proses instance Compute Engine, yang mencakup berbagai status yang dapat dilalui instance tersebut dari pembuatan hingga penghapusan. Untuk mempelajari cara memeriksa status satu atau beberapa instance, lihat bagian berikut:
Dengan memahami siklus proses instance, Anda dapat melakukan hal berikut secara lebih
efektif:
Memecahkan masalah instance.
Mengelola resource instance.
Merencanakan migrasi instance.
Status instance
Instance komputasi dapat bertransisi melalui berbagai status sebagai bagian dari
siklus prosesnya. Saat membuat instance, Compute Engine akan menyediakan resource untuk memulainya, setelah itu instance akan beralih ke staging dan bersiap untuk booting pertama. Setelah instance dimulai, instance tersebut dianggap berjalan. Instance yang berjalan
dapat dihentikan dan dimulai ulang berulang kali, atau ditangguhkan dan dilanjutkan,
hingga dihapus.
Diagram berikut menunjukkan berbagai status yang dapat ditetapkan Compute Engine untuk instance:
Status yang ditampilkan dalam diagram sebelumnya adalah sebagai berikut:
PROVISIONING: pada tahap pertama instance,
Compute Engine mengalokasikan resource untuk instance.
STAGING: Compute Engine sedang menyiapkan instance untuk booting
pertama karena salah satu alasan berikut:
Compute Engine masih membuat dan mengonfigurasi instance.
Anda, atau operasi terjadwal, telah meminta untuk memulai ulang atau melanjutkan
instance.
Dalam status ini, instance belum berjalan.
RUNNING: Compute Engine sedang melakukan booting instance, atau instance sedang berjalan. Dalam status ini, Anda dapat menghentikan, menangguhkan, atau menghapus instance. Selain itu, Compute Engine dapat menghentikan atau menghapus instance untuk tindakan terjadwal, atau memperbaikinya jika instance adalah bagian dari grup instance terkelola (MIG) dan terjadi error hardware.
PENDING_STOP: instance dimatikan dengan tuntas. Proses shutdown ini hanya terjadi jika Anda telah mengaktifkan shutdown yang benar dan Anda telah meminta untuk menghentikan atau menghapus instance, atau Compute Engine melakukannya secara otomatis untuk penghentian atau penghapusan terjadwal. Status instance
berubah menjadi STOPPING jika salah satu hal berikut terjadi:
Anda mengakhiri penonaktifan yang tuntas secara manual.
Periode penghentian tuntas berakhir. Jika ada tugas yang masih berjalan, Compute Engine akan menghentikannya secara paksa.
STOPPING: instance sedang mematikan OS tamu, yang terjadi dalam
skenario berikut:
Anda, atau operasi terjadwal, telah meminta untuk menghentikan atau menghapus
instance.
Terjadi error hardware.
Waktu shutdown bergantung pada
jenis instance;
namun, jika instance berhenti karena error hardware, waktu
shutdown mungkin bervariasi. Setelah Compute Engine mematikan OS tamu, Compute Engine akan menetapkan status instance ke TERMINATED, lalu menyelesaikan operasi penghentian atau menghapus instance dan semua resource terlampir.
TERMINATED: Compute Engine telah menyelesaikan operasi penghentian.
Resource terlampir akan tetap terlampir kecuali jika Anda melepaskannya. Dalam
status ini, instance akan tetap dihentikan hingga Anda memulai ulang atau menghapusnya.
REPAIRING: Compute Engine sedang memperbaiki instance.
Compute Engine memperbaiki instance jika instance mengalami error internal atau server host instance tidak tersedia karena pemeliharaan. Saat
instance sedang dalam perbaikan, hal berikut akan terjadi:
Jika Compute Engine berhasil memperbaiki instance, Compute Engine akan mengembalikan status instance ke status aslinya sebelum operasi perbaikan dimulai.
Status ini dapat berupa STAGING, RUNNING, SUSPENDING, atau STOPPING.
SUSPENDING: Compute Engine telah memulai operasi penangguhan
instance setelah Anda meminta untuk menangguhkannya. Dalam status ini, Anda hanya dapat menunggu operasi penangguhan selesai.
SUSPENDED: Compute Engine telah menyelesaikan operasi penangguhan.
Dalam status ini, Anda dapat melanjutkan atau menghapus instance. Jika instance tetap berada dalam status SUSPENDED selama lebih dari 60 hari, Compute Engine akan menghentikan instance dan mengalihkan statusnya ke TERMINATED.
Kegagalan hardware
Terkadang, instance komputasi dapat gagal karena pemadaman layanan yang tidak terduga, error hardware, atau masalah sistem lainnya. Google merekomendasikan untuk mengurangi risiko kegagalan hardware dengan menggunakan volume penyimpanan persisten, mencadangkan data Anda secara rutin, dan mendesain sistem agar kegagalan satu instance tidak menjadi bencana. Untuk
mengetahui informasi selengkapnya, lihat cara
mendesain sistem yang andal.
Jika instance gagal, Compute Engine akan otomatis memulai ulang instance menggunakan setelan instance, metadata, dan disk booting yang sama. Untuk mengubah
perilaku mulai ulang otomatis instance, lihat
Menetapkan kebijakan pemeliharaan host VM.
Harga
Anda akan ditagih untuk instance komputasi sebagai berikut:
Untuk penggunaan CPU, Anda akan dikenai biaya saat instance berada dalam status berikut:
RUNNING
PENDING_STOP
Untuk penggunaan memori, Anda akan ditagih saat instance berada dalam status berikut:
RUNNING
PENDING_STOP
SUSPENDING
SUSPENDED
Untuk resource terlampir seperti disk atau alamat IP eksternal, Anda akan ditagih
hingga resource tersebut ada, terlepas dari status instance.
[[["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-03 UTC."],[[["\u003cp\u003eCompute Engine instances transition through various states, including \u003ccode\u003ePROVISIONING\u003c/code\u003e, \u003ccode\u003eSTAGING\u003c/code\u003e, \u003ccode\u003eRUNNING\u003c/code\u003e, \u003ccode\u003ePENDING_STOP\u003c/code\u003e, \u003ccode\u003eSTOPPING\u003c/code\u003e, \u003ccode\u003eTERMINATED\u003c/code\u003e, \u003ccode\u003eREPAIRING\u003c/code\u003e, \u003ccode\u003eSUSPENDING\u003c/code\u003e, and \u003ccode\u003eSUSPENDED\u003c/code\u003e, each representing a different stage in the instance lifecycle.\u003c/p\u003e\n"],["\u003cp\u003eUnderstanding the lifecycle states of a Compute Engine instance is crucial for effective troubleshooting, managing resources, and planning instance migrations.\u003c/p\u003e\n"],["\u003cp\u003eInstances in \u003ccode\u003eRUNNING\u003c/code\u003e and \u003ccode\u003ePENDING_STOP\u003c/code\u003e states incur charges for CPU and memory usage, while memory charges also apply during \u003ccode\u003eSUSPENDING\u003c/code\u003e and \u003ccode\u003eSUSPENDED\u003c/code\u003e states, and resources like disks and IP addresses are charged regardless of the instance's current state.\u003c/p\u003e\n"],["\u003cp\u003eCompute Engine automatically restarts failed instances, but this behavior can be modified through the VM host maintenance policy settings.\u003c/p\u003e\n"],["\u003cp\u003eThe shutdown process of an instance may be graceful, provided that the user enabled graceful shutdown, otherwise the instance will be forced to shut down upon request.\u003c/p\u003e\n"]]],[],null,["*** ** * ** ***\n\nThis document explains the lifecycle of a Compute Engine instance, covering\nthe various states it can go through from creation to deletion. To learn how\nto check the state of one or more instances, see the following:\n\n- [View a list of instances](/compute/docs/instances/get-list)\n\n- [View the details of a single instance](/compute/docs/instances/view-vm-details)\n\nBy understanding the lifecycle of an instance, you can do the following more\neffectively:\n\n- Troubleshoot instance issues.\n\n- Manage instance resources.\n\n- Plan instance migrations.\n\nInstance states\n\nA compute instance can transition through different states as part of its\nlifecycle. When creating an instance, Compute Engine provisions\nresources to start it, after which the instance moves into staging and prepares\nfor first boot. After the instance starts, it's considered running. A running\ninstance can be repeatedly stopped and restarted, or suspended and resumed,\nuntil its deletion.\n\nThe following diagram shows the different states that Compute Engine can\nset an instance to:\n\nThe states shown in the preceding diagram are as follows:\n\n- **`PROVISIONING`**: in the first stage of an instance,\n Compute Engine allocates resources for the instance.\n\n- **`STAGING`**: Compute Engine is preparing the instance for first\n boot due to one of the following reasons:\n\n - Compute Engine is still creating and configuring the instance.\n\n - You, or a scheduled operation, have requested to restart or resume the\n instance.\n\n In this state, the instance isn't running yet.\n- **`RUNNING`**: Compute Engine is booting up the instance, or the\n instance is running. In this state, you can stop, suspend, or delete the\n instance. Additionally, Compute Engine can stop or delete the\n instance for scheduled actions, or repair it if the instance is part of\n a managed instance group (MIG) and a hardware error occurs.\n\n- **`PENDING_STOP`** : the instance is gracefully shutting down. This shutdown\n process happens only if you've enabled\n [graceful shutdown](/compute/docs/instances/graceful-shutdown-overview) and\n you've requested to stop or delete the instance, or Compute Engine\n is doing so automatically for a scheduled stop or deletion. The instance\n state changes to `STOPPING` when one of the following happens:\n\n - You manually end the graceful shutdown.\n\n - The graceful shutdown period times out. If any tasks are still running,\n then Compute Engine forcefully stops them.\n\n- **`STOPPING`**: the instance is shutting down its guest OS, which happens in\n the following scenarios:\n\n - You, or a scheduled operation, have requested to stop or delete the\n instance.\n\n - A hardware error occurred.\n\n The shutdown time depends on the\n [instance type](/compute/docs/instances/suspend-stop-reset-instances-overview#stopping-instance);\n however, if the instance is stopping due to a hardware error, the shutdown\n time might vary. After Compute Engine shuts down the guest OS, it\n sets the instance state to `TERMINATED`, and then either completes the stop\n operation or deletes the instance and all attached resources.\n- **`TERMINATED`**: Compute Engine has completed the stop operation.\n The attached resources remain attached unless you detach them. In this\n state, the instance remains stopped until you restart or delete it.\n\n- **`REPAIRING`**: Compute Engine is repairing the instance.\n Compute Engine repairs an instance if it encounters an internal\n error or the instance's host server is unavailable due to maintenance. While\n an instance is in repair, the following happens:\n\n - You can't use it.\n\n - The [service level agreement (SLA)](/compute/sla) doesn't cover it.\n\n If Compute Engine successfully repairs the instance, then it returns\n the instance state to its original state before the repair operation began.\n This state can be `STAGING`, `RUNNING`, `SUSPENDING`, or `STOPPING`.\n- **`SUSPENDING`**: Compute Engine has started the suspend operation\n of the instance after you've requested to suspend it. In this state, you can\n only wait for the suspend operation to complete.\n\n- **`SUSPENDED`** : Compute Engine has completed the suspend operation.\n In this state, you can resume or delete the instance. If an instance remains\n in the `SUSPENDED` state for more than 60 days, then Compute Engine\n stops the instance and transitions its state to `TERMINATED`.\n\nHardware failure\n\nRarely, a compute instance might fail due to an unexpected outage, hardware\nerror, or another system issue. Google recommends mitigating hardware failures\nby using persistent storage volumes, routinely backing up your data, and\ndesigning your system so that a single instance failure isn't catastrophic. For\nmore information, see how to\n[design robust systems](/compute/docs/robustsystems).\n\nIf an instance fails, then Compute Engine automatically restarts the\ninstance using the same boot disk, metadata, and instance settings. To modify\nthe automatic restart behavior of an instance, see\n[Set VM host maintenance policy](/compute/docs/instances/setting-instance-scheduling-options).\n\nPricing\n\nYou're charged for a compute instance as follows:\n\n- For CPU usage, you're charged when the instance is in the following states:\n\n - `RUNNING`\n\n - `PENDING_STOP`\n\n- For memory usage, you're charged when the instance is in the following\n states:\n\n - `RUNNING`\n\n - `PENDING_STOP`\n\n - `SUSPENDING`\n\n - `SUSPENDED`\n\n- For attached resources like disks or external IP addresses, you're charged\n until the resources exist, regardless of the instance state.\n\nFor more information, see [VM instance pricing](/compute/vm-instance-pricing).\n\nWhat's next\n\n- Learn how to view the state of one or more compute instances:\n\n - [Get a list of VMs](/compute/docs/instances/get-list)\n\n - [View the details of a VM](/compute/docs/instances/view-vm-details)\n\n- Learn more about\n [suspending, stopping, or resetting instances](/compute/docs/instances/suspend-stop-reset-instances-overview).\n\n- Learn more about\n [live migration during maintenance events](/compute/docs/instances/live-migration).\n\n- Learn how to\n [delete an instance](/compute/docs/instances/deleting-instance)."]]
