Re: Update on stable 3.5 release estimate

[Norbert Kalmar]

Hi!

The filter doesn't seem to work for me. But basically what's left is the
fix on java11 build and maven migration. Both should be ready soon. There
is also ZOOKEEPER-3204
 looking at it.

It should be released fairly soon, I think, and hope by the end of February?

The filter I used:
https://issues.apache.org/jira/browse/ZOOKEEPER-3204?jql=project%20%3D%20ZooKeeper%20AND%20priority%20in%20(Blocker)%20AND%20resolution%20%3D%20Unresolved%20ORDER%20BY%20priority%20DESC
If you are referring to this one, this doesn't filter on 3.5 affect
version. So not all of this needs to be fixed for a 3.5 stable.

Regards,
Norbert

On Tue, Jan 22, 2019 at 9:58 PM Felix Jancso-Szabo
 wrote:

> Hi!
>
> I looked at an old threat on this mailing list  (
>
> http://zookeeper-user.578899.n2.nabble.com/stable-3-5-release-td7583547.html
> )
> that seemed to suggest a stable 3.5 release was coming.  The blockers
> mentioned in that thread don't seem to have really gone anywhere as far as
> I can tell?
>
> Is there an estimate on when a stable release could be expected?  Even an
> order of magnitude estimate would be helpful - is it months away or will it
> be past the end of 2019?
>
> - Felix
>

Update on stable 3.5 release estimate

[Felix Jancso-Szabo]

Hi!

I looked at an old threat on this mailing list  (
http://zookeeper-user.578899.n2.nabble.com/stable-3-5-release-td7583547.html)
that seemed to suggest a stable 3.5 release was coming.  The blockers
mentioned in that thread don't seem to have really gone anywhere as far as
I can tell?

Is there an estimate on when a stable release could be expected?  Even an
order of magnitude estimate would be helpful - is it months away or will it
be past the end of 2019?

- Felix

Re: acceptedEpoch and currentEpoch values not matching exception message

[Andor Molnar]

Hi,

Looks there’re a couple of overlapping Jiras around this issue like this:
https://issues.apache.org/jira/browse/ZOOKEEPER-1621 


Mohammad Arshad has provided a patch for ZK-2307 and promised to create a 
rebased PR. Maybe you should ping him to do that or create a PR yourself if you 
feel confidence.

Either way we can fix this for the 3.5 release the earliest.

To workaround the problem I think you should manually update the epoch files to 
match and let ZooKeeper start.

Regards,
Andor




> On 2019. Jan 22., at 12:09, hrvoje  wrote:
> 
> Hi,
> 
> I have zookeeper.version=3.4.10, and I have the same problem, and I see:
> 
> https://issues.apache.org/jira/browse/ZOOKEEPER-2307
> 
> So, this issue is still not resolved, what are my options then? The problem
> appeared due to disk full, and now I cannot start zookeeper.
> 
> 
> 
> --
> Sent from: http://zookeeper-user.578899.n2.nabble.com/

Re: acceptedEpoch and currentEpoch values not matching exception message

[hrvoje]

Hi,

I have zookeeper.version=3.4.10, and I have the same problem, and I see:

https://issues.apache.org/jira/browse/ZOOKEEPER-2307

So, this issue is still not resolved, what are my options then? The problem
appeared due to disk full, and now I cannot start zookeeper.



--
Sent from: http://zookeeper-user.578899.n2.nabble.com/