[
https://issues.apache.org/jira/browse/MESOS-1457?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14324784#comment-14324784
]
Palak Choudhary commented on MESOS-1457:
----------------------------------------
Sorry for the mess, my bad, wasn't aware of the procedure.
[~adam-mesos] Like I mentioned in the previous comment, if ID is to be made
mandatory, then constructor for Process class would also change and it would
have to be explicitly called everywhere. (Currently only ProcessBase
constructor gets called)
Its the Process class which is use way more often than ProcessBase so multiple
callers would get modified, all of which already are passing ID prefix anyway.
Note:
To be clear to anyone reading this, mandatory ID being discussed here is ID
with a prefix attached to it. (Every process even those invoked passing "" have
a unique ID /* its a number*/ already)
Eg: TEST_process_tests_1, TEST_process_tests_2, TEST_Benchmarks_1 etc. instead
of 1, 2, 3
> Process IDs should be required to be human-readable
> ----------------------------------------------------
>
> Key: MESOS-1457
> URL: https://issues.apache.org/jira/browse/MESOS-1457
> Project: Mesos
> Issue Type: Improvement
> Components: libprocess
> Reporter: Dominic Hamon
> Assignee: Palak Choudhary
> Priority: Minor
>
> When debugging, it's very useful to understand which processes are getting
> timeslices. As such, the human-readable names that can be passed to
> {{ProcessBase}} are incredibly valuable, however they are currently optional.
> If the constructor of {{ProcessBase}} took a mandatory string, every process
> would get a human-readable name and debugging would be much easier.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
