Right now I am testing it that way. Once it is working and if that becomes
a problem then moving it into a mesosFramework project is no problem.   if
we do that it would be beneficial if they were organized under some
resource manager folder or something.

The way I wrote https://issues.apache.org/jira/browse/KAFKA-1206 was with
that in mind so folks have a light interface for doing this.  The specific
systems resource negotiator implementation could go in their project and
just importing the ResourceNegotiator trait in the project's reference of
the jar.

/*******************************************
 Joe Stein
 Founder, Principal Consultant
 Big Data Open Source Security LLC
 http://www.stealth.ly
 Twitter: @allthingshadoop <http://www.twitter.com/allthingshadoop>
********************************************/


On Thu, Jan 16, 2014 at 12:23 AM, Jun Rao <jun...@gmail.com> wrote:

> Hi, Joe,
>
> Thanks for looking into this. Do you plan to add a dependency to Mesos in
> kafka jar?
>
> Jun
>
>
> On Wed, Jan 15, 2014 at 10:50 AM, Joe Stein <joe.st...@stealth.ly> wrote:
>
> > Hi, I am working at adding some code to the kafka.Kafka.scala file.
> >
> > What I was thinking for the Utils.loadProps is to create some
> > ResourceNegotiatedConfiguration class or something to sit with it so
> > various frameworks can be supported.
> >
> > For Mesos I am thinking of storing the properties in zookeeper. For a new
> > node joining => registering a default config (originally set by a tool)
> and
> > saving it unique for that broker in a znode.  This znode would be the
> input
> > to the serverConfig for the KafkaServerStartable.
> >
> > I am going to create a kafka.tools.ResourceNegotiator.ApacheMesos tool
> too.
> >  that tool will take in a server.properties file to set the original
> > default. Once loaded in zookeeper another command to take a property and
> > flag it with a function to run (like the "use new broker id value") and
> > such.
> >
> > I would rather have some implementation in Kafka.scala and have object
> > KafkaMesos be in Kafka.scala too but wasn't sure what other thoughts
> folks
> > might have?
> >
> > I will be creating JIRA soon for it.
> >
> > /*******************************************
> >  Joe Stein
> >  Founder, Principal Consultant
> >  Big Data Open Source Security LLC
> >  http://www.stealth.ly
> >  Twitter: @allthingshadoop <http://www.twitter.com/allthingshadoop>
> > ********************************************/
> >
>

Reply via email to