[jira] [Resolved] (MESOS-235) Mesos daemon ignores --conf option

["Charles Reiss (JIRA)" <ji...@apache.org>]

     [ https://issues.apache.org/jira/browse/MESOS-235?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Charles Reiss resolved MESOS-235.
---------------------------------

       Resolution: Invalid
    Fix Version/s: 0.14.0

The --conf option indeed went away in favor of using environment variables and command-line arguments only to configure slaves. The correspondingly updated deploy scripts now source a shell script to set environment variables for the mesos slave or master. This file can include non-shared files, even based on querying the current hostname or similar, which I believe solves the use-case desired here.
                
> Mesos daemon ignores --conf option
> ----------------------------------
>
>                 Key: MESOS-235
>                 URL: https://issues.apache.org/jira/browse/MESOS-235
>             Project: Mesos
>          Issue Type: Bug
>          Components: master, slave
>            Reporter: Jessica J
>            Priority: Minor
>             Fix For: 0.14.0
>
>
> Currently mesos-daemon.sh ignores the --conf option even though mesos-master and mesos-slave allow this option. The ability to specify a conf directory is highly desirable under circumstances in which the MESOS-INSTALL directory is shared among the masters and slaves; in this case the user could specify a non-shared directory in the original mesos.conf so that all masters and slaves would get their node-specific settings from their individual conf files.
> E.g., in mesos-install/var/mesos/conf/mesos.conf:
> conf=/some/non/shared/directory
> And in /some/non/shared/directory/mesos.conf:
> ip=my.specific.ip.address
> Currently the only way to enable this sort of behavior is to manually edit mesos-daemon.sh and hardcode the path to the non-shared directory. This is non-intuitive and not very user-friendly.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira