Re: Upgrading existing non-TLS cluster with no downtime

[Sankalp Bhatia]

Thanks Mate for the responses. Brings a lot of clarity to me. I was able to
get it working this time without downtime. Don't know what I did wrong the
last time though.

On Mon, 20 Jul 2020 at 12:57, Szalay-Bekő Máté 
wrote:

> echo "stat" | nc localhost 2182Hi,
>
> I guess this is the part you are referring:
>
> https://zookeeper.apache.org/doc/r3.5.8/zookeeperAdmin.html#Upgrading+existing+nonTLS+cluster
> (your link was pointing to the 3.3.2 admin guide where this chapter was
> missing)
>
> > 1) When I set sslQuorum=true  and portUnification=true on the first
> server,
> does it go out of the quorum? And when these properties are set in the
> second server, a new quorum of first and second server is formed and now
> the third server is out of quorum. When the 3rd server follows suit, it is
> added back to the quorum.
>
> the "sslQuorum=true  and portUnification=true" setting is needed in step 4
> (although the numbering is bad in the markdown...). After step 3 you
> already have a 3 server quorum up with portUnification=true, meaning the
> cluster can handle both TLS/SSL and regular/non-secure connections. So when
> you restart server 1 with sslQuorum=true, then it will be able to re-join
> to the quorum, as server 2 and 3 are capable of handling SSL connections
> (even if they are not using it for connection initiation). So ideally
> between restarting each servers with sslQuorum=true, you always should have
> a 3 node full quorum.
>
> > 2) The guideline says to check after restarting every broker that the
> quorum is healthy, is there any metric to track that?
>
> I send the "stat" command to all nodes to see if everyone is connected to
> the quorum. E.g.: echo "stat" | nc localhost 2181
> I usually use 4-letter-word commands but the REST admin API works as well,
> and actually that is the officially recommended way, as the 4-letter-words
> are / will be deprecated some time.
> For the admin server see:
> https://zookeeper.apache.org/doc/r3.5.8/zookeeperAdmin.html#sc_adminserver
>
> Kind regards,
> Mate
>
> On Tue, Jul 14, 2020 at 10:52 PM Sankalp Bhatia  >
> wrote:
>
> > +users
> >
> > On Tue, 14 Jul 2020 at 21:51, Sankalp Bhatia 
> > wrote:
> >
> > > Hi All,
> > >
> > > I am trying to follow the section "Upgrading existing non-TLS cluster
> > with
> > > no downtime" in the zookeeper guide :
> > > https://zookeeper.apache.org/doc/r3.3.2/zookeeperAdmin.html
> > >
> > > I have an ensemble of 3 servers. I have a couple of questions:
> > >
> > > 1) When I set sslQuorum=true  and portUnification=true on the first
> > > server, does it go out of the quorum? And when these properties are set
> > > in the second server, a new quorum of first and second server is formed
> > and
> > > now the third server is out of quorum. When the 3rd server follows
> suit,
> > it
> > > is added back to the quorum.
> > >
> > > If this is the case, what is the use of a the port-unification feature
> > > here?
> > >
> > > 2) The guideline says to check after restarting every broker that the
> > > quorum is healthy, is there any metric to track that?
> > >
> > > Thanks,
> > > Sankalp
> > >
> > >
> > >
> > >
> >
>

Re: [IMPORTANT] - Migration to ci-builds.a.o

[Enrico Olivelli]

Il Lun 20 Lug 2020, 19:40 Andor Molnar  ha scritto:

> Hi Enrico,
>
> No worries, I only created a few jobs to make some progress, but feel free
> to ignore that and do it in a better way. The “View” or “Folder” that I was
> adding jobs is
>
> https://ci-hadoop.apache.org/view/ZooKeeper/
>
>
> Andor
>

This is an example from Apache Maven  project. It is very complex because
tests are in another repo and for lots if other reasons. We just have to
create a simpler file.

If nobody volunteers I can try to spend some time but I won't have a fast
pace these weeks


Enrico



>
>
> > On 2020. Jul 20., at 19:34, Enrico Olivelli  wrote:
> >
> > Il Lun 20 Lug 2020, 19:02 Patrick Hunt  ha scritto:
> >
> >> On Mon, Jul 20, 2020 at 9:47 AM Enrico Olivelli 
> >> wrote:
> >>
> >>> Il Lun 20 Lug 2020, 18:41 Patrick Hunt  ha scritto:
> >>>
>  On Sat, Jul 18, 2020 at 12:20 PM Andor Molnar 
> >> wrote:
> 
> > Hi Pat,
> >
> > I have admin rights in the new system too and probably can work on
> >> this
>  on
> > Monday.
> > What’s “matrix” config? Shouldn’t we just replicate the same jobs on
> >>> the
> > new instance?
> >
> >
>  Not sure on the exact name/feature but "matrix" is basically the
> >> ability
> >>> to
>  say "run this build/test across a set of JDK versions" rather than a
> >>> single
>  version. As a result, instead of 3 jobs for zk3.6.0, jdk 1/2/3 you end
> >> up
>  with a single job which runs three times, one for each jdk type and
>  summarizes the results. I've seen this before, I assume it's a feature
> >> of
>  jenkins itself?
> 
> >>>
> >>> We should use Jenkins files and this configuration will be easy and
> >>> committed to git
> >>>
> >>
> >> The ability to do "gitops" would be amazing!
> >>
> >
> > Yes.
> > But I saw on Slack that Andor already started to create new jobs.
> > We should do only one way in order not to waste time.
> >
> > Andor can you please share your work?
> > Thanks for doing it
> >
> > Enrico
> >
> >
> >
> >> Patrick
> >>
> >>
> >>>
> >>> Enrico
> >>>
> >>>
> >>>
>  Patrick
> 
> 
> > Andor
> >
> >
> >
> >> On 2020. Jul 17., at 2:51, Patrick Hunt  wrote:
> >>
> >> I updated the job I linked earlier based on what's the latest on
> >> the
> > legacy
> >> jenkins. It ran successfully
> >> https://ci-hadoop.apache.org/job/zookeeper-master-maven/215/
> >>
> >> I didn't replicate every config setting - main gap is the spotbugs
> >> post-build, which seems to be missing from the new jenkins plugins.
> >>
> >> That's just maven master though. Not sure about the rest. Can we do
>  more
> > of
> >> a "matrix" config in the new system vs cloning all the time?
> >>
> >> Patrick
> >>
> >> On Thu, Jul 16, 2020 at 3:31 PM Patrick Hunt 
> >>> wrote:
> >>
> >>>
> >>> On Thu, Jul 16, 2020 at 3:22 PM Patrick Hunt 
>  wrote:
> >>>
> 
> 
>  On Thu, Jul 16, 2020 at 12:56 PM Enrico Olivelli <
>  eolive...@gmail.com>
>  wrote:
> 
> > FYI
> >
> 
>  Fun. I do notice it says "Hadoop and related projects have their
> >>> own
>  migration path to follow" - any insight on that? We are or are
> >> not
> > lumped
>  in? I would assume we are?
> 
>  This (eventual migration) came up a while back on the Hadoop PMC
> >>> and
>  I
>  volunteered to try for us (ZK). I was never able to get it to
> >>> work, I
>  provided feedback to infra  but they never got back, as such we
> >>> have
>  a
>  project here that's not working with some basic dependencies
> >>> missing:
>  https://ci-hadoop.apache.org/job/zookeeper-master-maven/
> 
>  That said, we can try again. Can we verify where ZK is supposed
> >> to
> > land?
>  Perhaps we can try to delete and recreate the POC job I created
> >> at
>  that
>  link to see if we can get it working?
> 
> 
> >>> I see another email thread on the list saying that we are part of
> >>> said
> >>> "related projects". We are expected to move to
> >>> http://ci-hadoop.apache.org/ within 4 weeks. Seems nodes are
> >>> already
> >>> being removed/migrated from the "H#" pool.
> >>>
> >>> Also this:
> >>>
> >>> There are over 400 plugins on the current builds.apache.org -
> >> most
> >>> of
> > which
> >>> we don't need any more, or are replaced with different plugins on
> >>> the
> > new
> >>> system. I expect there may be some plugins we still need to
> >> install
> >>> to
> > get
> >>> you going again, which is why it is vitally important that you
> >> start
> >>> testing and migrating your jobs over *now*. You should all have
> >>> auth.
> >>>
> >>> Any questions, feel free to email the
> >> hadoop-migrati...@apache.org
> > 

Re: [IMPORTANT] - Migration to ci-builds.a.o

[Andor Molnar]

Hi Enrico,

No worries, I only created a few jobs to make some progress, but feel free to 
ignore that and do it in a better way. The “View” or “Folder” that I was adding 
jobs is 

https://ci-hadoop.apache.org/view/ZooKeeper/

Andor



> On 2020. Jul 20., at 19:34, Enrico Olivelli  wrote:
> 
> Il Lun 20 Lug 2020, 19:02 Patrick Hunt  ha scritto:
> 
>> On Mon, Jul 20, 2020 at 9:47 AM Enrico Olivelli 
>> wrote:
>> 
>>> Il Lun 20 Lug 2020, 18:41 Patrick Hunt  ha scritto:
>>> 
 On Sat, Jul 18, 2020 at 12:20 PM Andor Molnar 
>> wrote:
 
> Hi Pat,
> 
> I have admin rights in the new system too and probably can work on
>> this
 on
> Monday.
> What’s “matrix” config? Shouldn’t we just replicate the same jobs on
>>> the
> new instance?
> 
> 
 Not sure on the exact name/feature but "matrix" is basically the
>> ability
>>> to
 say "run this build/test across a set of JDK versions" rather than a
>>> single
 version. As a result, instead of 3 jobs for zk3.6.0, jdk 1/2/3 you end
>> up
 with a single job which runs three times, one for each jdk type and
 summarizes the results. I've seen this before, I assume it's a feature
>> of
 jenkins itself?
 
>>> 
>>> We should use Jenkins files and this configuration will be easy and
>>> committed to git
>>> 
>> 
>> The ability to do "gitops" would be amazing!
>> 
> 
> Yes.
> But I saw on Slack that Andor already started to create new jobs.
> We should do only one way in order not to waste time.
> 
> Andor can you please share your work?
> Thanks for doing it
> 
> Enrico
> 
> 
> 
>> Patrick
>> 
>> 
>>> 
>>> Enrico
>>> 
>>> 
>>> 
 Patrick
 
 
> Andor
> 
> 
> 
>> On 2020. Jul 17., at 2:51, Patrick Hunt  wrote:
>> 
>> I updated the job I linked earlier based on what's the latest on
>> the
> legacy
>> jenkins. It ran successfully
>> https://ci-hadoop.apache.org/job/zookeeper-master-maven/215/
>> 
>> I didn't replicate every config setting - main gap is the spotbugs
>> post-build, which seems to be missing from the new jenkins plugins.
>> 
>> That's just maven master though. Not sure about the rest. Can we do
 more
> of
>> a "matrix" config in the new system vs cloning all the time?
>> 
>> Patrick
>> 
>> On Thu, Jul 16, 2020 at 3:31 PM Patrick Hunt 
>>> wrote:
>> 
>>> 
>>> On Thu, Jul 16, 2020 at 3:22 PM Patrick Hunt 
 wrote:
>>> 
 
 
 On Thu, Jul 16, 2020 at 12:56 PM Enrico Olivelli <
 eolive...@gmail.com>
 wrote:
 
> FYI
> 
 
 Fun. I do notice it says "Hadoop and related projects have their
>>> own
 migration path to follow" - any insight on that? We are or are
>> not
> lumped
 in? I would assume we are?
 
 This (eventual migration) came up a while back on the Hadoop PMC
>>> and
 I
 volunteered to try for us (ZK). I was never able to get it to
>>> work, I
 provided feedback to infra  but they never got back, as such we
>>> have
 a
 project here that's not working with some basic dependencies
>>> missing:
 https://ci-hadoop.apache.org/job/zookeeper-master-maven/
 
 That said, we can try again. Can we verify where ZK is supposed
>> to
> land?
 Perhaps we can try to delete and recreate the POC job I created
>> at
 that
 link to see if we can get it working?
 
 
>>> I see another email thread on the list saying that we are part of
>>> said
>>> "related projects". We are expected to move to
>>> http://ci-hadoop.apache.org/ within 4 weeks. Seems nodes are
>>> already
>>> being removed/migrated from the "H#" pool.
>>> 
>>> Also this:
>>> 
>>> There are over 400 plugins on the current builds.apache.org -
>> most
>>> of
> which
>>> we don't need any more, or are replaced with different plugins on
>>> the
> new
>>> system. I expect there may be some plugins we still need to
>> install
>>> to
> get
>>> you going again, which is why it is vitally important that you
>> start
>>> testing and migrating your jobs over *now*. You should all have
>>> auth.
>>> 
>>> Any questions, feel free to email the
>> hadoop-migrati...@apache.org
> list if
>>> you are one of the projects listed below. The rest of you, not
 listed, a
>>> similar email to this one will be posted for you shortly on
 builds@a.o.
>>> 
>>> 
>>> full details
>>> 
> 
 
>>> 
>> https://lists.apache.org/thread.html/r21c9d40cdbf5461143dd7eb4ff48a200c2fd20c50e946884f61318fd%40%3Cbuilds.apache.org%3E
>>> 
>>> Patrick
>>> 
>>> 
>>> 
 Patrick
 
 
> 
> -- Forwarded message -
> Da: Gavin McDonald 
> Date: Gio 16 Lug 2020, 18:33
> Subject: 

Re: [IMPORTANT] - Migration to ci-builds.a.o

[Enrico Olivelli]

Il Lun 20 Lug 2020, 19:02 Patrick Hunt  ha scritto:

> On Mon, Jul 20, 2020 at 9:47 AM Enrico Olivelli 
> wrote:
>
> > Il Lun 20 Lug 2020, 18:41 Patrick Hunt  ha scritto:
> >
> > > On Sat, Jul 18, 2020 at 12:20 PM Andor Molnar 
> wrote:
> > >
> > > > Hi Pat,
> > > >
> > > > I have admin rights in the new system too and probably can work on
> this
> > > on
> > > > Monday.
> > > > What’s “matrix” config? Shouldn’t we just replicate the same jobs on
> > the
> > > > new instance?
> > > >
> > > >
> > > Not sure on the exact name/feature but "matrix" is basically the
> ability
> > to
> > > say "run this build/test across a set of JDK versions" rather than a
> > single
> > > version. As a result, instead of 3 jobs for zk3.6.0, jdk 1/2/3 you end
> up
> > > with a single job which runs three times, one for each jdk type and
> > > summarizes the results. I've seen this before, I assume it's a feature
> of
> > > jenkins itself?
> > >
> >
> > We should use Jenkins files and this configuration will be easy and
> > committed to git
> >
>
> The ability to do "gitops" would be amazing!
>

Yes.
But I saw on Slack that Andor already started to create new jobs.
We should do only one way in order not to waste time.

Andor can you please share your work?
Thanks for doing it

Enrico



> Patrick
>
>
> >
> > Enrico
> >
> >
> >
> > > Patrick
> > >
> > >
> > > > Andor
> > > >
> > > >
> > > >
> > > > > On 2020. Jul 17., at 2:51, Patrick Hunt  wrote:
> > > > >
> > > > > I updated the job I linked earlier based on what's the latest on
> the
> > > > legacy
> > > > > jenkins. It ran successfully
> > > > > https://ci-hadoop.apache.org/job/zookeeper-master-maven/215/
> > > > >
> > > > > I didn't replicate every config setting - main gap is the spotbugs
> > > > > post-build, which seems to be missing from the new jenkins plugins.
> > > > >
> > > > > That's just maven master though. Not sure about the rest. Can we do
> > > more
> > > > of
> > > > > a "matrix" config in the new system vs cloning all the time?
> > > > >
> > > > > Patrick
> > > > >
> > > > > On Thu, Jul 16, 2020 at 3:31 PM Patrick Hunt 
> > wrote:
> > > > >
> > > > >>
> > > > >> On Thu, Jul 16, 2020 at 3:22 PM Patrick Hunt 
> > > wrote:
> > > > >>
> > > > >>>
> > > > >>>
> > > > >>> On Thu, Jul 16, 2020 at 12:56 PM Enrico Olivelli <
> > > eolive...@gmail.com>
> > > > >>> wrote:
> > > > >>>
> > > >  FYI
> > > > 
> > > > >>>
> > > > >>> Fun. I do notice it says "Hadoop and related projects have their
> > own
> > > > >>> migration path to follow" - any insight on that? We are or are
> not
> > > > lumped
> > > > >>> in? I would assume we are?
> > > > >>>
> > > > >>> This (eventual migration) came up a while back on the Hadoop PMC
> > and
> > > I
> > > > >>> volunteered to try for us (ZK). I was never able to get it to
> > work, I
> > > > >>> provided feedback to infra  but they never got back, as such we
> > have
> > > a
> > > > >>> project here that's not working with some basic dependencies
> > missing:
> > > > >>> https://ci-hadoop.apache.org/job/zookeeper-master-maven/
> > > > >>>
> > > > >>> That said, we can try again. Can we verify where ZK is supposed
> to
> > > > land?
> > > > >>> Perhaps we can try to delete and recreate the POC job I created
> at
> > > that
> > > > >>> link to see if we can get it working?
> > > > >>>
> > > > >>>
> > > > >> I see another email thread on the list saying that we are part of
> > said
> > > > >> "related projects". We are expected to move to
> > > > >> http://ci-hadoop.apache.org/ within 4 weeks. Seems nodes are
> > already
> > > > >> being removed/migrated from the "H#" pool.
> > > > >>
> > > > >> Also this:
> > > > >>
> > > > >> There are over 400 plugins on the current builds.apache.org -
> most
> > of
> > > > which
> > > > >> we don't need any more, or are replaced with different plugins on
> > the
> > > > new
> > > > >> system. I expect there may be some plugins we still need to
> install
> > to
> > > > get
> > > > >> you going again, which is why it is vitally important that you
> start
> > > > >> testing and migrating your jobs over *now*. You should all have
> > auth.
> > > > >>
> > > > >> Any questions, feel free to email the
> hadoop-migrati...@apache.org
> > > > list if
> > > > >> you are one of the projects listed below. The rest of you, not
> > > listed, a
> > > > >> similar email to this one will be posted for you shortly on
> > > builds@a.o.
> > > > >>
> > > > >>
> > > > >> full details
> > > > >>
> > > >
> > >
> >
> https://lists.apache.org/thread.html/r21c9d40cdbf5461143dd7eb4ff48a200c2fd20c50e946884f61318fd%40%3Cbuilds.apache.org%3E
> > > > >>
> > > > >> Patrick
> > > > >>
> > > > >>
> > > > >>
> > > > >>> Patrick
> > > > >>>
> > > > >>>
> > > > 
> > > >  -- Forwarded message -
> > > >  Da: Gavin McDonald 
> > > >  Date: Gio 16 Lug 2020, 18:33
> > > >  Subject: [IMPORTANT] - Migration to ci-builds.a.o
> > > >  To: builds 
> > > > 
> > > > 
> > > >  Hi All,
> > > 

Re: [IMPORTANT] - Migration to ci-builds.a.o

[Patrick Hunt]

On Mon, Jul 20, 2020 at 9:47 AM Enrico Olivelli  wrote:

> Il Lun 20 Lug 2020, 18:41 Patrick Hunt  ha scritto:
>
> > On Sat, Jul 18, 2020 at 12:20 PM Andor Molnar  wrote:
> >
> > > Hi Pat,
> > >
> > > I have admin rights in the new system too and probably can work on this
> > on
> > > Monday.
> > > What’s “matrix” config? Shouldn’t we just replicate the same jobs on
> the
> > > new instance?
> > >
> > >
> > Not sure on the exact name/feature but "matrix" is basically the ability
> to
> > say "run this build/test across a set of JDK versions" rather than a
> single
> > version. As a result, instead of 3 jobs for zk3.6.0, jdk 1/2/3 you end up
> > with a single job which runs three times, one for each jdk type and
> > summarizes the results. I've seen this before, I assume it's a feature of
> > jenkins itself?
> >
>
> We should use Jenkins files and this configuration will be easy and
> committed to git
>

The ability to do "gitops" would be amazing!

Patrick


>
> Enrico
>
>
>
> > Patrick
> >
> >
> > > Andor
> > >
> > >
> > >
> > > > On 2020. Jul 17., at 2:51, Patrick Hunt  wrote:
> > > >
> > > > I updated the job I linked earlier based on what's the latest on the
> > > legacy
> > > > jenkins. It ran successfully
> > > > https://ci-hadoop.apache.org/job/zookeeper-master-maven/215/
> > > >
> > > > I didn't replicate every config setting - main gap is the spotbugs
> > > > post-build, which seems to be missing from the new jenkins plugins.
> > > >
> > > > That's just maven master though. Not sure about the rest. Can we do
> > more
> > > of
> > > > a "matrix" config in the new system vs cloning all the time?
> > > >
> > > > Patrick
> > > >
> > > > On Thu, Jul 16, 2020 at 3:31 PM Patrick Hunt 
> wrote:
> > > >
> > > >>
> > > >> On Thu, Jul 16, 2020 at 3:22 PM Patrick Hunt 
> > wrote:
> > > >>
> > > >>>
> > > >>>
> > > >>> On Thu, Jul 16, 2020 at 12:56 PM Enrico Olivelli <
> > eolive...@gmail.com>
> > > >>> wrote:
> > > >>>
> > >  FYI
> > > 
> > > >>>
> > > >>> Fun. I do notice it says "Hadoop and related projects have their
> own
> > > >>> migration path to follow" - any insight on that? We are or are not
> > > lumped
> > > >>> in? I would assume we are?
> > > >>>
> > > >>> This (eventual migration) came up a while back on the Hadoop PMC
> and
> > I
> > > >>> volunteered to try for us (ZK). I was never able to get it to
> work, I
> > > >>> provided feedback to infra  but they never got back, as such we
> have
> > a
> > > >>> project here that's not working with some basic dependencies
> missing:
> > > >>> https://ci-hadoop.apache.org/job/zookeeper-master-maven/
> > > >>>
> > > >>> That said, we can try again. Can we verify where ZK is supposed to
> > > land?
> > > >>> Perhaps we can try to delete and recreate the POC job I created at
> > that
> > > >>> link to see if we can get it working?
> > > >>>
> > > >>>
> > > >> I see another email thread on the list saying that we are part of
> said
> > > >> "related projects". We are expected to move to
> > > >> http://ci-hadoop.apache.org/ within 4 weeks. Seems nodes are
> already
> > > >> being removed/migrated from the "H#" pool.
> > > >>
> > > >> Also this:
> > > >>
> > > >> There are over 400 plugins on the current builds.apache.org - most
> of
> > > which
> > > >> we don't need any more, or are replaced with different plugins on
> the
> > > new
> > > >> system. I expect there may be some plugins we still need to install
> to
> > > get
> > > >> you going again, which is why it is vitally important that you start
> > > >> testing and migrating your jobs over *now*. You should all have
> auth.
> > > >>
> > > >> Any questions, feel free to email the hadoop-migrati...@apache.org
> > > list if
> > > >> you are one of the projects listed below. The rest of you, not
> > listed, a
> > > >> similar email to this one will be posted for you shortly on
> > builds@a.o.
> > > >>
> > > >>
> > > >> full details
> > > >>
> > >
> >
> https://lists.apache.org/thread.html/r21c9d40cdbf5461143dd7eb4ff48a200c2fd20c50e946884f61318fd%40%3Cbuilds.apache.org%3E
> > > >>
> > > >> Patrick
> > > >>
> > > >>
> > > >>
> > > >>> Patrick
> > > >>>
> > > >>>
> > > 
> > >  -- Forwarded message -
> > >  Da: Gavin McDonald 
> > >  Date: Gio 16 Lug 2020, 18:33
> > >  Subject: [IMPORTANT] - Migration to ci-builds.a.o
> > >  To: builds 
> > > 
> > > 
> > >  Hi All,
> > > 
> > >  This NOTICE is for everyone on builds.apache.org. We are
> migrating
> > > to a
> > >  new
> > >  Cloudbees based Client Master called https://ci-builds.apache.org
> .
> > > The
> > >  migrations of all jobs needs to be done before the switch off date
> > of
> > >  15th
> > >  August 2020, so you have a maximum of 4 weeks.
> > > 
> > >  There is no tool or automated way of migrating your jobs, the
> > >  differences in the platforms, the plugins and the setup makes it
> > >  impossible
> > >  to do in a safe way. So, you all 

Re: [IMPORTANT] - Migration to ci-builds.a.o

[Enrico Olivelli]

Il Lun 20 Lug 2020, 18:41 Patrick Hunt  ha scritto:

> On Sat, Jul 18, 2020 at 12:20 PM Andor Molnar  wrote:
>
> > Hi Pat,
> >
> > I have admin rights in the new system too and probably can work on this
> on
> > Monday.
> > What’s “matrix” config? Shouldn’t we just replicate the same jobs on the
> > new instance?
> >
> >
> Not sure on the exact name/feature but "matrix" is basically the ability to
> say "run this build/test across a set of JDK versions" rather than a single
> version. As a result, instead of 3 jobs for zk3.6.0, jdk 1/2/3 you end up
> with a single job which runs three times, one for each jdk type and
> summarizes the results. I've seen this before, I assume it's a feature of
> jenkins itself?
>

We should use Jenkins files and this configuration will be easy and
committed to git

Enrico



> Patrick
>
>
> > Andor
> >
> >
> >
> > > On 2020. Jul 17., at 2:51, Patrick Hunt  wrote:
> > >
> > > I updated the job I linked earlier based on what's the latest on the
> > legacy
> > > jenkins. It ran successfully
> > > https://ci-hadoop.apache.org/job/zookeeper-master-maven/215/
> > >
> > > I didn't replicate every config setting - main gap is the spotbugs
> > > post-build, which seems to be missing from the new jenkins plugins.
> > >
> > > That's just maven master though. Not sure about the rest. Can we do
> more
> > of
> > > a "matrix" config in the new system vs cloning all the time?
> > >
> > > Patrick
> > >
> > > On Thu, Jul 16, 2020 at 3:31 PM Patrick Hunt  wrote:
> > >
> > >>
> > >> On Thu, Jul 16, 2020 at 3:22 PM Patrick Hunt 
> wrote:
> > >>
> > >>>
> > >>>
> > >>> On Thu, Jul 16, 2020 at 12:56 PM Enrico Olivelli <
> eolive...@gmail.com>
> > >>> wrote:
> > >>>
> >  FYI
> > 
> > >>>
> > >>> Fun. I do notice it says "Hadoop and related projects have their own
> > >>> migration path to follow" - any insight on that? We are or are not
> > lumped
> > >>> in? I would assume we are?
> > >>>
> > >>> This (eventual migration) came up a while back on the Hadoop PMC and
> I
> > >>> volunteered to try for us (ZK). I was never able to get it to work, I
> > >>> provided feedback to infra  but they never got back, as such we have
> a
> > >>> project here that's not working with some basic dependencies missing:
> > >>> https://ci-hadoop.apache.org/job/zookeeper-master-maven/
> > >>>
> > >>> That said, we can try again. Can we verify where ZK is supposed to
> > land?
> > >>> Perhaps we can try to delete and recreate the POC job I created at
> that
> > >>> link to see if we can get it working?
> > >>>
> > >>>
> > >> I see another email thread on the list saying that we are part of said
> > >> "related projects". We are expected to move to
> > >> http://ci-hadoop.apache.org/ within 4 weeks. Seems nodes are already
> > >> being removed/migrated from the "H#" pool.
> > >>
> > >> Also this:
> > >>
> > >> There are over 400 plugins on the current builds.apache.org - most of
> > which
> > >> we don't need any more, or are replaced with different plugins on the
> > new
> > >> system. I expect there may be some plugins we still need to install to
> > get
> > >> you going again, which is why it is vitally important that you start
> > >> testing and migrating your jobs over *now*. You should all have auth.
> > >>
> > >> Any questions, feel free to email the hadoop-migrati...@apache.org
> > list if
> > >> you are one of the projects listed below. The rest of you, not
> listed, a
> > >> similar email to this one will be posted for you shortly on
> builds@a.o.
> > >>
> > >>
> > >> full details
> > >>
> >
> https://lists.apache.org/thread.html/r21c9d40cdbf5461143dd7eb4ff48a200c2fd20c50e946884f61318fd%40%3Cbuilds.apache.org%3E
> > >>
> > >> Patrick
> > >>
> > >>
> > >>
> > >>> Patrick
> > >>>
> > >>>
> > 
> >  -- Forwarded message -
> >  Da: Gavin McDonald 
> >  Date: Gio 16 Lug 2020, 18:33
> >  Subject: [IMPORTANT] - Migration to ci-builds.a.o
> >  To: builds 
> > 
> > 
> >  Hi All,
> > 
> >  This NOTICE is for everyone on builds.apache.org. We are migrating
> > to a
> >  new
> >  Cloudbees based Client Master called https://ci-builds.apache.org.
> > The
> >  migrations of all jobs needs to be done before the switch off date
> of
> >  15th
> >  August 2020, so you have a maximum of 4 weeks.
> > 
> >  There is no tool or automated way of migrating your jobs, the
> >  differences in the platforms, the plugins and the setup makes it
> >  impossible
> >  to do in a safe way. So, you all need to start creating new jobs on
> >  ci-infra.a.o and then , when you are happy, turn off your old builds
> > on
> >  builds.a.o.
> > 
> >  There are currently 4 agents over there ready to take jobs, plus a
> >  floating
> >  agent which is shared amongst many masters (more to come). I will
> > migrate
> >  away 2 more agents from builds.a.o to ci-builds.a.o every few days,
> > and
> >  will keep an eye 

Re: [IMPORTANT] - Migration to ci-builds.a.o

[Patrick Hunt]

On Sat, Jul 18, 2020 at 12:20 PM Andor Molnar  wrote:

> Hi Pat,
>
> I have admin rights in the new system too and probably can work on this on
> Monday.
> What’s “matrix” config? Shouldn’t we just replicate the same jobs on the
> new instance?
>
>
Not sure on the exact name/feature but "matrix" is basically the ability to
say "run this build/test across a set of JDK versions" rather than a single
version. As a result, instead of 3 jobs for zk3.6.0, jdk 1/2/3 you end up
with a single job which runs three times, one for each jdk type and
summarizes the results. I've seen this before, I assume it's a feature of
jenkins itself?

Patrick


> Andor
>
>
>
> > On 2020. Jul 17., at 2:51, Patrick Hunt  wrote:
> >
> > I updated the job I linked earlier based on what's the latest on the
> legacy
> > jenkins. It ran successfully
> > https://ci-hadoop.apache.org/job/zookeeper-master-maven/215/
> >
> > I didn't replicate every config setting - main gap is the spotbugs
> > post-build, which seems to be missing from the new jenkins plugins.
> >
> > That's just maven master though. Not sure about the rest. Can we do more
> of
> > a "matrix" config in the new system vs cloning all the time?
> >
> > Patrick
> >
> > On Thu, Jul 16, 2020 at 3:31 PM Patrick Hunt  wrote:
> >
> >>
> >> On Thu, Jul 16, 2020 at 3:22 PM Patrick Hunt  wrote:
> >>
> >>>
> >>>
> >>> On Thu, Jul 16, 2020 at 12:56 PM Enrico Olivelli 
> >>> wrote:
> >>>
>  FYI
> 
> >>>
> >>> Fun. I do notice it says "Hadoop and related projects have their own
> >>> migration path to follow" - any insight on that? We are or are not
> lumped
> >>> in? I would assume we are?
> >>>
> >>> This (eventual migration) came up a while back on the Hadoop PMC and I
> >>> volunteered to try for us (ZK). I was never able to get it to work, I
> >>> provided feedback to infra  but they never got back, as such we have a
> >>> project here that's not working with some basic dependencies missing:
> >>> https://ci-hadoop.apache.org/job/zookeeper-master-maven/
> >>>
> >>> That said, we can try again. Can we verify where ZK is supposed to
> land?
> >>> Perhaps we can try to delete and recreate the POC job I created at that
> >>> link to see if we can get it working?
> >>>
> >>>
> >> I see another email thread on the list saying that we are part of said
> >> "related projects". We are expected to move to
> >> http://ci-hadoop.apache.org/ within 4 weeks. Seems nodes are already
> >> being removed/migrated from the "H#" pool.
> >>
> >> Also this:
> >>
> >> There are over 400 plugins on the current builds.apache.org - most of
> which
> >> we don't need any more, or are replaced with different plugins on the
> new
> >> system. I expect there may be some plugins we still need to install to
> get
> >> you going again, which is why it is vitally important that you start
> >> testing and migrating your jobs over *now*. You should all have auth.
> >>
> >> Any questions, feel free to email the hadoop-migrati...@apache.org
> list if
> >> you are one of the projects listed below. The rest of you, not listed, a
> >> similar email to this one will be posted for you shortly on builds@a.o.
> >>
> >>
> >> full details
> >>
> https://lists.apache.org/thread.html/r21c9d40cdbf5461143dd7eb4ff48a200c2fd20c50e946884f61318fd%40%3Cbuilds.apache.org%3E
> >>
> >> Patrick
> >>
> >>
> >>
> >>> Patrick
> >>>
> >>>
> 
>  -- Forwarded message -
>  Da: Gavin McDonald 
>  Date: Gio 16 Lug 2020, 18:33
>  Subject: [IMPORTANT] - Migration to ci-builds.a.o
>  To: builds 
> 
> 
>  Hi All,
> 
>  This NOTICE is for everyone on builds.apache.org. We are migrating
> to a
>  new
>  Cloudbees based Client Master called https://ci-builds.apache.org.
> The
>  migrations of all jobs needs to be done before the switch off date of
>  15th
>  August 2020, so you have a maximum of 4 weeks.
> 
>  There is no tool or automated way of migrating your jobs, the
>  differences in the platforms, the plugins and the setup makes it
>  impossible
>  to do in a safe way. So, you all need to start creating new jobs on
>  ci-infra.a.o and then , when you are happy, turn off your old builds
> on
>  builds.a.o.
> 
>  There are currently 4 agents over there ready to take jobs, plus a
>  floating
>  agent which is shared amongst many masters (more to come). I will
> migrate
>  away 2 more agents from builds.a.o to ci-builds.a.o every few days,
> and
>  will keep an eye of load across both and adjust accordingly.
> 
>  If needed, create a ticket on INFRA jira for any issues that crop up,
> or
>  email here on builds@a.o. there may be one or two plugins we need to
>  install/tweak etc.
> 
>  We will be not using 'Views' at the top level, but rather we will take
>  advantage of 'Folders Plus' - each project will get its own Folder and
>  have
>  authorisation access to create/edit jobs etc 

Grafana dashboard, update?

[Simon Karberg]

Hi,

I have tried to import the dashboard 10465 (ZooKeeper by Prometheusby
maoling)
I found out that many of the graphs doesn't include the use of the
defined DS_PROMETHEUS so it just defaults to our default data source which
is influxdb.

I haven't been through the whole json file since it's almost 9000 lines,
but is there an updated version on it's way?

-- 

*Simon Karberg* / Operations Engineer
Mobile: +45 28901033

[image: Agillic logo]

www.agillic.com
Support Desk: +45 32 63 08 00
Copenhagen Office: +45 70 25 28 25
London Office: +44 7711 744892

[image: Facebook] 
[image: LinkedIn] 

Re: [IMPORTANT] - Migration to ci-builds.a.o

[Andor Molnar]

There's one thing I noticed is that the summary of each build is
missing from the build's status page. It's probably caused by a missing
Jenkins plugin, but I don't know. Build preferences are roughly the
same.

Andor



On Mon, 2020-07-20 at 15:48 +0200, Andor Molnar wrote:
> Hi,
> 
> I created a few new jobs based on your suggestions. Before going
> forward please take a look at them.
> 
> I created Jdk LTS jobs (8 and 11) for all active branches: 3.5, 3.6
> and
> master. Also added the Maven option surefire.forkcount=4 to all jobs
> to
> limit the number of concurrent threads in unit tests.
> 
> Do you think we also need non-LTS Java build jobs too?
> 
> https://ci-hadoop.apache.org/view/ZooKeeper/
> 
> Andor
> 
> 
> 
> On Sun, 2020-07-19 at 07:50 +0200, Enrico Olivelli wrote:
> > Il Sab 18 Lug 2020, 21:20 Andor Molnar  ha
> > scritto:
> > 
> > > Hi Pat,
> > > 
> > > I have admin rights in the new system too and probably can work
> > > on
> > > this on
> > > Monday.
> > > What’s “matrix” config? Shouldn’t we just replicate the same jobs
> > > on the
> > > new instance?
> > > 
> > 
> > This is my list of important jobs:
> > - maven builds of master against every supported jdk +EA (for JDK
> > outreach
> > quality program)
> > - maven build of master on windows on jdk8
> > - maven build of branch-3.5 and branch-3.6
> > - ant build of branch-3.5 on jdk8
> > - maven precommit job
> > 
> > Enrico
> > 
> > 
> > > Andor
> > > 
> > > 
> > > 
> > > > On 2020. Jul 17., at 2:51, Patrick Hunt 
> > > > wrote:
> > > > 
> > > > I updated the job I linked earlier based on what's the latest
> > > > on
> > > > the
> > > legacy
> > > > jenkins. It ran successfully
> > > > https://ci-hadoop.apache.org/job/zookeeper-master-maven/215/
> > > > 
> > > > I didn't replicate every config setting - main gap is the
> > > > spotbugs
> > > > post-build, which seems to be missing from the new jenkins
> > > > plugins.
> > > > 
> > > > That's just maven master though. Not sure about the rest. Can
> > > > we
> > > > do more
> > > of
> > > > a "matrix" config in the new system vs cloning all the time?
> > > > 
> > > > Patrick
> > > > 
> > > > On Thu, Jul 16, 2020 at 3:31 PM Patrick Hunt 
> > > > wrote:
> > > > 
> > > > > On Thu, Jul 16, 2020 at 3:22 PM Patrick Hunt <
> > > > > ph...@apache.org>
> > > > > wrote:
> > > > > 
> > > > > > On Thu, Jul 16, 2020 at 12:56 PM Enrico Olivelli <
> > > > > > eolive...@gmail.com>
> > > > > > wrote:
> > > > > > 
> > > > > > > FYI
> > > > > > > 
> > > > > > 
> > > > > > Fun. I do notice it says "Hadoop and related projects have
> > > > > > their own
> > > > > > migration path to follow" - any insight on that? We are or
> > > > > > are not
> > > lumped
> > > > > > in? I would assume we are?
> > > > > > 
> > > > > > This (eventual migration) came up a while back on the
> > > > > > Hadoop
> > > > > > PMC and I
> > > > > > volunteered to try for us (ZK). I was never able to get it
> > > > > > to
> > > > > > work, I
> > > > > > provided feedback to infra  but they never got back, as
> > > > > > such
> > > > > > we have a
> > > > > > project here that's not working with some basic
> > > > > > dependencies
> > > > > > missing:
> > > > > > https://ci-hadoop.apache.org/job/zookeeper-master-maven/
> > > > > > 
> > > > > > That said, we can try again. Can we verify where ZK is
> > > > > > supposed to
> > > land?
> > > > > > Perhaps we can try to delete and recreate the POC job I
> > > > > > created at that
> > > > > > link to see if we can get it working?
> > > > > > 
> > > > > > 
> > > > > I see another email thread on the list saying that we are
> > > > > part
> > > > > of said
> > > > > "related projects". We are expected to move to
> > > > > http://ci-hadoop.apache.org/ within 4 weeks. Seems nodes are
> > > > > already
> > > > > being removed/migrated from the "H#" pool.
> > > > > 
> > > > > Also this:
> > > > > 
> > > > > There are over 400 plugins on the current builds.apache.org -
> > > > > most of
> > > which
> > > > > we don't need any more, or are replaced with different
> > > > > plugins
> > > > > on the
> > > new
> > > > > system. I expect there may be some plugins we still need to
> > > > > install to
> > > get
> > > > > you going again, which is why it is vitally important that
> > > > > you
> > > > > start
> > > > > testing and migrating your jobs over *now*. You should all
> > > > > have
> > > > > auth.
> > > > > 
> > > > > Any questions, feel free to email the 
> > > > > hadoop-migrati...@apache.org
> > > list if
> > > > > you are one of the projects listed below. The rest of you,
> > > > > not
> > > > > listed, a
> > > > > similar email to this one will be posted for you shortly on 
> > > > > builds@a.o.
> > > > > 
> > > > > 
> > > > > full details
> > > > > 
> > > https://lists.apache.org/thread.html/r21c9d40cdbf5461143dd7eb4ff48a200c2fd20c50e946884f61318fd%40%3Cbuilds.apache.org%3E
> > > > > Patrick
> > > > > 
> > > > > 
> > > > > 
> > > > > > Patrick
> > > > > > 
> > > > > > 
> > > > > > > 

Re: [IMPORTANT] - Migration to ci-builds.a.o

[Andor Molnar]

Hi,

I created a few new jobs based on your suggestions. Before going
forward please take a look at them.

I created Jdk LTS jobs (8 and 11) for all active branches: 3.5, 3.6 and
master. Also added the Maven option surefire.forkcount=4 to all jobs to
limit the number of concurrent threads in unit tests.

Do you think we also need non-LTS Java build jobs too?

https://ci-hadoop.apache.org/view/ZooKeeper/

Andor



On Sun, 2020-07-19 at 07:50 +0200, Enrico Olivelli wrote:
> Il Sab 18 Lug 2020, 21:20 Andor Molnar  ha scritto:
> 
> > Hi Pat,
> > 
> > I have admin rights in the new system too and probably can work on
> > this on
> > Monday.
> > What’s “matrix” config? Shouldn’t we just replicate the same jobs
> > on the
> > new instance?
> > 
> 
> This is my list of important jobs:
> - maven builds of master against every supported jdk +EA (for JDK
> outreach
> quality program)
> - maven build of master on windows on jdk8
> - maven build of branch-3.5 and branch-3.6
> - ant build of branch-3.5 on jdk8
> - maven precommit job
> 
> Enrico
> 
> 
> > Andor
> > 
> > 
> > 
> > > On 2020. Jul 17., at 2:51, Patrick Hunt  wrote:
> > > 
> > > I updated the job I linked earlier based on what's the latest on
> > > the
> > legacy
> > > jenkins. It ran successfully
> > > https://ci-hadoop.apache.org/job/zookeeper-master-maven/215/
> > > 
> > > I didn't replicate every config setting - main gap is the
> > > spotbugs
> > > post-build, which seems to be missing from the new jenkins
> > > plugins.
> > > 
> > > That's just maven master though. Not sure about the rest. Can we
> > > do more
> > of
> > > a "matrix" config in the new system vs cloning all the time?
> > > 
> > > Patrick
> > > 
> > > On Thu, Jul 16, 2020 at 3:31 PM Patrick Hunt 
> > > wrote:
> > > 
> > > > On Thu, Jul 16, 2020 at 3:22 PM Patrick Hunt 
> > > > wrote:
> > > > 
> > > > > 
> > > > > On Thu, Jul 16, 2020 at 12:56 PM Enrico Olivelli <
> > > > > eolive...@gmail.com>
> > > > > wrote:
> > > > > 
> > > > > > FYI
> > > > > > 
> > > > > 
> > > > > Fun. I do notice it says "Hadoop and related projects have
> > > > > their own
> > > > > migration path to follow" - any insight on that? We are or
> > > > > are not
> > lumped
> > > > > in? I would assume we are?
> > > > > 
> > > > > This (eventual migration) came up a while back on the Hadoop
> > > > > PMC and I
> > > > > volunteered to try for us (ZK). I was never able to get it to
> > > > > work, I
> > > > > provided feedback to infra  but they never got back, as such
> > > > > we have a
> > > > > project here that's not working with some basic dependencies
> > > > > missing:
> > > > > https://ci-hadoop.apache.org/job/zookeeper-master-maven/
> > > > > 
> > > > > That said, we can try again. Can we verify where ZK is
> > > > > supposed to
> > land?
> > > > > Perhaps we can try to delete and recreate the POC job I
> > > > > created at that
> > > > > link to see if we can get it working?
> > > > > 
> > > > > 
> > > > I see another email thread on the list saying that we are part
> > > > of said
> > > > "related projects". We are expected to move to
> > > > http://ci-hadoop.apache.org/ within 4 weeks. Seems nodes are
> > > > already
> > > > being removed/migrated from the "H#" pool.
> > > > 
> > > > Also this:
> > > > 
> > > > There are over 400 plugins on the current builds.apache.org -
> > > > most of
> > which
> > > > we don't need any more, or are replaced with different plugins
> > > > on the
> > new
> > > > system. I expect there may be some plugins we still need to
> > > > install to
> > get
> > > > you going again, which is why it is vitally important that you
> > > > start
> > > > testing and migrating your jobs over *now*. You should all have
> > > > auth.
> > > > 
> > > > Any questions, feel free to email the 
> > > > hadoop-migrati...@apache.org
> > list if
> > > > you are one of the projects listed below. The rest of you, not
> > > > listed, a
> > > > similar email to this one will be posted for you shortly on 
> > > > builds@a.o.
> > > > 
> > > > 
> > > > full details
> > > > 
> > https://lists.apache.org/thread.html/r21c9d40cdbf5461143dd7eb4ff48a200c2fd20c50e946884f61318fd%40%3Cbuilds.apache.org%3E
> > > > Patrick
> > > > 
> > > > 
> > > > 
> > > > > Patrick
> > > > > 
> > > > > 
> > > > > > -- Forwarded message -
> > > > > > Da: Gavin McDonald 
> > > > > > Date: Gio 16 Lug 2020, 18:33
> > > > > > Subject: [IMPORTANT] - Migration to ci-builds.a.o
> > > > > > To: builds 
> > > > > > 
> > > > > > 
> > > > > > Hi All,
> > > > > > 
> > > > > > This NOTICE is for everyone on builds.apache.org. We are
> > > > > > migrating
> > to a
> > > > > > new
> > > > > > Cloudbees based Client Master called 
> > > > > > https://ci-builds.apache.org.
> > The
> > > > > > migrations of all jobs needs to be done before the switch
> > > > > > off date of
> > > > > > 15th
> > > > > > August 2020, so you have a maximum of 4 weeks.
> > > > > > 
> > > > > > There is no tool or automated way of migrating your jobs,
> 

Re: Upgrading existing non-TLS cluster with no downtime

[Szalay-Bekő Máté]

echo "stat" | nc localhost 2182Hi,

I guess this is the part you are referring:
https://zookeeper.apache.org/doc/r3.5.8/zookeeperAdmin.html#Upgrading+existing+nonTLS+cluster
(your link was pointing to the 3.3.2 admin guide where this chapter was
missing)

> 1) When I set sslQuorum=true  and portUnification=true on the first
server,
does it go out of the quorum? And when these properties are set in the
second server, a new quorum of first and second server is formed and now
the third server is out of quorum. When the 3rd server follows suit, it is
added back to the quorum.

the "sslQuorum=true  and portUnification=true" setting is needed in step 4
(although the numbering is bad in the markdown...). After step 3 you
already have a 3 server quorum up with portUnification=true, meaning the
cluster can handle both TLS/SSL and regular/non-secure connections. So when
you restart server 1 with sslQuorum=true, then it will be able to re-join
to the quorum, as server 2 and 3 are capable of handling SSL connections
(even if they are not using it for connection initiation). So ideally
between restarting each servers with sslQuorum=true, you always should have
a 3 node full quorum.

> 2) The guideline says to check after restarting every broker that the
quorum is healthy, is there any metric to track that?

I send the "stat" command to all nodes to see if everyone is connected to
the quorum. E.g.: echo "stat" | nc localhost 2181
I usually use 4-letter-word commands but the REST admin API works as well,
and actually that is the officially recommended way, as the 4-letter-words
are / will be deprecated some time.
For the admin server see:
https://zookeeper.apache.org/doc/r3.5.8/zookeeperAdmin.html#sc_adminserver

Kind regards,
Mate

On Tue, Jul 14, 2020 at 10:52 PM Sankalp Bhatia 
wrote:

> +users
>
> On Tue, 14 Jul 2020 at 21:51, Sankalp Bhatia 
> wrote:
>
> > Hi All,
> >
> > I am trying to follow the section "Upgrading existing non-TLS cluster
> with
> > no downtime" in the zookeeper guide :
> > https://zookeeper.apache.org/doc/r3.3.2/zookeeperAdmin.html
> >
> > I have an ensemble of 3 servers. I have a couple of questions:
> >
> > 1) When I set sslQuorum=true  and portUnification=true on the first
> > server, does it go out of the quorum? And when these properties are set
> > in the second server, a new quorum of first and second server is formed
> and
> > now the third server is out of quorum. When the 3rd server follows suit,
> it
> > is added back to the quorum.
> >
> > If this is the case, what is the use of a the port-unification feature
> > here?
> >
> > 2) The guideline says to check after restarting every broker that the
> > quorum is healthy, is there any metric to track that?
> >
> > Thanks,
> > Sankalp
> >
> >
> >
> >
>