Mailing-List: contact kafka-dev-help@incubator.apache.org; run by ezmlm
Precedence: bulk
Reply-To: kafka-dev@incubator.apache.org
Received-SPF: softfail (athena.apache.org: transitioning domain of
 list@toolazydogs.com does not designate 209.85.210.175 as permitted sender)
Content-Type: text/plain; charset=utf-8
Mime-Version: 1.0 (Apple Message framework v1251.1)
Subject: Re: skype meeting on replication roadmap
From: "Alan D. Cabrera" <list@toolazydogs.com>
In-Reply-To: 
 <CAFbh0Q1fk2_db+7jb-p7fU7x-j3XygGBCKsraH79UQG-qy6Byw@mail.gmail.com>
Date: Thu, 5 Jan 2012 16:58:30 -0800
Content-Transfer-Encoding: quoted-printable
Message-Id: <C5304A23-828D-4935-8ED3-C5E211D398C6@toolazydogs.com>
References: 
 <CAFbh0Q3eSP1oip+J788SgzGD0hqDaNafhELJ6nfTH0fa03w=RA@mail.gmail.com>
 <CAFbh0Q1fk2_db+7jb-p7fU7x-j3XygGBCKsraH79UQG-qy6Byw@mail.gmail.com>
To: kafka-dev@incubator.apache.org

I need to point out my personal understanding of the parameters of a =
conference call meeting.  Conference calls can be useful to facilitate =
design discussions though their use is not encouraged at ASF.  It's =
important that participants understand and abide by the following =
guidelines:

- while consensus can be built at the call no final decision can be made
- meeting minutes are posted to the mailing lists
- an adequate effort is made to give the larger community the ability to =
participate in a meaningful way after the call


Regards,
Alan

On Jan 5, 2012, at 11:11 AM, Jun Rao wrote:

> Hi, everyone,
>=20
> So far, the following people have sent me their skype id:
>=20
> Joe, David, Jeffrey, and Andrew.
>=20
> So the meeting is on. I encourage everyone to look at the design doc =
in
> kafka-50 and the new wire format at
> =
https://cwiki.apache.org/confluence/display/KAFKA/New+Wire+Format+Proposal=
before
> the meeting.
>=20
> Here is a breakdown of all the jiras and their dependencies related to =
the
> replication work:
>=20
> 1. kafka-47: create/delete data structures in ZK, automatically create
> topic, and use them (making partitions logical, supporting only 1 =
replica,
> no failure support). =EF=BB=BF=EF=BB=BF(L1)
>  1.1 kafka-237: create/delete ZK path for a topic in an admin tool =
(L0)
>  1.2 kafka-238: add a getTopicMetaData method in broker and expose it =
to
> producer
>  1.3 kafka-239: Wire existing producer and consumer to use the new ZK =
data
> structure
> 2. kafka-202: decouple request handler and socket sever; enabling long =
poll
> in the consumer (L1)
> 3. kafka-240: implement new producer and consumer request format (L1)
> 4. kafka-49: add ack to ProduceRequest (L2). depending on #3
> 5. kafka-48: long poll in consumer (L2). depending on #2
> 6. kafka-44: commit thread, replica fetcher thread (L3). depending on =
#1,
> #4, #5
> 7. kafka-45: broker starting up, leader election (L3). depending on #1
> 8. kafka-46: various ZK listeners (L3). depending on #1
> 9. kafka-43: move master to preferred replica when possible (L4).
> optimization
> 10. kafka-42: rebalance partition with new brokers (L4). extra feature
>=20
> Thanks,
>=20
> Jun
>=20
> On Wed, Jan 4, 2012 at 10:11 AM, Jun Rao <junrao@gmail.com> wrote:
>=20
>> Hi,
>>=20
>> We'd like have a meeting discussing the roadmap for replication (our =
0.8
>> release) and how people can contribute. How about a Skype meeting at =
2pm
>> Jan 6 (Friday)? If you are interested, please send me your Skype id.
>>=20
>> Thanks,
>>=20
>> Jun
>>=20