Yes, there is, in fact, some more tuning to be done! The executor takes a command line flag, --announcer-ensemble, which should be the host:port of your ZK ensemble where tasks should be announced. You can configure the flags passed to the executor when its launched via the -thermos_executor_flags (see: https://github.com/apache/aurora/blob/master/docs/reference/scheduler-configuration.md for all scheduler args) argument on the scheduler.
If you look at the aurora-scheduler.conf we use for our vagrant image, you can see an example of wiring this all together: https://github.com/apache/aurora/blob/master/examples/vagrant/upstart/aurora-scheduler.conf#L45 . Cheers, Joshua On Thu, May 12, 2016 at 10:26 AM, Adrian Fraisse <[email protected]> wrote: > Hi dear Aurora friends ! > > I need to deploy services on Aurora with inter-dependencies between them. > I am looking into using Aurora’s service discovery feature in conjonction > with tellapart/aurproxy (https://github.com/tellapart/aurproxy) to allow > my services to find each other. > > However, I cannot get things to work. It seems that despite the fact that > I use an Announcer object inside my configuration, Aurora doesn’t register > my tasks into Zookeeper. > > I have read the documentation over and over. Something bugs me in the > Announcer object’s documentation : each task will be registered in the > ServerSet /aurora/role/environment/jobname in the* zookeeper ensemble > configured by the executor. *What is « the zookeeper ensemble configured > by the executor » ? Does that mean there is some more tuning to be done on > thermos in order to perform service discovery ? > > Any though would be greatly appreciated ! > > Thanks. > Adrian >
