[jira] [Commented] (MESOS-3377) mesos docker container with container_name as ENV variable

[ https://issues.apache.org/jira/browse/MESOS-3377?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=14733177#comment-14733177 ] haosdent commented on MESOS-3377: - Because you has already test it manually and you just add a env, I

[jira] [Commented] (MESOS-3372) Allow mesos agent attributes to be tokenized in taskInfo

[ https://issues.apache.org/jira/browse/MESOS-3372?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=14732290#comment-14732290 ] Klaus Ma commented on MESOS-3372: - Why not use slave's attributes when launch tasks? {code} ...

[jira] [Commented] (MESOS-3169) FrameworkInfo should only be updated if the re-registration is valid

[ https://issues.apache.org/jira/browse/MESOS-3169?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=14732225#comment-14732225 ] Guangya Liu commented on MESOS-3169: [~jvanremoortere] I think that the fix should be add a checking

[jira] [Comment Edited] (MESOS-3169) FrameworkInfo should only be updated if the re-registration is valid

[ https://issues.apache.org/jira/browse/MESOS-3169?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=14732225#comment-14732225 ] Guangya Liu edited comment on MESOS-3169 at 9/6/15 6:20 AM: [~jvanremoortere]

[jira] [Commented] (MESOS-2875) Add containerId to ResourceUsage to enable QoS controller to target a container

[ https://issues.apache.org/jira/browse/MESOS-2875?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=14732244#comment-14732244 ] Klaus Ma commented on MESOS-2875: - Is there any steps to trigger this case? > Add containerId to

[jira] [Commented] (MESOS-486) TaskInfo should include a 'source' in order to enable getting resource monitoring statistics.

[ https://issues.apache.org/jira/browse/MESOS-486?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=14732280#comment-14732280 ] Klaus Ma commented on MESOS-486: If add {{source}} in TaskInfo, framework will set it to task one by one;

[jira] [Assigned] (MESOS-2930) Allow the Resource Estimator to express over-allocation of revocable resources.

[ https://issues.apache.org/jira/browse/MESOS-2930?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Klaus Ma reassigned MESOS-2930: --- Assignee: Klaus Ma > Allow the Resource Estimator to express over-allocation of revocable >

[jira] [Commented] (MESOS-3372) Allow mesos agent attributes to be tokenized in taskInfo

[ https://issues.apache.org/jira/browse/MESOS-3372?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=14732385#comment-14732385 ] Chad Heuschober commented on MESOS-3372: When last I checked, even though those attributes are

[jira] [Assigned] (MESOS-2845) Command tasks lead to a mixing of revocable / non-revocable cpus and memory within the container.

[ https://issues.apache.org/jira/browse/MESOS-2845?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Klaus Ma reassigned MESOS-2845: --- Assignee: Klaus Ma > Command tasks lead to a mixing of revocable / non-revocable cpus and memory >

[jira] [Commented] (MESOS-3376) mess-slave is not respecting --docker_socket

er.sock > {code} > unfortunately in stdeer I see: > {code} > I0906 09:37:30.637190 1041 exec.cpp:132] Version: 0.23.0 > I0906 09:37:30.641223 1042 exec.cpp:206] Executor registered on slave > 20150906-092832-168470720-5050-376-S0 > Post > http:///var/run/docker.sock/v1.20/

[jira] [Commented] (MESOS-3349) PersistentVolumeTest.AccessPersistentVolume fails when run as root.

[ https://issues.apache.org/jira/browse/MESOS-3349?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=14732390#comment-14732390 ] haosdent commented on MESOS-3349: - The strange thing here is "Device or resource busy" happends when

[jira] [Commented] (MESOS-2913) Scheduler driver should send Call messages to the master

[ https://issues.apache.org/jira/browse/MESOS-2913?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=14732319#comment-14732319 ] Klaus Ma commented on MESOS-2913: - After the patch, should we re-factor protobuf call to delegate to Call?

[jira] [Commented] (MESOS-3363) custom executor's child process intermittently leaks to be a child of slave

[ https://issues.apache.org/jira/browse/MESOS-3363?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=14732359#comment-14732359 ] James DeFelice commented on MESOS-3363: --- No I did not have that namespace enabled when I observed

[jira] [Commented] (MESOS-1615) Create design document for Optimistic Offers

[ https://issues.apache.org/jira/browse/MESOS-1615?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=14732350#comment-14732350 ] Klaus Ma commented on MESOS-1615: - [~bmahler], any documents to share? > Create design document for

[jira] [Commented] (MESOS-3363) custom executor's child process intermittently leaks to be a child of slave

[ https://issues.apache.org/jira/browse/MESOS-3363?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=14732337#comment-14732337 ] Stephan Erb commented on MESOS-3363: Have you tried using the `namespace/pid` isolator? I'd guess it

[jira] [Assigned] (MESOS-2081) Add safety constraints for maintenance primitives.

[ https://issues.apache.org/jira/browse/MESOS-2081?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Klaus Ma reassigned MESOS-2081: --- Assignee: Klaus Ma > Add safety constraints for maintenance primitives. >

[jira] [Commented] (MESOS-3374) Improve High Availability documentation

[ https://issues.apache.org/jira/browse/MESOS-3374?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=14732365#comment-14732365 ] Stephan Erb commented on MESOS-3374: Additional ideas: * Co-location of frameworks with Mesos masters

[jira] [Created] (MESOS-3376) mess-slave is not respecting --docker_socket

:30.637190 1041 exec.cpp:132] Version: 0.23.0 I0906 09:37:30.641223 1042 exec.cpp:206] Executor registered on slave 20150906-092832-168470720-5050-376-S0 Post http:///var/run/docker.sock/v1.20/containers/create?name=mesos-20150906-092832-168470720-5050-376-S0.191ef5b7-ad03-4fbf-b09b-5f5099d6fa6c

[jira] [Commented] (MESOS-3349) PersistentVolumeTest.AccessPersistentVolume fails when run as root.

[ https://issues.apache.org/jira/browse/MESOS-3349?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=14732492#comment-14732492 ] haosdent commented on MESOS-3349: - And further investigation for this, I do similar progress in

[jira] [Commented] (MESOS-3377) mesos docker container with container_name as ENV variable

[ https://issues.apache.org/jira/browse/MESOS-3377?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=14732497#comment-14732497 ] Wojciech Sielski commented on MESOS-3377: - The 2nd approach is much more beautiful :) I just have

[jira] [Commented] (MESOS-3273) EventCall Test Framework is flaky

[ https://issues.apache.org/jira/browse/MESOS-3273?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=14732498#comment-14732498 ] haosdent commented on MESOS-3273: - Your env is Ubuntu or OSX? > EventCall Test Framework is flaky >

[jira] [Commented] (MESOS-3377) mesos docker container with container_name as ENV variable

[ https://issues.apache.org/jira/browse/MESOS-3377?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=14732499#comment-14732499 ] haosdent commented on MESOS-3377: - LoL, need add "-e". > mesos docker container with container_name as

[jira] [Created] (MESOS-3377) mesos docker container with container_name as ENV variable

Wojciech Sielski created MESOS-3377: --- Summary: mesos docker container with container_name as ENV variable Key: MESOS-3377 URL: https://issues.apache.org/jira/browse/MESOS-3377 Project: Mesos

[jira] [Commented] (MESOS-3377) mesos docker container with container_name as ENV variable

[ https://issues.apache.org/jira/browse/MESOS-3377?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=14732461#comment-14732461 ] haosdent commented on MESOS-3377: - {code} mesos doesn't use local docker binary {code} slave have this

[jira] [Commented] (MESOS-3376) mess-slave is not respecting --docker_socket

de} > unfortunately in stdeer I see: > {code} > I0906 09:37:30.637190 1041 exec.cpp:132] Version: 0.23.0 > I0906 09:37:30.641223 1042 exec.cpp:206] Executor registered on slave > 20150906-092832-168470720-5050-376-S0 > Post > http:///var/run/docker.sock/v1.20/containers/cr

[jira] [Commented] (MESOS-3377) mesos docker container with container_name as ENV variable

[ https://issues.apache.org/jira/browse/MESOS-3377?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=14732503#comment-14732503 ] haosdent commented on MESOS-3377: - How about send a patch according

[jira] [Commented] (MESOS-3377) mesos docker container with container_name as ENV variable

[ https://issues.apache.org/jira/browse/MESOS-3377?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=14732508#comment-14732508 ] Wojciech Sielski commented on MESOS-3377: - I'm only afraid of this "test cases" to create, my C++

[jira] [Commented] (MESOS-3377) mesos docker container with container_name as ENV variable

[ https://issues.apache.org/jira/browse/MESOS-3377?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=14732512#comment-14732512 ] Wojciech Sielski commented on MESOS-3377: - I'm only afraid of this "test cases" to create, my C++

[jira] [Issue Comment Deleted] (MESOS-3377) mesos docker container with container_name as ENV variable

[ https://issues.apache.org/jira/browse/MESOS-3377?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Wojciech Sielski updated MESOS-3377: Comment: was deleted (was: I'm only afraid of this "test cases" to create, my C++ skills