Thanks for the responses. Filed a ticket for this:
- https://issues.apache.org/jira/browse/MESOS-4737
- Erik
On Mon, Feb 22, 2016 at 1:23 PM, Sargun Dhillon wrote:
> As someone who has been there and back again (Reusing task-IDs, and
> realizing it's a terrible idea), I'd
As someone who has been there and back again (Reusing task-IDs, and
realizing it's a terrible idea), I'd put some advise in the docs +
mesos.proto to compose task IDs from GUIDs, and add that it's
dangerous to reuse them.
I would advocate for a mechanism to prevent the usage of non
>> time reconciling which instance of the task is on which node and in
>>>> which status, since it expects only one instance to exist at a time.
>>>> You may be better off using a fixed taskId prefix and appending an
>>>> incrementing instance/trial numb
an
>>> incrementing instance/trial number so that each run gets a uniqueId.
>>> Also note that taskIds only need to be unique within a single
>>> frameworkId, so don't worry about conflicting with other frameworks.
>>> TL;DR: I wouldn't recomme
as hard to monitor that you can start again a
>> task than get a mechanism to know it’s ID.
>>
>>
>>
>> On 10 Jul 2015, at 19:14, Jie Yu >> <mailto:yujie@gmail.com>> wrote:
>>>
>>> Re-using Task IDs is definitely not e
e assume Task ID is unique. So I probably
won't risk that.
On Fri, Jul 10, 2015 at 10:06 AM, Sargun Dhillon mailto:sar...@sargun.me>> wrote:
Is reusing Task IDs good behaviour? Let's say that I have some
singleton task - I'll call it a monitoring serv
t; the Mesos code assume Task ID is unique. So I probably won't risk that.
>
>
> On Fri, Jul 10, 2015 at 10:06 AM, Sargun Dhillon wrote:
>
>> Is reusing Task IDs good behaviour? Let's say that I have some
>> singleton task - I'll call it a monitoring service. I
efinitely not encouraged. As far as I know, many of the
> Mesos code assume Task ID is unique. So I probably won't risk that.
>
>
> On Fri, Jul 10, 2015 at 10:06 AM, Sargun Dhillon <mailto:sar...@sargun.me>> wrote:
> Is reusing Task IDs good behaviour? Let's say th
Re-using Task IDs is definitely not encouraged. As far as I know, many of
the Mesos code assume Task ID is unique. So I probably won't risk that.
On Fri, Jul 10, 2015 at 10:06 AM, Sargun Dhillon wrote:
> Is reusing Task IDs good behaviour? Let's say that I have some
> singl
argun Dhillon" wrote:
>Is reusing Task IDs good behaviour? Let's say that I have some
>singleton task - I'll call it a monitoring service. It's always going
>to be the same process, doing the same thing, and there will only ever
>be one around (per instance of a fra
Is reusing Task IDs good behaviour? Let's say that I have some
singleton task - I'll call it a monitoring service. It's always going
to be the same process, doing the same thing, and there will only ever
be one around (per instance of a framework). Reading the protobuf doc,
11 matches
Mail list logo
