[[["容易理解","easyToUnderstand","thumb-up"],["確實解決了我的問題","solvedMyProblem","thumb-up"],["其他","otherUp","thumb-up"]],[["難以理解","hardToUnderstand","thumb-down"],["資訊或程式碼範例有誤","incorrectInformationOrSampleCode","thumb-down"],["缺少我需要的資訊/範例","missingTheInformationSamplesINeed","thumb-down"],["翻譯問題","translationIssue","thumb-down"],["其他","otherDown","thumb-down"]],["上次更新時間：2025-09-04 (世界標準時間)。"],[[["\u003cp\u003eThe \u003ccode\u003egcloud CLI dataproc clusters diagnose\u003c/code\u003e command helps troubleshoot issues with Dataproc on GKE by gathering and archiving cluster-related data.\u003c/p\u003e\n"],["\u003cp\u003eThe archive file created by the diagnose command contains system metrics like CPU and memory usage for GKE nodes and pods, as well as network and file system status.\u003c/p\u003e\n"],["\u003cp\u003eConfiguration details, including cluster configmap, Kubernetes deployment, and Role-Based Access Control (RBAC) information, are included in the diagnose archive.\u003c/p\u003e\n"],["\u003cp\u003eThe archive file also contains various logs, including agent logs, Spark engine logs, and recent Spark driver job logs.\u003c/p\u003e\n"],["\u003cp\u003eJob and pod-related information, such as JobAttempt and Kubernetes Pod objects, are captured in the archive file for analysis.\u003c/p\u003e\n"]]],[],null,["Dataproc provides a [gcloud CLI dataproc clusters diagnose](/sdk/gcloud/reference/dataproc/clusters/diagnose)\ncommand to help you troubleshoot Dataproc on GKE cluster and job issues. This\ncommand gathers and archives cluster-related configuration files, logs, and outputs\ninto an archive file. and then uploads the archive to the Cloud Storage\nstaging bucket you specified when you\n[created your Dataproc on GKE cluster](/dataproc/docs/guides/dpgke/quickstarts/dataproc-gke-quickstart-create-cluster#create_a_on_cluster).\n\nDiagnose archive file\n\nThe following tables list metrics and other information included in the\n`dataproc clusters diagnose` command archive file.\n\nSystem information\n\n| Item | Archive location |\n|-----------------------------------------------------------------|------------------------------------------------------|\n| **GKE node metrics where virtual Dataproc on GKE pods run:** |\n| - CPU usage - Memory usage | `/system/`\u003cvar translate=\"no\"\u003eNODE_NAME\u003c/var\u003e`.json` |\n| **Network metrics and file system status of running pods:** |\n| - CPU usage - Memory usage - Network status - Filesystem status | `/system/`\u003cvar translate=\"no\"\u003ePOD_NAME\u003c/var\u003e`.json` |\n\nConfiguration information\n\n| Item | Archive location |\n|---------------------------------------------------------------------------------------|------------------------------------------------------------|\n| Cluster configmap | `/conf/configmap` |\n| Kubernetes deployment | `/conf/deployment` |\n| [Role Based Access Control (RBAC)](/kubernetes-engine/docs/how-to/google-groups-rbac) | - `/conf/role` - `/conf/rolebind` - `/conf/serviceaccount` |\n\nLogs\n\n| Item | Archive location |\n|--------------------------------------------------------------------|---------------------------------------------|\n| Agent log | `/logs/agent.log` |\n| Spark engine log | `/logs/sparkengine.log` |\n| Spark driver running and completed job logs over the last 24 hours | `/logs/`\u003cvar translate=\"no\"\u003eDRIVER_ID\u003c/var\u003e |\n\nJob and pod information\n\n| Item | Archive location |\n|-----------------------|------------------|\n| JobAttempt object | `/jobattempts` |\n| Kubernetes Pod object | `/pods` |\n\nWhat's next\n\n- See [Diagnose Dataproc clusters](/dataproc/docs/support/diagnose-command#sharing_the_data_gathered_by_diagnose)."]]
