Re: [3.4.12] Missing OVERSEER doc. solr-user@lucene....

2019-05-22 Thread Andor Molnar
Hi Will,

What is your question to the ZooKeeper community?

Andor



On Wed, May 22, 2019 at 5:53 AM Will Martin  wrote:

> Cross-posting this for a sound reporter. He is a top technical
> resource on the list. Not given to hyperbole in bug reports.
>
>
>
> Is there a acl’d JIRA for zookeeper?
>
> 
>
> to solr-user
>
> [image: https://mail.google.com/mail/u/0/images/cleardot.gif]
>
> We have a 6.6.2 cluster in prod that appears to have no overseer. In
> /overseer_elect on ZK, there is an election folder, but no leader document.
> An OVERSEERSTATUS request fails with a timeout.
>
> I’m going to try ADDROLE, but I’d be delighted to hear any other ideas.
> We’ve diverted all the traffic to the backing cluster, so we can blow this
> one away and rebuild.
>
> Looking at the Zookeeper logs, I see a few instances of network failures
> across all three nodes.
>
>
>
>
>
> I **have the logs** from each of the Zookeepers.
>
> We are running 3.4.12.
>
>
>
> 
>


Re: 3.4.12

2018-03-15 Thread Flavio Junqueira
+1 for cutting a 3.4.12 RC. Thanks for volunteering, Abe.

-Flavio

> On 8 Mar 2018, at 18:53, Rakesh Radhakrishnan  wrote:
> 
> Appreciate Abe for the initiative and efforts!
> 
> +1, for "3.4.12" releasing.
> 
> Please feel free to ping me if any help needed when making this release.
> 
> Regards,
> Rakesh
> 
> On Sat, Mar 3, 2018 at 4:19 AM, Abraham Fine  wrote:
> 
>> I am very much interested in taking a turn as a RM and I think it is a
>> great time to do a release (now that 2967, 2249, and 2960 arge merged in).
>> 
>> I agree that ZOOKEEPER-2184 can be pushed again and I don't think there is
>> anything else that we need to merge in before cutting a release.
>> 
>> Abe
>> 
>> On Thu, Mar 1, 2018, at 21:52, Patrick Hunt wrote:
>>> There are 19 resolved issues http://bit.ly/2oK9aTx
>>> and 14 unresolved http://bit.ly/2oFWywS
>>> ZOOKEEPER-2184 is the only unresolved blocker, however that's not a
>>> regression and was pushed from 3.4.11, we could do so again given it's
>>> still being worked on.
>>> 
>>> Abe are you interested in taking a turn as RM?
>>> 
>>> Patrick
>>> 
>>> On Thu, Mar 1, 2018 at 4:38 PM, Andor Molnar  wrote:
>>> 
 Hi dev,
 
 User has recently run into the regression of 3.4.11 (ZOOKEEPER-2960
 ) (again?)
 Are we good to cut 3.4.12 soon or still waiting for something to be
 committed?
 
 Andor
 
>> 



Re: 3.4.12

2018-03-08 Thread Rakesh Radhakrishnan
Appreciate Abe for the initiative and efforts!

+1, for "3.4.12" releasing.

Please feel free to ping me if any help needed when making this release.

Regards,
Rakesh

On Sat, Mar 3, 2018 at 4:19 AM, Abraham Fine  wrote:

> I am very much interested in taking a turn as a RM and I think it is a
> great time to do a release (now that 2967, 2249, and 2960 arge merged in).
>
> I agree that ZOOKEEPER-2184 can be pushed again and I don't think there is
> anything else that we need to merge in before cutting a release.
>
> Abe
>
> On Thu, Mar 1, 2018, at 21:52, Patrick Hunt wrote:
> > There are 19 resolved issues http://bit.ly/2oK9aTx
> > and 14 unresolved http://bit.ly/2oFWywS
> > ZOOKEEPER-2184 is the only unresolved blocker, however that's not a
> > regression and was pushed from 3.4.11, we could do so again given it's
> > still being worked on.
> >
> > Abe are you interested in taking a turn as RM?
> >
> > Patrick
> >
> > On Thu, Mar 1, 2018 at 4:38 PM, Andor Molnar  wrote:
> >
> > > Hi dev,
> > >
> > > User has recently run into the regression of 3.4.11 (ZOOKEEPER-2960
> > > ) (again?)
> > > Are we good to cut 3.4.12 soon or still waiting for something to be
> > > committed?
> > >
> > > Andor
> > >
>


Re: 3.4.12

2018-03-05 Thread Abraham Fine
Thank's Pat.

I'll get started on this ASAP.

On Mon, Mar 5, 2018, at 10:14, Patrick Hunt wrote:
> Thanks for "volunteering" Abe. :-)
> 
> sgtm, +1 - there are some important fixes to get out for 3.4.
> 
> FYI the "how to release" page is here:
> https://cwiki.apache.org/confluence/display/ZOOKEEPER/HowToRelease+using+git
> ff to ping me if you run into issues (update that page if you do find
> issues)
> 
> Regards,
> 
> Patrick
> 
> On Fri, Mar 2, 2018 at 2:49 PM, Abraham Fine  wrote:
> 
> > I am very much interested in taking a turn as a RM and I think it is a
> > great time to do a release (now that 2967, 2249, and 2960 arge merged in).
> >
> > I agree that ZOOKEEPER-2184 can be pushed again and I don't think there is
> > anything else that we need to merge in before cutting a release.
> >
> > Abe
> >
> > On Thu, Mar 1, 2018, at 21:52, Patrick Hunt wrote:
> > > There are 19 resolved issues http://bit.ly/2oK9aTx
> > > and 14 unresolved http://bit.ly/2oFWywS
> > > ZOOKEEPER-2184 is the only unresolved blocker, however that's not a
> > > regression and was pushed from 3.4.11, we could do so again given it's
> > > still being worked on.
> > >
> > > Abe are you interested in taking a turn as RM?
> > >
> > > Patrick
> > >
> > > On Thu, Mar 1, 2018 at 4:38 PM, Andor Molnar  wrote:
> > >
> > > > Hi dev,
> > > >
> > > > User has recently run into the regression of 3.4.11 (ZOOKEEPER-2960
> > > > ) (again?)
> > > > Are we good to cut 3.4.12 soon or still waiting for something to be
> > > > committed?
> > > >
> > > > Andor
> > > >
> >


Re: 3.4.12

2018-03-05 Thread Patrick Hunt
Thanks for "volunteering" Abe. :-)

sgtm, +1 - there are some important fixes to get out for 3.4.

FYI the "how to release" page is here:
https://cwiki.apache.org/confluence/display/ZOOKEEPER/HowToRelease+using+git
ff to ping me if you run into issues (update that page if you do find
issues)

Regards,

Patrick

On Fri, Mar 2, 2018 at 2:49 PM, Abraham Fine  wrote:

> I am very much interested in taking a turn as a RM and I think it is a
> great time to do a release (now that 2967, 2249, and 2960 arge merged in).
>
> I agree that ZOOKEEPER-2184 can be pushed again and I don't think there is
> anything else that we need to merge in before cutting a release.
>
> Abe
>
> On Thu, Mar 1, 2018, at 21:52, Patrick Hunt wrote:
> > There are 19 resolved issues http://bit.ly/2oK9aTx
> > and 14 unresolved http://bit.ly/2oFWywS
> > ZOOKEEPER-2184 is the only unresolved blocker, however that's not a
> > regression and was pushed from 3.4.11, we could do so again given it's
> > still being worked on.
> >
> > Abe are you interested in taking a turn as RM?
> >
> > Patrick
> >
> > On Thu, Mar 1, 2018 at 4:38 PM, Andor Molnar  wrote:
> >
> > > Hi dev,
> > >
> > > User has recently run into the regression of 3.4.11 (ZOOKEEPER-2960
> > > ) (again?)
> > > Are we good to cut 3.4.12 soon or still waiting for something to be
> > > committed?
> > >
> > > Andor
> > >
>


Re: 3.4.12

2018-03-02 Thread Abraham Fine
I am very much interested in taking a turn as a RM and I think it is a great 
time to do a release (now that 2967, 2249, and 2960 arge merged in).

I agree that ZOOKEEPER-2184 can be pushed again and I don't think there is 
anything else that we need to merge in before cutting a release.

Abe

On Thu, Mar 1, 2018, at 21:52, Patrick Hunt wrote:
> There are 19 resolved issues http://bit.ly/2oK9aTx
> and 14 unresolved http://bit.ly/2oFWywS
> ZOOKEEPER-2184 is the only unresolved blocker, however that's not a
> regression and was pushed from 3.4.11, we could do so again given it's
> still being worked on.
> 
> Abe are you interested in taking a turn as RM?
> 
> Patrick
> 
> On Thu, Mar 1, 2018 at 4:38 PM, Andor Molnar  wrote:
> 
> > Hi dev,
> >
> > User has recently run into the regression of 3.4.11 (ZOOKEEPER-2960
> > ) (again?)
> > Are we good to cut 3.4.12 soon or still waiting for something to be
> > committed?
> >
> > Andor
> >


Re: 3.4.12

2018-03-01 Thread Patrick Hunt
There are 19 resolved issues http://bit.ly/2oK9aTx
and 14 unresolved http://bit.ly/2oFWywS
ZOOKEEPER-2184 is the only unresolved blocker, however that's not a
regression and was pushed from 3.4.11, we could do so again given it's
still being worked on.

Abe are you interested in taking a turn as RM?

Patrick

On Thu, Mar 1, 2018 at 4:38 PM, Andor Molnar  wrote:

> Hi dev,
>
> User has recently run into the regression of 3.4.11 (ZOOKEEPER-2960
> ) (again?)
> Are we good to cut 3.4.12 soon or still waiting for something to be
> committed?
>
> Andor
>