Ah, thanks for the clarification. I can't find any logs from the framework indicating that we got the initial offer, so it looks like it could have been dropped. We haven't set --offer-timeout on our masters, so your explanation makes sense. Thanks!
On Mon, Apr 25, 2016 at 4:17 PM, Vinod Kone <vinodk...@apache.org> wrote: > > I0421 21:03:32.014999 17071 master.cpp:4290] Sending 1 offers to >> framework sy3x4 (sy3x4) at >> scheduler-6bb2bcf0-d060-4072-a25b-917d8007fb1c@172.16.13.243:56861 >> > > This shows that the slaves resources were sent to a framework. Looks like > the framework is holding on to the offer for a long time? > > >> I0421 21:03:32.019800 17076 hierarchical.hpp:588] Slave >> 20151116-203437-35000492-5050-17068-S70 (lively-rice) updated with >> oversubscribed resources (total: mem(*):217609; cpus(*):210; >> ports(*):[2048-3048]; disk(*):639829, allocated: mem(*):217609; >> cpus(*):210; ports(*):[2048-3048]; disk(*):639829) >> > > This says that from the view point of master/allocator, all the resources > are allocated. This is because the framework hasn't replied to the offer. > Did the framework receive the offer or was it dropped by the network due to > the networking issues? > >
