Merge pull request #249192 from Padmalathas/PendingTask-Limitation-patch-1

Include Limitation Note to Autoscaling

Author: prmerger-automator[bot]

articles/batch/batch-automatic-scaling.md

@@ -2,7 +2,7 @@
 title: Autoscale compute nodes in an Azure Batch pool
 description: Enable automatic scaling on an Azure Batch cloud pool to dynamically adjust the number of compute nodes in the pool.
 ms.topic: how-to
-ms.date: 05/26/2023
+ms.date: 08/23/2023
 ms.custom: H1Hack27Feb2017, fasttrack-edit, devx-track-csharp, devx-track-linux
 ---
 
@@ -58,6 +58,8 @@ pendingTaskSamples = pendingTaskSamplePercent < 70 ? startingNumberOfVMs : avg($
 $TargetDedicatedNodes=min(maxNumberofVMs, pendingTaskSamples);
 $NodeDeallocationOption = taskcompletion;
 ```
+> [!IMPORTANT]
+> Currently, Batch Service has limitaion with the resolution of the pending tasks. When a task is added to the job, it's also added into a internal queue used by Batch service for scheduling. If the task is deleted before it can be scheduled, the task might persist within the queue, causing it to still be counted in `$PendingTasks`. This deleted task will eventually be cleared from the queue when Batch gets chance to pull tasks from the queue to schedule with idle nodes in the Batch pool.
 
 #### Preempted nodes
 

articles/batch/batch-docker-container-workloads.md

@@ -38,7 +38,8 @@ You should be familiar with container concepts and how to create a Batch pool an
 > - Batch Python SDK version 14.0.0
 > - Batch Java SDK version 11.0.0
 > - Batch Node.js SDK version 11.0.0
-> the `containerConfiguration` requires `Type` property to be passed and the supported values are: `ContainerType.DockerCompatible` and `ContainerType.CriCompatible`.
+
+Currently, the `containerConfiguration` requires `Type` property to be passed and the supported values are: `ContainerType.DockerCompatible` and `ContainerType.CriCompatible`.
 
 Keep in mind the following limitations: