You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@aurora.apache.org by "Zameer Manji (JIRA)" <ji...@apache.org> on 2017/03/01 23:27:45 UTC

[jira] [Created] (AURORA-1897) Remove task length restrictions.

Zameer Manji created AURORA-1897:
------------------------------------

             Summary: Remove task length restrictions.
                 Key: AURORA-1897
                 URL: https://issues.apache.org/jira/browse/AURORA-1897
             Project: Aurora
          Issue Type: Task
            Reporter: Zameer Manji
            Priority: Minor


Currently we restrict the total name of a task because of a Mesos bug:
{noformat}
  // 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.");
    }
{noformat} 

However [~codyg] recently [asked|https://lists.apache.org/thread.html/ca92420fe6394d6467f70989e1ffadac23775e84cf7356ff8c9efdd5@%3Cdev.mesos.apache.org%3E] on the mesos mailing list about MESOS-691 and learned that it is no longer valid.

We should remove this restriction.



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