Menghapus atau memulai ulang instance Looker (Google Cloud core)
Tetap teratur dengan koleksi
Simpan dan kategorikan konten berdasarkan preferensi Anda.
Anda dapat menghapus atau memulai ulang instance Looker (Google Cloud core).
Peran yang diperlukan
Untuk mendapatkan izin yang
diperlukan untuk menghapus atau memulai ulang instance Looker (Google Cloud core),
minta administrator untuk memberi Anda
peran IAM Looker Admin (roles/looker.admin)
di project tempat instance dibuat.
Untuk mengetahui informasi selengkapnya tentang cara memberikan peran, lihat Mengelola akses ke project, folder, dan organisasi.
Anda mungkin juga bisa mendapatkan
izin yang diperlukan melalui peran
khusus atau peran
bawaan lainnya.
Menghapus instance Looker (Google Cloud core)
Penghapusan instance bersifat permanen dan tidak dapat dipulihkan.
Menghapus instance Looker (Google Cloud core) yang dikaitkan dengan langganan Looker Studio Pro akan langsung mengonversi lisensi Looker Studio Pro gratis yang sedang digunakan menjadi lisensi berbayar.
Untuk menghapus instance Looker (Google Cloud core), pilih salah satu opsi berikut:
console
Di halaman Instances, klik menu tiga titik di samping instance.
Pilih Hapus Instance. Jika instance sedang dimodifikasi, Anda tidak akan dapat menghapusnya.
Di jendela pop-up, konfirmasi bahwa Anda ingin menghapus instance dengan mengetik nama instance di kolom yang disediakan, lalu klik DELETE.
Anda juga dapat menghapus instance dari halaman konfigurasinya dengan mengklik HAPUS di kolom ikon halaman konfigurasi instance.
Memulai ulang instance Looker (Google Cloud core) akan menghentikan semua proses Looker yang sedang berjalan di instance — termasuk kueri, jadwal, dan pemberitahuan yang sedang berjalan — lalu memulai ulang instance. Setelah dimulai ulang, instance akan otomatis melanjutkan operasi normalnya. Semua kueri yang berjalan pada saat memulai ulang tidak akan selesai kecuali Anda memulainya kembali. Jadwal dan pemberitahuan akan berjalan sesuai irama yang ditentukan, tetapi tugas apa pun yang dijadwalkan atau yang sedang dijalankan selama memulai ulang tidak akan selesai.
Jika instance sedang dimodifikasi, tunggu hingga instance menyelesaikan pembaruannya sebelum Anda mencoba memulai ulang.
Untuk memulai ulang instance Looker (Google Cloud core), pilih salah satu opsi berikut:
console
Di halaman Instances, klik nama instance untuk melihat setelan konfigurasinya.
Klik RESTART di kolom ikon halaman konfigurasi 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-08-25 UTC."],[],[],null,["# Delete or restart a Looker (Google Cloud core) instance\n\n| **Caution:** Instance deletion is permanent and unrecoverable.\n\nYou can delete or restart a Looker (Google Cloud core) instance.\n\nRequired role\n-------------\n\n\nTo get the permissions that\nyou need to delete or restart a Looker (Google Cloud core) instance,\n\nask your administrator to grant you the\n\n\n[Looker Admin](/iam/docs/roles-permissions/looker#looker.admin) (`roles/looker.admin`)\nIAM role on the project in which the instance was created.\n\n\nFor more information about granting roles, see [Manage access to projects, folders, and organizations](/iam/docs/granting-changing-revoking-access).\n\n\nYou might also be able to get\nthe required permissions through [custom\nroles](/iam/docs/creating-custom-roles) or other [predefined\nroles](/iam/docs/roles-overview#predefined).\n\nDelete a Looker (Google Cloud core) instance\n--------------------------------------------\n\nInstance deletion is permanent and unrecoverable.\n\nDeleting a Looker (Google Cloud core) instance that is [associated with a Looker Studio Pro subscription](/looker/docs/looker-core-lsp) immediately converts any in-use complimentary Looker Studio Pro licenses to paid licenses.\n\nTo delete a Looker (Google Cloud core) instance, select one of the following options: \n\n### console\n\n1. On the **Instances** page, click the three-dot menu beside the instance.\n2. Select **Delete Instance**. If the instance is currently being modified, you will not be able to delete it.\n3. In the pop-up, confirm that you want to delete your instance by typing the instance name in the provided field and clicking **DELETE**.\n\nYou can also delete an instance from its configuration page by clicking **DELETE** in the instance configuration page icon bar.\n\n### gcloud\n\n```\ngcloud looker instances delete INSTANCE_NAME --region=REGION --async\n```\n\nReplace the following:\n\n- \u003cvar translate=\"no\"\u003eINSTANCE_NAME\u003c/var\u003e: the [name](/looker/docs/looker-core-view-console#the_instances_page) of the Looker (Google Cloud core) instance\n- \u003cvar translate=\"no\"\u003eREGION\u003c/var\u003e: the [region](/looker/docs/looker-core-view-console#the_instances_page) the instance was created in\n\nRestart a Looker (Google Cloud core) instance\n---------------------------------------------\n\nRestarting a Looker (Google Cloud core) instance stops any in-process Looker processes on the instance --- including running queries, schedules, and alerts --- and then restarts the instance. Once the restart has been completed, the instance will automatically resume its normal operations. Any queries that were running at the time of restart won't be completed unless you reinitiate them. Schedules and alerts will run on their specified cadence, but any jobs that were scheduled or that were being executed during the restart won't be completed.\n\nIf the instance is currently being modified, wait for it to complete its updates before you attempt a restart.\n\nTo restart a Looker (Google Cloud core) instance, select one of the following options: \n\n### console\n\n1. On the **Instances** page, click the name of the instance to view its configuration settings.\n2. Click **RESTART** in the instance configuration page icon bar.\n\n### gcloud\n\n```\ngcloud looker instances restart INSTANCE_NAME --region=REGION --async\n```\n\nReplace the following:\n\n- \u003cvar translate=\"no\"\u003eINSTANCE_NAME\u003c/var\u003e: the [name](/looker/docs/looker-core-view-console#the_instances_page) of the Looker (Google Cloud core) instance\n- \u003cvar translate=\"no\"\u003eREGION\u003c/var\u003e: the [region](/looker/docs/looker-core-view-console#the_instances_page) the instance was created in\n| **Note:** If your `gcp.restrictTLSCipherSuites` organization policy constraint doesn't include any cipher suites that are in the [MODERN SSL policy profile](/load-balancing/docs/ssl-policies-concepts#defining_an_ssl_policy), Looker will return an error, and the instance restart will fail. Update the policy to resolve the error and restart the instance. See the [Restrict TLS cipher suites](/looker/docs/looker-core-tls-cipher-suites#policy_violations) documentation page for more information.\n\nWhat's next\n-----------\n\n- [Create a Looker (Google Cloud core) instance](/looker/docs/looker-core-instance-create)\n- [Administer a Looker (Google Cloud core) instance from the Google Cloud Google Cloud console](/looker/docs/looker-core-admin-console)\n- [Back up and restore a Looker (Google Cloud core) instance](/looker/docs/looker-core-backup-restore)\n- [Looker (Google Cloud core) admin settings](/looker/docs/looker-core-admin-looker)"]]
