[
https://issues.apache.org/jira/browse/MESOS-361?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13981685#comment-13981685
]
Jameel Al-Aziz commented on MESOS-361:
--------------------------------------
[~bmahler], (2) seems to be a bug in Mesos, although I'm not 100% sure. It only
occurred when upgrading the Mesos slaves from 0.17 to 0.18. I didn't change the
version of Chronos. So either, Chronos is no longer fully compatible with 0.18
or something changed in Mesos that broke Task IDs that include spaces.
As for (1), I'm referring to the browse API call. I tracked down the problem to
a bug in Libprocess and have submitted a patch to [~benjaminhindman] that
should address the problem.
> Restrict the character space of user provided TaskIDs.
> ------------------------------------------------------
>
> Key: MESOS-361
> URL: https://issues.apache.org/jira/browse/MESOS-361
> Project: Mesos
> Issue Type: Bug
> Reporter: Benjamin Mahler
> Assignee: Dominic Hamon
> Labels: newbie
> Fix For: 0.19.0
>
>
> We need to restrict the character space of our identifiers.
> -FrameworkID
> -ExecutorID
> -ExecutorInfo.source
> -TaskID
> Using whitespace in these is messy, but using things like forward slashes
> will break functionality!
> In particular, file system operations using the ids, as well as statistics
> usage potentially.
--
This message was sent by Atlassian JIRA
(v6.2#6252)
