[jira] [Commented] (REEF-106) Make parameters used in MesosScheduler configurable using TANG

["John Yang (JIRA)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/REEF-106?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14288950#comment-14288950 ] 

John Yang commented on REEF-106:
--------------------------------

I have questions regarding NodeDescriptorProto. It seems to contain node information(in case of YARN runtime: NodeManager's information) consisting of 5 attributes:
- identifier
- host_name
- port
- memory_size
- rack_name

I was wondering about the need for host_name and port. Is there such a case where we want to directly talk to the slave nodes? Also it would be good to add vcore_size.

> Make parameters used in MesosScheduler configurable using TANG
> --------------------------------------------------------------
>
>                 Key: REEF-106
>                 URL: https://issues.apache.org/jira/browse/REEF-106
>             Project: REEF
>          Issue Type: Task
>          Components: REEF-Runtime-Mesos
>            Reporter: John Yang
>            Priority: Minor
>
> First, MESOS_SLAVE_PORT is statically set to 5051 to be used in constructing nodeDescriptorProtos upon resourceOffers(). It would be good to make it configurable as clusters can have different settings. 
> Even so, a cluster may have Mesos slaves that use different ports. Unlike YARN, we cannot ask Mesos Master for the ports of Mesos slaves and an offer in resourceOffers() contains only the slave's hostname, excluding its port number. But as it is not a common case, I think we can postpone discussing it.
> Second, the Mesos framework user name is statically defined as ""(an empty string) which indicates using the framework submitter's user name. Making it configurable via Tang should also be a straightforward task.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)