Looker(Google Cloud 핵심 서비스) 인스턴스를 삭제하거나 다시 시작할 수 있습니다.
필요한 역할
Looker(Google Cloud 핵심 서비스) 인스턴스를 삭제하거나 다시 시작하는 데 필요한 권한을 얻으려면 관리자에게 인스턴스가 생성된 프로젝트에 대한 Looker 관리자(roles/looker.admin) IAM 역할을 부여해 달라고 요청하세요.
역할 부여에 대한 자세한 내용은 프로젝트, 폴더, 조직에 대한 액세스 관리를 참조하세요.
Looker(Google Cloud 핵심 서비스) 인스턴스를 다시 시작하면 쿼리, 일정, 알림 등 인스턴스에서 진행 중인 Looker 프로세스가 중지된 후 인스턴스가 다시 시작됩니다. 다시 시작이 완료되면 인스턴스가 자동으로 정상 작동을 재개합니다. 다시 시작할 때 실행 중이었던 모든 쿼리는 다시 시작하지 않는 한 완료되지 않습니다. 일정 및 알림은 지정된 주기에 따라 실행되지만 다시 시작하는 동안 예약되었거나 실행 중이었던 모든 작업은 완료되지 않습니다.
인스턴스가 현재 수정 중인 경우 업데이트가 완료될 때까지 기다린 후에 다시 시작합니다.
Looker(Google Cloud 핵심 서비스) 인스턴스를 다시 시작하려면 다음 옵션 중 하나를 선택합니다.
[[["이해하기 쉬움","easyToUnderstand","thumb-up"],["문제가 해결됨","solvedMyProblem","thumb-up"],["기타","otherUp","thumb-up"]],[["이해하기 어려움","hardToUnderstand","thumb-down"],["잘못된 정보 또는 샘플 코드","incorrectInformationOrSampleCode","thumb-down"],["필요한 정보/샘플이 없음","missingTheInformationSamplesINeed","thumb-down"],["번역 문제","translationIssue","thumb-down"],["기타","otherDown","thumb-down"]],["최종 업데이트: 2024-12-22(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)"]]
