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 wrote:
> Sounds like you
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
If my understanding of how Mesos allocation algorithm works, there are
allocations made if there are offers made. An allocator performs
allocation, which is used by the master to generate offers to frameworks,
which, in turn, may be accepted or declined. Have you tried to increase the
log level
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 wrote:
> If the offer is rejected by your framework,
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 <
aharipriy...@gmail.com> wrote:
> Alex,
>
> The problem I am facing is that there are no allocations made. Mesos
> -master gives 5
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
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
>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
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 wrote:
> >Well, the log you mentioned above is when the resource offer is accepted
> and mesos-master
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
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
11 matches
Mail list logo