StackOverflow2013

Note that there are some explanatory texts on larger screens.

plurals

PO
primarykey
Id
7991630
data
AcceptedAnswerId
0
AnswerCount
0
ClosedDate
CommentCount
1
CommunityOwnedDate
CreationDate
2011-11-03T07:47:02.520
FavoriteCount
0
LastActivityDate
2011-11-03T07:54:07.870
LastEditDate
2011-11-03T07:54:07.870
LastEditorUserId
948593
OwnerUserId
948593
ParentId
7665358
PostTypeId
2
Score
7
ViewCount
0
LastEditorDisplayName
text
Body
The recommended way for distributing traffic from your ELB is to have an equal number of instances across multiple availability zones. For example: ELB <ul> <li>Instance 1 (us-east-a)</li> <li>Instance 2 (us-east-a)</li> <li>Instance 3 (us-east-b)</li> <li>Instance 4 (us-east-b)</li> </ul> Now there are two ELB APIs of interest provided that allow you to programmatically (or via the control panel) detach instances: <ol> <li>Deregister an instance</li> <li>Disable an availability zone (which subsequently disables the instances within that zone)</li> </ol> The <a href="http://docs.amazonwebservices.com/ElasticLoadBalancing/latest/DeveloperGuide/">ELB Developer Guide</a> has a section that describes the effects of disabling an availability zone. A note in that section is of particular interest: <blockquote> Your load balancer always distributes traffic to all the enabled Availability Zones. If all the instances in an Availability Zone are deregistered or unhealthy before that Availability Zone is disabled for the load balancer, all requests sent to that Availability Zone will fail until DisableAvailabilityZonesForLoadBalancer calls for that Availability Zone. </blockquote> Whats interesting about the above note is that it could imply that if you call DisableAvailabilityZonesForLoadBalancer, the ELB could instantly start sending requests only to available zones - possibly resulting in a 0 downtime experience while you perform maintenance on the servers in the disabled availability zone. The above 'theory' needs detailed testing or acknowledgement from an Amazon cloud engineer. 
Tags
Title
singulars
PostAcceptedAnswerId
1. This table or related slice is empty.
PostParentId
1. POHow to gracefully shut down or remove AWS instances from an ELB group
 singulars
 PostTypePostTypeId
 PTQuestion
PostTypePostTypeId
1. PTAnswer
UserLastEditorUserId
1. USFaraz
UserOwnerUserId
1. USFaraz
plurals
PostLinksPostIdRelatedPostId
1. This table or related slice is empty.
PostLinksRelatedPostIdPostId
1. This table or related slice is empty.
PostsAcceptedAnswerId
1. This table or related slice is empty.
PostsParentIdCreationDate
1. This table or related slice is empty.
VotesPostIdCreationDate
1. VO
 singulars
 PostPostId
 PO
 UserUserId
 This table or related slice is empty.
 VoteTypeVoteTypeId
 VTUpMod
2. VO
 singulars
 PostPostId
 PO
 UserUserId
 This table or related slice is empty.
 VoteTypeVoteTypeId
 VTUpMod
3. VO
 singulars
 PostPostId
 PO
 UserUserId
 This table or related slice is empty.
 VoteTypeVoteTypeId
 VTUpMod
CommentsPostId
1. COSounds promising, I didn't think of that! I'll definitely check this out! Thanks.
 singulars
 PostPostId
 PO
 UserUserId
 USJohann Philipp Strathausen

Querying!

Guidance

A row detail

Detail views are divided into sections. All the information in the data section comes from columns in the selected row. The other sections display data from other, related rows.

Related data can be related in a to-one or a to-many fashion. Captions of data related in a to-many fashion link to a list view showing a filtered view of the table.

Try moving around until you find a non-empty to-many entry and click on the label to get to one. You can move back to the root by clicking on the database name in the header.