Merge pull request #207602 from JasonFreeberg/patch-121

JBoss Clustering scaling notes

Author: prmerger-automator[bot]

articles/app-service/configure-language-java.md

@@ -1137,6 +1137,16 @@ When clustering is enabled, the JBoss EAP instances use the FILE_PING JGroups di
 
 The Premium V3 and Isolated V2 App Service Plan types can optionally be distributed across Availability Zones to improve resiliency and reliability for your business-critical workloads. This architecture is also known as [zone redundancy](../availability-zones/migrate-app-service.md). The JBoss EAP clustering feature is compatabile with the zone redundancy feature. 
 
+#### Auto-Scale Rules
+
+When configuring auto-scale rules for horizontal scaling it is important to remove instances incrementally (one at a time) to ensure each removed instance can transfer its activity (such as handling a database transaction) to another member of the cluster. When configuring your autoscale rules in the Portal to scale down, use the following options:
+
+- **Operation**: "Decrease count by"
+- **Cool down**: "5 minutes" or greater
+- **Instance count**: 1
+
+You do not need to incrementally add instances (scaling out), you can add multiple instances to the cluster at a time.
+
 ### JBoss EAP App Service Plans
 
 <a id="jboss-eap-hardware-options"></a>