[
https://issues.apache.org/jira/browse/MESOS-7047?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Michael Park updated MESOS-7047:
--------------------------------
Description:
Agents use the role name in the file system path for persistent volumes: a
persistent volume is written to
{{work_dir/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 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.
was:
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 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.
> Update agent for hierarchical roles.
> ------------------------------------
>
> Key: MESOS-7047
> URL: https://issues.apache.org/jira/browse/MESOS-7047
> Project: Mesos
> Issue Type: Task
> 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/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 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)
