You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@mesos.apache.org by "Neil Conway (JIRA)" <ji...@apache.org> on 2017/02/01 18:07:51 UTC

[jira] [Commented] (MESOS-7047) Update agent for hierarchical roles

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

Neil Conway commented on MESOS-7047:
------------------------------------

[~jieyu] pointed out a problem with #3: we might get collisions between persistence IDs and nested roles. For example, if role {{a/b/c}} creates a volume with persistence ID {{d}}, this would collide with a volume created by role {{a/b/c/d}}.

> Update agent for hierarchical roles
> -----------------------------------
>
>                 Key: MESOS-7047
>                 URL: https://issues.apache.org/jira/browse/MESOS-7047
>             Project: Mesos
>          Issue Type: Bug
>          Components: agent
>            Reporter: Neil Conway
>              Labels: mesosphere
>
> Agents use the role name in the file system path for persistent volumes: a persistent volume is written to {{work_dir/meta/volumes/roles/<role-name>/<persistence-id>}}. When using hierarchical roles, {{role-name}} might contain slashes. It seems like there are three options here:
> # When converting the role name into the file system path, escape any slashes that appear.
> # Hash or otherwise encode the role name before using it in the file system path.
> # Create a directory hierarchy that corresponds to the nesting in the role name. So a volume for role {{a/b/c/d}} would be stored in {{roles/a/b/c/d/<persistence-id>}}.
> If we adopt #3, we'd probably also want to cleanup the filesystem when a volume is removed.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)