Thank you very much for the reply Please see inline
On Fri, Dec 23, 2016 at 11:10 AM, Terence Yim <cht...@gmail.com> wrote: > Hi, > > 1. It really depends on how much resources that your application need. > Twill simply act as a bridge between your app and YARN, however, the YARN > cluster itself needs to have enough resources (memory and vcores) to run > your application. > I definitely agree that YARN should have capacity. What I am trying to say is that if I want to change my mind and resize 2nd time before 1st request was satisfied I can not do it. What if I mistyped number of requested containers - put 100 instead of 10 and YARN will never have this capacity. If I change back to 10 it won't change it unless 100 is satisfied. > > 2. You should be able to do that through the TwillRunner.lookup method. Do > you mean you tried but it doesn't return anything? > TwillRunner.lookup works ONLY if application that uses TwillRunner.lookup (YARN/Twill client another words) NEVER restarted - if it restarted all the information is lost and I am not sure how to make TwillRunner to obtain it again from running cluster. > > Terence > > On Thu, Dec 22, 2016 at 2:20 PM, Yuliya Feldman <yul...@dremio.com> wrote: > > > Hello there, > > > > I started using Twill recently and I came across couple of issues I > wanted > > to check on: > > > > 1. If I resize YARN cluster to more capacity it can handle I can't resize > > down, as it did not satisfy first request > > > > 2. If my application that spawns up Twill YARN Cluster restarts (meaning > I > > am losing YarnTwillRunnerService) I can not get hold of the > TwillController > > after it even I know runId and what not. > > > > Could anybody advise/confirm/deny on the issues I am seeing? > > > > Thanks in advance > > >
