[DOCS] Add anchors for Asciidoctor migration (#41648)

Author: jrodewig

docs/reference/docs/update.asciidoc

@@ -150,6 +150,7 @@ curl -XPOST 'localhost:9200/test/type1/1/_update' -d '{
 --------------------------------------------------
 
 [float]
+[[scripted_upsert]]
 ==== `scripted_upsert`
 
 If you would like your script to run regardless of whether the document exists
@@ -173,6 +174,7 @@ curl -XPOST 'localhost:9200/sessions/session/dh3sgudg8gsrgl/_update' -d '{
 --------------------------------------------------
 
 [float]
+[[doc_as_upsert]]
 ==== `doc_as_upsert`
 
 Instead of sending a partial `doc` plus an `upsert` doc, setting

docs/reference/getting-started.asciidoc

@@ -384,6 +384,7 @@ This REST access pattern is pervasive throughout all the API commands that if yo
 Elasticsearch provides data manipulation and search capabilities in near real time. By default, you can expect a one second delay (refresh interval) from the time you index/update/delete your data until the time that it appears in your search results. This is an important distinction from other platforms like SQL wherein data is immediately available after a transaction is completed.
 
 [float]
+[[indexing-replacing-documents]]
 === Indexing/Replacing Documents
 
 We've previously seen how we can index a single document. Let's recall that command again:

docs/reference/mapping/fields/source-field.asciidoc

@@ -6,6 +6,7 @@ JSON that was used as the indexed document. It is not indexed (searchable),
 just stored. When executing "fetch" requests, like <<docs-get,get>> or
 <<search-search,search>>, the `_source` field is returned by default.
 
+[[disable-source-field]]
 ==== Disabling source
 
 Though very handy to have around, the source field does incur storage overhead

docs/reference/modules/snapshots.asciidoc

@@ -433,6 +433,7 @@ GET /_snapshot/my_backup/snapshot_1,snapshot_2/_status
 // AUTOSENSE
 
 [float]
+[[monitor-snapshot-restore-progress]]
 === Monitoring snapshot/restore progress
 
 There are several ways to monitor the progress of the snapshot and restores processes while they are running. Both

docs/reference/modules/threadpool.asciidoc

@@ -80,6 +80,7 @@ The following are the types of thread pools that can be used and their
 respective parameters:
 
 [float]
+[[cached]]
 ==== `cache`
 
 The `cache` thread pool is an unbounded thread pool that will spawn a
@@ -94,6 +95,7 @@ threadpool:
 --------------------------------------------------
 
 [float]
+[[fixed]]
 ==== `fixed`
 
 The `fixed` thread pool holds a fixed size of threads to handle the
@@ -118,12 +120,24 @@ threadpool:
 --------------------------------------------------
 
 [float]
+<<<<<<< HEAD
 [[processors]]
 === Processors setting
 The number of processors is automatically detected, and the thread pool
 settings are automatically set based on it. In some cases it can be
 useful to override the number of detected processors. This can be done
 by explicitly setting the `processors` setting.
+=======
+[[scaling]]
+==== `scaling`
+
+The `scaling` thread pool holds a dynamic number of threads. This number is
+proportional to the workload and varies between 1 and the value of the
+`size` parameter.
+
+The `keep_alive` parameter determines how long a thread should be kept
+around in the thread pool without it doing any work.
+>>>>>>> 045a4029b80... [DOCS] Add anchors for Asciidoctor migration (#41648)
 
 [source,js]
 --------------------------------------------------