Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Update application-gateway-faq.md #7805

Merged
merged 2 commits into from Apr 30, 2018
Merged

Update application-gateway-faq.md #7805

Changes from 1 commit
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
bdca9ca
Update application-gateway-faq.md
Apr 27, 2018
1e3a53d
Update application-gateway-faq.md
Apr 30, 2018
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Jump to
Jump to file
Failed to load files.
Diff view
Diff view
4 changes: 4 additions & 0 deletions articles/application-gateway/application-gateway-faq.md
View file
Open in desktop
Expand Up @@ -174,6 +174,10 @@ No, but Application Gateway has a throughput metric that can be used to alert yo

There is no downtime, instances are distributed across upgrade domains and fault domains.

**Q. Does changing backend pool members cause disruption?**

You can configure connection draining to change members within a backend pool without disruption. This will allow existing connections to continue to be sent to their previous destination until either that connection is closed or a configurable timeout expires.

**Q. Can I change instance size from medium to large without disruption?**

Yes, Azure distributes instances across update and fault domains to ensure that all instances do not fail at the same time. Application Gateway supports scaling by adding multiple instances of the same gateway to share the load.
Expand Down