rdhabalia commented on a change in pull request #12025:
URL: https://github.com/apache/pulsar/pull/12025#discussion_r773533656



##########
File path: site2/docs/reference-configuration.md
##########
@@ -356,6 +356,7 @@ brokerServiceCompactionThresholdInBytes|If the estimated 
backlog size is greater
 | additionalServletDirectory | Location of broker additional servlet NAR 
directory | ./brokerAdditionalServlet |
 | brokerEntryMetadataInterceptors | Set broker entry metadata interceptors.<br 
/><br />Multiple interceptors should be separated by commas. <br /><br 
/>Available 
values:<li>org.apache.pulsar.common.intercept.AppendBrokerTimestampMetadataInterceptor</li><li>org.apache.pulsar.common.intercept.AppendIndexMetadataInterceptor</li>
 <br /><br />Example<br 
/>brokerEntryMetadataInterceptors=org.apache.pulsar.common.intercept.AppendBrokerTimestampMetadataInterceptor,
 org.apache.pulsar.common.intercept.AppendIndexMetadataInterceptor|N/A |
 | enableExposingBrokerEntryMetadataToClient|Whether to expose broker entry 
metadata to client or not.<br /><br />Available 
values:<li>true</li><li>false</li><br />Example<br 
/>enableExposingBrokerEntryMetadataToClient=true  | false |
+| strictBookieAffinityEnabled | Enable or disable the strict bookie isolation 
strategy. If enabled, <br /> - `bookie-ensemble` first tries to choose bookies 
that belong to a namespace's affinity group. If the number of bookies is not 
enough, then the rest bookies are chosen. <br /> - If namespace has no affinity 
group, `bookie-ensemble` only chooses bookies that belong to no region. If the 
number of bookies is not enough, `BKNotEnoughBookiesException` is thrown.| 
false |

Review comment:
       that's how it works with secondary group and no need for extra config. 
such extra config really confuses the users.




-- 
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]


Reply via email to