Re: Sharded Service Coordination

Tracking this at https://issues.apache.org/jira/browse/AURORA-587 -=Bill On Fri, Jul 11, 2014 at 2:24 PM, Joe Stein wrote: > +1 for adding it to Aurora, looking forward to using it, thanks > > /*** > Joe Stein > Founder, Principal Consultant > Big

Re: Sharded Service Coordination

+1 for adding it to Aurora, looking forward to using it, thanks /*** Joe Stein Founder, Principal Consultant Big Data Open Source Security LLC http://www.stealth.ly Twitter: @allthingshadoop *

Re: Sharded Service Coordination

Unfortunately the mesos log API does not currently support reading the log from non-leading replicas. Depending on where we go with the storage overhaul, it's possible we could enable reads from non-leading schedulers, however. That said, querying this from the leading scheduler is relatively che

Re: Sharded Service Coordination

Bill, I'm hoping we could also pull information like host, port, process, state, etc from WAL replica logs stored in scheduler. No? On Wed, Jul 9, 2014 at 1:35 PM, Bill Farner wrote: > FWIW at Twitter we do something that sounds like a mix between (1) and (2). > We consume the (otherwise unused)

Re: Sharded Service Coordination

*Nudge nudge* We would love to take advantage of this tool if you folks would be so kind! Thanks, James On 7/9/14 1:35 PM, "Bill Farner" wrote: >FWIW at Twitter we do something that sounds like a mix between (1) and >(2). > We consume the (otherwise unused) Announcer configuration parameter [

Re: Sharded Service Coordination

FWIW at Twitter we do something that sounds like a mix between (1) and (2). We consume the (otherwise unused) Announcer configuration parameter [1] to 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