Hello,

I'm looking for a way to initially obtain a full report of cluster
nodes in the application master. That would be the equivalent of
ClientRMService.getClusterNodes (which seems to be intended for use by
the client only?)

If my understanding is correct AMResponse.getUpdatedNodes would give
me deltas that can be used subsequently to maintain the list?

Thanks,
Thomas

AMResponse.getUpdatedNodes() would give you only nodes that have been
updated. Say they are lost or become healthy again. So you won't get total
cluster information from that.
On 6/22/12 3:10 PM, "Thomas Weise" <[EMAIL PROTECTED]> wrote:

>Hello,
>
>I'm looking for a way to initially obtain a full report of cluster
>nodes in the application master. That would be the equivalent of
>ClientRMService.getClusterNodes (which seems to be intended for use by
>the client only?)
>
>If my understanding is correct AMResponse.getUpdatedNodes would give
>me deltas that can be used subsequently to maintain the list?
>
>Thanks,
>Thomas
>

That's right, how to fetch the full list from app master?

On Fri, Jun 22, 2012 at 3:29 PM, Bikas Saha <[EMAIL PROTECTED]> wrote:
>
> AMResponse.getUpdatedNodes() would give you only nodes that have been
> updated. Say they are lost or become healthy again. So you won't get total
> cluster information from that.
>
>
> On 6/22/12 3:10 PM, "Thomas Weise" <[EMAIL PROTECTED]> wrote:
>
>>Hello,
>>
>>I'm looking for a way to initially obtain a full report of cluster
>>nodes in the application master. That would be the equivalent of
>>ClientRMService.getClusterNodes (which seems to be intended for use by
>>the client only?)
>>
>>If my understanding is correct AMResponse.getUpdatedNodes would give
>>me deltas that can be used subsequently to maintain the list?
>>
>>Thanks,
>>Thomas
>>
>
>

It's fine to use ClientRMService.getNodes from the AM too, you'll need to instantiate an extra proxy of course.

On Jun 22, 2012, at 3:37 PM, Thomas Weise wrote:

> That's right, how to fetch the full list from app master?
>
> On Fri, Jun 22, 2012 at 3:29 PM, Bikas Saha <[EMAIL PROTECTED]> wrote:
>>
>> AMResponse.getUpdatedNodes() would give you only nodes that have been
>> updated. Say they are lost or become healthy again. So you won't get total
>> cluster information from that.
>>
>>
>> On 6/22/12 3:10 PM, "Thomas Weise" <[EMAIL PROTECTED]> wrote:
>>
>>> Hello,
>>>
>>> I'm looking for a way to initially obtain a full report of cluster
>>> nodes in the application master. That would be the equivalent of
>>> ClientRMService.getClusterNodes (which seems to be intended for use by
>>> the client only?)
>>>
>>> If my understanding is correct AMResponse.getUpdatedNodes would give
>>> me deltas that can be used subsequently to maintain the list?
>>>
>>> Thanks,
>>> Thomas
>>>
>>
>>

--
Arun C. Murthy
Hortonworks Inc.
http://hortonworks.com/

AMResponse.getUpdatedNodes returns nodes that have been updated
_since_when_ ?  The doc comments leave too much to the imagination in that
regard.

A reasonable assumption could be that the first time you call it that you
get a full snapshot.

Presumably the second (and later) calls return updates since the previous
call, but even that isn't clear.

On 6/22/12 3:29 PM, "Bikas Saha" <[EMAIL PROTECTED]> wrote:

>
>AMResponse.getUpdatedNodes() would give you only nodes that have been
>updated. Say they are lost or become healthy again. So you won't get total
>cluster information from that.
>
>
>On 6/22/12 3:10 PM, "Thomas Weise" <[EMAIL PROTECTED]> wrote:
>
>>Hello,
>>
>>I'm looking for a way to initially obtain a full report of cluster
>>nodes in the application master. That would be the equivalent of
>>ClientRMService.getClusterNodes (which seems to be intended for use by
>>the client only?)
>>
>>If my understanding is correct AMResponse.getUpdatedNodes would give
>>me deltas that can be used subsequently to maintain the list?
>>
>>Thanks,
>>Thomas
>>
>
>

Here's the javadoc for getUpdatedNodes(). It says that the return value is
the delta of the updated nodes since the last response. So the API gives
one the difference between the updated nodes since the last time one
called allocate().
One could augment the doc to clarify that nothing will be returned in the
first call to allocate(). Also, it will help everyone if the wording of
the doc could be made more clear. So I would gladly change that based on
suggestions. Or you could do it yourself.

  /**
   * Get the list of updated <code>NodeReport</code>s. Updates
could be
   * changes in health, availability etc of the nodes.
   * @return The delta of updated nodes since the last response
   */

On 6/28/12 10:21 AM, "Finger, Jay" <[EMAIL PROTECTED]> wrote:

>AMResponse.getUpdatedNodes returns nodes that have been updated
>_since_when_ ?  The doc comments leave too much to the imagination in that
>regard.
>
>A reasonable assumption could be that the first time you call it that you
>get a full snapshot.
>
>Presumably the second (and later) calls return updates since the previous
>call, but even that isn't clear.
>
>On 6/22/12 3:29 PM, "Bikas Saha" <[EMAIL PROTECTED]> wrote:
>
>>
>>AMResponse.getUpdatedNodes() would give you only nodes that have been
>>updated. Say they are lost or become healthy again. So you won't get
>>total
>>cluster information from that.
>>
>>
>>On 6/22/12 3:10 PM, "Thomas Weise" <[EMAIL PROTECTED]> wrote:
>>
>>>Hello,
>>>
>>>I'm looking for a way to initially obtain a full report of cluster
>>>nodes in the application master. That would be the equivalent of
>>>ClientRMService.getClusterNodes (which seems to be intended for use by
>>>the client only?)
>>>
>>>If my understanding is correct AMResponse.getUpdatedNodes would give
>>>me deltas that can be used subsequently to maintain the list?
>>>
>>>Thanks,
>>>Thomas
>>>
>>
>>
>
>