[jira] [Updated] (MESOS-6400) Not able to remove Orphan Tasks
[
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://github.com/mesosphere/marathon/issues/616
When I found Orphan Tasks happen, I
1. restart marathon
2. marathon do not sync Orphan Tasks, but start new tasks.
3. but Orphan Tasks still taked the resource, have to delete them.
4. all Orphan Tasks in under `ef169d8a-24fc-41d1-8b0d-c67718937a48-`
curl -XGET `http://c196:5050/master/frameworks` shows that framework is
`unregistered_frameworks`
{code}
{
"frameworks": [
.
],
"completed_frameworks": [ ],
"unregistered_frameworks": [
"ef169d8a-24fc-41d1-8b0d-c67718937a48-",
"ef169d8a-24fc-41d1-8b0d-c67718937a48-",
"ef169d8a-24fc-41d1-8b0d-c67718937a48-"
]
}
{code}
5.Try {code}curl -XPOST http://c196:5050/master/teardown -d
'frameworkId=ef169d8a-24fc-41d1-8b0d-c67718937a48-' {code}
， but get `No framework found with specified ID`
So I have no idea to delete Orphan Tasks
was:
The problem maybe cause by Mesos and Marathon out of sync
https://github.com/mesosphere/marathon/issues/616
When I found Orphan Tasks happen, I
1. restart marathon
2. marathon do not sync Orphan Tasks, but start new tasks.
3. curl -XGET `http://c196:5050/master/frameworks` :
{code}
{
"frameworks": [
.
],
"completed_frameworks": [ ],
"unregistered_frameworks": [
"ef169d8a-24fc-41d1-8b0d-c67718937a48-",
"ef169d8a-24fc-41d1-8b0d-c67718937a48-",
"ef169d8a-24fc-41d1-8b0d-c67718937a48-"
]
}
{code}
all Orphan Tasks in under `ef169d8a-24fc-41d1-8b0d-c67718937a48-`
5.Try {code}curl -XPOST http://c196:5050/master/teardown -d
'frameworkId=ef169d8a-24fc-41d1-8b0d-c67718937a48-' {code}
， but get `No framework found with specified ID`
So I have no idea to delete Orphan Tasks
> Not able to remove Orphan Tasks
> ---
>
> Key: MESOS-6400
> URL: https://issues.apache.org/jira/browse/MESOS-6400
> Project: Mesos
> Issue Type: Bug
>Affects Versions: 1.0.1
> Environment: centos 7 x64
>Reporter: kasim
>
> The problem maybe cause by Mesos and Marathon out of sync
> https://github.com/mesosphere/marathon/issues/616
> When I found Orphan Tasks happen, I
> 1. restart marathon
> 2. marathon do not sync Orphan Tasks, but start new tasks.
> 3. but Orphan Tasks still taked the resource, have to delete them.
> 4. all Orphan Tasks in under `ef169d8a-24fc-41d1-8b0d-c67718937a48-`
> curl -XGET `http://c196:5050/master/frameworks` shows that framework is
> `unregistered_frameworks`
> {code}
> {
> "frameworks": [
> .
> ],
> "completed_frameworks": [ ],
> "unregistered_frameworks": [
> "ef169d8a-24fc-41d1-8b0d-c67718937a48-",
> "ef169d8a-24fc-41d1-8b0d-c67718937a48-",
> "ef169d8a-24fc-41d1-8b0d-c67718937a48-"
> ]
> }
> {code}
> 5.Try {code}curl -XPOST http://c196:5050/master/teardown -d
> 'frameworkId=ef169d8a-24fc-41d1-8b0d-c67718937a48-' {code}
> ， but get `No framework found with specified ID`
> So I have no idea to delete Orphan Tasks
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (MESOS-5222) Add benchmark for writing events on the persistent connection.
[ 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 connection for HTTP frameworks wrt driver based frameworks. The benchmark can be as simple as trying to stream generated reconciliation status update events on the persistent connection between the master and the scheduler. (was: It would be good to add a benchmark for scale testing the HTTP frameworks wrt driver based frameworks. The benchmark can be as simple as trying to launch N tasks (parameterized) with the old/new API. We can then focus on fixing performance issues that we find as a result of this exercise.) > Add benchmark for writing events on the persistent connection. > -- > > Key: MESOS-5222 > URL: https://issues.apache.org/jira/browse/MESOS-5222 > Project: Mesos > Issue Type: Task >Reporter: Anand Mazumdar >Assignee: Anand Mazumdar > Labels: mesosphere > Fix For: 1.0.0 > > > It would be good to add a benchmark for testing writing events on the > persistent connection for HTTP frameworks wrt driver based frameworks. The > benchmark can be as simple as trying to stream generated reconciliation > status update events on the persistent connection between the master and the > scheduler. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (MESOS-5222) Add benchmark for writing events on the persistent connection.
[ 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 benchmark for scale testing HTTP frameworks) > Add benchmark for writing events on the persistent connection. > -- > > Key: MESOS-5222 > URL: https://issues.apache.org/jira/browse/MESOS-5222 > Project: Mesos > Issue Type: Task >Reporter: Anand Mazumdar >Assignee: Anand Mazumdar > Labels: mesosphere > Fix For: 1.0.0 > > > It would be good to add a benchmark for scale testing the HTTP frameworks wrt > driver based frameworks. The benchmark can be as simple as trying to launch N > tasks (parameterized) with the old/new API. We can then focus on fixing > performance issues that we find as a result of this exercise. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Assigned] (MESOS-6380) mesos-local failed to start without sudo
[
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
>
>
> Key: MESOS-6380
> URL: https://issues.apache.org/jira/browse/MESOS-6380
> Project: Mesos
> Issue Type: Bug
>Reporter: haosdent
>Assignee: haosdent
>
> Got this error when launch mesos-local without sudo
> {code}
> message: 'Failed to launch container: Failed to make the containerizer
> runtime directory
> '/var/run/mesos/containers/f2d6947f-2916-4f1a-90dc-3d137b360b9c': Permission
> denied; Abnormal executor termination: unknown container'
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Created] (MESOS-6399) Allowed to pass extra envs when launch development scripts.
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: Improvement
Reporter: haosdent
Assignee: haosdent
Now set envs before launch developement scripts would not effective.
{code}
MESOS_WORK_DIR=/tmp/mesos/bar ./bin/mesos-local.sh
Flags
... --work_dir=/tmp/mesos
{code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
