Merge pull request #304632 from EXPEkesheth/patch-741433

Revise reindex job parameters in documentation

Author: prmerger-automator[bot]

articles/healthcare-apis/fhir/how-to-run-a-reindex.md

@@ -1,6 +1,6 @@
 ---
 title:  How to run a reindex job in FHIR service - Azure Health Data Services
-description: How to run a reindex job to index any search or sort parameters that haven't yet been indexed in your database
+description: How to run a reindex job to index any search or sort parameters that are not yet indexed in your database
 author: expekesheth
 ms.service: azure-health-data-services
 ms.subservice: fhir
@@ -78,15 +78,11 @@ Content-Location: https://{{FHIR URL}}/_operations/reindex/560c7c61-2c70-4c54-b8
             "valueString": "Queued"
         },
         {
-            "name": "maximumConcurrency",
-            "valueDecimal": 3.0
-        },
-        {
-            "name": "queryDelayIntervalInMilliseconds",
-            "valueDecimal": 500.0
+            "name": "maximumNumberOfResourcesPerQuery",
+            "valueDecimal": 100.0
         },
         {
-            "name": "maximumNumberOfResourcesPerQuery",
+            "name": "maximumNumberOfResourcesPerWrite",
             "valueDecimal": 100.0
         }
     ]
@@ -113,7 +109,7 @@ content-type: application/fhir+json
 }
  ```
 > [!NOTE]
-> To check the status of, or cancel a reindex job, you need the reindex ID. This is the `"id"` carried in the `"parameter"` value of the response. In the preceding example, the ID for the reindex job would be `560c7c61-2c70-4c54-b86d-c53a9d29495e`.
+> To check the status of, or cancel a reindex job, you need the reindex ID. Reindex ID is the `"id"` carried in the `"parameter"` value of the response. In the preceding example, the ID for the reindex job would be `560c7c61-2c70-4c54-b86d-c53a9d29495e`.
 
  ## How to check the status of a reindex job
 
@@ -167,10 +163,6 @@ Here's an example response.
             "name": "status",
             "valueString": "Completed"
         },
-        {
-            "name": "maximumConcurrency",
-            "valueDecimal": 3.0
-        },
         {
             "name": "resources",
             "valueString": "{{LIST_OF_IMPACTED_RESOURCES}}"
@@ -184,11 +176,11 @@ Here's an example response.
             "valueString": "{{LIST_OF_SEARCHPARAM_URLS}}"
         },
         {
-            "name": "queryDelayIntervalInMilliseconds",
-            "valueDecimal": 500.0
+            "name": "maximumNumberOfResourcesPerQuery",
+            "valueDecimal": 100.0
         },
         {
-            "name": "maximumNumberOfResourcesPerQuery",
+            "name": "maximumNumberOfResourcesPerWrite",
             "valueDecimal": 100.0
         }
     ]
@@ -199,7 +191,7 @@ The following information is shown in the preceding response:
 
 * `totalResourcesToReindex`: Includes the total number of resources that are being reindexed in this job.
 
-* `resourcesSuccessfullyReindexed`: The total number of resources that have already been reindexed in this job.
+* `resourcesSuccessfullyReindexed`: The total number of resources reindexed in this job.
 
 * `progress`: Reindex job percent complete. Equals `resourcesSuccessfullyReindexed`/`totalResourcesToReindex` x 100.
 
@@ -219,20 +211,8 @@ If you need to cancel a reindex job, use a `DELETE` call and specify the reindex
 
 ## Performance considerations
 
-A reindex job can be quite performance intensive. The FHIR service offers throttling controls to help manage how a reindex job runs on your database.
-
-> [!NOTE]
-> It is not uncommon on large datasets for a reindex job to run for days.
-
-Below is a table outlining the available parameters, defaults, and recommended ranges for controlling reindex job compute resources. You can use these parameters to either speed up the process (use more compute) or slow down the process (use less compute). 
-
-| **Parameter**                     | **Description**              | **Default**        | **Available Range**            |
-| --------------------------------- | ---------------------------- | ------------------ | ------------------------------- |
-| `QueryDelayIntervalInMilliseconds`  | The delay between each batch of resources being kicked off during the reindex job. A smaller number speeds up the job while a larger number slows it down. | 500 MS (.5 seconds) | 50 to 500000 |
-| `MaximumResourcesPerQuery`  | The maximum number of resources included in the batch to be reindexed.  | 100 | 1-5000 |
-| `MaximumConcurrency`  | The number of batches done at a time.  | 1 | 1-10 |
-
-If you want to use any of the preceding parameters, you can pass them into the `Parameters` resource when you send the initial `POST` request to start a reindex job.
+A reindex job can be quite performance intensive. The FHIR service offers throttling controls to help manage how a reindex job runs on your database. You can use `MaximumResourcesPerQuery` parameter to either speed up the process (use more compute) or slow down the process (use less compute). `MaximumResourcesPerQuery` parameter allows to set the maximum number of resources included in the batch to be reindexed. The default value is 100 and you can set value between 1-5000. 
+Sample request with the parameter:
 
 ```json
 
@@ -241,24 +221,20 @@ content-type: application/fhir+json
 {
   "resourceType": "Parameters",
   "parameter": [
-    {
-      "name": "maximumConcurrency",
-      "valueInteger": "3"
-    },
-    {
-      "name": "queryDelayIntervalInMilliseconds",
-      "valueInteger": "1000"
-    },
     {
       "name": "maximumNumberOfResourcesPerQuery",
       "valueInteger": "1"
     }
   ]
 }
 ```
+
+> [!NOTE]
+> It is not uncommon on large datasets for a reindex job to run for days.
+
 ## Next steps
 
-In this article, you've learned how to perform a reindex job in your FHIR service. To learn how to define custom search parameters, see 
+In this article, you learned how to perform a reindex job in your FHIR service. To learn how to define custom search parameters, see 
 
 >[!div class="nextstepaction"]
 >[Defining custom search parameters](how-to-do-custom-search.md)