Details
-
Task
-
Status: Resolved
-
Minor
-
Resolution: Fixed
-
None
-
None
-
None
Description
Currently we restrict the total name of a task because of a Mesos bug:
// This number is derived from the maximum file name length limit on most UNIX systems, less // the number of characters we've observed being added by mesos for the executor ID, prefix, and // delimiters. @VisibleForTesting static final int MAX_TASK_ID_LENGTH = 255 - 90; .... // TODO(maximk): This is a short-term hack to stop the bleeding from // https://issues.apache.org/jira/browse/MESOS-691 if (taskIdGenerator.generate(task, totalInstances).length() > MAX_TASK_ID_LENGTH) { throw new TaskValidationException( "Task ID is too long, please shorten your role or job name."); }
However codyg recently asked on the mesos mailing list about MESOS-691 and learned that it is no longer valid.
We should remove this restriction.
Attachments
Issue Links
- relates to
-
MESOS-691 Slave should not crash on failure to launch/kill executors
- Resolved