[jira] [Assigned] (MESOS-3270) Fix error GMOCK_CONFIG_CMD in CMake

[ https://issues.apache.org/jira/browse/MESOS-3270?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] haosdent reassigned MESOS-3270: --- Assignee: haosdent Fix error GMOCK_CONFIG_CMD in CMake

[jira] [Commented] (MESOS-2588) Create pre-create hook before a Docker container launches

[ https://issues.apache.org/jira/browse/MESOS-2588?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14698301#comment-14698301 ] haosdent commented on MESOS-2588: - ping [~tnachen] Could you review the patch again? Thank

[jira] [Updated] (MESOS-3270) Fix error GMOCK_CONFIG_CMD in CMake

[ https://issues.apache.org/jira/browse/MESOS-3270?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] haosdent updated MESOS-3270: Description: The GMOCK_CONFIG_CMD don't contains $\{CMAKE_CXX_FLAGS\}, this make gmock build

[jira] [Updated] (MESOS-3270) Fix error GMOCK_CONFIG_CMD in CMake

[ https://issues.apache.org/jira/browse/MESOS-3270?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] haosdent updated MESOS-3270: Description: The GMOCK_CONFIG_CMD don't contains \$\{CMAKE_CXX_FLAGS\}, this make gmock build

[jira] [Created] (MESOS-3270) Fix error GMOCK_CONFIG_CMD in CMake

haosdent created MESOS-3270: --- Summary: Fix error GMOCK_CONFIG_CMD in CMake Key: MESOS-3270 URL: https://issues.apache.org/jira/browse/MESOS-3270 Project: Mesos Issue Type: Bug Reporter

[jira] [Updated] (MESOS-3270) Fix error GMOCK_CONFIG_CMD in CMake

[ https://issues.apache.org/jira/browse/MESOS-3270?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] haosdent updated MESOS-3270: Description: The GMOCK_CONFIG_CMD don't contains {code}${CMAKE_CXX_FLAGS}{code}, this make gmock build

[jira] [Updated] (MESOS-3270) Fix error GMOCK_CONFIG_CMD in CMake

[ https://issues.apache.org/jira/browse/MESOS-3270?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] haosdent updated MESOS-3270: Description: The GMOCK_CONFIG_CMD don't contains ${CMAKE_CXX_FLAGS}, this make gmock build

[jira] [Created] (MESOS-3247) Add missing unimplemented.hpp to windows specific OS code

haosdent created MESOS-3247: --- Summary: Add missing unimplemented.hpp to windows specific OS code Key: MESOS-3247 URL: https://issues.apache.org/jira/browse/MESOS-3247 Project: Mesos Issue Type

[jira] [Commented] (MESOS-3218) Enhance the bootstrap script

[ https://issues.apache.org/jira/browse/MESOS-3218?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14660100#comment-14660100 ] gyliu commented on MESOS-3218: -- The bootstrap is only for developers and it is not suggested

[jira] [Commented] (MESOS-2337) __init__.py not getting installed in $PREFIX/lib/pythonX.Y/site-packages/mesos

[ https://issues.apache.org/jira/browse/MESOS-2337?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14653859#comment-14653859 ] haosdent commented on MESOS-2337: - Refrence openstack, them have /usr/lib/python2.7/dist

[jira] [Comment Edited] (MESOS-3141) Compiler warning when mocking function type has an enum return type.

[ https://issues.apache.org/jira/browse/MESOS-3141?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14645670#comment-14645670 ] haosdent edited comment on MESOS-3141 at 8/6/15 7:56 AM: - I also

[jira] [Commented] (MESOS-3126) Building mesos.jar, uses old javadoc plugin in maven.

[ https://issues.apache.org/jira/browse/MESOS-3126?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14642756#comment-14642756 ] haosdent commented on MESOS-3126: - You could try this docker image. https

[jira] [Commented] (MESOS-3144) Update Homebrew formula for Mesos (Mac OSX)

[ https://issues.apache.org/jira/browse/MESOS-3144?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14643754#comment-14643754 ] haosdent commented on MESOS-3144: - Yes, only need update sha256 in your pull request

[jira] [Commented] (MESOS-3141) Compiler warning when mocking function type has an enum return type.

[ https://issues.apache.org/jira/browse/MESOS-3141?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14643768#comment-14643768 ] haosdent commented on MESOS-3141: - [~mcypark] Seems rbt use git diff to generate patch

[jira] [Assigned] (MESOS-2960) Configure DiscoveryInfo and Visibility per port

[ https://issues.apache.org/jira/browse/MESOS-2960?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] haosdent reassigned MESOS-2960: --- Assignee: haosdent Configure DiscoveryInfo and Visibility per port

[jira] [Commented] (MESOS-3081) Default configuration of google logging

[ https://issues.apache.org/jira/browse/MESOS-3081?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14642528#comment-14642528 ] haosdent commented on MESOS-3081: - This ticket seems duplicated with https

[jira] [Commented] (MESOS-3057) Mesos web ui sorting by Id results in non-intuitive order.

[ https://issues.apache.org/jira/browse/MESOS-3057?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14642550#comment-14642550 ] haosdent commented on MESOS-3057: - I think this ticket is not a problem. The task id maybe

[jira] [Commented] (MESOS-3057) Mesos web ui sorting by Id results in non-intuitive order.

[ https://issues.apache.org/jira/browse/MESOS-3057?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14642556#comment-14642556 ] haosdent commented on MESOS-3057: - [~Croseborough] Could you give your framework name

[jira] [Commented] (MESOS-527) Command Executors do not have Executor IDs in the master.

[ https://issues.apache.org/jira/browse/MESOS-527?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14643813#comment-14643813 ] haosdent commented on MESOS-527: Sorry for misunderstand this ticket #_#. Let me update

[jira] [Created] (MESOS-3149) Use setuptools to install python cli package

haosdent created MESOS-3149: --- Summary: Use setuptools to install python cli package Key: MESOS-3149 URL: https://issues.apache.org/jira/browse/MESOS-3149 Project: Mesos Issue Type: Task

[jira] [Commented] (MESOS-3139) Incorporate CMake into standard documentation

[ https://issues.apache.org/jira/browse/MESOS-3139?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14642028#comment-14642028 ] haosdent commented on MESOS-3139: - Got it. Looking forward CMake and running mesos

[jira] [Commented] (MESOS-3111) Executor Process gets killed before executor_shutdown_grace_period

[ https://issues.apache.org/jira/browse/MESOS-3111?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14642202#comment-14642202 ] haosdent commented on MESOS-3111: - {code} class ShutdownProcess : public

[jira] [Commented] (MESOS-3141) Compiler warning when mocking function type has an enum return type.

[ https://issues.apache.org/jira/browse/MESOS-3141?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14642221#comment-14642221 ] haosdent commented on MESOS-3141: - I update gmock to 1.7.0 Compiler warning when mocking

[jira] [Assigned] (MESOS-3111) Executor Process gets killed before executor_shutdown_grace_period

[ https://issues.apache.org/jira/browse/MESOS-3111?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] haosdent reassigned MESOS-3111: --- Assignee: haosdent Executor Process gets killed before executor_shutdown_grace_period

[jira] [Commented] (MESOS-3141) Compiler warning when mocking function type has an enum return type.

[ https://issues.apache.org/jira/browse/MESOS-3141?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14642241#comment-14642241 ] haosdent commented on MESOS-3141: - LoL. [~mcypark] Seems review board not support binary

[jira] [Commented] (MESOS-3091) Failed to build scheduler using C++ API: google/protobuf/stubs/common.h: No such file or directory

[ https://issues.apache.org/jira/browse/MESOS-3091?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14642343#comment-14642343 ] haosdent commented on MESOS-3091: - I think you need install protobuf 2.5.0 manually. Mesos

[jira] [Commented] (MESOS-3087) Typos in oversubscription doc

[ https://issues.apache.org/jira/browse/MESOS-3087?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14642319#comment-14642319 ] haosdent commented on MESOS-3087: - Patch: https://reviews.apache.org/r/36839/ Typos

[jira] [Assigned] (MESOS-3087) Typos in oversubscription doc

[ https://issues.apache.org/jira/browse/MESOS-3087?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] haosdent reassigned MESOS-3087: --- Assignee: haosdent Typos in oversubscription doc

[jira] [Comment Edited] (MESOS-3091) Failed to build scheduler using C++ API: google/protobuf/stubs/common.h: No such file or directory

[ https://issues.apache.org/jira/browse/MESOS-3091?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14642343#comment-14642343 ] haosdent edited comment on MESOS-3091 at 7/27/15 6:39 AM: -- I

[jira] [Commented] (MESOS-3126) Building mesos.jar, uses old javadoc plugin in maven.

[ https://issues.apache.org/jira/browse/MESOS-3126?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14642056#comment-14642056 ] haosdent commented on MESOS-3126: - {code} [ERROR] Java heap space - [Help 1] [ERROR

[jira] [Commented] (MESOS-3126) Building mesos.jar, uses old javadoc plugin in maven.

[ https://issues.apache.org/jira/browse/MESOS-3126?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14642377#comment-14642377 ] haosdent commented on MESOS-3126: - [~hbogert] I could build it successfully. Is it because

[jira] [Assigned] (MESOS-3104) Add an endpoint that exposes component flags.

[ https://issues.apache.org/jira/browse/MESOS-3104?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] haosdent reassigned MESOS-3104: --- Assignee: haosdent Add an endpoint that exposes component flags

[jira] [Commented] (MESOS-3139) Incorporate CMake into standard documentation

[ https://issues.apache.org/jira/browse/MESOS-3139?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14640884#comment-14640884 ] haosdent commented on MESOS-3139: - @hausdorff Got it thank you. Incorporate CMake

[jira] [Comment Edited] (MESOS-3098) Implement WindowsContainerizer and WindowsDockerContainerizer

[ https://issues.apache.org/jira/browse/MESOS-3098?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14641595#comment-14641595 ] haosdent edited comment on MESOS-3098 at 7/25/15 1:55 PM

[jira] [Commented] (MESOS-527) Command Executors do not have Executor IDs in the master.

[ https://issues.apache.org/jira/browse/MESOS-527?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14641651#comment-14641651 ] haosdent commented on MESOS-527: Patch: https://reviews.apache.org/r/36814/ I use executor

[jira] [Commented] (MESOS-2411) trailing slash in work_dir causes sandbox link issues

[ https://issues.apache.org/jira/browse/MESOS-2411?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14641494#comment-14641494 ] haosdent commented on MESOS-2411: - Could not reproduce this problem in 0.23. Please check

[jira] [Commented] (MESOS-3040) Update submitting-a-patch.md

[ https://issues.apache.org/jira/browse/MESOS-3040?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14625750#comment-14625750 ] gyliu commented on MESOS-3040: -- The step 7 in submitting a patch is: Make your changes

[jira] [Created] (MESOS-3040) Update submitting-a-patch.md

gyliu created MESOS-3040: Summary: Update submitting-a-patch.md Key: MESOS-3040 URL: https://issues.apache.org/jira/browse/MESOS-3040 Project: Mesos Issue Type: Documentation Components

[jira] [Updated] (MESOS-3059) Allow http endpoint to dynamically change the slave attributes

[ https://issues.apache.org/jira/browse/MESOS-3059?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nitin updated MESOS-3059: - Description: This is well understood that - changing the attributes dynamically is not safe without a restart

[jira] [Commented] (MESOS-3023) Factoring out the pattern for URL generation

[ https://issues.apache.org/jira/browse/MESOS-3023?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14630891#comment-14630891 ] haosdent commented on MESOS-3023: - Hi, [~klaus1982] Thank you for your patch, I also write

[jira] [Created] (MESOS-3091) Failed to build scheduler using C++ API: google/protobuf/stubs/common.h: No such file or directory

Mohamed created MESOS-3091: -- Summary: Failed to build scheduler using C++ API: google/protobuf/stubs/common.h: No such file or directory Key: MESOS-3091 URL: https://issues.apache.org/jira/browse/MESOS-3091

[jira] [Commented] (MESOS-3706) Tasks stuck in staging.

[ https://issues.apache.org/jira/browse/MESOS-3706?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=14966818#comment-14966818 ] haosdent commented on MESOS-3706: - As you stay, stdout and stderr are empty. Could you try use strace

[jira] [Commented] (MESOS-1582) Improve build time.

[ https://issues.apache.org/jira/browse/MESOS-1582?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=14972825#comment-14972825 ] haosdent commented on MESOS-1582: - Add the missing libprocess build time for every object: http

[jira] [Commented] (MESOS-3793) Cannot start mesos local on a Debian GNU/Linux 8 docker machine

[ https://issues.apache.org/jira/browse/MESOS-3793?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=14971183#comment-14971183 ] haosdent commented on MESOS-3793: - Please add --launcher=posix or mount cgroup as rw when launch docker

[jira] [Commented] (MESOS-1582) Improve build time.

[ https://issues.apache.org/jira/browse/MESOS-1582?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=14973107#comment-14973107 ] haosdent commented on MESOS-1582: - I found most time are spent in #include files. For example, #include

[jira] [Commented] (MESOS-3506) Build instructions for CentOS 6.6 should include `sudo yum update`

[ https://issues.apache.org/jira/browse/MESOS-3506?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=14971413#comment-14971413 ] haosdent commented on MESOS-3506: - I test this in CentOS 6 docker image, seem don't contains default

[jira] [Commented] (MESOS-3545) Investigate restoring tasks/executors after machine reboot.

[ https://issues.apache.org/jira/browse/MESOS-3545?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=14969497#comment-14969497 ] Megha commented on MESOS-3545: -- Here's the first draft of the design for Persistent Tasks. Looking forward

[jira] [Commented] (MESOS-3787) As a developer, I'd like to be able to expand environment variables through the Docker executor.

[ https://issues.apache.org/jira/browse/MESOS-3787?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=14975836#comment-14975836 ] haosdent commented on MESOS-3787: - Add a test case to verify above proposal could works. https

[jira] [Commented] (MESOS-3787) As a developer, I'd like to be able to expand environment variables through the Docker executor.

[ https://issues.apache.org/jira/browse/MESOS-3787?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=14975486#comment-14975486 ] haosdent commented on MESOS-3787: - I think we just need run it use the shell way, not need extra variables

[jira] [Comment Edited] (MESOS-3787) As a developer, I'd like to be able to expand environment variables through the Docker executor.

[ https://issues.apache.org/jira/browse/MESOS-3787?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=14975486#comment-14975486 ] haosdent edited comment on MESOS-3787 at 10/27/15 1:28 AM: --- I think we just need

[jira] [Comment Edited] (MESOS-2635) Web UI Display Bug when starting lots of tasks with small cpu value

[ https://issues.apache.org/jira/browse/MESOS-2635?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=14975492#comment-14975492 ] haosdent edited comment on MESOS-2635 at 10/27/15 1:34 AM: --- Seems I could

[jira] [Commented] (MESOS-2635) Web UI Display Bug when starting lots of tasks with small cpu value

[ https://issues.apache.org/jira/browse/MESOS-2635?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=14975492#comment-14975492 ] haosdent commented on MESOS-2635: - Seems I could not found values depends on metrics in frameworks.html

[jira] [Commented] (MESOS-3599) COMMAND health checks with marathon running in slave context broken

[ https://issues.apache.org/jira/browse/MESOS-3599?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=14976671#comment-14976671 ] haosdent commented on MESOS-3599: - As you see, I expose it as $MESOS_CONTAINER_NAME in https

[jira] [Commented] (MESOS-3599) COMMAND health checks with marathon running in slave context broken

[ https://issues.apache.org/jira/browse/MESOS-3599?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=14976675#comment-14976675 ] haosdent commented on MESOS-3599: - I think we could ping [~tnachen] again to review the patch

[jira] [Commented] (MESOS-3216) virtual memory exhausted:: Cannot allocate memory

[ https://issues.apache.org/jira/browse/MESOS-3216?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=14976728#comment-14976728 ] haosdent commented on MESOS-3216: - hmm, last time I try to build Mesos in a virtual machine which only

[jira] [Commented] (MESOS-3809) Expose advertise_ip and advertise_port as command line options in mesos slave

[ https://issues.apache.org/jira/browse/MESOS-3809?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=14977853#comment-14977853 ] haosdent commented on MESOS-3809: - +1 please also update https://github.com/apache/mesos/blob/master/docs

[jira] [Created] (MESOS-3803) system requirenments on debian

shiyao.ma created MESOS-3803: Summary: system requirenments on debian Key: MESOS-3803 URL: https://issues.apache.org/jira/browse/MESOS-3803 Project: Mesos Issue Type: Documentation

[jira] [Commented] (MESOS-3224) Create a Mesos Contributor Newbie Guide

[ https://issues.apache.org/jira/browse/MESOS-3224?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=14973318#comment-14973318 ] haosdent commented on MESOS-3224: - {noformat} NewbieContributionOverview.jpg {noformat} Seems could

[jira] [Commented] (MESOS-3224) Create a Mesos Contributor Newbie Guide

[ https://issues.apache.org/jira/browse/MESOS-3224?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=14966771#comment-14966771 ] haosdent commented on MESOS-3224: - Move to github pull request or review board? > Create a Me

[jira] [Commented] (MESOS-3787) As a developer, I'd like to be able to expand environment variables through the Docker executor.

[ https://issues.apache.org/jira/browse/MESOS-3787?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=14968410#comment-14968410 ] haosdent commented on MESOS-3787: - For CommandInfo, I think Mesos already set them when start a docker

[jira] [Commented] (MESOS-3870) Prevent out-of-order libprocess message delivery

[ https://issues.apache.org/jira/browse/MESOS-3870?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=14998837#comment-14998837 ] haosdent commented on MESOS-3870: - Ohoh, got it. Thank you for explanation. > Prevent out-of-or

[jira] [Comment Edited] (MESOS-3870) Prevent out-of-order libprocess message delivery

[ https://issues.apache.org/jira/browse/MESOS-3870?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=14998700#comment-14998700 ] haosdent edited comment on MESOS-3870 at 11/10/15 3:09 PM: --- Suppose a Process

[jira] [Commented] (MESOS-3870) Prevent out-of-order libprocess message delivery

[ https://issues.apache.org/jira/browse/MESOS-3870?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=14998884#comment-14998884 ] haosdent commented on MESOS-3870: - I think have another case make same Process run in different thread

[jira] [Commented] (MESOS-3870) Prevent out-of-order libprocess message delivery

[ https://issues.apache.org/jira/browse/MESOS-3870?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=14998700#comment-14998700 ] haosdent commented on MESOS-3870: - Suppose a Process enqueue to runq twice(Or impossible, seems I could

[jira] [Commented] (MESOS-3870) Prevent out-of-order libprocess message delivery

[ https://issues.apache.org/jira/browse/MESOS-3870?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=14998757#comment-14998757 ] haosdent commented on MESOS-3870: - Yes, but ProcessBase.state don't have violate. I am not sure

[jira] [Commented] (MESOS-3870) Prevent out-of-order libprocess message delivery

[ https://issues.apache.org/jira/browse/MESOS-3870?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=14998686#comment-14998686 ] haosdent commented on MESOS-3870: - I think ProcessManager could dequeue same Process in different work

[jira] [Commented] (MESOS-3870) Prevent out-of-order libprocess message delivery

[ https://issues.apache.org/jira/browse/MESOS-3870?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=14998730#comment-14998730 ] haosdent commented on MESOS-3870: - Yes, but I think it still could be enqueue twice? Because

[jira] [Comment Edited] (MESOS-3870) Prevent out-of-order libprocess message delivery

[ https://issues.apache.org/jira/browse/MESOS-3870?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=14998884#comment-14998884 ] haosdent edited comment on MESOS-3870 at 11/10/15 4:49 PM: --- I think have another

[jira] [Commented] (MESOS-3870) Prevent out-of-order libprocess message delivery

[ https://issues.apache.org/jira/browse/MESOS-3870?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=14998971#comment-14998971 ] haosdent commented on MESOS-3870: - ... Looks not possible. Only after consume event A, ProcessBase.state

[jira] [Assigned] (MESOS-3216) virtual memory exhausted:: Cannot allocate memory

[ https://issues.apache.org/jira/browse/MESOS-3216?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] haosdent reassigned MESOS-3216: --- Assignee: haosdent > virtual memory exhausted:: Cannot allocate mem

[jira] [Commented] (MESOS-3827) Improve compilation speed of GMock tests

[ https://issues.apache.org/jira/browse/MESOS-3827?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=14995690#comment-14995690 ] haosdent commented on MESOS-3827: - Sounds great! > Improve compilation speed of GMock te

[jira] [Commented] (MESOS-3906) post-reviews.py does not correctly upload binary files

[ https://issues.apache.org/jira/browse/MESOS-3906?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15003432#comment-15003432 ] haosdent commented on MESOS-3906: - Hi, this is not post-reviews.py problem. Please apply this https

[jira] [Commented] (MESOS-3915) Upgrade vendored Boost to 1.59

[ https://issues.apache.org/jira/browse/MESOS-3915?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15004260#comment-15004260 ] haosdent commented on MESOS-3915: - +1 > Upgrade vendored Boost to 1

[jira] [Comment Edited] (MESOS-3928) ROOT tests fail on Mesos 0.26 on Ubuntu/CentOS

[ https://issues.apache.org/jira/browse/MESOS-3928?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15005726#comment-15005726 ] haosdent edited comment on MESOS-3928 at 11/15/15 4:55 AM: --- Do you try disable

[jira] [Commented] (MESOS-3928) ROOT tests fail on Mesos 0.26 on Ubuntu/CentOS

[ https://issues.apache.org/jira/browse/MESOS-3928?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15005726#comment-15005726 ] haosdent commented on MESOS-3928: - Do you try disable iptables and change you localhost to a accessible ip

[jira] [Commented] (MESOS-2262) Adding GPGPU resource into Mesos, so we can know if any GPU/Heterogeneous resource are available from slave

[ https://issues.apache.org/jira/browse/MESOS-2262?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15005880#comment-15005880 ] haosdent commented on MESOS-2262: - I think you could use the docker image provided by Nvidia https

[jira] [Issue Comment Deleted] (MESOS-3815) docker executor not works when SSL enable

[ https://issues.apache.org/jira/browse/MESOS-3815?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] haosdent updated MESOS-3815: Comment: was deleted (was: Patch: https://reviews.apache.org/r/39944/ https://reviews.apache.org/r/39945

[jira] [Commented] (MESOS-3815) docker executor not works when SSL enable

[ https://issues.apache.org/jira/browse/MESOS-3815?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15007758#comment-15007758 ] haosdent commented on MESOS-3815: - Let me delete my comment. > docker executor not works when SSL ena

[jira] [Created] (MESOS-3901) Enable Mesos to be able know when it is hosted behind a proxy with a URL prefix

Harpreet created MESOS-3901: --- Summary: Enable Mesos to be able know when it is hosted behind a proxy with a URL prefix Key: MESOS-3901 URL: https://issues.apache.org/jira/browse/MESOS-3901 Project: Mesos

[jira] [Commented] (MESOS-3851) Investigate recent crashes in Command Executor

[ https://issues.apache.org/jira/browse/MESOS-3851?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=14998453#comment-14998453 ] haosdent commented on MESOS-3851: - In the error log, registered and launchTaks have different thread id

[jira] [Commented] (MESOS-2376) Allow libprocess ip and port to be configured

[ https://issues.apache.org/jira/browse/MESOS-2376?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=14998645#comment-14998645 ] Dimitri commented on MESOS-2376: [~hfaran] What do you mean ? I am trying to set the mesos binding ip

[jira] [Commented] (MESOS-3870) Prevent out-of-order libprocess message delivery

[ https://issues.apache.org/jira/browse/MESOS-3870?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=14998605#comment-14998605 ] haosdent commented on MESOS-3870: - I think although send could be ordered when only have a connection

[jira] [Created] (MESOS-3815) os environment variables not passing to docker-executor environment variables correctly

haosdent created MESOS-3815: --- Summary: os environment variables not passing to docker-executor environment variables correctly Key: MESOS-3815 URL: https://issues.apache.org/jira/browse/MESOS-3815 Project

[jira] [Assigned] (MESOS-3815) os environment variables not passing to docker-executor environment variables correctly

[ https://issues.apache.org/jira/browse/MESOS-3815?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] haosdent reassigned MESOS-3815: --- Assignee: haosdent > os environment variables not passing to docker-executor environment variab

[jira] [Commented] (MESOS-3740) LIBPROCESS_IP not passed to Docker containers

[ https://issues.apache.org/jira/browse/MESOS-3740?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=14984315#comment-14984315 ] haosdent commented on MESOS-3740: - Hi, [~cmaloney] A little thing I could not understand here, in which

[jira] [Created] (MESOS-3817) Rename offers to outstanding offers

haosdent created MESOS-3817: --- Summary: Rename offers to outstanding offers Key: MESOS-3817 URL: https://issues.apache.org/jira/browse/MESOS-3817 Project: Mesos Issue Type: Bug Components

[jira] [Commented] (MESOS-2960) Configure DiscoveryInfo and Visibility per port

[ https://issues.apache.org/jira/browse/MESOS-2960?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=14985342#comment-14985342 ] haosdent commented on MESOS-2960: - ping [~adam-mesos][~mcypark] Could you help review the patch

[jira] [Commented] (MESOS-3822) Cannot specify multiple masters when slave start up

[ https://issues.apache.org/jira/browse/MESOS-3822?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=14986760#comment-14986760 ] haosdent commented on MESOS-3822: - I think this is just because document not sync with code. Need change

[jira] [Commented] (MESOS-3821) DOCKER_HOST does not work well with --executor_environment_variables

[ https://issues.apache.org/jira/browse/MESOS-3821?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=14986758#comment-14986758 ] haosdent commented on MESOS-3821: - hmm, let me submit a patch to this later. > DOCKER_HOST does not w

[jira] [Assigned] (MESOS-3821) DOCKER_HOST does not work well with --executor_environment_variables

[ https://issues.apache.org/jira/browse/MESOS-3821?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] haosdent reassigned MESOS-3821: --- Assignee: haosdent > DOCKER_HOST does not work well with --executor_environment_variab

[jira] [Updated] (MESOS-3822) Cannot specify multiple masters when slave start up

[ https://issues.apache.org/jira/browse/MESOS-3822?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] haosdent updated MESOS-3822: Labels: docuentation (was: ) > Cannot specify multiple masters when slave start

[jira] [Commented] (MESOS-3829) Error on gracefully shutdown task

[ https://issues.apache.org/jira/browse/MESOS-3829?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=14990959#comment-14990959 ] haosdent commented on MESOS-3829: - DOCKER_STOP_TIMEOUT is used for http://docs.docker.com/engine

[jira] [Commented] (MESOS-3829) Error on gracefully shutdown task

[ https://issues.apache.org/jira/browse/MESOS-3829?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=14990960#comment-14990960 ] haosdent commented on MESOS-3829: - Maybe because of this https://github.com/docker/docker/pull/3240 ? I

[jira] [Commented] (MESOS-3829) Error on gracefully shutdown task

[ https://issues.apache.org/jira/browse/MESOS-3829?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=14991926#comment-14991926 ] haosdent commented on MESOS-3829: - Looks correct. > Error on gracefully shutdown t

[jira] [Updated] (MESOS-3462) Containerization issues with mesos running on CoreOS

[ https://issues.apache.org/jira/browse/MESOS-3462?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] haosdent updated MESOS-3462: Assignee: (was: haosdent) > Containerization issues with mesos running on Cor

[jira] [Commented] (MESOS-809) External control of the ip that Mesos components publish to zookeeper

[ https://issues.apache.org/jira/browse/MESOS-809?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=14994998#comment-14994998 ] Dimitri commented on MESOS-809: --- Sorry for interupting. I am trying hard to make mesos bind to a local

[jira] [Commented] (MESOS-2587) libprocess should allow configuration of ip/port separate from the ones it binds to

[ https://issues.apache.org/jira/browse/MESOS-2587?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=14994999#comment-14994999 ] Dimitri commented on MESOS-2587: Sorry for interupting. I am trying hard to make mesos bind to a local

[jira] [Commented] (MESOS-3815) docker executor not works when SSL enable

[ https://issues.apache.org/jira/browse/MESOS-3815?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=14995123#comment-14995123 ] haosdent commented on MESOS-3815: - Use exactly environment variables. https://reviews.apache.org/r/40046

[jira] [Commented] (MESOS-3787) As a developer, I'd like to be able to expand environment variables through the Docker executor.

[ https://issues.apache.org/jira/browse/MESOS-3787?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=14988693#comment-14988693 ] haosdent commented on MESOS-3787: - Because have two process? > As a developer, I'd like to be a

[jira] [Commented] (MESOS-3787) As a developer, I'd like to be able to expand environment variables through the Docker executor.

[ https://issues.apache.org/jira/browse/MESOS-3787?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=14988726#comment-14988726 ] haosdent commented on MESOS-3787: - I notice the second item in you post about "ps" have al

<    5   6   7   8   9   10   11   12   13   14   >