I tried this out and the task that was previously scheduled was not able to hop over so it looks like the issue is probably outside of Aurora.
Thanks Bill! On Mon, Feb 4, 2019 at 6:52 PM Bill Farner <wfar...@apache.org> wrote: > I’m pretty sure I’ve seen this combination working in the (distant) past, > for limit:1 and other values. > > As a sanity check, if you remove the host that _is_ having the task > scheduled, does the task move to the other host? > > On Mon, Feb 4, 2019 at 5:10 PM Renan DelValle <renanidelva...@gmail.com> > wrote: > > > I have two dedicated nodes with a dedicated X attribute. I launched a Job > > containing the dedicated constraint X and a limit:1 and the job has two > > instances. > > Only one instance is able to find a match while the other alternates > > between being vetoed for not matching the dedicated attribute and not > > matching the limit attribute. > > > > I've checked that the offers from the dedicated nodes are coming through > > with the right attributes. > > Has anyone else been able to do this successfully? > > > > -Renan > > >
