zookeeper-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Norbert Kalmar <nkal...@cloudera.com.INVALID>
Subject Re: Re: ZooKeeper 3.5 blocker issues
Date Tue, 04 Sep 2018 08:25:31 GMT
I agree on the list.

Looks like every one has someone working on it or even a PR available.
Except ZOOKEEPER-2846. That looks like a tough one. I will take a look, but
can't promise I will be able to work much on it in September.
So if anyone has an idea feel free to chip in! :)

Regards,
Norbert

On Mon, Sep 3, 2018 at 4:01 PM 岭秀 <maoling199210191@sina.com> wrote:

> waiting for the release of 3.5.
> I will take the work of ZOOKEEPER-2778 if I have the time
> ----- 原始邮件 -----
> 发件人:Andor Molnar <andor@cloudera.com.INVALID>
> 收件人:DevZooKeeper <dev@zookeeper.apache.org>
> 主题:Re: ZooKeeper 3.5 blocker issues
> 日期:2018年09月03日 18点17分
>
> Unfortunately I haven't got feedback on this blocker list, can we say that
> we have an agreement on it? :)
> - ZOOKEEPER-236 (SSL/TLS support for Atomic Broadcast protocol)
> - ZOOKEEPER-1549 (Data inconsistency when follower is receiving a DIFF with
> a dirty snapshot)
> - ZOOKEEPER-1818 (Fix don't care for trunk)
> - ZOOKEEPER-2418 (txnlog diff sync can skip sending some transactions to
> followers)
> - ZOOKEEPER-2778 (Potential server deadlock between follower sync with
> leader and follower receiving external connection requests.)
> - ZOOKEEPER-2846 (Leader follower sync with on disk txns can possibly leads
> to data inconsistency) (might be duplicate of ZK-2418)
> - ZOOKEEPER-2930 (Leader cannot be elected due to network timeout of some
> members.)
> Most of these tickets are having patch available in Jira or in Github. I'll
> review them in the next few weeks to see how we could resolve the issues. I
> believe that if these tickets can be closed in one way or the other, we'll
> be able to release the upcoming 3.5 version as stable.
> Thoughts?
> Regards,
> Andor
> On Tue, Aug 14, 2018 at 11:08 AM, Andor Molnar <andor@cloudera.com> wrote:
> > One more item to the list which is very-very important:
> >
> > ZOOKEEPER-236 (SSL/TLS support for Atomic Broadcast protocol)
> >
> > Andor
> >
> >
> >
> > On Mon, Aug 13, 2018 at 2:09 PM, Andor Molnar <andor@apache.org> wrote:
> >
> >> Looking at the list of Critical issues, I think the following items
> might
> >> be considered as blockers too:
> >>
> >> ZOOKEEPER-2418 (data inconsistency)
> >> ZOOKEEPER-2778
> >> ZOOKEEPER-2846 (data inconsistency)
> >> ZOOKEEPER-2930 (leader election deadlock)
> >>
> >> Regards,
> >> Andor
> >>
> >>
> >>
> >>
> >> > On 2018. Aug 13., at 12:38, Andor Molnar <andor@apache.org> wrote:
> >> >
> >> > Hi folks,
> >> >
> >> > This has been raised on the user list recently as well, so I think
> it’s
> >> good time to review what’s left for a stable 3.5 release. The list of
> >> unresolved blocker issues from Jira is the following:
> >> >
> >> > https://issues.apache.org/jira/issues/?jql=project%20%3D%
> >> 20ZooKeeper%20AND%20priority%20in%20(Blocker)%20AND%
> >> 20resolution%20%3D%20Unresolved%20ORDER%20BY%20priority%20DESC <
> >> https://issues.apache.org/jira/issues/?jql=project%20=%20Zo
> >> oKeeper%20AND%20priority%20in%20(Blocker)%20AND%20resolution
> >> %20=%20Unresolved%20ORDER%20BY%20priority%20DESC>
> >> >
> >> > It seems to me that the following items are the real blockers for a
> >> stable 3.5-release:
> >> >
> >> > ZOOKEEPER-1549
> >> > ZOOKEEPER-1818
> >> >
> >> > The rest of the list should be revisited and Jira should be amended
> >> accordingly. (e.g. ZOOKEEPER-2159 is a blocker improvement??)
> >> >
> >> > Please correct me if I’m wrong and share your thoughts.
> >> >
> >> > Regards,
> >> > Andor
> >> >
> >> >
> >>
> >>
> >
>

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