aurora-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Oliver, James" <>
Subject Re: Sharded Service Coordination
Date Wed, 09 Jul 2014 22:48:24 GMT
*Nudge nudge*

We would love to take advantage of this tool if you folks would be so kind!


On 7/9/14 1:35 PM, "Bill Farner" <> wrote:

>FWIW at Twitter we do something that sounds like a mix between (1) and
> We consume the (otherwise unused) Announcer configuration parameter [1]
>Job, and extend the executor to publish all allocated {{thermos.port[x]}}s
>to ZooKeeper.  This is something we would love to open source, so please
>nudge us to do so if you would like this feature!
>On Wed, Jul 9, 2014 at 10:24 AM, Oliver, James <>
>> Good morning,
>> My company is in the process of adopting Apache's open source stack, and
>> I've been tasked with building Aurora jobs to deploy a few popular open
>> source technologies on Mesos. Aurora is an elegant scheduler and in our
>> estimation will met our company's needs. However, we are struggling to
>> some of the configuration requirements of some of the tools we wish to
>> deploy.
>> Scenario: When a distributed service is deployed, we need to
>> programmatically determine all hosts selected for deployment and their
>> reserved ports in order to properly configure the service. We've solved
>> this in a few not-so-elegant ways:
>>  1.  We wrote a Process to publish host/port information to a
>> file system, block until {{instances}} were written, read the
>> and finally configure the service. This works, but IMO it is not an
>> solution.
>>  2.  Next, we designed a REST API for service registration (based off of
>> the Aurora job key) and published this information to our ZooKeeper
>> ensemble. This solution removes the dependency on a pre-configured
>> distributed file system. However, some overhead is still required
>> instances are necessary so as to not introduce a point of failure).
>> jobs now require some initial configuration to be able to communicate
>> the service. Communication to this API is a little non-trivial because
>> REST service doesn't block until all information is communicated ­ this
>> would be problematic due to the nature of the HTTP protocol.
>> At this point, we realized that an even better solution might be to
>> communicate directly to Aurora scheduler to get this data. Seeing as
>> scripts are just Python, we could probably implement it in a reusable
>> fashionŠbut I'm curious if anyone has already gone down this path?
>> Thank you,
>> James O

View raw message