Yes -- bare minimum I would like to know if the provisioning/recipe has failed to complete successfully.
> On Dec 10, 2014, at 5:25 PM, Konstantin Boudnik <[email protected]> wrote: > > Rob, > > following on our IRC chat I will Cc here two guys from the community who know > Puppet the best. Nate and Rich are likely to have the answer. Guys, if you can > chime in on the topic - it'd be great! > > To reiterate it: you are looking to a way to automatically tell if a recipe > has failed and repeat it, if required, right? > >> On Sun, Nov 30, 2014 at 09:50PM, Leidle, Rob wrote: >> Thanks Cos, >> >> This would be something that I would want to automate as it would be >> running many times across many different clusters. Ideally I would fix any >> issues causing the puppet scripts to not complete properly, but I don╧t >> know how realistic that is in the short term so I would like to setup >> retry logic if that is the recommended way of doing things. That╧s why I >> was hoping for some direction on how often to run the retry. >> >>> On 11/29/14, 5:12 PM, "Konstantin Boudnik" <[email protected]> wrote: >>> >>>> On Sun, Nov 30, 2014 at 12:50AM, Leidle, Rob wrote: >>>> Thanks Roman, >>>> >>>> I actually fixed the problem. I had an existing process monitoring the >>>> daemon and restarting it if it terminated. However, puppet encapsulates >>>> this >>>> so it is no longer needed. Also, this process was causing the namenode >>>> service to terminate once. I removed my existing monitoring process and >>>> everything is working fine. >>>> >>>> That being said is there a recommended number of times we should retry >>>> the >>>> puppet scripts on failure? >>> >>> Good to see you're coming through! As for the retries: if something >>> doesn't >>> work I usually check the logs immediatelly. Sometimes after a second >>> re-run. >>> >>> Cos >>
