techdocsmith commented on a change in pull request #11480:
URL: https://github.com/apache/druid/pull/11480#discussion_r685623217
##########
File path: docs/configuration/index.md
##########
@@ -1202,13 +1202,12 @@ Example: a function that sends batch_index_task to
workers 10.0.0.1 and 10.0.0.2
###### Affinity
-Affinity configs can be provided to the _equalDistribution_ and _fillCapacity_
strategies using the "affinityConfig"
-field. If not provided, the default is to not use affinity at all.
+Affinity configs can be provided to the _equalDistribution_ and _fillCapacity_
strategies using the "affinityConfig" field. If not provided, the default is to
not use affinity at all.
Review comment:
```suggestion
Use the `affinityConfig` field to pass affinity configuration to the
_equalDistribution_ and _fillCapacity_ strategies. If not provided, the default
is to not use affinity at all.
```
##########
File path: docs/configuration/index.md
##########
@@ -1202,13 +1202,12 @@ Example: a function that sends batch_index_task to
workers 10.0.0.1 and 10.0.0.2
###### Affinity
-Affinity configs can be provided to the _equalDistribution_ and _fillCapacity_
strategies using the "affinityConfig"
-field. If not provided, the default is to not use affinity at all.
+Affinity configs can be provided to the _equalDistribution_ and _fillCapacity_
strategies using the "affinityConfig" field. If not provided, the default is to
not use affinity at all.
|Property|Description|Default|
|--------|-----------|-------|
|`affinity`|JSON object mapping a datasource String name to a list of indexing
service MiddleManager host:port String values. Druid doesn't perform DNS
resolution, so the 'host' value must match what is configured on the
MiddleManager and what the MiddleManager announces itself as (examine the
Overlord logs to see what your MiddleManager announces itself as).|{}|
-|`strong`|With weak affinity (the default), tasks for a dataSource may be
assigned to other MiddleManagers if their affinity-mapped MiddleManagers are
not able to run all pending tasks in the queue for that dataSource. With strong
affinity, tasks for a dataSource will only ever be assigned to their
affinity-mapped MiddleManagers, and will wait in the pending queue if
necessary.|false|
+|`strong`|A boolean determining whether tasks for a datasource must be
assigned to affinity-mapped MiddleManagers, causing tasks to remain queued
until a slot is available. If `false`, tasks for a datasource may be assigned
to other MiddleManagers whenever affinity-mapped MiddleManagers are not
available to run queued tasks.|false|
Review comment:
```suggestion
|`strong`|When `true` tasks for a datasource must be assigned to
affinity-mapped MiddleManagers. Tasks remain queued until a slot becomes
available. When `false`, Druid may assign tasks for a datasource to other
MiddleManagers when affinity-mapped MiddleManagers are unavailable to run
queued tasks.|false|
```
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: [email protected]
For queries about this service, please contact Infrastructure at:
[email protected]
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
