zookeeper-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From rammohan ganapavarapu <rammohanga...@gmail.com>
Subject Re: quorum.cnxn.threads.size
Date Thu, 12 Dec 2019 17:18:19 GMT
No, my loglevel setting is INFO.

 ps -ef |grep zoo|awk '{print $10}'
-Dzookeeper.root.logger=INFO,CONSOLE

Just to clarify, i am upgrading from 3.4.5 to 3.4.14 and i am upgrading
observers firs then followers (yet to do) and see this flood of log
messages in observer logs.

Observer: 3.4.14 version
Leader: 3.4.5 version

On Thu, Dec 12, 2019 at 9:13 AM Flavio Junqueira <fpj@apache.org> wrote:

> If you set up logging at DEBUG level and you see this message:
>    "Not initializing connection executor as quorum sasl auth is disabled"
> then you are good.
>
> -Flavio
>
> > On 12 Dec 2019, at 18:06, rammohan ganapavarapu <rammohanganap@gmail.com>
> wrote:
> >
> > I am assuming its only logging, is there any way i can verify its not
> > opening cnxn threads?
> >
> >
> >
> > On Thu, Dec 12, 2019 at 7:15 AM Flavio Junqueira <fpj@apache.org> wrote:
> >
> >> 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 <
> rammohanganap@gmail.com>
> >> 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 <fpj@apache.org> 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 <
> >> rammohanganap@gmail.com>
> >>>> wrote:
> >>>>>
> >>>>> Any idea?
> >>>>>
> >>>>> On Wed, Dec 11, 2019, 2:23 PM rammohan ganapavarapu <
> >>>> rammohanganap@gmail.com>
> >>>>> 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 <
> >>>>>> rammohanganap@gmail.com> 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
> >>>>>>>
> >>>>>>
> >>>>
> >>>>
> >>
> >>
>
>

Mime
  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message