If it is just logging the value of the property, then it is fine because the property is set, but it is not used if SASL is disabled.
-Flavio > On 12 Dec 2019, at 16:01, rammohan ganapavarapu <[email protected]> > wrote: > > Flavio, > > Thanks for clarification, I have a cluster with sasl disabled but in start > up log I still see number of threads set to default 20. > > Thanks, > Ram > On Thu, Dec 12, 2019, 6:43 AM Flavio Junqueira <[email protected]> wrote: > >> Hi Ram, >> >> Yes, this parameter is only applicable when SASL is enabled, see in >> QuorumCnxManager#initializeAuth how it doesn't have a chance to use the >> parameter when SASL is disabled. >> >> Your assessment is correct about it being based on the number of >> participants, excluding observers. This parameter is used in >> QuorumCnxManager, which manages connections for leader election, and >> observers do not participate in the election. >> >> -Flavio >> >>> On 12 Dec 2019, at 14:41, rammohan ganapavarapu <[email protected]> >> wrote: >>> >>> Any idea? >>> >>> On Wed, Dec 11, 2019, 2:23 PM rammohan ganapavarapu < >> [email protected]> >>> wrote: >>> >>>> And to add more on the same property, the description says >>>> >>>> >>>> >>>> >>>> >>>> *"For example, consider a 3-node cluster,# during quorum formation at >>>> least 3 outgoing connection requests and 3 incoming connection# requests >>>> will occur. So total 6 threads will be used. It is recommended to >> configure >>>> 2x# number of threads for smooth execution, where 'x' represents the >>>> cluster size"* >>>> >>>> Here* cluster size* is number of *followers* right not both followers >> and >>>> observers?? >>>> >>>> Ram >>>> >>>> On Wed, Dec 11, 2019 at 2:19 PM rammohan ganapavarapu < >>>> [email protected]> wrote: >>>> >>>>> Is this property only applicable in case of sasl auth enabled? or does >> it >>>>> work even when we turn off authentication? >>>>> >>>>> >>>>> *quorum.cnxn.threads.size* >>>>> >>>>> Thanks, >>>>> Ram >>>>> >>>> >> >>
