{ "api_version": "1", "kind": "dse_post", "self": "https://update.dsesecurity.com/api/v1/posts/dse-20260908-158-choose-whether-cluster-anti-affinity-should-yield-during-a-node-outage/", "item": { "id": "https://update.dsesecurity.com/updates/dse-20260908-158-choose-whether-cluster-anti-affinity-should-yield-during-a-node-outage/", "slug": "dse-20260908-158-choose-whether-cluster-anti-affinity-should-yield-during-a-node-outage", "url": "https://update.dsesecurity.com/updates/dse-20260908-158-choose-whether-cluster-anti-affinity-should-yield-during-a-node-outage/", "alternate_urls": { "markdown": "https://update.dsesecurity.com/updates/dse-20260908-158-choose-whether-cluster-anti-affinity-should-yield-during-a-node-outage.md", "json": "https://update.dsesecurity.com/api/v1/posts/dse-20260908-158-choose-whether-cluster-anti-affinity-should-yield-during-a-node-outage/" }, "title": "Choose whether cluster anti-affinity should yield during a node outage", "summary": "Should two clustered roles stay separated even when only one node remains available?", "format": { "slug": "guide", "name": "Guide" }, "priority": { "slug": "info", "name": "Information" }, "featured": false, "image": { "theme": "network-infrastructure", "label": "Networks & infrastructure", "alt": "Resilient network core with engineered blue and gold data paths.", "card_url": "https://update.dsesecurity.com/assets/editorial/network-infrastructure-card.webp?v=1.8.20", "hero_url": "https://update.dsesecurity.com/assets/editorial/network-infrastructure-hero.webp?v=1.8.20", "social_url": "https://update.dsesecurity.com/assets/editorial/network-infrastructure-social-v2.jpg?v=1.8.20", "width": 2400, "height": 1350 }, "topics": [ { "slug": "it", "name": "IT", "url": "https://update.dsesecurity.com/topic/it/" }, { "slug": "networks-infrastructure", "name": "Networks & Infrastructure", "url": "https://update.dsesecurity.com/topic/networks-infrastructure/" } ], "author": { "name": "DSE Security Editorial Team", "url": "https://update.dsesecurity.com/#editorial-team", "type": "Organization" }, "publisher": { "name": "Detection Systems & Engineering", "url": "https://dsesecurity.com/" }, "published_at": "2026-09-08T18:14:33+00:00", "modified_at": "2026-09-08T18:26:31+00:00", "reviewed_on": "2026-09-08", "reading_minutes": 1, "word_count": 181, "potentially_affected": "Administrators setting anti-affinity for Windows failover-cluster roles.", "dse_recommendation": "Record that tradeoff before choosing the anti-affinity setting.", "primary_source": { "name": "Cluster affinity", "url": "https://learn.microsoft.com/en-us/windows-server/failover-clustering/Cluster-Affinity", "published_on": null, "authority": "Microsoft Learn" }, "publishing_principles": "https://update.dsesecurity.com/updates/dse-updates-editorial-methodology/", "usage_info": "https://update.dsesecurity.com/usage/", "copyright_notice": "Copyright © 2026 Detection Systems & Engineering. All rights reserved.", "content_html": "

Source facts

\n

Microsoft uses anti-affinity to try to keep selected roles on different nodes. The AntiAffinityClassNames setting is a soft constraint; the documentation also describes enforcing a hard separation. Microsoft warns that, in a two-node configuration with enforced anti-affinity, losing one node means both separated groups cannot run. Microsoft documentation.

\n

Applicability

\n

Identify the roles, their resource demand, available nodes, and service priorities. Ask workload owners whether maintaining separation or keeping both services running should take precedence during reduced capacity.

\n

DSE recommendation

\n

Record that tradeoff before choosing the anti-affinity setting. Name the roles that belong to the same separation class and define the accepted outage behavior. Have the cluster owner review capacity and the application owners approve any intentional loss of service under enforcement.

\n

Verification

\n

Inspect the configured class values and observe placement under normal conditions. In an approved maintenance test, remove one eligible node and compare the resulting role state with the decision. Preserve an unavailable role as an expected or unexpected outcome explicitly; do not equate policy enforcement with application availability.

\n

Official references

\n

Microsoft Learn: Cluster affinity. Source reviewed September 8, 2026.

", "content_text": "Source facts\nMicrosoft uses anti-affinity to try to keep selected roles on different nodes. The AntiAffinityClassNames setting is a soft constraint; the documentation also describes enforcing a hard separation. Microsoft warns that, in a two-node configuration with enforced anti-affinity, losing one node means both separated groups cannot run. Microsoft documentation.\nApplicability\nIdentify the roles, their resource demand, available nodes, and service priorities. Ask workload owners whether maintaining separation or keeping both services running should take precedence during reduced capacity.\nDSE recommendation\nRecord that tradeoff before choosing the anti-affinity setting. Name the roles that belong to the same separation class and define the accepted outage behavior. Have the cluster owner review capacity and the application owners approve any intentional loss of service under enforcement.\nVerification\nInspect the configured class values and observe placement under normal conditions. In an approved maintenance test, remove one eligible node and compare the resulting role state with the decision. Preserve an unavailable role as an expected or unexpected outcome explicitly; do not equate policy enforcement with application availability.\nOfficial references\nMicrosoft Learn: Cluster affinity. Source reviewed September 8, 2026.", "content_markdown": "## Source facts\n\nMicrosoft uses anti-affinity to try to keep selected roles on different nodes. The AntiAffinityClassNames setting is a soft constraint; the documentation also describes enforcing a hard separation. Microsoft warns that, in a two-node configuration with enforced anti-affinity, losing one node means both separated groups cannot run. [Microsoft documentation](https://learn.microsoft.com/en-us/windows-server/failover-clustering/Cluster-Affinity).\n\n## Applicability\n\nIdentify the roles, their resource demand, available nodes, and service priorities. Ask workload owners whether maintaining separation or keeping both services running should take precedence during reduced capacity.\n\n## DSE recommendation\n\nRecord that tradeoff before choosing the anti-affinity setting. Name the roles that belong to the same separation class and define the accepted outage behavior. Have the cluster owner review capacity and the application owners approve any intentional loss of service under enforcement.\n\n## Verification\n\nInspect the configured class values and observe placement under normal conditions. In an approved maintenance test, remove one eligible node and compare the resulting role state with the decision. Preserve an unavailable role as an expected or unexpected outcome explicitly; do not equate policy enforcement with application availability.\n\n## Official references\n\n[Microsoft Learn: Cluster affinity](https://learn.microsoft.com/en-us/windows-server/failover-clustering/Cluster-Affinity). Source reviewed September 8, 2026." }, "json_ld": { "@context": "https://schema.org", "@graph": [ { "@type": "Organization", "@id": "https://dsesecurity.com/#organization", "name": "Detection Systems & Engineering", "alternateName": "DSE Security", "url": "https://dsesecurity.com/", "logo": { "@type": "ImageObject", "url": "https://update.dsesecurity.com/assets/dse-logo-20260812.png?v=1.8.20" } }, { "@type": "Organization", "@id": "https://update.dsesecurity.com/#editorial-team", "name": "DSE Security Editorial Team", "url": "https://update.dsesecurity.com/", "parentOrganization": { "@id": "https://dsesecurity.com/#organization" } }, { "@type": "WebSite", "@id": "https://update.dsesecurity.com/#website", "name": "DSE Updates", "alternateName": "DSE Security Knowledge Hub", "url": "https://update.dsesecurity.com/", "inLanguage": "en-US", "publisher": { "@id": "https://dsesecurity.com/#organization" }, "potentialAction": { "@type": "SearchAction", "target": { "@type": "EntryPoint", "urlTemplate": "https://update.dsesecurity.com/?q={search_term_string}" }, "query-input": "required name=search_term_string" } }, { "@type": "WebPage", "@id": "https://update.dsesecurity.com/updates/dse-20260908-158-choose-whether-cluster-anti-affinity-should-yield-during-a-node-outage/", "url": "https://update.dsesecurity.com/updates/dse-20260908-158-choose-whether-cluster-anti-affinity-should-yield-during-a-node-outage/", "isPartOf": { "@id": "https://update.dsesecurity.com/#website" }, "lastReviewed": "2026-09-08" }, { "@type": "BreadcrumbList", "@id": "https://update.dsesecurity.com/updates/dse-20260908-158-choose-whether-cluster-anti-affinity-should-yield-during-a-node-outage/#breadcrumbs", "itemListElement": [ { "@type": "ListItem", "position": 1, "name": "DSE Updates", "item": "https://update.dsesecurity.com/" }, { "@type": "ListItem", "position": 2, "name": "Choose whether cluster anti-affinity should yield during a node outage", "item": "https://update.dsesecurity.com/updates/dse-20260908-158-choose-whether-cluster-anti-affinity-should-yield-during-a-node-outage/" } ] }, { "@type": [ "Article", "TechArticle" ], "@id": "https://update.dsesecurity.com/updates/dse-20260908-158-choose-whether-cluster-anti-affinity-should-yield-during-a-node-outage/#article", "identifier": "https://update.dsesecurity.com/updates/dse-20260908-158-choose-whether-cluster-anti-affinity-should-yield-during-a-node-outage/", "url": "https://update.dsesecurity.com/updates/dse-20260908-158-choose-whether-cluster-anti-affinity-should-yield-during-a-node-outage/", "headline": "Choose whether cluster anti-affinity should yield during a node outage", "description": "Should two clustered roles stay separated even when only one node remains available?", "abstract": "Should two clustered roles stay separated even when only one node remains available?", "articleBody": "Source facts\nMicrosoft uses anti-affinity to try to keep selected roles on different nodes. The AntiAffinityClassNames setting is a soft constraint; the documentation also describes enforcing a hard separation. Microsoft warns that, in a two-node configuration with enforced anti-affinity, losing one node means both separated groups cannot run. Microsoft documentation.\nApplicability\nIdentify the roles, their resource demand, available nodes, and service priorities. Ask workload owners whether maintaining separation or keeping both services running should take precedence during reduced capacity.\nDSE recommendation\nRecord that tradeoff before choosing the anti-affinity setting. Name the roles that belong to the same separation class and define the accepted outage behavior. Have the cluster owner review capacity and the application owners approve any intentional loss of service under enforcement.\nVerification\nInspect the configured class values and observe placement under normal conditions. In an approved maintenance test, remove one eligible node and compare the resulting role state with the decision. Preserve an unavailable role as an expected or unexpected outcome explicitly; do not equate policy enforcement with application availability.\nOfficial references\nMicrosoft Learn: Cluster affinity. Source reviewed September 8, 2026.", "datePublished": "2026-09-08T18:14:33+00:00", "dateModified": "2026-09-08T18:26:31+00:00", "mainEntityOfPage": { "@id": "https://update.dsesecurity.com/updates/dse-20260908-158-choose-whether-cluster-anti-affinity-should-yield-during-a-node-outage/" }, "inLanguage": "en-US", "isAccessibleForFree": true, "author": { "@type": "Organization", "name": "DSE Security Editorial Team", "url": "https://update.dsesecurity.com/#editorial-team" }, "publisher": { "@id": "https://dsesecurity.com/#organization" }, "image": { "@type": "ImageObject", "@id": "https://update.dsesecurity.com/updates/dse-20260908-158-choose-whether-cluster-anti-affinity-should-yield-during-a-node-outage/#primaryimage", "url": "https://update.dsesecurity.com/assets/editorial/network-infrastructure-social-v2.jpg?v=1.8.20", "contentUrl": "https://update.dsesecurity.com/assets/editorial/network-infrastructure-social-v2.jpg?v=1.8.20", "width": 1200, "height": 630, "caption": "Choose whether cluster anti-affinity should yield during a node outage" }, "articleSection": [ "IT", "Networks & Infrastructure" ], "keywords": [ "IT", "Networks & Infrastructure", "Guide", "Information priority" ], "genre": "Guide", "about": [ { "@type": "Thing", "name": "IT", "url": "https://update.dsesecurity.com/topic/it/" }, { "@type": "Thing", "name": "Networks & Infrastructure", "url": "https://update.dsesecurity.com/topic/networks-infrastructure/" } ], "wordCount": 181, "timeRequired": "PT1M", "publishingPrinciples": "https://update.dsesecurity.com/updates/dse-updates-editorial-methodology/", "usageInfo": "https://update.dsesecurity.com/usage/", "copyrightHolder": { "@id": "https://dsesecurity.com/#organization" }, "copyrightNotice": "Copyright © 2026 Detection Systems & Engineering. All rights reserved.", "citation": { "@type": "CreativeWork", "name": "Cluster affinity", "url": "https://learn.microsoft.com/en-us/windows-server/failover-clustering/Cluster-Affinity" } } ] } }