reef-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Dhruv Mahajan <dhruv.maha...@gmail.com>
Subject Re: Issue with EvaluatorRequestor wrt. number of cores
Date Wed, 20 Apr 2016 01:37:24 GMT
This is the log from EvaluatorReuestor.Submit()
INFO: Submitting request for 500 evaluators and 6000 MB memory and  2 core
to rack .

These are what I get as result in driver.stderr from java side

INFO: allocated evaluator - serialized evaluator descriptor:
IP=CISL-SLAVE-028.sys-sqlsvr.local/10.200.145.216, Port=45454,
HostName=CISL-SLAVE-028.sys-sqlsvr.local, Memory=6144, Core=1,
RuntimeName=Yarn

Seems like a bug? I could not fine any other logs related to this.

On Tue, Apr 19, 2016 at 1:34 PM, Dhruv Mahajan <dhruv.mahajan@gmail.com>
wrote:

> Lemme check.
>
> Dhruv
>
> On Tue, Apr 19, 2016 at 1:23 PM, Markus Weimer <markus@weimo.de> wrote:
>
>> On 4/18/2016 11:12 PM, Dhruv Mahajan wrote:
>>
>>> In IMRU I was trying to allocate evaluators with 2 cores each. I verified
>>> that request consisted of 2 core evaluators in C#. On checking java
>>> stderr
>>> logs, I found the following:-
>>>
>>> INFO: allocated evaluator - serialized evaluator descriptor:
>>> IP=CISL-SLAVE-103.sys-sqlsvr.local/10.200.144.38, Port=45454,
>>> HostName=CISL-SLAVE-103.sys-sqlsvr.local, Memory=6144, Core=1,
>>> RuntimeName=Yarn
>>>
>>
>> This is the allocation, right? Do we have a log when the request goes
>> out? I'm asking because it could be that the RM is rounding down OR that we
>> send the wrong request.
>>
>> Markus
>>
>
>

Mime
  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message