Meta tags:

Headings (most frequently used words):

the, console, gcloud, deleting, health, check, autohealing, and, up, what, resources, instance, using, for, highly, available, apps, stay, organized, with, collections, save, categorize, content, based, on, your, preferences, objectives, costs, before, you, begin, app, architecture, create, set, web, service, simulate, failures, view, autohealer, history, optional, clean, next, how, probes, demo, webservice, makes, good, project, specific, products, pricing, support, engage, group, template, firewall, rules,

Text of the page (most frequently used words):
the (358), create (167), and (150), for (149), vms (116), #instance (97), health (89), with (76), server (73), you (72), check (69), about (65), cloud (62), troubleshoot (62), google (58), project (55), compute (51), manage (48), set (48), this (46), using (45), delete (45), that (43), disk (43), http (42), group (41), view (40), use (39), mig (38), instances (36), disks (35), configure (34), web (33), managed (33), windows (33), resources (31), from (31), overview (31), performance (30), console (29), select (28), network (28), engine (28), template (27), autohealing (27), reservation (27), gcloud (25), when (25), machine (25), groups (24), default (24), click (24), page (23), webserver (23), can (22), monitor (22), firewall (21), hyperdisk (21), sql (21), your (20), images (20), more (18), load (18), europe (18), west1 (18), configuration (18), demo (18), time (18), startup (18), access (18), enable (18), gpu (18), tutorial (17), allow (17), custom (17), image (17), linux (17), policies (16), checks (16), autohealer (16), delay (16), healthy (16), install (16), regional (16), reservations (16), new (15), unhealthy (15), service (15), roles (15), virtual (15), snapshots (15), ssh (15), recommendations (15), type (14), start (14), app (14), initial (14), internal (14), get (14), number (14), management (14), availability (14), workload (14), creation (14), host (14), apply (14), connect (14), must (13), zone (13), update (13), name (13), path (13), request (13), response (13), bulk (13), microsoft (13), cluster (13), samples (12), status (12), region (12), note (12), multiple (12), how (12), run (12), value (12), venv (12), probes (12), workloads (12), storage (12), sole (12), persistent (12), best (12), action (11), see (11), information (11), highly (11), balancing (11), available (11), templates (11), uses (11), has (11), existing (11), metadata (11), options (11), defines (11), migs (11), based (11), practices (11), stateful (11), all (10), other (10), deleting (10), boot (10), requests (10), back (10), rule (10), addresses (10), deploy (10), high (10), role (10), machines (10), attached (10), migrate (10), add (10), logs (10), zones (10), down (9), rules (9), projects (9), created (9), setting (9), running (9), process (9), wait (9), tcp (9), between (9), enter (9), recovery (9), application (9), licenses (9), tenant (9), openshift (9), shutdown (9), hpc (9), license (8), learn (8), apps (8), applications (8), next (8), following (8), stop (8), operations (8), than (8), make (8), during (8), cli (8), change (8), regions (8), threshold (8), remove (8), permission (8), usage (8), manually (8), import (8), cpu (8), resource (8), login (8), optimize (8), choose (8), disaster (8), agent (8), guest (8), keys (8), h4d (8), flexibility (8), dns (8), optimized (8), tpu (8), started (7), thumb (7), need (7), autoscaling (7), list (7), work (7), after (7), should (7), failures (7), error (7), verify (7), seconds (7), python (7), docs (7), ranges (7), section (7), mode (7), interval (7), data (7), networking (7), commitments (7), benchmark (7), idle (7), scale (7), mysql (7), zonal (7), maintenance (7), snapshot (7), backup (7), events (6), otherwise (6), are (6), send (6), systems (6), what (6), specific (6), plan (6), future (6), finish (6), values (6), one (6), monitoring (6), none (6), again (6), return (6), 500 (6), gunicorn (6), 200 (6), script (6), git (6), python3 (6), bin (6), source (6), timeout (6), failed (6), probe (6), api (6), apis (6), through (6), build (6), security (6), migration (6), updates (6), instant (6), files (6), nested (6), gpus (6), across (6), demand (6), pools (6), failover (6), extension (6), transfer (6), customized (6), spot (6), code (5), github (5), understand (5), under (5), details (5), scalable (5), used (5), then (5), have (5), any (5), command (5), finished (5), health_state (5), instance_template (5), version_name (5), last_error (5), fail (5), local (5), not (5), changes (5), simulate (5), target (5), tags (5), leave (5), location (5), too (5), amount (5), protocol (5), port (5), services (5), latency (5), cross (5), policy (5), account (5), databases (5), accounts (5), errors (5), drivers (5), virtualization (5), nvidia (5), placement (5), node (5), multi (5), modify (5), capacity (5), schedules (5), audit (5), symphony (5), email (5), scripts (5), manager (5), operating (5), enhanced (5), capabilities (5), tenancy (5), restore (5), types (5), control (5), workstation (5), faq (5), flex (5), português (4), español (4), sign (4), support (4), its (4), resilient (4), try (4), top (4), deletion (4), checkbox (4), want (4), quota (4), might (4), these (4), filter (4), indicating (4), rebooting (4), shell (4), ip_address (4), makes (4), stops (4), let (4), address (4), external (4), initialize (4), increase (4), allows (4), indicates (4), timer (4), starts (4), field (4), size (4), 300 (4), apt (4), https (4), pip3 (4), ipv4 (4), drop (4), autoscale (4), advanced (4), less (4), 191 (4), 130 (4), 211 (4), sequential (4), considered (4), pro (4), global (4), owner (4), grant (4), serviceusage (4), required (4), selector (4), selecting (4), resourcemanager (4), perform (4), automatically (4), tools (4), distributed (4), authentication (4), issues (4), ubuntu (4), bandwidth (4), pmu (4), ssd (4), share (4), upgrade (4), live (4), calendar (4), single (4), metrics (4), active (4), clusters (4), containers (4), container (4), database (4), postgresql (4), extensions (4), suspend (4), resize (4), graceful (4), locations (4), plans (4), replication (4), review (4), bound (4), terms (3), products (3), content (3), apache (3), window (3), confirm (3), before (3), help (3), instead (3), com (3), keep (3), only (3), they (3), off (3), repair (3), practice (3), longer (3), takes (3), may (3), free (3), 0zx6 (3), recreating (3), curl (3), connection (3), export (3), copy (3), save (3), green (3), times (3), failure (3), 3600 (3), period (3), servers (3), ready (3), googlecloudplatform (3), requirements (3), protocols (3), ports (3), traffic (3), like (3), busy (3), equal (3), don (3), restart (3), them (3), connections (3), either (3), detect (3), unresponsive (3), same (3), identity (3), provider (3), enabled (3), require (3), iam (3), costs (3), compromised (3), clients (3), guides (3), infrastructure (3), observability (3), analytics (3), automatic (3), troubleshooting (3), encryption (3), serial (3), configurations (3), patterns (3), higher (3), discounts (3), cuds (3), manual (3), balancer (3), prevent (3), testing (3), ibm (3), spectrum (3), deploying (3), prepare (3), deployment (3), rhel (3), environment (3), protect (3), certificates (3), query (3), state (3), disable (3), properties (3), schedule (3), lifecycle (3), design (3), non (3), pool (3), move (3), creating (3), workstations (3), series (3), tpus (3), product (3), 한국어 (2), 日本語 (2), עברית (2), brasil (2), italiano (2), indonesia (2), français (2), américa (2), latina (2), deutsch (2), english (2), our (2), site (2), youtube (2), architecture (2), center (2), getting (2), system (2), pricing (2), problem (2), last (2), updated (2), 2026 (2), utc (2), licensed (2), feedback (2), architectures (2), quickstarts (2), limits (2), such (2), also (2), done (2), deleted (2), separate (2), clean (2), sections (2), turn (2), viewing (2), historical (2), history (2), minimum (2), serving (2), risk (2), possible (2), conservative (2), being (2), restarted (2), real (2), behavior (2), concurrent (2), actions (2), pressing (2), ctrl (2), reports (2), first (2), session (2), take (2), head (2), causes (2), specifically (2), yourself (2), quickly (2), working (2), minute (2), returns (2), column (2), open (2), few (2), minutes (2), grey (2), square (2), checkmark (2), most (2), displays (2), similar (2), browser (2), out (2), expected (2), edit (2), ignores (2), unsuccessful (2), because (2), prevents (2), prematurely (2), receives (2), complete (2), completes (2), succeeds (2), verifying (2), currentaction (2), project_id (2), medium (2), pip (2), clone (2), txt (2), bind (2), daemon (2), chdir (2), include (2), specified (2), targets (2), settings (2), would (2), second (2), long (2), short (2), protects (2), against (2), recreate (2), aggressive (2), good (2), come (2), sure (2), checking (2), succeed (2), waits (2), criteria (2), reduce (2), components (2), without (2), likely (2), already (2), admin (2), serviceusageadmin (2), billing (2), procedure (2), steps (2), removing (2), associated (2), creator (2), which (2), contains (2), projectcreator (2), doesn (2), been (2), granted (2), evaluate (2), scenarios (2), test (2), bring (2), downtime (2), interactive (2), documentation (2), sdk (2), languages (2), frameworks (2), industry (2), solutions (2), hybrid (2), multicloud (2), pipelines (2), hosting (2), development (2), commitment (2), consumption (2), standard (2), full (2), registration (2), sles (2), collecting (2), nodes (2), report (2), arm (2), core (2), rdp (2), general (2), analyze (2), visible (2), cores (2), committed (2), generation (2), underutilized (2), insights (2), utilization (2), globally (2), iis (2), shared (2), reserve (2), autoscaler (2), autoscalers (2), activity (2), kubernetes (2), place (2), directory (2), redis (2), cloning (2), writer (2), always (2), alwayson (2), file (2), volumes (2), authenticate (2), method (2), synchronization (2), switch (2), byol (2), payg (2), byos (2), families (2), guide (2), securing (2), event (2), topology (2), together (2), repairs (2), suspended (2), stopped (2), distribution (2), physical (2), cancel (2), once (2), limit (2), interfaces (2), ipv6 (2), static (2), decrease (2), basic (2), consistent (2), scoped (2), appliances (2), asynchronous (2), throughput (2), encrypt (2), names (2), format (2), mount (2), memory (2), extreme (2), balanced (2), credentials (2), organization (2), user (2), rdma (2), preemptible (2), provisioning (2), models (2), rtx (2), vws (2), constraints (2), accelerator (2), reference (2), technology (2), areas (2), close (2), subscribe, newsletter, third, decade, climate, join, cookies, privacy, tech, twitter, blog, engage, training, certification, release, notes, community, forums, contact, sales, marketplace, easy, easytounderstand, solved, solvedmyproblem, otherup, hard, hardtounderstand, incorrect, sample, incorrectinformationorsamplecode, missing, missingtheinformationsamplesineed, otherdown, tell, except, noted, java, registered, trademark, oracle, affiliates, developers, creative, commons, attribution, building, designing, robust, another, checkboxes, named, individually, dialog, shut, effects, explore, tutorials, reusing, avoid, exceeding, preserve, urls, url, selected, inside, whole, appspot, ids, lost, tasks, document, everything, caution, entire, incurring, charges, describe, operationtype, optional, determine, needed, somewhat, stuck, loop, heal, fast, parameters, explained, mistakenly, there, happens, feel, repeat, exercise, here, some, ideas, statuses, current, life, cycle, successfully, stopping, columns, making, makeunhealthy, dev, null, refused, external_ip_address, bash, variable, external_ip, sessions, installed, show, 4qbx, m5v5, while, sleep, periodically, recent, refresh, clicking, button, tab, opens, navigate, provides, ways, force, taking, consider, adjusting, input, initialization, instancetemplates, healthchecks, scroll, find, automation, expand, reveal, several, sub, appear, launches, stored, was, implemented, repository, two, nor, caught, soon, enough, become, measurably, given, sent, every, generous, five, unexpected, delays, slow, sufficient, ideally, rare, packet, loss, preemptively, mistake, unnecessarily, reducing, bottom, scope, direct, away, distinction, causing, unnecessary, unavailability, users, tip, dependencies, achieve, residency, convenient, passes, success, sends, ssl, categories, webservice, each, deny, includes, installing, init, idp, federated, prefer, line, world, customers, credits, begin, billable, including, witness, objectives, lets, promptly, detects, recreates, served, designed, serve, minimal, crashes, freezes, experience, shows, categorize, preferences, stay, organized, collections, home, operation, renewal, nvme, resizing, common, pay, output, diagnostic, sudoers, screenshots, generate, bug, blackwell, soft, lockups, bus, locks, rescue, inaccessible, dumps, kernel, panic, fstab, suspension, reboots, shutdowns, connectivity, tips, nics, dpdk, improve, resiliency, communication, compact, idpf, interface, irdma, driver, nic, customize, threads, per, sustained, merge, split, extend, renew, purchase, cost, savings, dynamic, overcommit, cpus, floating, reliable, udp, backends, routing, scaling, consuming, consume, combine, cud, sharing, decisions, signals, predictions, organize, labels, replica, states, observe, tensorflow, inference, tensorrt5, learning, monte, carlo, methods, spark, forwarding, others, integrate, clustering, exchange, 2016, sharepoint, strategies, passive, inactive, setups, built, integrations, validation, were, deployed, transition, hammerdb, bucket, aws, ec2, pacemaker, s2d, block, netapp, hot, standby, drbd, client, private, mailjet, mailgun, sendgrid, sending, blue, deployments, lamp, joomla, asp, net, mongodb, flask, terraform, over, mtls, random, generator, virtio, rng, accurate, ntp, append, els, restrictions, packages, deprecate, versions, family, trusted, red, hat, knowledgebase, functionality, risks, vpc, controls, confidential, kek, secure, expiration, shielded, attributes, predefined, handle, notices, faulty, unmanaged, affect, preserved, alternate, fails, repairing, maintain, upgrades, override, selectively, applying, accelerate, outage, rebalance, reenable, proactive, redistribution, shape, distribute, define, info, accidental, spread, rename, reset, resume, referrers, uuid, recover, corrupted, duplicate, clones, alerts, backups, vss, regionally, different, protection, considerations, synchronous, consistency, failback, replicate, provisioned, iops, kms, customer, supplied, symbolic, links, device, ram, attach, additional, exapools, ptr, record, rates, restrict, automate, password, powershell, sac, securely, root, vpn, bastion, iap, networks, within, iso, imported, prerequisites, importing, exporting, own, detach, reattach, constraint, accounting, provision, examples, slurm, reserved, team, slice, slices, adds, deterministic, base, aci, configured, preempted, alternative, ops, logging, subnet, public, gpudirect, ultra, specify, platform, hostname, permissions, office, licensing, premium, strategy, gemini, bare, metal, accelerators, platforms, scores, purpose, discover, skip, main,

Text of the page (random words):
an the expected response time the timeout must be less than or equal to the check interval this protects against unexpected delays like busy instances or a slow network connection check interval this value should be between 1 second and two times the timeout not too long nor too short when a value is too long a failed instance is not caught soon enough when a value is too short the instances and the network can become measurably busy given the high number of health check probes being sent every second set up the web service this tutorial uses a web app that is stored on github if you would like learn more about how the app was implemented see the googlecloudplatform python docs samples github repository to set up the demo web service create an instance template that launches the demo web server on startup then use this instance template to deploy a managed instance group and enable autohealing console create an instance template include a startup script that starts up the demo web server in the google cloud console go to the create instance template page go to create instance template set the name to webserver template in the location section from the region drop down select europe west1 in the machine configuration section for the machine type drop down select e2 medium in the firewall section select the allow http traffic checkbox expand the advanced options section to reveal advanced settings several sub sections appear in the management section find automation and enter the following startup script apt get update apt get y install git python3 pip python3 venv git clone https github com googlecloudplatform python docs samples git python3 m venv venv venv bin pip3 install ur python docs samples compute managed instances demo requirements txt venv bin pip3 install gunicorn venv bin gunicorn bind 0 0 0 0 80 app app daemon chdir python docs samples compute managed instances demo leave default values for the other options click create deploy the web server as a managed instance group in the google cloud console go to the create instance group page go to create instance group set the name to webserver group for instance template select webserver template for region select europe west1 for zone select europe west1 b in the autoscaling section for autoscaling mode select off do not autoscale scroll back to the number of instances field and set it to 3 in the autohealing section do the following in the health check drop down select autohealer check set initial delay to 300 note the initial delay is the number of seconds that a new vm takes to initialize and run its startup script during a vm s initial delay period the mig ignores unsuccessful health checks because the vm might be in the startup process this prevents the mig from prematurely recreating a vm if the health check receives a healthy response during the initial delay it indicates that the startup process is complete and the vm is ready the initial delay timer starts when the vm s currentaction field changes to verifying the timer stops when the set time completes or when a health check succeeds the value of initial delay must be between 0 and 3600 seconds in the console the default value is 300 seconds leave default values for the other options click create create a firewall rule that allows http requests to the web servers in the google cloud console go to the create firewall rule page go to create firewall rule for name enter default allow http for network select default for targets select specified target tags for target tags enter http server for source filter select ipv4 ranges for source ipv4 ranges enter 0 0 0 0 0 to allow access for all ip addresses in protocols and ports select tcp and enter 80 leave default values for the other options click create gcloud create an instance template include a startup script that starts the demo web server gcloud compute instance templates create webserver template instance template region europe west1 machine type e2 medium tags http server metadata startup script apt get update apt get y install git python3 pip python3 venv git clone https github com googlecloudplatform python docs samples git python3 m venv venv venv bin pip3 install ur python docs samples compute managed instances demo requirements txt venv bin pip3 install gunicorn venv bin gunicorn bind 0 0 0 0 80 app app daemon chdir python docs samples compute managed instances demo create a managed instance group gcloud compute instance groups managed create webserver group zone europe west1 b template projects project_id regions europe west1 instancetemplates webserver template size 3 health check projects project_id regions europe west1 healthchecks autohealer check initial delay 300 note the initial delay is the number of seconds that a new vm takes to initialize and run its startup script during a vm s initial delay period the mig ignores unsuccessful health checks because the vm might be in the startup process this prevents the mig from prematurely recreating a vm if the health check receives a healthy response during the initial delay it indicates that the startup process is complete and the vm is ready the initial delay timer starts when the vm s currentaction field changes to verifying the timer stops when the set time completes or when a health check succeeds the value of initial delay must be between 0 and 3600 seconds the default value is 0 create a firewall rule that allows http requests to the web servers gcloud compute firewall rules create default allow http network default allow tcp 80 target tags http server wait a few minutes for the managed instance group to create and verify its vms note if your health checks fail your vms may be taking longer to initialize than expected consider adjusting your initial delay in the google cloud console go to the instance groups page click webserver group click edit under initialization period increase the number of seconds you may input a number from 0 to 3600 click save and wait for the managed instance group to update simulate health check failures to simulate health check failures the demo web server provides ways for you to force a health check failure console navigate to a web server vm in the google cloud console go to the vm instances page go to vm instances for any webserver group vm under the external ip column click the ip address a new tab opens in your web browser if the request times out or the web page is not available wait a minute to let the server finish setting up and try again the demo web server displays a page similar to the following on the demo web page click make unhealthy this causes the web server to fail the health check specifically the web server makes the health path return an http 500 internal server error you can verify this yourself by quickly clicking the check health button this stops working after the autohealer has started rebooting the vm wait for the autohealer to take action in the google cloud console go to the vm instances page go to vm instances wait for the status of the web server vm to change the green checkmark next to the vm name should change to a grey square indicating that the autohealer has started rebooting the unhealthy vm click refresh at the top of the page periodically to get the most recent status the autohealing process is finished when the grey square changes back to a green checkmark indicating the vm is healthy again gcloud monitor the status of the managed instance group when you have finished stop by pressing ctrl c while do gcloud compute instance groups managed list instances webserver group zone europe west1 b sleep 5 wait for 5 seconds done name webserver group 0zx6 zone europe west1 b status running health_state healthy action none instance_template webserver template version_name last_error name webserver group 4qbx zone europe west1 b status running health_state healthy action none instance_template webserver template version_name last_error name webserver group m5v5 zone europe west1 b status running health_state healthy action none instance_template webserver template version_name last_error all vms in the group must show status running and action none if not wait a few minutes to let the vms finish setting up and try again open a new cloud shell session with the google cloud cli installed note if you re using cloud shell you can open multiple sessions get the address of a web server vm gcloud compute instances list filter webserver group under the external_ip column copy the ip address of any web server vm and save it as a local bash variable export ip_address external_ip_address verify the web server has finished setting up the server returns an http 200 ok response curl head ip_address health http 1 1 200 ok server gunicorn if you get a connection refused error wait a minute to let the server finish setting up and try again make the web server unhealthy curl ip_address makeunhealthy dev null this causes the web server to fail the health check specifically the web server makes the health path return an http 500 internal server error you can verify this yourself by quickly making a request to health this stops working after the autohealer has started rebooting the vm curl head ip_address health http 1 1 500 internal server error server gunicorn return to your first shell session to monitor the managed instance group and wait for the autohealer to take action when the autohealing process has started the status and action columns update indicating that the autohealer has started rebooting the unhealthy vm name webserver group 0zx6 zone europe west1 b status stopping health_state unhealthy action recreating instance_template webserver template version_name last_error the autohealing process has finished when the vm again reports a status of running and an action of none indicating the vm is successfully restarted name webserver group 0zx6 zone europe west1 b status running health_state healthy action none instance_template webserver template version_name last_error when you have finished monitoring the managed instance group stop by pressing ctrl c note for more information about possible vm statuses and actions see instance life cycle and current actions on instances feel free to repeat this exercise here are some ideas what happens if you make all vms unhealthy at one time for more information about autohealing behavior during concurrent failures see autohealing behavior can you update the health check configuration to heal vms as fast as possible in practice you should set the health check parameters to use conservative values as explained in this tutorial otherwise you may risk vms being mistakenly deleted and restarted when there is no real problem the managed instance group has an initial delay configuration setting can you determine the minimum delay needed for this demo web server in practice you should set the delay to somewhat longer 10 20 than it takes for a vm to boot and start serving app requests otherwise you risk the vm getting stuck in an autohealing boot loop view autohealer history optional to view a history of autohealer operations use the following gcloud command gcloud compute operations list filter operationtype compute instances repair for more information see viewing historical autohealing operations clean up after you finish the tutorial you can clean up the resources that you created so that they stop using quota and incurring charges the following sections describe how to delete or turn off these resources if you created a separate project for this tutorial delete the entire project otherwise if the project has resources that you want to keep only delete the specific resources created in this tutorial deleting the project caution deleting a project has the following effects everything in the project is deleted if you used an existing project for the tasks in this document when you delete it you also delete any other work you ve done in the project custom project ids are lost when you created this project you might have created a custom project id that you want to use in the future to preserve the urls that use the project id such as an appspot com url delete selected resources inside the project instead of deleting the whole project if you plan to explore multiple architectures tutorials or quickstarts reusing projects can help you avoid exceeding project quota limits in the google cloud console go to the manage resources page go to manage resources in the project list select the project that you want to delete and then click delete in the dialog type the project id and then click shut down to delete the project deleting specific resources if you can t delete the project used for this tutorial delete the tutorial resources individually deleting the instance group console in the google cloud console go to the instance groups page go to instance groups select the checkbox for your webserver group instance group to delete the instance group click delete delete gcloud gcloud compute instance groups managed delete webserver group zone europe west1 b q deleting the instance template note you must delete the managed instance group before deleting the instance template you can t delete an instance template if a managed instance group uses it console in the google cloud console go to the instance templates page go to instance templates click the checkbox next to the instance template click delete delete at the top of the page in the new window click delete to confirm the deletion gcloud gcloud compute instance templates delete webserver template q region europe west1 deleting the health check note you must delete the managed instance group before deleting the health check you can t delete a health check if other resources use it console in the google cloud console go to the health checks page go to health checks click the checkbox next to the health check click delete delete at the top of the page in the new window click delete to confirm the deletion gcloud gcloud compute health checks delete autohealer check q region europe west1 deleting the firewall rules console in the google cloud console go to the firewall rules page go to firewall rules click the checkboxes next to the firewall rules named default allow http and default allow http health check click delete delete at the top of the page in the new window click delete to confirm the deletion gcloud gcloud compute firewall rules delete default allow http default allow http health check q what s next try another tutorial using load balancing for highly available applications using autoscaling for highly scalable applications learn more about managed instance groups learn more about designing robust systems learn more about building scalable and resilient web apps on google cloud send feedback except as otherwise noted the content of this page is licensed under the creative commons attribution 4 0 license and code samples are licensed under the apache 2 0 licen...