Okay, I think that serves an alternate purpose of detecting any newly gone bad node and excluding it.
+1 for covering the original scenario under anti-affinity. ~ Bhupesh On Fri, Dec 2, 2016 at 9:14 AM, Munagala Ramanath <r...@datatorrent.com> wrote: > It only takes effect after failures -- no way to exclude from the get-go. > > Ram > > On Dec 1, 2016 7:15 PM, "Bhupesh Chawda" <bhup...@datatorrent.com> wrote: > > > As suggested by Sandesh, the parameter > > MAX_CONSECUTIVE_CONTAINER_FAILURES_FOR_BLACKLIST seems to do exactly > what > > is needed. > > Why would this not work? > > > > ~ Bhupesh > > >
