[
https://issues.apache.org/jira/browse/MESOS-2900?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14593798#comment-14593798
]
Marco Massenzio commented on MESOS-2900:
----------------------------------------
from email thread:
{quote}
Hi Aditi,
thanks for this and super-quick reply.
You should feel free to reply in the ticket itself (so others will see it too,
and they most likely know a lot more than I do :)
My comment was actually referring to the size of the payload - we had to add a
/summary endpoint, as clients (eg Marathon) requesting the /state had to wait
too long to get stuff back.
I don't really feel strongly either way, if this does not add much more data
and it's perceived to be useful, sure, we should add it.
I'll accept the task and assign to you, and you should feel free to submit the
code review.
Marco Massenzio
Distributed Systems Engineer
On Fri, Jun 19, 2015 at 11:30 AM, Aditi Dixit ... wrote:
Hi Marco,
It's just a small patch.
https://gist.github.com/atidix/758cf1b91d04a7995e17
Is it fine?
Also, can you please delete the issue MESOS-2899. I can't because I don't the
permission to do so.
Thanks!
Aditi
{quote}
> Display capabilities in state.json
> ----------------------------------
>
> Key: MESOS-2900
> URL: https://issues.apache.org/jira/browse/MESOS-2900
> Project: Mesos
> Issue Type: Bug
> Reporter: Aditi Dixit
> Assignee: Aditi Dixit
> Priority: Minor
>
> The capabilities field was added to FrameworkInfo recently. It should be
> displayed in the state.json HTTP endpoint.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
