Meta tags:
Headings (most frequently used words):
stateful, instance, and, workloads, what, configuration, managed, groups, stay, organized, with, collections, save, categorize, content, based, on, your, preferences, how, are, different, from, stateless, when, to, use, migs, makes, mig, feedback, next, policy, per, configurations, example, of, products, pricing, support, resources, engage,
Text of the page (most frequently used words):
the (147), and (146), #instance (121), create (119), vms (112), stateful (102), for (101), with (92), about (66), mig (66), disk (64), troubleshoot (62), disks (58), configuration (54), manage (46), using (41), from (39), server (39), view (38), configure (37), you (34), use (33), windows (33), overview (32), set (31), instances (30), compute (30), performance (30), workloads (29), cloud (28), google (27), reservation (27), migs (26), machine (26), managed (25), that (25), metadata (24), engine (24), data (23), network (22), sql (22), groups (21), your (21), image (21), per (21), hyperdisk (21), policy (20), monitor (20), images (20), workload (19), linux (19), boot (18), custom (18), addresses (18), can (18), application (18), gpu (18), resources (17), template (17), node (17), stateless (17), apply (17), access (17), policies (16), persistent (16), creation (16), applications (16), reservations (16), snapshots (15), ssh (15), recommendations (15), are (14), existing (14), cluster (14), host (14), load (14), virtual (14), connect (14), example (13), name (13), attached (13), regional (13), availability (13), management (13), bulk (13), microsoft (13), type (12), configurations (12), zones (12), delete (12), storage (12), sole (12), best (12), migrate (11), names (11), when (11), specific (11), add (11), group (11), updates (11), multiple (11), machines (11), based (11), practices (11), all (10), autohealing (10), new (10), start (10), zonal (10), update (10), logs (10), support (9), how (9), key (9), preserve (9), state (9), choose (9), available (9), dns (9), service (9), mysql (9), multi (9), scale (9), high (9), recovery (9), licenses (9), tenant (9), openshift (9), shutdown (9), time (9), hpc (9), license (8), after (8), remove (8), must (8), manually (8), deploy (8), zone (8), import (8), cpu (8), resource (8), login (8), optimize (8), internal (8), install (8), disaster (8), agent (8), guest (8), keys (8), h4d (8), flexibility (8), optimized (8), tpu (8), events (7), thumb (7), more (7), its (7), work (7), value (7), app (7), additional (7), legacy (7), items (7), uses (7), device (7), defines (7), defined (7), such (7), across (7), databases (7), highly (7), networking (7), commitments (7), startup (7), balancing (7), benchmark (7), enable (7), idle (7), request (7), back (7), maintenance (7), templates (7), snapshot (7), backup (7), send (6), learn (6), creating (6), become (6), adding (6), default (6), replication (6), postgresql (6), deployments (6), operations (6), between (6), build (6), usage (6), security (6), migration (6), instant (6), files (6), nested (6), gpus (6), mode (6), demand (6), pools (6), run (6), failover (6), extension (6), change (6), transfer (6), customized (6), spot (6), code (5), samples (5), see (5), understand (5), need (5), details (5), feedback (5), share (5), recreated (5), common (5), one (5), because (5), each (5), not (5), removing (5), changes (5), size (5), updating (5), have (5), automatically (5), non (5), review (5), failure (5), autoscaling (5), number (5), database (5), monitoring (5), accounts (5), errors (5), future (5), drivers (5), virtualization (5), nvidia (5), placement (5), modify (5), capacity (5), schedules (5), audit (5), symphony (5), options (5), email (5), scripts (5), manager (5), operating (5), systems (5), enhanced (5), capabilities (5), stop (5), tenancy (5), restore (5), regions (5), types (5), control (5), workstation (5), faq (5), flex (5), português (4), español (4), other (4), down (4), information (4), this (4), apache (4), pairs (4), preserves (4), individual (4), xyz273 (4), attaches (4), them (4), specified (4), treats (4), according (4), auto (4), created (4), interfaces (4), make (4), rolling (4), recreation (4), preserved (4), resilient (4), deploying (4), running (4), services (4), scalable (4), web (4), automatic (4), tools (4), distributed (4), authentication (4), issues (4), ubuntu (4), console (4), bandwidth (4), tcp (4), pmu (4), local (4), ssd (4), get (4), projects (4), upgrade (4), live (4), cross (4), region (4), requests (4), calendar (4), single (4), metrics (4), health (4), active (4), clusters (4), containers (4), container (4), extensions (4), suspend (4), location (4), resize (4), graceful (4), locations (4), plans (4), bound (4), terms (3), last (3), updated (3), content (3), configuring (3), want (3), sets (3), has (3), before (3), recreates (3), standard (3), following (3), treat (3), those (3), unique (3), don (3), specify (3), include (3), only (3), recreate (3), method (3), optional (3), verify (3), setting (3), serving (3), fully (3), level (3), elasticsearch (3), cassandra (3), functionality (3), event (3), address (3), consider (3), mongodb (3), like (3), improve (3), automated (3), scaling (3), different (3), guides (3), infrastructure (3), observability (3), analytics (3), troubleshooting (3), encryption (3), pro (3), serial (3), patterns (3), higher (3), discounts (3), cuds (3), manual (3), autoscale (3), balancer (3), prevent (3), project (3), list (3), testing (3), ibm (3), spectrum (3), perform (3), plan (3), during (3), prepare (3), deployment (3), rhel (3), environment (3), protect (3), certificates (3), query (3), disable (3), properties (3), account (3), increase (3), schedule (3), lifecycle (3), design (3), pool (3), move (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), sign (2), our (2), site (2), youtube (2), center (2), started (2), system (2), pricing (2), products (2), 2026 (2), utc (2), page (2), licensed (2), under (2), read (2), preserving (2), what (2), next (2), team (2), been (2), also (2), version (2), pair (2), deleting (2), then (2), debian (2), gnu (2), recreating (2), config (2), effective (2), creates (2), generated (2), configured (2), specifies (2), attach (2), which (2), individually (2), dynamic (2), treated (2), interface (2), proactive (2), note (2), affect (2), states (2), applied (2), applies (2), empty (2), continue (2), requirements (2), replicate (2), replicas (2), long (2), computation (2), failed (2), while (2), batch (2), checkpointing (2), they (2), monolith (2), servers (2), kafka (2), deciding (2), focus (2), processing (2), deal (2), spark (2), preservable (2), including (2), where (2), scratch (2), care (2), any (2), horizontally (2), deleted (2), frontend (2), built (2), identity (2), require (2), deletion (2), examples (2), restart (2), resiliency (2), documentation (2), sdk (2), languages (2), frameworks (2), costs (2), industry (2), solutions (2), hybrid (2), multicloud (2), pipelines (2), hosting (2), development (2), quota (2), commitment (2), consumption (2), full (2), registration (2), sles (2), export (2), port (2), collecting (2), nodes (2), report (2), arm (2), core (2), api (2), rdp (2), general (2), latency (2), analyze (2), visible (2), cores (2), committed (2), generation (2), underutilized (2), insights (2), utilization (2), globally (2), iis (2), external (2), shared (2), reserve (2), autoscaler (2), autoscalers (2), activity (2), kubernetes (2), provider (2), place (2), directory (2), redis (2), cloning (2), writer (2), always (2), alwayson (2), file (2), volumes (2), authenticate (2), synchronization (2), global (2), switch (2), byol (2), payg (2), byos (2), families (2), guide (2), securing (2), simulate (2), topology (2), together (2), repairs (2), repair (2), check (2), failures (2), suspended (2), stopped (2), target (2), distribution (2), physical (2), cancel (2), once (2), limit (2), ipv6 (2), static (2), decrease (2), basic (2), consistent (2), scoped (2), copy (2), appliances (2), asynchronous (2), throughput (2), encrypt (2), format (2), mount (2), memory (2), extreme (2), balanced (2), credentials (2), organization (2), user (2), through (2), advanced (2), rdma (2), preemptible (2), provisioning (2), models (2), rtx (2), vws (2), constraints (2), accelerator (2), apis (2), reference (2), technology (2), areas (2), close (2), subscribe, newsletter, third, decade, climate, action, join, cookies, privacy, tech, twitter, blog, engage, training, certification, architecture, getting, github, status, release, notes, community, forums, contact, sales, marketplace, easy, easytounderstand, solved, problem, solvedmyproblem, otherup, hard, hardtounderstand, incorrect, sample, incorrectinformationorsamplecode, missing, missingtheinformationsamplesineed, otherdown, tell, except, otherwise, noted, java, registered, trademark, oracle, affiliates, developers, creative, commons, attribution, working, cases, challenges, invite, discuss, com, detaches, first, deletes, original, assuming, same, still, three, two, isn, does, named, individuality, chart, here, supported, detached, however, ips, item, updater, replacement, takes, combination, subsequent, decreasing, abandoning, inspecting, whether, convert, considered, makes, computing, meets, limitations, achieve, resilience, against, redundant, relying, served, remaining, checkpointed, results, anticipation, preemption, checkpoint, these, store, rely, values, teamcity, jenkins, bamboo, flink, tasks, dataflow, zookeeper, intended, whenever, would, simplify, controlling, allowed, disruption, orchestrating, rollouts, features, horizontal, interchangeable, differently, than, another, quickly, replace, ones, lost, machinery, cannot, easily, could, shards, changing, overall, both, difference, shard, retain, describes, provides, uptime, computations, save, categorize, preferences, stay, organized, collections, home, concurrent, operation, renewal, nvme, resizing, pay, viewing, output, diagnostic, sudoers, screenshots, generate, bug, blackwell, soft, lockups, bus, locks, rescue, inaccessible, dumps, kernel, panic, fstab, unresponsive, suspension, reboots, shutdowns, connectivity, tips, nics, dpdk, communication, reduce, compact, idpf, irdma, driver, nic, customize, threads, sustained, merge, split, extend, renew, without, purchase, cost, savings, overcommit, cpus, floating, reliable, udp, backends, routing, https, consuming, consume, combine, cud, allow, sharing, decisions, signals, predictions, organize, labels, replica, observe, reports, tensorflow, inference, tensorrt5, learning, monte, carlo, methods, forwarding, others, integrate, clustering, exchange, 2016, sharepoint, strategies, passive, inactive, setups, integrations, validation, were, deployed, transition, test, hammerdb, bucket, aws, ec2, pacemaker, s2d, block, netapp, hot, standby, drbd, architectures, client, private, mailjet, mailgun, sendgrid, sending, blue, green, lamp, joomla, asp, net, interactive, flask, terraform, over, mtls, random, generator, virtio, rng, accurate, protocol, ntp, append, els, restrictions, packages, deprecate, versions, family, trusted, red, hat, knowledgebase, risks, command, vpc, controls, confidential, kek, secure, expiration, shielded, attributes, predefined, handle, notices, process, faulty, unmanaged, turn, off, alternate, fails, repairing, maintain, click, upgrades, override, selectively, applying, accelerate, out, outage, rebalance, reenable, redistribution, shape, distribute, define, info, accidental, spread, edit, rename, reset, resume, referrers, source, uuid, recover, corrupted, duplicate, clones, alerts, backups, vss, regionally, protection, considerations, synchronous, consistency, failback, provisioned, iops, limits, evaluate, settings, help, kms, customer, supplied, symbolic, links, practice, ram, exapools, ptr, record, rates, tags, restrict, automate, password, powershell, sac, securely, apps, root, vpn, bastion, iap, connection, browser, connections, networks, within, iso, imported, prerequisites, importing, exporting, bring, own, path, detach, reattach, constraint, accounting, provision, slurm, reserved, slice, slices, adds, scenarios, deterministic, base, ready, aci, preempted, historical, alternative, similar, displays, ops, logging, subnet, public, gpudirect, enabled, ultra, minimum, platform, hostname, quickstarts, iam, roles, permissions, office, licensing, premium, strategy, gemini, bare, metal, accelerators, platforms, scores, purpose, discover, free, skip, main,
Text of the page (random words):
shoot general tips troubleshoot connectivity troubleshoot rdp troubleshoot ssh troubleshoot os login troubleshoot vms troubleshoot vm operations troubleshoot vm creation troubleshoot resource availability errors troubleshoot bulk api vm creation troubleshoot vm reboots and shutdowns troubleshoot vm suspension troubleshoot vm updates troubleshoot unresponsive vms troubleshoot vm startup troubleshoot fstab errors troubleshoot kernel panic collecting core dumps rescue an inaccessible vm troubleshoot cpu bus locks troubleshoot cpu soft lockups troubleshoot vm configurations troubleshoot arm vms troubleshoot gpu vms troubleshoot nvidia gpu errors generate a nvidia bug report for blackwell gpus troubleshoot nested virtualization troubleshoot using vm screenshots troubleshoot sole tenant nodes troubleshoot vm performance issues troubleshoot sudoers files troubleshoot windows vms troubleshoot windows vms collecting diagnostic information troubleshoot using the serial console troubleshoot using the serial console viewing serial port output troubleshoot instance groups troubleshoot managed instance groups migs troubleshoot os management troubleshoot licenses troubleshoot image import and export troubleshooting sles pay as you go registration troubleshooting ubuntu pro registration troubleshoot metadata server troubleshoot metadata server troubleshoot networking issues troubleshoot common networking issues troubleshoot network drivers troubleshoot vm performance issues troubleshoot storage troubleshoot disk creation troubleshoot full disks and disk resizing troubleshoot disk encryption troubleshoot nvme disks troubleshoot instant snapshots troubleshoot standard snapshots troubleshoot reservations and commitments troubleshoot reservation creation troubleshoot reservation consumption troubleshooting reservation monitoring troubleshoot reservation updates troubleshoot future reservation creation and updates troubleshoot automatic commitment renewal troubleshoot quota errors troubleshoot concurrent operation quota errors troubleshoot workload authentication troubleshoot default service accounts troubleshoot workload to workload authentication ai and ml application development application hosting compute data analytics and pipelines databases distributed hybrid and multicloud industry solutions migration networking observability and monitoring security storage access and resources management costs and usage management infrastructure as code sdk languages frameworks and tools home documentation compute compute engine guides send feedback stateful managed instance groups stay organized with collections save and categorize content based on your preferences you can build highly available deployments of stateful workloads on vm instances using stateful managed instance groups stateful migs stateful workloads include applications with stateful data or configurations such as databases legacy monolith applications and long running batch computations with checkpointing with stateful migs you can improve the uptime and resiliency of such stateful applications with autohealing automatic recovery of failed workloads multi zone deployments and automated rolling updates a stateful managed instance group preserves the unique state of each instance including instance name attached persistent disks ip addresses and metadata on vm restart recreation autohealing or update this page describes when to use stateful migs and provides a high level overview of how they work for more information see how stateful migs work to learn how to set up a stateful mig see configuring stateful migs how stateful workloads are different from stateless workloads you can use managed instance groups to support both stateful and stateless workloads the key difference between stateful and stateless workloads is that stateful workloads preserve individual vm state for example a database shard or app configuration on the vm s disks while stateless workloads like a web frontend don t retain any state on the individual vms you treat vms with stateful workloads like custom built machinery you care about vm identity name ip address metadata and data on each individual machine you cannot easily scale stateful workloads horizontally because scaling could require data replication creation or deletion of data shards or changing the overall application configuration when recreating or updating a machine with a stateful workload you must preserve the vm s unique state examples of stateful applications include cassandra elasticsearch mongodb mysql postgresql and kafka you treat vms with stateless workloads as interchangeable and only care about the number of serving vms that you have no one vm is treated any differently than another you can quickly scale stateless workloads horizontally by adding or removing vms when updating your application you can delete machines and replace them with new ones with different names ip addresses metadata and disks when a stateless vm is deleted or recreated all data on the machine is lost the disks are deleted or recreated from scratch a web frontend is an example of a stateless application stateful mig stateless mig workload stateful workloads where disks ip addresses and or metadata are preserved on vm recreate operations highly available and scalable stateless workloads where disks and ip addresses are recreated from scratch on horizontal scaling autohealing auto updating and vm recreation mig features autohealing automated rolling updates multi zone deployments autohealing automated rolling updates multi zone deployments autoscaling preservable items instance names persistent disks including support for disks that are not defined in the instance template instance specific metadata ip addresses instance names all migs support custom and preservable instance names when to use stateful migs consider using stateful managed instance groups stateful migs whenever you deploy a stateful application or cluster to compute engine and would like to improve its availability with autohealing and multi zone deployments or you want to simplify updates of stateful instances by orchestrating update rollouts and controlling the allowed level of disruption to the instances stateful migs are intended for applications with stateful data or configuration such as databases for example cassandra elasticsearch mongodb and zookeeper before deciding on stateful migs consider using fully managed services for example mysql and postgresql are available in cloud sql to focus on your applications and not have to deal with vms data processing applications for example kafka and flink before deciding on stateful migs consider using fully managed services for example dataflow or managed service for apache spark to focus on your data processing tasks and not have to deal with vms other stateful applications for example teamcity jenkins bamboo dns servers with stateful ip address and custom stateful workloads legacy monolith applications these applications store application state on a boot disk or additional persistent disks or they rely on stateful configuration such as specific vm instance names ip addresses or metadata key values batch workloads with checkpointing with this configuration you can preserve checkpointed results of long running computation in anticipation of workload or vm failure or instance preemption stateful migs can recreate a failed machine while preserving its data disk so that your computation can continue from the last checkpoint to achieve resilience against zonal failure your application must replicate data across multiple instances at the application level for example elasticsearch and cassandra support such functionality you can use a regional mig to make such an application resilient to zonal failure by deploying redundant replicas to multiple zones and relying on your application s data replication functionality in the event of a zonal failure your data is served from available replicas in the remaining zones review the limitations to verify if a stateful mig fully meets your requirements note your workload must start automatically on vm boot so that it can continue serving or computing after autohealing auto updating and instance recreation events what makes a mig stateful a mig is considered stateful if you have created a stateful configuration you can create a stateful configuration when you create your mig or you can convert a group from stateless to stateful after its creation by adding a configuration you create a stateful configuration by setting a non empty stateful policy or one or more non empty per instance configurations a stateful policy defines items that you want to preserve for all instances in your mig a per instance configuration defines items to preserve for a specific vm instance the configuration is effective after you or the mig applies it a mig automatically applies your stateful policy configuration to new and existing instances when creating or updating per instance configurations you can choose whether to apply the new configuration manually or have it applied automatically after the stateful configuration stateful policy or per instance configurations is applied you can verify it by inspecting the preserved state of each managed instance subsequent changes to your mig s stateful configuration or size for example decreasing the mig s size or deleting or abandoning instances from the mig can affect the preserved states of the instances stateful configuration a stateful managed instance group mig takes its instance configuration from a combination of the instance template optional all instances configuration optional stateful policy and optional per instance configurations that you set after you set the configuration for your group the mig uses that configuration when creating vms to apply an updated configuration to existing vms see apply new vm configurations in a mig note if you only need to preserve vm instance names you don t need to configure a stateful policy or per instance configurations migs preserve instance names on recreation and on autohealing by default for proactive rolling updates to preserve instance names you must set the updater replacement method to recreate stateful policy a stateful policy defines common stateful items for all instances in a managed instance group each item that you include in the stateful policy must be defined in the mig s instance template you can make the following changes to a stateful policy configure disks to become stateful by adding them to the stateful policy configure disks to become stateless by removing them from the stateful policy specify that ip addresses must be stateful by adding network interface configuration to the stateful policy specify that ip addresses must be treated as stateless by removing the configuration from stateful policy per instance configurations a per instance configuration defines stateful items that are unique for a specific managed instance such as instance specific disks metadata key value pairs and ip addresses instance specific metadata and disks don t need to be defined in the mig s instance template however network interfaces for stateful ips must be defined in the mig s instance template you can make the following changes to a per instance configuration for a specific instance in a mig configure disks that are defined in the instance template to become stateful for the instance by adding those disks to the per instance configuration or to become stateless by removing those disks from the per instance configuration configure existing disks not defined in the instance template to be attached and become stateful for the instance by adding those disks to the per instance configuration or to be detached from the instance removing disks from the per instance configuration add or remove stateful metadata key value pairs that are specific to the instance configuring ip addresses individually for instances in a mig to become stateful or stateless per instance configurations for ip addresses are not supported for dynamic network interfaces example of stateful configuration here is an example of a stateful configuration in this chart the instance template defines a common configuration for all vm instances in a mig the stateful policy defines a common stateful configuration for disks with device name data disk which are defined by the instance template and which are created and attached individually to each vm instance in the mig the per instance configuration defines a stateful configuration for a specific vm instance named node 1 it specifies to attach an existing disk my legacy 1 to the node 1 instance and treat it as stateful it also specifies one metadata key value to preserve individuality for the node 1 instance node id xyz273 when creating the node 1 vm the mig does the following uses the n2 standard 2 machine type according to the instance template creates and attaches a boot disk with an auto generated disk name boot node 1 and device name boot disk using a debian gnu linux image according to the instance template the mig treats the boot node 1 boot disk as stateless because it isn t configured in the stateful policy or in the per instance configuration creates and attaches an additional disk with an auto generated disk name data disk 1 and device name data disk using a custom image according to the instance template the mig treats the data disk 1 additional disk as stateful because its device name is specified in the stateful policy attaches an existing disk with the disk name my legacy 1 and uses device name legacy disk according to the per instance configuration the mig treats the my legacy 1 additional disk as stateful because its device name is specified in the per instance configuration sets three metadata key value pairs two from the instance template app example stateful app version 1 0 and one from the per instance config node id xyz273 the mig treats the node id xyz273 key value pair as stateful because it is specified in the per instance configuration when recreating the node 1 vm assuming the same config is still effective the mig recreates the stateless items and preserves the stateful items recreates the boot disk from the original image first it deletes the boot node 1 boot disk and then it recreates it from the debian gnu linux image as specified in the instance template preserves additional disks data disk 1 and my legacy 1 detaches the additional disks before deleting the vm and then attaches them to the vm after it has been recreated preserves the individual metadata key value pair node id xyz273 sets the metadata after the vm has been recreated also sets the common key value pairs from the instance template app example stateful app and version 1 0 feedback we want to learn about your use cases challenges and feedback about stateful migs we invite you to share your feedback with our team at mig discuss google com what s next...
|
