blocks|key|2282062|text|如文档所述，Placements是那些应用程序(如果需要在实例之间使用最快的网络速度)的组，因此实例不能跨越可用性区域。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|2282063|然而，仅仅因为您在布局组中有一些机器，并不意味着您也不能在另一个放置组中拥有一组重复的机器，在一个单独的AZ中，甚至在一个单独的区域中，以满足您的DR+/冗余需求。|2282064|entityMap^0|0|0^^$0|@$1|2|3|4|5|6|7|F|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|G|8|@]|9|@]|A|$]]|$1|D|3|-4|5|6|7|H|8|@]|9|@]|A|$]]]|E|$]]

Placements groups, as the documentation states, is for those applications were it needs the fastest possible network speeds between your instances, and because of that the instances can't span availability zones.

However, just because you have some of you machines in a placement group doesn't mean you can't also have a duplicate set of machines in another placement group in a separate AZ or even a separate region for your DR / redundancy needs.

blocks|key|2282088|text|放置组是一组物理上接近的服务器组，通过10个GBE网络(可能是Intel+x+540-t2)连接。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|2282089|这组服务器都将与10+all网络互联。下一个安置小组也将与10+The完全互联。但是，这些组之间的连接需要处理这些组之间的所有传入和传出通信量。如果在这一点上允许10+the通信量跨越放置组，您将很快耗尽组内连接的带宽。|2282090|由于这个原因，10+them只允许在一个布局组中使用，如果需要考虑可用性，则需要部署到多个布局组中，并在它们之间进行某种形式的负载平衡。|2282091|entityMap^0|0|0|0^^$0|@$1|2|3|4|5|6|7|H|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|I|8|@]|9|@]|A|$]]|$1|D|3|E|5|6|7|J|8|@]|9|@]|A|$]]|$1|F|3|-4|5|6|7|K|8|@]|9|@]|A|$]]]|G|$]]

A placement group is a physically close group of servers, that are connected via 10 GBE networks (likely the Intel X540-T2) 

That group of servers will all be interconnected with 10GBE networks. The next placement group along will also be fully interconnected with 10GBE. However the connection between these groups would need to handle all incoming and outgoing traffic between those groups. If at that point you allowed 10GBE traffic to cross across placement groups you would very quickly run out of bandwidth on the intragroup connections. 

For this reason 10GBE is only allowed within a placement group, if availability is a concern, then you would need to deploy into multiple placement groups and have some manner of load balancing between them.

blocks|key|154633|text|布局组的思想是将实例“本地”链接起来。所以，您是对的，但它的目的也不是解决单个AZ的风险，而是让本地服务器更有效地相互交谈。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|154634|它可能是可能的混淆与ELB和自动缩放组使用布局组参数给您的HA超过多个AZs，您所追求的。|154635|entityMap^0|0|0^^$0|@$1|2|3|4|5|6|7|F|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|G|8|@]|9|@]|A|$]]|$1|D|3|-4|5|6|7|H|8|@]|9|@]|A|$]]]|E|$]]

the idea of the placement group is to link instances "locally". so you're right but also the purpose of it isn't to resolve the risk of the single AZ rather to make local servers talk more efficiently to each other.

it may be possible to mix up the env with ELBs and Auto Scaling Groups using placement group parameters to give you the HA over multiple AZs you're after.

blocks|key|2282153|text|布局组的策略确定如何在组内组织实例。有3种类型的安置组。请查看以下内容，以了解不同之处：|type|unstyled|depth|inlineStyleRanges|entityRanges|data|2282154|​|2282155|📷|atomic|offset|length|2282156|2282157|entityMap|0|IMAGE|mutability|IMMUTABLE|imageUrl|https://developer.qcloudimg.com/http-save/yehe-900000/3251d461cdd74b5ce2cb3045c7df0146.png|imageAlt^0|0|0|0|1|0|0|0^^$0|@$1|2|3|4|5|6|7|S|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|T|8|@]|9|@]|A|$]]|$1|D|3|E|5|F|7|U|8|@]|9|@$G|V|H|W|1|X]]|A|$]]|$1|I|3|C|5|6|7|Y|8|@]|9|@]|A|$]]|$1|J|3|-4|5|6|7|Z|8|@]|9|@]|A|$]]]|K|$L|$5|M|N|O|A|$P|Q|R|-4]]]]

The strategy of the placement group determines how the instances are organized within the group. There are 3 types of placement group. Please check below to know the differences:
<a href="https://i.stack.imgur.com/iCBZV.png" rel="nofollow noreferrer"><img src="https://i.stack.imgur.com/iCBZV.png" alt="Differences b/w Cluster , Partition and Spread" /></a>

According to <a href="http://docs.aws.amazon.com/AWSEC2/latest/UserGuide/placement-groups.html" rel="nofollow">AWS</a> placement group is required to be able to utilize 10gbps network performance. Given that instances are required to be placed in same availability zone for placement group, this sounds risky. For ex, unavailability of one availability zone would bring down the infrastructure.
Considering the risk, why would some use placement group?

AWS Placement groups

翻译质量差，导致语言生硬或混乱。

没有提供实际的解决方法或示例。

解答不清晰，无法理解或解决问题。

页面排版不美观，阅读体验差。

文章

问答

视频

学习中心

腾讯云实验室

直播

竞赛

腾讯云代码分析专区

腾讯iOA零信任安全管理系统专区

腾讯云架构师技术同盟交流圈

腾讯云数据库专区

腾讯云顾问专区

腾讯云原生专区

腾讯混元专区

腾讯云TCE专区

腾讯云Lighthouse专区

腾讯云HAI专区

腾讯云Edgeone专区

腾讯云存储专区

腾讯云智能专区

腾讯轻联专区 

腾讯云开发专区

TAPD专区

腾讯轻量云游戏服专区

腾讯云最具价值专家

腾讯云架构师技术同盟

腾讯云创作之星

腾讯云开发者先锋

腾讯云代码助手

云原生构建

TAPD 敏捷项目管理

Cloud Studio

SDK中心

API中心

命令行工具

涵盖代码开发、场景应用、自动测试全流程，助你从零构建专属AI助手

一站式MCP教程库，解锁AI应用新玩法

根据的要求，布局组必须能够利用10 10gbps的网络性能。考虑到需要将实例放置在放置组的相同可用性区域中，这听起来很危险。对于ex来说，一个可用区域的不可用性会降低基础设施。考虑到风险，为什么要使用安置组？

问AWS安置小组
EN

Stack Overflow用户

社区

活动

圈层

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问AWS安置小组EN