[[["易于理解","easyToUnderstand","thumb-up"],["解决了我的问题","solvedMyProblem","thumb-up"],["其他","otherUp","thumb-up"]],[["很难理解","hardToUnderstand","thumb-down"],["信息或示例代码不正确","incorrectInformationOrSampleCode","thumb-down"],["没有我需要的信息/示例","missingTheInformationSamplesINeed","thumb-down"],["翻译问题","translationIssue","thumb-down"],["其他","otherDown","thumb-down"]],["最后更新时间 (UTC):2025-09-04。"],[],[],null,["If jobs in Google Distributed Cloud time out and you believe the behavior isn't due to\nan underlying problem with your installation, you can increase the timeout\ninterval. This document describes how to adjust the timeout intervals for\nmachine jobs and batch jobs by using annotations in the config spec.\n\nJob types and errors\n\nThere are two types of Google Distributed Cloud commands and routines: machine\njobs and batch jobs. Many things can affect how long it takes for a job to\ncomplete, such as hardware configuration, network configuration, and cluster\nconfiguration. Google Distributed Cloud has default timeouts that are intended to\naccommodate typical installations.\n\nThe following are example job timeout error messages:\n\n- A machine job timeout error message (wrapped for clarity) from a preflight\n log like\n `bmctl-workspace/cluster1/logs/preflight-20210501-000426/172.18.0.4`:\n\n Pod:172.18.0.4-machine-preflf3a32c8a2f7a2449545c7e8ff954c961-652st\n Result:Failed Reason:DeadlineExceeded Time:Wed Feb 3 16:59:56 2021\n\n- Output from `kubectl logs` for a failed Pod might show a similar\n `DeadlineExceeded` message (wrapped):\n\n cluster-cluster1\n 172.18.0.4-machine-preflf3a32c8a2f7a2449545c7e8ff954c961-652st ● 0/1\n 0 DeadlineExceeded 192.168.122.180 bmctl-control-plane 7m12\n\nAdjust the machine job timeout interval\n\nA machine job is a routine that runs on one machine only, like a preflight check\nthat is confined to a single machine. Google Distributed Cloud machine jobs have\na default timeout of 900 seconds, or 15 minutes. You can adjust the machine job\ntimeout interval with the `baremetal.cluster.gke.io/machine-job-deadline-seconds`\nannotation in the cluster config file.\n\nThe following example sets the machine job timeout interval to 1,800 seconds,\nor 30 minutes: \n\n apiVersion: baremetal.cluster.gke.io/v1\n kind: Cluster\n metadata:\n name: cluster1\n namespace: cluster-cluster1\n annotations:\n baremetal.cluster.gke.io/machine-job-deadline-seconds: \"1800\"\n spec:\n ...\n\nYour timeout interval value is applied when you create new clusters with\n`bmctl create cluster` or when you upgrade existing clusters with `bmctl upgrade\ncluster`. The new interval is used for all single machine jobs, including\n`bmctl check preflight`, `bmctl check -c `\u003cvar translate=\"no\"\u003eCLUSTER_NAME\u003c/var\u003e, and\nmore.\n\nAdjust the batch job timeout interval\n\nA batch job is a routine that runs across multiple machines, like a network\npreflight check. The default timeout interval for Google Distributed Cloud batch\njobs is dependent upon the number of machines in the network. The default\ntimeout interval is 900 seconds, plus an additional 20 seconds for each machine.\n\nFor example, if your batch job runs on 60 machines, the default timeout interval\nis 2,100 seconds (*900 + (20 \\* 60) = 2100*), or 35 minutes.\n\nYou can adjust the batch job timeout interval with the\n`baremetal.cluster.gke.io/batch-job-deadline-seconds` annotation in the cluster\nconfig file.\n\nThe following example sets the batch job timeout interval to 10,800 seconds, or\n3 hours: \n\n apiVersion: baremetal.cluster.gke.io/v1\n kind: Cluster\n metadata:\n name: cluster1\n namespace: cluster-cluster1\n annotations:\n baremetal.cluster.gke.io/batch-job-deadline-seconds: \"10800\"\n spec:\n ...\n\nYour timeout interval value is applied when you create new clusters with\n`bmctl create cluster` or when you upgrade existing clusters with `bmctl upgrade\ncluster`.\n\nWhat's next\n\nIf you need additional assistance, reach out to\n\n[Cloud Customer Care](/support-hub).\nYou can also see\n[Getting support](/kubernetes-engine/distributed-cloud/bare-metal/docs/getting-support) for more information about support resources, including the following:\n\n- [Requirements](/kubernetes-engine/distributed-cloud/bare-metal/docs/getting-support#intro-support) for opening a support case.\n- [Tools](/kubernetes-engine/distributed-cloud/bare-metal/docs/getting-support#support-tools) to help you troubleshoot, such as your environment configuration, logs, and metrics.\n- Supported [components](/kubernetes-engine/distributed-cloud/bare-metal/docs/getting-support#what-we-support)."]]