I'm very sorry! I thought I did reply back to this email thread - not sure how I missed this.
The issue is resolved after I upgraded to latest version of marathon - it has better logging enabled too.. On Wed, Sep 2, 2015 at 10:09 AM, Vinod Kone <[email protected]> wrote: > Sounds like you should bump up the logging level of marathon. Did you ask > in the marathon mailing list? > > On Wed, Sep 2, 2015 at 10:02 AM, Haripriya Ayyalasomayajula < > [email protected]> wrote: > >> Alex, >> >> The problem I am facing is that there are no allocations made. Mesos >> -master gives 5 requests to marathon. But marathon DECLINE s all the >> offers. I am trying to debug the reason why it is rejecting the offers. I >> traced down the source code to see that it calls the ResourceMatcher to >> match the resource offered vs. Resource Available and in my case it says it >> has problem with the cpu's offered (not sufficient resources ). I am trying >> to get the details of the resource offer made available - the cpu's being >> offered and I'm stuck there.. >> >> I really appreciate if you have any suggestions! Thanks. >> >> On Wed, Sep 2, 2015 at 9:54 AM, Alex Rukletsov <[email protected]> >> wrote: >> >>> To what Haosdent said: you cannot get a list of offers from master logs, >>> but you can get a list of allocations from the built-in allocator in you >>> bump up the log level (GLOG_v=2). >>> >>> On Wed, Sep 2, 2015 at 7:36 AM, haosdent <[email protected]> wrote: >>> >>>> If the offer is rejected by your framework, could you find this log in >>>> mesos: >>>> >>>> ``` >>>> xxx Processing DECLINE call for offers xxx >>>> ``` >>>> >>>> On Wed, Sep 2, 2015 at 1:31 PM, haosdent <[email protected]> wrote: >>>> >>>>> >Well, the log you mentioned above is when the resource offer is >>>>> accepted and mesos-master then allocates the cpu. >>>>> Hi, @Haripriya As far as i know, the log I show above is allocator >>>>> allocate resource and make a offer. And then trigger Master::offer to send >>>>> offer to frameworks. So the log above is not resource offer is >>>>> accepted, it is before send offer to framework and it also is the details >>>>> about that offer. >>>>> >>>>> For you problem >>>>> >In my case, the offer is being rejected >>>>> If you mean the offer is rejected by your framework after your >>>>> framework receive it? Or you mean your framework never receive offers from >>>>> mesos? >>>>> >>>>> >>>>> On Wed, Sep 2, 2015 at 1:51 AM, Haripriya Ayyalasomayajula < >>>>> [email protected]> wrote: >>>>> >>>>>> Well, the log you mentioned above is when the resource offer is >>>>>> accepted and mesos-master then allocates the cpu. In my case, the offer >>>>>> is >>>>>> being rejected. I am trying to debug the reason as to why the resource >>>>>> offer is being rejected. >>>>>> >>>>>> On Tue, Sep 1, 2015 at 10:00 AM, haosdent <[email protected]> wrote: >>>>>> >>>>>>> Yes, currently only print number for offers in mesos code in default >>>>>>> log level. If you want get more details about it, you could start with >>>>>>> set >>>>>>> environment variable GLOG_v2=1 Then you should got some similar message >>>>>>> like this: >>>>>>> >>>>>>> I0902 00:55:17.465920 143396864 hierarchical.hpp:935] Allocating >>>>>>> cpus(*):x; mem(*):x; disk(*):x; ports(*):[x-x] on slave >>>>>>> 20150902-005512-16777343-5050-46447-S0 to framework 20150902-00551 >>>>>>> 2-16777343-5050-46447-0000 >>>>>>> >>>>>>> But use GLOG_v2 would have a lot of log. If you just want to get the >>>>>>> resources allocated to task or executor, you could get those >>>>>>> informations >>>>>>> from slave state.json endpoint. >>>>>>> >>>>>>> On Wed, Sep 2, 2015 at 12:41 AM, Haripriya Ayyalasomayajula < >>>>>>> [email protected]> wrote: >>>>>>> >>>>>>>> Thanks, but is there no way without tweaking the source code of the >>>>>>>> framework scheduler that I get the details of the resource offer? I >>>>>>>> don't >>>>>>>> see anything in my logs. >>>>>>>> >>>>>>>> All I can see is >>>>>>>> >>>>>>>> mesos-master: Sending 5 offers to framework 20150815-.... >>>>>>>> (marathon) at scheduler-50ajaja@pqr >>>>>>>> >>>>>>>> I can't find any other details in the logs.. >>>>>>>> >>>>>>>> On Mon, Aug 31, 2015 at 8:36 PM, haosdent <[email protected]> >>>>>>>> wrote: >>>>>>>> >>>>>>>>> Hi, Haripriya. >>>>>>>>> >>>>>>>>> >1. I am trying to see the details of the resource offer made by >>>>>>>>> the mesos master. I can see in the logs that there are 5 resource >>>>>>>>> offers >>>>>>>>> made but I am not sure where to get the details of the resource >>>>>>>>> offers - >>>>>>>>> the cpu, memory etc. >>>>>>>>> >>>>>>>>> You could print offer details in your >>>>>>>>> framework Scheduler#resourceOffers methods. These offer message also >>>>>>>>> could >>>>>>>>> find from mesos log. >>>>>>>>> >>>>>>>>> >2. How can I list the number of slaves registered with the >>>>>>>>> master and the details of the slaves on the command line( apart from >>>>>>>>> seeing >>>>>>>>> it in the UI)? >>>>>>>>> >>>>>>>>> We have some endpoints(state.json and state-summary) in master and >>>>>>>>> slave to expose these informations, you could got this from >>>>>>>>> >>>>>>>>> ``` >>>>>>>>> curl -s "http://localhost:5050/master/state-summary"; |jq .slaves >>>>>>>>> ``` >>>>>>>>> >>>>>>>>> >>>>>>>>> On Tue, Sep 1, 2015 at 6:47 AM, Haripriya Ayyalasomayajula < >>>>>>>>> [email protected]> wrote: >>>>>>>>> >>>>>>>>>> Hello, >>>>>>>>>> >>>>>>>>>> I'm having trouble with some basic details: >>>>>>>>>> >>>>>>>>>> 1. I am trying to see the details of the resource offer made by >>>>>>>>>> the mesos master. I can see in the logs that there are 5 resource >>>>>>>>>> offers >>>>>>>>>> made but I am not sure where to get the details of the resource >>>>>>>>>> offers - >>>>>>>>>> the cpu, memory etc. >>>>>>>>>> >>>>>>>>>> 2. How can I list the number of slaves registered with the master >>>>>>>>>> and the details of the slaves on the command line( apart from seeing >>>>>>>>>> it in >>>>>>>>>> the UI)? >>>>>>>>>> >>>>>>>>>> Thanks for the help. >>>>>>>>>> >>>>>>>>>> -- >>>>>>>>>> Regards, >>>>>>>>>> Haripriya Ayyalasomayajula >>>>>>>>>> >>>>>>>>>> >>>>>>>>> >>>>>>>>> >>>>>>>>> -- >>>>>>>>> Best Regards, >>>>>>>>> Haosdent Huang >>>>>>>>> >>>>>>>> >>>>>>>> >>>>>>>> >>>>>>>> -- >>>>>>>> Regards, >>>>>>>> Haripriya Ayyalasomayajula >>>>>>>> >>>>>>>> >>>>>>> >>>>>>> >>>>>>> -- >>>>>>> Best Regards, >>>>>>> Haosdent Huang >>>>>>> >>>>>> >>>>>> >>>>>> >>>>>> -- >>>>>> Regards, >>>>>> Haripriya Ayyalasomayajula >>>>>> >>>>>> >>>>> >>>>> >>>>> -- >>>>> Best Regards, >>>>> Haosdent Huang >>>>> >>>> >>>> >>>> >>>> -- >>>> Best Regards, >>>> Haosdent Huang >>>> >>> >>> >> >> >> -- >> Regards, >> Haripriya Ayyalasomayajula >> >> > -- Regards, Haripriya Ayyalasomayajula
