[jira] [Commented] (MESOS-6136) Duplicate framework id handling

[ https://issues.apache.org/jira/browse/MESOS-6136?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15680429#comment-15680429 ] Christopher Hunt commented on MESOS-6136: - > Why is reusing the same framework ID important?

[jira] [Commented] (MESOS-6136) Duplicate framework id handling

[ https://issues.apache.org/jira/browse/MESOS-6136?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15679435#comment-15679435 ] Neil Conway commented on MESOS-6136: Mesos prevents a framework *with the same ID* from registering,

[jira] [Commented] (MESOS-6136) Duplicate framework id handling

[ https://issues.apache.org/jira/browse/MESOS-6136?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15679434#comment-15679434 ] Neil Conway commented on MESOS-6136: Why is reusing the same framework ID important? Reusing

[jira] [Commented] (MESOS-6136) Duplicate framework id handling

[ https://issues.apache.org/jira/browse/MESOS-6136?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15525478#comment-15525478 ] Markus Jura commented on MESOS-6136: In other words: If the failover_timeout has expired, Mesos master

[jira] [Commented] (MESOS-6136) Duplicate framework id handling

[ https://issues.apache.org/jira/browse/MESOS-6136?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15485571#comment-15485571 ] Christopher Hunt commented on MESOS-6136: - > Can you clarify which behavior you're referring to

[jira] [Commented] (MESOS-6136) Duplicate framework id handling

[ https://issues.apache.org/jira/browse/MESOS-6136?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15483578#comment-15483578 ] Neil Conway commented on MESOS-6136: Can you clarify which behavior you're referring to when you say

[jira] [Commented] (MESOS-6136) Duplicate framework id handling

[ https://issues.apache.org/jira/browse/MESOS-6136?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15475329#comment-15475329 ] Christopher Hunt commented on MESOS-6136: - Thanks - sounds reasonable. I still think that

[jira] [Commented] (MESOS-6136) Duplicate framework id handling

[ https://issues.apache.org/jira/browse/MESOS-6136?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15473653#comment-15473653 ] Neil Conway commented on MESOS-6136: We might want to distinguish between "framework has been

[jira] [Commented] (MESOS-6136) Duplicate framework id handling

[ https://issues.apache.org/jira/browse/MESOS-6136?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15472407#comment-15472407 ] Christopher Hunt commented on MESOS-6136: - > So in a situation where a framework no longer

[jira] [Commented] (MESOS-6136) Duplicate framework id handling

[ https://issues.apache.org/jira/browse/MESOS-6136?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15472393#comment-15472393 ] Joseph Wu commented on MESOS-6136: -- I'd argue that Mesos is responsible for resource management. So in a

[jira] [Commented] (MESOS-6136) Duplicate framework id handling

[ https://issues.apache.org/jira/browse/MESOS-6136?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15472313#comment-15472313 ] Christopher Hunt commented on MESOS-6136: - Thanks for the reply. However I'm not asking for either

[jira] [Commented] (MESOS-6136) Duplicate framework id handling

[ https://issues.apache.org/jira/browse/MESOS-6136?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15472146#comment-15472146 ] Joseph Wu commented on MESOS-6136: -- Sounds like you're asking for: a) A way to orphan tasks on purpose;