[
https://issues.apache.org/jira/browse/MESOS-6400?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
kasim updated MESOS-6400:
-
Description:
The problem maybe cause by Mesos and Marathon out of sync
[
https://issues.apache.org/jira/browse/MESOS-5222?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Anand Mazumdar updated MESOS-5222:
--
Description: It would be good to add a benchmark for testing writing events
on the persistent
[
https://issues.apache.org/jira/browse/MESOS-5222?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Anand Mazumdar updated MESOS-5222:
--
Summary: Add benchmark for writing events on the persistent connection.
(was: Create a
[
https://issues.apache.org/jira/browse/MESOS-6380?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
haosdent reassigned MESOS-6380:
---
Assignee: haosdent
> mesos-local failed to start without sudo
>
haosdent created MESOS-6399:
---
Summary: Allowed to pass extra envs when launch development
scripts.
Key: MESOS-6399
URL: https://issues.apache.org/jira/browse/MESOS-6399
Project: Mesos
Issue Type: