[
https://issues.apache.org/jira/browse/MESOS-9040?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16531608#comment-16531608
]
Benjamin Hindman commented on MESOS-9040:
-----------------------------------------
As [~tillt] mentioned, it's meant to be a convenience for framework developers
who don't want to have to spin up a Mesos cluster when doing local testing.
This can dramatically decrease the friction for writing integration tests.
I also agree with [~tillt] that we could have users run {{mesos-local}} by
themselves in order to do local testing or make their integration tests call
{{mesos-local}}. If we really don't have any users using this that might be the
most prudent path.
Alternatively, could we create a {{libmesos-local.so}} and then dynamically
load that library only if we go down the local path?
> Break scheduler driver dependency on mesos-local.
> -------------------------------------------------
>
> Key: MESOS-9040
> URL: https://issues.apache.org/jira/browse/MESOS-9040
> Project: Mesos
> Issue Type: Task
> Components: build, scheduler driver
> Reporter: James Peach
> Priority: Minor
>
> The scheduler driver in {{src/sched/sched.cpp}} has some special dependencies
> on the {{mesos-local}} code. This seems fairly hacky, but it also causes
> binary dependencies on {{src/local/local.cpp}} to be dragged into
> {{libmesos.so}}. {{libmesos.so}} would not otherwise require this code, which
> could be isolated in the {{mesos-local}} command.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
