Hi, 1. Currently the contract is one container per one runnable instance. This is to provide the best resources isolation between different instances.
2. Twill only has Java API right now and uses SLF4J as the logging interface for applications to emit logs. This mean that only languages that runs in JVM would have logs collected by twill. What language are you trying to use? 3. It is actually by design that service discovery is asynchronous and it maintains an in memory cache of entries in ZK. However, the initial sync may take some time, hence you can get empty result if you try to get right away. One way to workaround it is to use the watchChanges method on the ServiceDiscovered object. Terence Sent from my iPhone > On Oct 8, 2016, at 4:52 AM, ...the end <549198...@qq.com> wrote: > > Hi，I'm using twill and here are some of my questions. > > > 1. When I configure more than one type of Runnables, how can I specify some > of them to run in the same container? > 2. How can I collect logs if I start the app writing in other languages? I'm > trying to use NFS now. Do you have some better advices? > 3. The service discover api will return null in the first time, and it will > return the results I want. I'm using zookeeper 3.4.6 and twill-incubator-0.7.0 > > > P.S. I've seen that you delivered the 0.8 release. Congratulations! > > > Hoping for your voices. > Thanks. > > > Haosu Guo
