[GitHub] [zookeeper] phunt commented on issue #962: ZOOKEEPER-3405: Upgrade the version of Jackson-databind to address OWASP CVE

[GitBox]

phunt commented on issue #962: ZOOKEEPER-3405: Upgrade the version of 
Jackson-databind to address OWASP CVE
URL: https://github.com/apache/zookeeper/pull/962#issuecomment-497200481
 
 
   retest maven build


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.
 
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org


With regards,
Apache Git Services

Re: ZooKeeper-Find-Flaky-Tests job updated

[Andor Molnar]

In theory, not. But I'm worried about too.
Enrico, can we have or already have a similar view of Maven builds in
Jenkins?
We'll also need a Maven based Find Flaky Test job too.

Andor



On Thu, May 30, 2019 at 1:43 AM Patrick Hunt  wrote:

> "less problems"? TBH the maven job seems super flakey compared to what I'm
> seeing with Ant, a step down. I submitted a PR and it's failed maven
> multiple times with random failures:
> https://github.com/apache/zookeeper/pull/962
> are we doing something different between the two?
>
> Patrick
>
> On Wed, May 29, 2019 at 3:22 PM Enrico Olivelli 
> wrote:
>
> > Good.
> > I hope to be able to drop ant soon.
> > Less jobs, less problems
> >
> > Enrico
> >
> > Il mer 29 mag 2019, 14:48 Andor Molnar  ha scritto:
> >
> > > Hi!
> > >
> > > I’ve updated the job to run on all recent builds based on the following
> > > view:
> > >
> > > https://builds.apache.org/view/S-Z/view/ZooKeeper/ <
> > > https://builds.apache.org/view/S-Z/view/ZooKeeper/>
> > >
> > > Andor
> > >
> > >
> >
>

Re: [ANNOUNCE] New ZooKeeper committer: Norbert Kalmar

[Michael Han]

Congratulations Norbert!

On Tue, May 28, 2019 at 2:29 PM Dinesh Appavoo 
wrote:

> Awesome. Congrats Norbert!
>
> On Tue, May 28, 2019 at 10:51 AM Brian Nixon 
> wrote:
>
> > Congrats, Norbert! Well earned.
> >
> > On Mon, May 27, 2019 at 3:49 AM Andor Molnar  >
> > wrote:
> >
> > > Congratulations Norbert!
> > >
> > > Andor
> > >
> > >
> > >
> > > On Mon, May 27, 2019 at 11:52 AM Flavio Junqueira 
> > wrote:
> > >
> > > > Congrats, Norbert!
> > > >
> > > > -Flavio
> > > >
> > > > > On 27 May 2019, at 11:01, Tamas Penzes  >
> > > > wrote:
> > > > >
> > > > > Congrats Norbert!
> > > > >
> > > > > On Sun, May 26, 2019 at 11:21 PM Patrick Hunt 
> > > wrote:
> > > > >
> > > > >> The Apache ZooKeeper PMC recently extended committer karma to
> > Norbert
> > > > >> and he has accepted. Norbert has made some great contributions and
> > we
> > > > >> are looking forward to even more :)
> > > > >>
> > > > >> Congratulations and welcome aboard, Norbert!
> > > > >>
> > > >
> > > >
> > >
> >
>

Re: [ANNOUNCE] New ZooKeeper committer: Enrico Olivelli

[Michael Han]

Congratulations Enrico!

On Tue, May 28, 2019 at 2:05 PM Dinesh Appavoo 
wrote:

> Great news. Congrats Enrico!
>
> On Tue, May 28, 2019 at 10:51 AM Brian Nixon 
> wrote:
>
> > Awesome! Congrats, Enrico!
> >
> > On Mon, May 27, 2019 at 3:56 AM Andor Molnar  >
> > wrote:
> >
> > > Congratulations Enrico.
> > >
> > > Andor
> > >
> > >
> > >
> > > On Mon, May 27, 2019 at 11:04 AM Tamas Penzes
> >  > > >
> > > wrote:
> > >
> > > > Congrats Enrico!
> > > >
> > > > On Sun, May 26, 2019 at 11:19 PM Patrick Hunt 
> > wrote:
> > > >
> > > > > The Apache ZooKeeper PMC recently extended committer karma to
> Enrico
> > > > > and he has accepted. Enrico has made some great contributions and
> we
> > > > > are looking forward to even more :)
> > > > >
> > > > > Congratulations and welcome aboard, Enrico!
> > > > >
> > > >
> > >
> >
>

[GitHub] [zookeeper] hanm commented on issue #953: ZOOKEEPER-3398 Learner.connectToLeader() may take too long to time-out

[GitBox]

hanm commented on issue #953: ZOOKEEPER-3398 Learner.connectToLeader() may take 
too long to time-out 
URL: https://github.com/apache/zookeeper/pull/953#issuecomment-497156627
 
 
   >> if this config could be generalized to be used exclusively for socket 
connection timeout
   
   I am not sure if all socket connection timeouts can be generalized. It seems 
to me the timeout configuration is case by case. But, an improvement regardless 
if we can generalize this or not, is to have a timeout provisioning class that 
provides a set of interfaces so we can query different timeouts with different 
semantics and have the actual timeout implementation in a single place, then we 
can get rid of all the `self.tickTime * self.initLimit` or `self.tickTime * 
self.syncLimit` scattered through code base. We could even consider teaching 
this class to be adaptive of network conditions instead of relying on static 
timeout values.


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.
 
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org


With regards,
Apache Git Services

[GitHub] [zookeeper] hanm commented on issue #953: ZOOKEEPER-3398 Learner.connectToLeader() may take too long to time-out

[GitBox]

hanm commented on issue #953: ZOOKEEPER-3398 Learner.connectToLeader() may take 
too long to time-out 
URL: https://github.com/apache/zookeeper/pull/953#issuecomment-497155402
 
 
   When a leader is partitioned after LE, a smaller socket timeout value will 
make it faster to detect the partition. But I can see choose a small value can 
also impact follower / leader connection in normal use case, especially if the 
latency between the two is big (e.g. over WAN). How do we choose a value that 
works for both cases?


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.
 
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org


With regards,
Apache Git Services

[GitHub] [zookeeper] hanm commented on a change in pull request #953: ZOOKEEPER-3398 Learner.connectToLeader() may take too long to time-out

[GitBox]

hanm commented on a change in pull request #953: ZOOKEEPER-3398 
Learner.connectToLeader() may take too long to time-out 
URL: https://github.com/apache/zookeeper/pull/953#discussion_r288816030
 
 

 ##
 File path: conf/zoo_sample.cfg
 ##
 @@ -6,6 +6,9 @@ initLimit=10
 # The number of ticks that can pass between 
 # sending a request and getting an acknowledgement
 syncLimit=5
+# The number of ticks that followers can take
+# to connect to the leader after leader election
+connectToLeaderLimit=5
 
 Review comment:
   I think we probably want to rename this variable to something like 
`connectToLearnerMasterLimit`, or if we keep the current name, at least 
document that this will also impact the socket timeout between observer and 
learner master. This is unfortunate, so maybe we ultimately want to rename the 
method of `connectToLeader` to something like `connectToLearnerMaster`?


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.
 
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org


With regards,
Apache Git Services

[GitHub] [zookeeper] hanm commented on a change in pull request #953: ZOOKEEPER-3398 Learner.connectToLeader() may take too long to time-out

[GitBox]

hanm commented on a change in pull request #953: ZOOKEEPER-3398 
Learner.connectToLeader() may take too long to time-out 
URL: https://github.com/apache/zookeeper/pull/953#discussion_r288816455
 
 

 ##
 File path: 
zookeeper-server/src/main/java/org/apache/zookeeper/server/quorum/QuorumPeer.java
 ##
 @@ -1735,8 +1741,22 @@ public void setSyncLimit(int syncLimit) {
 LOG.info("syncLimit set to " + syncLimit);
 this.syncLimit = syncLimit;
 }
-
-
+
+/**
+ * Get the connectToLeaderLimit
+ */
+public int getConnectToLeaderLimit() {
+return connectToLeaderLimit;
+}
+
+/**
+ * Set the connectToLeaderLimit
+ */
+public void setConnectToLeaderLimit(int connectToLeaderLimit) {
+LOG.info("connectToLeaderLimit set to " + connectToLeaderLimit);
 
 Review comment:
   nit: use parameterized (`{}`) log.


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.
 
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org


With regards,
Apache Git Services

[GitHub] [zookeeper] hanm commented on issue #931: ZOOKEEPER-3373:need change description for "Single System Image" guarantee in document

[GitBox]

hanm commented on issue #931: ZOOKEEPER-3373:need change description for 
"Single System Image" guarantee in document
URL: https://github.com/apache/zookeeper/pull/931#issuecomment-497152729
 
 
   I agree the original statement is not very clear, but instead of changing 
it, how about actually clarify it with this:
   
   A client will see the same view of the service regardless of the server that 
it connects to, and a client will never see an older view of the system even if 
the client fails over to a different server with the same session.


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.
 
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org


With regards,
Apache Git Services

Re: ZooKeeper-Find-Flaky-Tests job updated

[Patrick Hunt]

"less problems"? TBH the maven job seems super flakey compared to what I'm
seeing with Ant, a step down. I submitted a PR and it's failed maven
multiple times with random failures:
https://github.com/apache/zookeeper/pull/962
are we doing something different between the two?

Patrick

On Wed, May 29, 2019 at 3:22 PM Enrico Olivelli  wrote:

> Good.
> I hope to be able to drop ant soon.
> Less jobs, less problems
>
> Enrico
>
> Il mer 29 mag 2019, 14:48 Andor Molnar  ha scritto:
>
> > Hi!
> >
> > I’ve updated the job to run on all recent builds based on the following
> > view:
> >
> > https://builds.apache.org/view/S-Z/view/ZooKeeper/ <
> > https://builds.apache.org/view/S-Z/view/ZooKeeper/>
> >
> > Andor
> >
> >
>

[GitHub] [zookeeper] enixon commented on issue #963: ZOOKEEPER-3406: Update website for new mailing lists

[GitBox]

enixon commented on issue #963: ZOOKEEPER-3406: Update website for new mailing 
lists
URL: https://github.com/apache/zookeeper/pull/963#issuecomment-497144847
 
 
   lgtm


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.
 
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org


With regards,
Apache Git Services

[jira] [Commented] (ZOOKEEPER-3382) Update Documentation: If you only have one storage device

[Hudson (JIRA)]

[ 
https://issues.apache.org/jira/browse/ZOOKEEPER-3382?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16851368#comment-16851368
 ] 

Hudson commented on ZOOKEEPER-3382:
---

SUCCESS: Integrated in Jenkins build Zookeeper-trunk-single-thread #379 (See 
[https://builds.apache.org/job/Zookeeper-trunk-single-thread/379/])
ZOOKEEPER-3382: Update Documentation: If you only have one storage (andor: rev 
f7bdab002aa01677145654f8a1f93a45969d22cd)
* (edit) zookeeper-docs/src/main/resources/markdown/zookeeperAdmin.md
* (edit) zookeeper-docs/src/main/resources/markdown/zookeeperProgrammers.md


> Update Documentation: If you only have one storage device
> -
>
> Key: ZOOKEEPER-3382
> URL: https://issues.apache.org/jira/browse/ZOOKEEPER-3382
> Project: ZooKeeper
>  Issue Type: Improvement
>  Components: documentation
>Affects Versions: 3.6.0, 3.5.5, 3.4.15
>Reporter: David Mollitor
>Assignee: David Mollitor
>Priority: Minor
>  Labels: pull-request-available
> Fix For: 3.6.0
>
>  Time Spent: 0.5h
>  Remaining Estimate: 0h
>
> {quote}
> If you only have one storage device, put trace files on NFS and increase the 
> snapshotCount; it doesn't eliminate the problem, but it should mitigate it.
> {quote}
> 'trace files' are no longer available in ZooKeeper; remove mention of it.  
> Also, there is no such configuration named 'snapshotCount'; update it.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Updated] (ZOOKEEPER-3407) Update POM file with new information

[Lars Francke (JIRA)]

 [ 
https://issues.apache.org/jira/browse/ZOOKEEPER-3407?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Lars Francke updated ZOOKEEPER-3407:

Summary: Update POM file with new information  (was: Update POM with new 
mailing lists)

> Update POM file with new information
> 
>
> Key: ZOOKEEPER-3407
> URL: https://issues.apache.org/jira/browse/ZOOKEEPER-3407
> Project: ZooKeeper
>  Issue Type: Task
>Reporter: Lars Francke
>Priority: Trivial
>  Labels: pull-request-available
>  Time Spent: 10m
>  Remaining Estimate: 0h
>




--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Updated] (ZOOKEEPER-3407) Update POM file with new information

[Lars Francke (JIRA)]

 [ 
https://issues.apache.org/jira/browse/ZOOKEEPER-3407?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Lars Francke updated ZOOKEEPER-3407:

Description: New mailing lists & Jenkins update

> Update POM file with new information
> 
>
> Key: ZOOKEEPER-3407
> URL: https://issues.apache.org/jira/browse/ZOOKEEPER-3407
> Project: ZooKeeper
>  Issue Type: Task
>Reporter: Lars Francke
>Priority: Trivial
>  Labels: pull-request-available
>  Time Spent: 10m
>  Remaining Estimate: 0h
>
> New mailing lists & Jenkins update



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Updated] (ZOOKEEPER-3407) Update POM with new mailing lists

[ASF GitHub Bot (JIRA)]

 [ 
https://issues.apache.org/jira/browse/ZOOKEEPER-3407?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

ASF GitHub Bot updated ZOOKEEPER-3407:
--
Labels: pull-request-available  (was: )

> Update POM with new mailing lists
> -
>
> Key: ZOOKEEPER-3407
> URL: https://issues.apache.org/jira/browse/ZOOKEEPER-3407
> Project: ZooKeeper
>  Issue Type: Task
>Reporter: Lars Francke
>Priority: Trivial
>  Labels: pull-request-available
>




--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[GitHub] [zookeeper] lfrancke opened a new pull request #964: ZOOKEEPER-3407: Update POM file

[GitBox]

lfrancke opened a new pull request #964: ZOOKEEPER-3407: Update POM file
URL: https://github.com/apache/zookeeper/pull/964
 
 
   


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.
 
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org


With regards,
Apache Git Services

Re: ZooKeeper-Find-Flaky-Tests job updated

[Enrico Olivelli]

Good.
I hope to be able to drop ant soon.
Less jobs, less problems

Enrico

Il mer 29 mag 2019, 14:48 Andor Molnar  ha scritto:

> Hi!
>
> I’ve updated the job to run on all recent builds based on the following
> view:
>
> https://builds.apache.org/view/S-Z/view/ZooKeeper/ <
> https://builds.apache.org/view/S-Z/view/ZooKeeper/>
>
> Andor
>
>

[jira] [Created] (ZOOKEEPER-3407) Update POM with new mailing lists

[Lars Francke (JIRA)]

Lars Francke created ZOOKEEPER-3407:
---

 Summary: Update POM with new mailing lists
 Key: ZOOKEEPER-3407
 URL: https://issues.apache.org/jira/browse/ZOOKEEPER-3407
 Project: ZooKeeper
  Issue Type: Task
Reporter: Lars Francke






--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Updated] (ZOOKEEPER-3406) Update website for new mailing lists

[ASF GitHub Bot (JIRA)]

 [ 
https://issues.apache.org/jira/browse/ZOOKEEPER-3406?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

ASF GitHub Bot updated ZOOKEEPER-3406:
--
Labels: pull-request-available  (was: )

> Update website for new mailing lists
> 
>
> Key: ZOOKEEPER-3406
> URL: https://issues.apache.org/jira/browse/ZOOKEEPER-3406
> Project: ZooKeeper
>  Issue Type: Task
>Reporter: Lars Francke
>Priority: Minor
>  Labels: pull-request-available
>
> This updates the website to include information about issues@ and 
> notifications@



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[GitHub] [zookeeper] lfrancke opened a new pull request #963: ZOOKEEPER-3406: Update website for new mailing lists

[GitBox]

lfrancke opened a new pull request #963: ZOOKEEPER-3406: Update website for new 
mailing lists
URL: https://github.com/apache/zookeeper/pull/963
 
 
   This updates the website with the new mailing lists.
   Probably makes sense to wait with merging until INFRA has completed the 
changes.
   
   Whoever merges this probably needs to follow the remaining steps here as 
well: https://cwiki.apache.org/confluence/display/ZOOKEEPER/WebSiteSetup


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.
 
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org


With regards,
Apache Git Services

[jira] [Created] (ZOOKEEPER-3406) Update website for new mailing lists

[Lars Francke (JIRA)]

Lars Francke created ZOOKEEPER-3406:
---

 Summary: Update website for new mailing lists
 Key: ZOOKEEPER-3406
 URL: https://issues.apache.org/jira/browse/ZOOKEEPER-3406
 Project: ZooKeeper
  Issue Type: Task
Reporter: Lars Francke


This updates the website to include information about issues@ and notifications@



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[NOTICE] Change of mailing list behavior (soon)

[Lars Francke]

In the next few days Jira & Git notifications will stop being sent to
dev@zookeeper.apache.org.

Only the creation of new issues will still be announced on dev@.

For everything else notifications will be sent to issues@ (for Jira related
things) and notifications@ (for Git related things).

If you're interested in these notiifcations please subscribe to these
mailing lists by sending a mail to:
issues-subscr...@zookeeper.apache.org
notifications-subscr...@zookeeper.apache.org

I'll update this thread when INFRA has made the necessary changes.

Thank you!

Re: [VOTE] Separate mailing lists for Jira and Github/Gitbox notifications - Take 2

[Lars Francke]

The two mailing lists have been created.

I opened  & <
https://issues.apache.org/jira/browse/INFRA-1852
5>

On Wed, May 29, 2019 at 11:34 PM Lars Francke 
wrote:

> Thank you Norbert, I'll submit
>
> You are right. I don't know either. But there's not really any written
> rules for this kind of change just a community consensus I believe.
>
> On Wed, May 29, 2019 at 12:02 PM Norbert Kalmar
>  wrote:
>
>> There is a source for the website [1], and the generated live site [2].
>> Also, there is a guide [3] available.
>>
>> I'm not sure a committer vote is binding here? :)
>>
>> [1]
>>
>> https://gitbox.apache.org/repos/asf?p=zookeeper.git;a=shortlog;h=refs/heads/website
>> [2]
>>
>> https://gitbox.apache.org/repos/asf?p=zookeeper.git;a=shortlog;h=refs/heads/asf-site
>> [3] https://cwiki.apache.org/confluence/display/ZOOKEEPER/WebSiteSetup
>>
>> On Wed, May 29, 2019 at 8:36 AM Lars Francke 
>> wrote:
>>
>> > Can anyone tell me where the site source lives?
>> >
>> > I assumed  but
>> that
>> > was updated 18 months ago but the site has information on release 3.5.5
>> so
>> > there must be something else somewhere.
>> >
>> > On Wed, May 29, 2019 at 8:30 AM Lars Francke 
>> > wrote:
>> >
>> > > Alright, I'm closing this.
>> > >
>> > > I've requested both issues@ and notifications@ and will file the
>> > > necessary tickets once that's done.
>> > > You should get a mail to private@ but I'll also check the status.
>> > >
>> > > On Mon, May 27, 2019 at 11:54 PM Lars Francke > >
>> > > wrote:
>> > >
>> > >> I'd like to close the vote but forgot to state the "rules" in the
>> > initial
>> > >> mail. I would think that this change requires lazy consensus which we
>> > have
>> > >> achieved already. But because I forgot I'll wait another day before I
>> > close
>> > >> this.
>> > >>
>> > >> 2 binding (both Enrico & Norbert are now committers,
>> congratulations!)
>> > >> 1 non-binding
>> > >>
>> > >> If there are no more objections until tomorrow I'll file the
>> necessary
>> > >> Jira tasks for INFRA (referring to this thread) and will request the
>> > >> mailing lists (using the same moderators as dev@).
>> > >>
>> > >> Cheers,
>> > >> Lars
>> > >>
>> > >> On Fri, May 17, 2019 at 7:06 PM Enrico Olivelli > >
>> > >> wrote:
>> > >>
>> > >>> +1
>> > >>>
>> > >>> Enrico
>> > >>>
>> > >>> Il ven 17 mag 2019, 17:11 Norbert Kalmar
>> > > >
>> > >>> ha
>> > >>> scritto:
>> > >>>
>> > >>> > +1 (non-binding)
>> > >>> >
>> > >>> > Whoever will do the change (if voted), needs to make sure stuff
>> like
>> > >>> > markmail are updated/checked.
>> > >>> > I see Apache projects going for separate mailing lists for
>> automated
>> > >>> > notifications (I subscribed to HBase and Thrift for example, they
>> > have
>> > >>> this
>> > >>> > separation).
>> > >>> >
>> > >>> > My +1 is to separate the automated messages from the dev list, we
>> can
>> > >>> > discuss the details. For example, we already have a commit list
>> [1].
>> > >>> Also,
>> > >>> > some automated messages might stay on this list, like creating a
>> new
>> > >>> jira
>> > >>> > (as mentioned on the DISCUSS thread).
>> > >>> >
>> > >>> > Regards,
>> > >>> > Norbert
>> > >>> >
>> > >>> > [1] https://zookeeper.apache.org/lists.html
>> > >>> >
>> > >>> > On Fri, May 17, 2019 at 5:00 PM Lars Francke <
>> lars.fran...@gmail.com
>> > >
>> > >>> > wrote:
>> > >>> >
>> > >>> > > And here is my +1 (non-binding)
>> > >>> > >
>> > >>> > > On Fri, May 17, 2019 at 4:55 PM Lars Francke <
>> > lars.fran...@gmail.com
>> > >>> >
>> > >>> > > wrote:
>> > >>> > >
>> > >>> > > > Hi ZooKeeper devs,
>> > >>> > > >
>> > >>> > > > I'd like to call a vote on whether we want to have separate
>> > mailing
>> > >>> > lists
>> > >>> > > > for dev chatter (mostly humans) and automated notifications
>> > >>> > > >
>> > >>> > > > Andor summarized this in another thread:
>> > >>> > > > - Jenkins build notifications: failures / successes,
>> > >>> > > > - Jira notifications: Created, Updated, Status change,
>> Commented,
>> > >>> etc.
>> > >>> > > > - Github notifications: opened/closed pull request, commented
>> on
>> > >>> pull
>> > >>> > > > request, etc.
>> > >>> > > >
>> > >>> > > > This was previously discussed in two threads[1][2]
>> > >>> > > >
>> > >>> > > > This is the suggestion:
>> > >>> > > > Jira
>> > >>> > > > 
>> > >>> > > > Issue created -> dev@zookeeper.apache.org + issues@
>> > >>> > > > Everything else -> iss...@zookeeper.apache.org
>> > >>> > > >
>> > >>> > > > Github/Gitbox
>> > >>> > > > --
>> > >>> > > > All notifications sent to notificati...@zookeeper.apache.org
>> > >>> > > >
>> > >>> > > > issues@ and notifications@ mailing lists have to be created
>> > first.
>> > >>> > > >
>> > >>> > > >
>> > >>> > > > Please vote on the issue. I'll leave the vote running for at
>> > least
>> > >>> 72
>> > >>> > > > 

Re: [VOTE] Separate mailing lists for Jira and Github/Gitbox notifications - Take 2

[Lars Francke]

Thank you Norbert, I'll submit

You are right. I don't know either. But there's not really any written
rules for this kind of change just a community consensus I believe.

On Wed, May 29, 2019 at 12:02 PM Norbert Kalmar
 wrote:

> There is a source for the website [1], and the generated live site [2].
> Also, there is a guide [3] available.
>
> I'm not sure a committer vote is binding here? :)
>
> [1]
>
> https://gitbox.apache.org/repos/asf?p=zookeeper.git;a=shortlog;h=refs/heads/website
> [2]
>
> https://gitbox.apache.org/repos/asf?p=zookeeper.git;a=shortlog;h=refs/heads/asf-site
> [3] https://cwiki.apache.org/confluence/display/ZOOKEEPER/WebSiteSetup
>
> On Wed, May 29, 2019 at 8:36 AM Lars Francke 
> wrote:
>
> > Can anyone tell me where the site source lives?
> >
> > I assumed  but that
> > was updated 18 months ago but the site has information on release 3.5.5
> so
> > there must be something else somewhere.
> >
> > On Wed, May 29, 2019 at 8:30 AM Lars Francke 
> > wrote:
> >
> > > Alright, I'm closing this.
> > >
> > > I've requested both issues@ and notifications@ and will file the
> > > necessary tickets once that's done.
> > > You should get a mail to private@ but I'll also check the status.
> > >
> > > On Mon, May 27, 2019 at 11:54 PM Lars Francke 
> > > wrote:
> > >
> > >> I'd like to close the vote but forgot to state the "rules" in the
> > initial
> > >> mail. I would think that this change requires lazy consensus which we
> > have
> > >> achieved already. But because I forgot I'll wait another day before I
> > close
> > >> this.
> > >>
> > >> 2 binding (both Enrico & Norbert are now committers, congratulations!)
> > >> 1 non-binding
> > >>
> > >> If there are no more objections until tomorrow I'll file the necessary
> > >> Jira tasks for INFRA (referring to this thread) and will request the
> > >> mailing lists (using the same moderators as dev@).
> > >>
> > >> Cheers,
> > >> Lars
> > >>
> > >> On Fri, May 17, 2019 at 7:06 PM Enrico Olivelli 
> > >> wrote:
> > >>
> > >>> +1
> > >>>
> > >>> Enrico
> > >>>
> > >>> Il ven 17 mag 2019, 17:11 Norbert Kalmar
>  > >
> > >>> ha
> > >>> scritto:
> > >>>
> > >>> > +1 (non-binding)
> > >>> >
> > >>> > Whoever will do the change (if voted), needs to make sure stuff
> like
> > >>> > markmail are updated/checked.
> > >>> > I see Apache projects going for separate mailing lists for
> automated
> > >>> > notifications (I subscribed to HBase and Thrift for example, they
> > have
> > >>> this
> > >>> > separation).
> > >>> >
> > >>> > My +1 is to separate the automated messages from the dev list, we
> can
> > >>> > discuss the details. For example, we already have a commit list
> [1].
> > >>> Also,
> > >>> > some automated messages might stay on this list, like creating a
> new
> > >>> jira
> > >>> > (as mentioned on the DISCUSS thread).
> > >>> >
> > >>> > Regards,
> > >>> > Norbert
> > >>> >
> > >>> > [1] https://zookeeper.apache.org/lists.html
> > >>> >
> > >>> > On Fri, May 17, 2019 at 5:00 PM Lars Francke <
> lars.fran...@gmail.com
> > >
> > >>> > wrote:
> > >>> >
> > >>> > > And here is my +1 (non-binding)
> > >>> > >
> > >>> > > On Fri, May 17, 2019 at 4:55 PM Lars Francke <
> > lars.fran...@gmail.com
> > >>> >
> > >>> > > wrote:
> > >>> > >
> > >>> > > > Hi ZooKeeper devs,
> > >>> > > >
> > >>> > > > I'd like to call a vote on whether we want to have separate
> > mailing
> > >>> > lists
> > >>> > > > for dev chatter (mostly humans) and automated notifications
> > >>> > > >
> > >>> > > > Andor summarized this in another thread:
> > >>> > > > - Jenkins build notifications: failures / successes,
> > >>> > > > - Jira notifications: Created, Updated, Status change,
> Commented,
> > >>> etc.
> > >>> > > > - Github notifications: opened/closed pull request, commented
> on
> > >>> pull
> > >>> > > > request, etc.
> > >>> > > >
> > >>> > > > This was previously discussed in two threads[1][2]
> > >>> > > >
> > >>> > > > This is the suggestion:
> > >>> > > > Jira
> > >>> > > > 
> > >>> > > > Issue created -> dev@zookeeper.apache.org + issues@
> > >>> > > > Everything else -> iss...@zookeeper.apache.org
> > >>> > > >
> > >>> > > > Github/Gitbox
> > >>> > > > --
> > >>> > > > All notifications sent to notificati...@zookeeper.apache.org
> > >>> > > >
> > >>> > > > issues@ and notifications@ mailing lists have to be created
> > first.
> > >>> > > >
> > >>> > > >
> > >>> > > > Please vote on the issue. I'll leave the vote running for at
> > least
> > >>> 72
> > >>> > > > hours considering we have a weekend ahead of us probably a bit
> > >>> longer.
> > >>> > > >
> > >>> > > > Cheers,
> > >>> > > > Lars
> > >>> > > >
> > >>> > > > [1] <
> > >>> > > >
> > >>> > >
> > >>> >
> > >>>
> >
> https://lists.apache.org/thread.html/ae530b1c7dae8b83740d83243f18b76d6e0e6572ff1bfb6189e6e0d6@%3Cdev.zookeeper.apache.org%3E
> > >>> > > > >
> > >>> > > > [2] <
> > >>> > > >
> > >>> > >
> > >>> >
> > >>>
> >
> 

[jira] [Commented] (ZOOKEEPER-3382) Update Documentation: If you only have one storage device

[Hudson (JIRA)]

[ 
https://issues.apache.org/jira/browse/ZOOKEEPER-3382?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16851096#comment-16851096
 ] 

Hudson commented on ZOOKEEPER-3382:
---

SUCCESS: Integrated in Jenkins build ZooKeeper-trunk #544 (See 
[https://builds.apache.org/job/ZooKeeper-trunk/544/])
ZOOKEEPER-3382: Update Documentation: If you only have one storage (andor: rev 
f7bdab002aa01677145654f8a1f93a45969d22cd)
* (edit) zookeeper-docs/src/main/resources/markdown/zookeeperProgrammers.md
* (edit) zookeeper-docs/src/main/resources/markdown/zookeeperAdmin.md


> Update Documentation: If you only have one storage device
> -
>
> Key: ZOOKEEPER-3382
> URL: https://issues.apache.org/jira/browse/ZOOKEEPER-3382
> Project: ZooKeeper
>  Issue Type: Improvement
>  Components: documentation
>Affects Versions: 3.6.0, 3.5.5, 3.4.15
>Reporter: David Mollitor
>Assignee: David Mollitor
>Priority: Minor
>  Labels: pull-request-available
> Fix For: 3.6.0
>
>  Time Spent: 0.5h
>  Remaining Estimate: 0h
>
> {quote}
> If you only have one storage device, put trace files on NFS and increase the 
> snapshotCount; it doesn't eliminate the problem, but it should mitigate it.
> {quote}
> 'trace files' are no longer available in ZooKeeper; remove mention of it.  
> Also, there is no such configuration named 'snapshotCount'; update it.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[GitHub] [zookeeper] anmolnar commented on issue #935: ZOOKEEPER-3382: Update Documentation: If you only have one storage device

[GitBox]

anmolnar commented on issue #935: ZOOKEEPER-3382: Update Documentation: If you 
only have one storage device
URL: https://github.com/apache/zookeeper/pull/935#issuecomment-496980833
 
 
   Merged to master. Thanks @BELUGABEHR !


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.
 
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org


With regards,
Apache Git Services

[jira] [Resolved] (ZOOKEEPER-3382) Update Documentation: If you only have one storage device

[Andor Molnar (JIRA)]

 [ 
https://issues.apache.org/jira/browse/ZOOKEEPER-3382?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Andor Molnar resolved ZOOKEEPER-3382.
-
Resolution: Fixed

Issue resolved by pull request 935
[https://github.com/apache/zookeeper/pull/935]

> Update Documentation: If you only have one storage device
> -
>
> Key: ZOOKEEPER-3382
> URL: https://issues.apache.org/jira/browse/ZOOKEEPER-3382
> Project: ZooKeeper
>  Issue Type: Improvement
>  Components: documentation
>Affects Versions: 3.6.0, 3.5.5, 3.4.15
>Reporter: David Mollitor
>Assignee: David Mollitor
>Priority: Minor
>  Labels: pull-request-available
> Fix For: 3.6.0
>
>  Time Spent: 10m
>  Remaining Estimate: 0h
>
> {quote}
> If you only have one storage device, put trace files on NFS and increase the 
> snapshotCount; it doesn't eliminate the problem, but it should mitigate it.
> {quote}
> 'trace files' are no longer available in ZooKeeper; remove mention of it.  
> Also, there is no such configuration named 'snapshotCount'; update it.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[GitHub] [zookeeper] asfgit closed pull request #935: ZOOKEEPER-3382: Update Documentation: If you only have one storage device

[GitBox]

asfgit closed pull request #935: ZOOKEEPER-3382: Update Documentation: If you 
only have one storage device
URL: https://github.com/apache/zookeeper/pull/935
 
 
   


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.
 
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org


With regards,
Apache Git Services

[GitHub] [zookeeper] anmolnar commented on issue #931: ZOOKEEPER-3373:need change description for "Single System Image" guarantee in document

[GitBox]

anmolnar commented on issue #931: ZOOKEEPER-3373:need change description for 
"Single System Image" guarantee in document
URL: https://github.com/apache/zookeeper/pull/931#issuecomment-496963385
 
 
   @hanm @phunt Do you agree with this change?


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.
 
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org


With regards,
Apache Git Services

[GitHub] [zookeeper] anmolnar commented on issue #878: ZOOKEEPER-3339: Improve Debug and Trace Log Statements

[GitBox]

anmolnar commented on issue #878: ZOOKEEPER-3339: Improve Debug and Trace Log 
Statements
URL: https://github.com/apache/zookeeper/pull/878#issuecomment-496959862
 
 
   We have so many committers nowadays. @lvfangmin @eolivelli @nkalmar Would 
you please let me have one of your approvals? :)


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.
 
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org


With regards,
Apache Git Services

[GitHub] [zookeeper] anmolnar commented on issue #878: ZOOKEEPER-3339: Improve Debug and Trace Log Statements

[GitBox]

anmolnar commented on issue #878: ZOOKEEPER-3339: Improve Debug and Trace Log 
Statements
URL: https://github.com/apache/zookeeper/pull/878#issuecomment-496959084
 
 
   retest maven build


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.
 
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org


With regards,
Apache Git Services

[GitHub] [zookeeper] anmolnar commented on issue #941: [ZOOKEEPER-3387] Use BufferedWriter instead of FileWriter

[GitBox]

anmolnar commented on issue #941: [ZOOKEEPER-3387] Use BufferedWriter instead 
of FileWriter
URL: https://github.com/apache/zookeeper/pull/941#issuecomment-496958325
 
 
   @bd2019us This patch doesn't compile:
   ```
   [ERROR] 
/home/travis/build/apache/zookeeper/zookeeper-jute/target/classes/org/apache/zookeeper/data/Stat.java:[273,17]
 error: reached end of file while parsing
   ```


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.
 
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org


With regards,
Apache Git Services

[GitHub] [zookeeper] anmolnar commented on issue #941: [ZOOKEEPER-3387] Use BufferedWriter instead of FileWriter

[GitBox]

anmolnar commented on issue #941: [ZOOKEEPER-3387] Use BufferedWriter instead 
of FileWriter
URL: https://github.com/apache/zookeeper/pull/941#issuecomment-496956993
 
 
   retest this please


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.
 
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org


With regards,
Apache Git Services

[GitHub] [zookeeper] anmolnar commented on issue #903: ZOOKEEPER-3357: Remove Dead Link from ZooKeeper Programmer Guide

[GitBox]

anmolnar commented on issue #903: ZOOKEEPER-3357: Remove Dead Link from 
ZooKeeper Programmer Guide
URL: https://github.com/apache/zookeeper/pull/903#issuecomment-496956167
 
 
   @BELUGABEHR Could be right, but I feel I can argue with. Not sure though.
   I would really just fix the URL instead of removing it. It's a very good 
video and available on YouTube since 2013.


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.
 
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org


With regards,
Apache Git Services

[GitHub] [zookeeper] eolivelli commented on issue #905: ZOOKEEPER-3359: Batch commits in the CommitProcessor

[GitBox]

eolivelli commented on issue #905:  ZOOKEEPER-3359: Batch commits in the 
CommitProcessor 
URL: https://github.com/apache/zookeeper/pull/905#issuecomment-496949661
 
 
   This is cool
   @anmolnar @nkalmar please take a look as well.
   I will review as soon as I can.
   The change is not trivial
   
   @enixon we need to rebase the change after review


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.
 
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org


With regards,
Apache Git Services

[GitHub] [zookeeper] eolivelli commented on issue #912: ZOOKEEPER-3365: Use Concurrent HashMap with Counter in NettyServerCnxnFactory

[GitBox]

eolivelli commented on issue #912: ZOOKEEPER-3365: Use Concurrent HashMap with 
Counter in NettyServerCnxnFactory
URL: https://github.com/apache/zookeeper/pull/912#issuecomment-496948713
 
 
   @nkalmar I have restarted the tests because this patch was approved but it 
is quite old.
   I hope tests will pass.
   Than we can commit it


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.
 
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org


With regards,
Apache Git Services

[GitHub] [zookeeper] eolivelli commented on issue #912: ZOOKEEPER-3365: Use Concurrent HashMap with Counter in NettyServerCnxnFactory

[GitBox]

eolivelli commented on issue #912: ZOOKEEPER-3365: Use Concurrent HashMap with 
Counter in NettyServerCnxnFactory
URL: https://github.com/apache/zookeeper/pull/912#issuecomment-496948507
 
 
   retest maven build


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.
 
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org


With regards,
Apache Git Services

[GitHub] [zookeeper] eolivelli commented on issue #912: ZOOKEEPER-3365: Use Concurrent HashMap with Counter in NettyServerCnxnFactory

[GitBox]

eolivelli commented on issue #912: ZOOKEEPER-3365: Use Concurrent HashMap with 
Counter in NettyServerCnxnFactory
URL: https://github.com/apache/zookeeper/pull/912#issuecomment-496948413
 
 
   retest ant build


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.
 
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org


With regards,
Apache Git Services

[GitHub] [zookeeper] eolivelli commented on issue #919: ZOOKEEPER-3356: Implement advanced Netty flow control based on feedback from ZK

[GitBox]

eolivelli commented on issue #919: ZOOKEEPER-3356: Implement advanced Netty 
flow control based on feedback from ZK
URL: https://github.com/apache/zookeeper/pull/919#issuecomment-496948152
 
 
   @lvfangmin we need to rebase.
   
   I hope @normanmaurer have cycles to take a look


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.
 
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org


With regards,
Apache Git Services

[GitHub] [zookeeper] eolivelli commented on issue #939: ZOOKEEPER-3385: Add admin command to display leader

[GitBox]

eolivelli commented on issue #939: ZOOKEEPER-3385: Add admin command to display 
leader
URL: https://github.com/apache/zookeeper/pull/939#issuecomment-496947055
 
 
   Please rebase @enixon 


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.
 
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org


With regards,
Apache Git Services

[GitHub] [zookeeper] eolivelli commented on issue #962: ZOOKEEPER-3405: Upgrade the version of Jackson-databind to address OWASP CVE

[GitBox]

eolivelli commented on issue #962: ZOOKEEPER-3405: Upgrade the version of 
Jackson-databind to address OWASP CVE
URL: https://github.com/apache/zookeeper/pull/962#issuecomment-496946298
 
 
   retest maven build


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.
 
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org


With regards,
Apache Git Services

ZooKeeper-Find-Flaky-Tests job updated

[Andor Molnar]

Hi!

I’ve updated the job to run on all recent builds based on the following view:

https://builds.apache.org/view/S-Z/view/ZooKeeper/ 


Andor

Re: [VOTE] Separate mailing lists for Jira and Github/Gitbox notifications - Take 2

[Norbert Kalmar]

There is a source for the website [1], and the generated live site [2].
Also, there is a guide [3] available.

I'm not sure a committer vote is binding here? :)

[1]
https://gitbox.apache.org/repos/asf?p=zookeeper.git;a=shortlog;h=refs/heads/website
[2]
https://gitbox.apache.org/repos/asf?p=zookeeper.git;a=shortlog;h=refs/heads/asf-site
[3] https://cwiki.apache.org/confluence/display/ZOOKEEPER/WebSiteSetup

On Wed, May 29, 2019 at 8:36 AM Lars Francke  wrote:

> Can anyone tell me where the site source lives?
>
> I assumed  but that
> was updated 18 months ago but the site has information on release 3.5.5 so
> there must be something else somewhere.
>
> On Wed, May 29, 2019 at 8:30 AM Lars Francke 
> wrote:
>
> > Alright, I'm closing this.
> >
> > I've requested both issues@ and notifications@ and will file the
> > necessary tickets once that's done.
> > You should get a mail to private@ but I'll also check the status.
> >
> > On Mon, May 27, 2019 at 11:54 PM Lars Francke 
> > wrote:
> >
> >> I'd like to close the vote but forgot to state the "rules" in the
> initial
> >> mail. I would think that this change requires lazy consensus which we
> have
> >> achieved already. But because I forgot I'll wait another day before I
> close
> >> this.
> >>
> >> 2 binding (both Enrico & Norbert are now committers, congratulations!)
> >> 1 non-binding
> >>
> >> If there are no more objections until tomorrow I'll file the necessary
> >> Jira tasks for INFRA (referring to this thread) and will request the
> >> mailing lists (using the same moderators as dev@).
> >>
> >> Cheers,
> >> Lars
> >>
> >> On Fri, May 17, 2019 at 7:06 PM Enrico Olivelli 
> >> wrote:
> >>
> >>> +1
> >>>
> >>> Enrico
> >>>
> >>> Il ven 17 mag 2019, 17:11 Norbert Kalmar  >
> >>> ha
> >>> scritto:
> >>>
> >>> > +1 (non-binding)
> >>> >
> >>> > Whoever will do the change (if voted), needs to make sure stuff like
> >>> > markmail are updated/checked.
> >>> > I see Apache projects going for separate mailing lists for automated
> >>> > notifications (I subscribed to HBase and Thrift for example, they
> have
> >>> this
> >>> > separation).
> >>> >
> >>> > My +1 is to separate the automated messages from the dev list, we can
> >>> > discuss the details. For example, we already have a commit list [1].
> >>> Also,
> >>> > some automated messages might stay on this list, like creating a new
> >>> jira
> >>> > (as mentioned on the DISCUSS thread).
> >>> >
> >>> > Regards,
> >>> > Norbert
> >>> >
> >>> > [1] https://zookeeper.apache.org/lists.html
> >>> >
> >>> > On Fri, May 17, 2019 at 5:00 PM Lars Francke  >
> >>> > wrote:
> >>> >
> >>> > > And here is my +1 (non-binding)
> >>> > >
> >>> > > On Fri, May 17, 2019 at 4:55 PM Lars Francke <
> lars.fran...@gmail.com
> >>> >
> >>> > > wrote:
> >>> > >
> >>> > > > Hi ZooKeeper devs,
> >>> > > >
> >>> > > > I'd like to call a vote on whether we want to have separate
> mailing
> >>> > lists
> >>> > > > for dev chatter (mostly humans) and automated notifications
> >>> > > >
> >>> > > > Andor summarized this in another thread:
> >>> > > > - Jenkins build notifications: failures / successes,
> >>> > > > - Jira notifications: Created, Updated, Status change, Commented,
> >>> etc.
> >>> > > > - Github notifications: opened/closed pull request, commented on
> >>> pull
> >>> > > > request, etc.
> >>> > > >
> >>> > > > This was previously discussed in two threads[1][2]
> >>> > > >
> >>> > > > This is the suggestion:
> >>> > > > Jira
> >>> > > > 
> >>> > > > Issue created -> dev@zookeeper.apache.org + issues@
> >>> > > > Everything else -> iss...@zookeeper.apache.org
> >>> > > >
> >>> > > > Github/Gitbox
> >>> > > > --
> >>> > > > All notifications sent to notificati...@zookeeper.apache.org
> >>> > > >
> >>> > > > issues@ and notifications@ mailing lists have to be created
> first.
> >>> > > >
> >>> > > >
> >>> > > > Please vote on the issue. I'll leave the vote running for at
> least
> >>> 72
> >>> > > > hours considering we have a weekend ahead of us probably a bit
> >>> longer.
> >>> > > >
> >>> > > > Cheers,
> >>> > > > Lars
> >>> > > >
> >>> > > > [1] <
> >>> > > >
> >>> > >
> >>> >
> >>>
> https://lists.apache.org/thread.html/ae530b1c7dae8b83740d83243f18b76d6e0e6572ff1bfb6189e6e0d6@%3Cdev.zookeeper.apache.org%3E
> >>> > > > >
> >>> > > > [2] <
> >>> > > >
> >>> > >
> >>> >
> >>>
> https://lists.apache.org/thread.html/bd7bdae9da67145dcde636219c6d3bd8429565cd864abc55358eb67f@
> >>> > > 
> >>> > > > >
> >>> > > >
> >>> > >
> >>> >
> >>>
> >>
>

Build failed in Jenkins: ZooKeeper-trunk-owasp #378

[Apache Jenkins Server]

See 


Changes:

[nkalmar] ZOOKEEPER-3401: Fix metric PROPOSAL_ACK_CREATION_LATENCY

[nkalmar] ZOOKEEPER-3404: Downgrade BouncyCastle to 1.60

--
[...truncated 14.66 KB...]
[ivy:retrieve]  confs: [default]
[ivy:retrieve]  23 artifacts copied, 0 already retrieved (10497kB/27ms)

ivy-retrieve-clover:

clover.check:

clover.setup:

clover:

ivy-retrieve-javacc:
[mkdir] Created dir: 

[ivy:retrieve] :: resolving dependencies :: 
org.apache.zookeeper#zookeeper;3.6.0-SNAPSHOT
[ivy:retrieve]  confs: [javacc]
[ivy:retrieve]  found net.java.dev.javacc#javacc;5.0 in maven2
[ivy:retrieve] :: resolution report :: resolve 21ms :: artifacts dl 2ms
-
|  |modules||   artifacts   |
|   conf   | number| search|dwnlded|evicted|| number|dwnlded|
-
|  javacc  |   1   |   0   |   0   |   0   ||   1   |   0   |
-
[ivy:retrieve] :: retrieving :: org.apache.zookeeper#zookeeper
[ivy:retrieve]  confs: [javacc]
[ivy:retrieve]  1 artifacts copied, 0 already retrieved (291kB/3ms)

generate_jute_parser:
[mkdir] Created dir: 

[ivy:artifactproperty] DEPRECATED: 'ivy.conf.file' is deprecated, use 
'ivy.settings.file' instead
[ivy:artifactproperty] :: loading settings :: file = 

 [move] Moving 1 file to 

   [javacc] Java Compiler Compiler Version 5.0 (Parser Generator)
   [javacc] (type "javacc" with no arguments for help)
   [javacc] Reading from file 

 . . .
   [javacc] File "TokenMgrError.java" does not exist.  Will create one.
   [javacc] File "ParseException.java" does not exist.  Will create one.
   [javacc] File "Token.java" does not exist.  Will create one.
   [javacc] File "SimpleCharStream.java" does not exist.  Will create one.
   [javacc] Parser generated successfully.

jute:
[javac] Compiling 39 source files to 

[javac] warning: [options] bootstrap class path not set in conjunction with 
-source 8
[javac] 1 warning

compile_jute_uptodate:

compile_jute:
[mkdir] Created dir: 

[mkdir] Created dir: 

 [java] ../../../src/main/resources/zookeeper.jute Parsed Successfully
 [java] ../../../zookeeper-jute/src/main/resources/zookeeper.jute Parsed 
Successfully
[touch] Creating 


ver-gen:
[javac] Compiling 1 source file to 

[javac] warning: [options] bootstrap class path not set in conjunction with 
-source 8
[javac] 1 warning

git-revision:
[mkdir] Created dir: 


version-info:

process-template:

build-generated:
[javac] Compiling 67 source files to 

[javac] warning: [options] bootstrap class path not set in conjunction with 
-source 8
[javac] 1 warning

compile:
[javac] Compiling 316 source files to 

[javac] warning: [options] bootstrap class path not set in conjunction with 
-source 8
[javac] 
:26:
 warning: [serial] serializable class ClientCnxnLimitException has no 
definition of serialVersionUID
[javac] public class ClientCnxnLimitException extends Exception {
[javac]^
[javac] 
:44:
 warning: [dep-ann] deprecated item is not annotated with @Deprecated
[javac] public class LogFormatter {
[javac]^
[javac] 

Re: [VOTE] Separate mailing lists for Jira and Github/Gitbox notifications - Take 2

[Lars Francke]

Can anyone tell me where the site source lives?

I assumed  but that
was updated 18 months ago but the site has information on release 3.5.5 so
there must be something else somewhere.

On Wed, May 29, 2019 at 8:30 AM Lars Francke  wrote:

> Alright, I'm closing this.
>
> I've requested both issues@ and notifications@ and will file the
> necessary tickets once that's done.
> You should get a mail to private@ but I'll also check the status.
>
> On Mon, May 27, 2019 at 11:54 PM Lars Francke 
> wrote:
>
>> I'd like to close the vote but forgot to state the "rules" in the initial
>> mail. I would think that this change requires lazy consensus which we have
>> achieved already. But because I forgot I'll wait another day before I close
>> this.
>>
>> 2 binding (both Enrico & Norbert are now committers, congratulations!)
>> 1 non-binding
>>
>> If there are no more objections until tomorrow I'll file the necessary
>> Jira tasks for INFRA (referring to this thread) and will request the
>> mailing lists (using the same moderators as dev@).
>>
>> Cheers,
>> Lars
>>
>> On Fri, May 17, 2019 at 7:06 PM Enrico Olivelli 
>> wrote:
>>
>>> +1
>>>
>>> Enrico
>>>
>>> Il ven 17 mag 2019, 17:11 Norbert Kalmar 
>>> ha
>>> scritto:
>>>
>>> > +1 (non-binding)
>>> >
>>> > Whoever will do the change (if voted), needs to make sure stuff like
>>> > markmail are updated/checked.
>>> > I see Apache projects going for separate mailing lists for automated
>>> > notifications (I subscribed to HBase and Thrift for example, they have
>>> this
>>> > separation).
>>> >
>>> > My +1 is to separate the automated messages from the dev list, we can
>>> > discuss the details. For example, we already have a commit list [1].
>>> Also,
>>> > some automated messages might stay on this list, like creating a new
>>> jira
>>> > (as mentioned on the DISCUSS thread).
>>> >
>>> > Regards,
>>> > Norbert
>>> >
>>> > [1] https://zookeeper.apache.org/lists.html
>>> >
>>> > On Fri, May 17, 2019 at 5:00 PM Lars Francke 
>>> > wrote:
>>> >
>>> > > And here is my +1 (non-binding)
>>> > >
>>> > > On Fri, May 17, 2019 at 4:55 PM Lars Francke >> >
>>> > > wrote:
>>> > >
>>> > > > Hi ZooKeeper devs,
>>> > > >
>>> > > > I'd like to call a vote on whether we want to have separate mailing
>>> > lists
>>> > > > for dev chatter (mostly humans) and automated notifications
>>> > > >
>>> > > > Andor summarized this in another thread:
>>> > > > - Jenkins build notifications: failures / successes,
>>> > > > - Jira notifications: Created, Updated, Status change, Commented,
>>> etc.
>>> > > > - Github notifications: opened/closed pull request, commented on
>>> pull
>>> > > > request, etc.
>>> > > >
>>> > > > This was previously discussed in two threads[1][2]
>>> > > >
>>> > > > This is the suggestion:
>>> > > > Jira
>>> > > > 
>>> > > > Issue created -> dev@zookeeper.apache.org + issues@
>>> > > > Everything else -> iss...@zookeeper.apache.org
>>> > > >
>>> > > > Github/Gitbox
>>> > > > --
>>> > > > All notifications sent to notificati...@zookeeper.apache.org
>>> > > >
>>> > > > issues@ and notifications@ mailing lists have to be created first.
>>> > > >
>>> > > >
>>> > > > Please vote on the issue. I'll leave the vote running for at least
>>> 72
>>> > > > hours considering we have a weekend ahead of us probably a bit
>>> longer.
>>> > > >
>>> > > > Cheers,
>>> > > > Lars
>>> > > >
>>> > > > [1] <
>>> > > >
>>> > >
>>> >
>>> https://lists.apache.org/thread.html/ae530b1c7dae8b83740d83243f18b76d6e0e6572ff1bfb6189e6e0d6@%3Cdev.zookeeper.apache.org%3E
>>> > > > >
>>> > > > [2] <
>>> > > >
>>> > >
>>> >
>>> https://lists.apache.org/thread.html/bd7bdae9da67145dcde636219c6d3bd8429565cd864abc55358eb67f@
>>> > > 
>>> > > > >
>>> > > >
>>> > >
>>> >
>>>
>>

Re: [VOTE] Separate mailing lists for Jira and Github/Gitbox notifications - Take 2

[Lars Francke]

Alright, I'm closing this.

I've requested both issues@ and notifications@ and will file the necessary
tickets once that's done.
You should get a mail to private@ but I'll also check the status.

On Mon, May 27, 2019 at 11:54 PM Lars Francke 
wrote:

> I'd like to close the vote but forgot to state the "rules" in the initial
> mail. I would think that this change requires lazy consensus which we have
> achieved already. But because I forgot I'll wait another day before I close
> this.
>
> 2 binding (both Enrico & Norbert are now committers, congratulations!)
> 1 non-binding
>
> If there are no more objections until tomorrow I'll file the necessary
> Jira tasks for INFRA (referring to this thread) and will request the
> mailing lists (using the same moderators as dev@).
>
> Cheers,
> Lars
>
> On Fri, May 17, 2019 at 7:06 PM Enrico Olivelli 
> wrote:
>
>> +1
>>
>> Enrico
>>
>> Il ven 17 mag 2019, 17:11 Norbert Kalmar 
>> ha
>> scritto:
>>
>> > +1 (non-binding)
>> >
>> > Whoever will do the change (if voted), needs to make sure stuff like
>> > markmail are updated/checked.
>> > I see Apache projects going for separate mailing lists for automated
>> > notifications (I subscribed to HBase and Thrift for example, they have
>> this
>> > separation).
>> >
>> > My +1 is to separate the automated messages from the dev list, we can
>> > discuss the details. For example, we already have a commit list [1].
>> Also,
>> > some automated messages might stay on this list, like creating a new
>> jira
>> > (as mentioned on the DISCUSS thread).
>> >
>> > Regards,
>> > Norbert
>> >
>> > [1] https://zookeeper.apache.org/lists.html
>> >
>> > On Fri, May 17, 2019 at 5:00 PM Lars Francke 
>> > wrote:
>> >
>> > > And here is my +1 (non-binding)
>> > >
>> > > On Fri, May 17, 2019 at 4:55 PM Lars Francke 
>> > > wrote:
>> > >
>> > > > Hi ZooKeeper devs,
>> > > >
>> > > > I'd like to call a vote on whether we want to have separate mailing
>> > lists
>> > > > for dev chatter (mostly humans) and automated notifications
>> > > >
>> > > > Andor summarized this in another thread:
>> > > > - Jenkins build notifications: failures / successes,
>> > > > - Jira notifications: Created, Updated, Status change, Commented,
>> etc.
>> > > > - Github notifications: opened/closed pull request, commented on
>> pull
>> > > > request, etc.
>> > > >
>> > > > This was previously discussed in two threads[1][2]
>> > > >
>> > > > This is the suggestion:
>> > > > Jira
>> > > > 
>> > > > Issue created -> dev@zookeeper.apache.org + issues@
>> > > > Everything else -> iss...@zookeeper.apache.org
>> > > >
>> > > > Github/Gitbox
>> > > > --
>> > > > All notifications sent to notificati...@zookeeper.apache.org
>> > > >
>> > > > issues@ and notifications@ mailing lists have to be created first.
>> > > >
>> > > >
>> > > > Please vote on the issue. I'll leave the vote running for at least
>> 72
>> > > > hours considering we have a weekend ahead of us probably a bit
>> longer.
>> > > >
>> > > > Cheers,
>> > > > Lars
>> > > >
>> > > > [1] <
>> > > >
>> > >
>> >
>> https://lists.apache.org/thread.html/ae530b1c7dae8b83740d83243f18b76d6e0e6572ff1bfb6189e6e0d6@%3Cdev.zookeeper.apache.org%3E
>> > > > >
>> > > > [2] <
>> > > >
>> > >
>> >
>> https://lists.apache.org/thread.html/bd7bdae9da67145dcde636219c6d3bd8429565cd864abc55358eb67f@
>> > > 
>> > > > >
>> > > >
>> > >
>> >
>>
>