[jira] [Updated] (MESOS-3558) Make the CommandExecutor use the Executor Library speaking HTTP
[
https://issues.apache.org/jira/browse/MESOS-3558?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Vinod Kone updated MESOS-3558:
--
Story Points: 13
> Make the CommandExecutor use the Executor Library speaking HTTP
> ---
>
> Key: MESOS-3558
> URL: https://issues.apache.org/jira/browse/MESOS-3558
> Project: Mesos
> Issue Type: Task
>Reporter: Anand Mazumdar
>Assignee: Qian Zhang
> Labels: mesosphere
>
> Instead of using the {{MesosExecutorDriver}} , we should make the
> {{CommandExecutor}} in {{src/launcher/executor.cpp}} use the new Executor
> HTTP Library that we create in {{MESOS-3550}}.
> This would act as a good validation of the {{HTTP API}} implementation.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Created] (MESOS-4460) Enable Framework->Executor message optimization for HTTP API
Anand Mazumdar created MESOS-4460: - Summary: Enable Framework->Executor message optimization for HTTP API Key: MESOS-4460 URL: https://issues.apache.org/jira/browse/MESOS-4460 Project: Mesos Issue Type: Task Reporter: Anand Mazumdar Currently, we support sending framework->executor messages directly as an optimization. This is not currently possible with using the Scheduler HTTP API. We should think about exploring possible alternatives for supporting this optimization. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (MESOS-4433) Implement a callback testing interface for the Executor Library
[
https://issues.apache.org/jira/browse/MESOS-4433?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15112996#comment-15112996
]
Anand Mazumdar commented on MESOS-4433:
---
Patch: https://reviews.apache.org/r/41288/
> Implement a callback testing interface for the Executor Library
> ---
>
> Key: MESOS-4433
> URL: https://issues.apache.org/jira/browse/MESOS-4433
> Project: Mesos
> Issue Type: Task
>Reporter: Anand Mazumdar
>Assignee: Anand Mazumdar
> Labels: mesosphere
>
> Currently, we do not have a mocking based callback interface for the executor
> library. This should look similar to the ongoing work for MESOS-3339 i.e. the
> corresponding issue for the scheduler library.
> The interface should allow us to set expectations like we do for the driver.
> An example:
> {code}
> EXPECT_CALL(executor, connected())
> .Times(1)
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Assigned] (MESOS-4455) Error on scrolling the page horizontally on website
[ https://issues.apache.org/jira/browse/MESOS-4455?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Benjamin Mahler reassigned MESOS-4455: -- Assignee: Benjamin Mahler > Error on scrolling the page horizontally on website > --- > > Key: MESOS-4455 > URL: https://issues.apache.org/jira/browse/MESOS-4455 > Project: Mesos > Issue Type: Bug > Components: project website >Reporter: Disha Singh >Assignee: Benjamin Mahler >Priority: Minor > Labels: newbie > > When the page :http://mesos.apache.org/documentation/latest/architecture/ > is scrolled horizontally the naval bar at the top discontinues creating a > bad look. > Also, this is occuring only because of the unadjusted size of the picture > architecture3.jpg. > This makes two finger-scrolling non-pleasant. > one of the these things can be done: > 1. Adjust the image's size. > 2. Fix the naval bar on it's position by adding ":fixed" in the CSS class > block itself to prevent any issues even in the future. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (MESOS-4449) SegFault on agent during executor startup
[ https://issues.apache.org/jira/browse/MESOS-4449?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15113104#comment-15113104 ] Joris Van Remoortere commented on MESOS-4449: - [~philwinder] Once 0.27 is released (soon) we will be doing a set of point fix releases. We will include this in the point fix release for 0.26. > SegFault on agent during executor startup > - > > Key: MESOS-4449 > URL: https://issues.apache.org/jira/browse/MESOS-4449 > Project: Mesos > Issue Type: Bug >Affects Versions: 0.26.0 > Environment: Some setup details: > - Master and agents running in separate docker containers on the same host. > - Containers based upon Ubuntu 14.04 using Mesosphere produced Mesos deb > files. For more details see > (https://github.com/ContainerSolutions/minimesos-docker) > - This only occurs with 0.26, not with 0.25. >Reporter: Philip Winder >Assignee: Anand Mazumdar >Priority: Blocker > Labels: mesosphere > Fix For: 0.27.0 > > Attachments: agent.txt, master.txt > > > When repeatedly performing our system tests we have found that we get a > segfault on one of the agents. It probably occurs about one time in ten. I > have attached the full log from that agent. I've attached the log from the > agent that failed and the master (although I think this is less helpful). > To reproduce > - I have no idea. It seems to occur at certain times. E.g. like if a packet > is created right on a minute boundary or something. But I don't think it's > something caused by our code because the timestamps are stamped by mesos. I > was surprised not to find a bug already open. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (MESOS-1664) Inform framework when rate limiting is active
[ https://issues.apache.org/jira/browse/MESOS-1664?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Anand Mazumdar updated MESOS-1664: -- Shepherd: Vinod Kone Story Points: 3 Labels: mesosphere (was: ) > Inform framework when rate limiting is active > - > > Key: MESOS-1664 > URL: https://issues.apache.org/jira/browse/MESOS-1664 > Project: Mesos > Issue Type: Improvement >Reporter: Dominic Hamon > Labels: mesosphere > > When we rate-limit messages from a framework, we should let them know so they > can proactively back-off to avoid putting extra pressure on the master. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (MESOS-3343) Rate Limiting functionality for HTTP Frameworks
[ https://issues.apache.org/jira/browse/MESOS-3343?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Anand Mazumdar updated MESOS-3343: -- Shepherd: Vinod Kone Story Points: 5 Labels: mesosphere (was: ) > Rate Limiting functionality for HTTP Frameworks > --- > > Key: MESOS-3343 > URL: https://issues.apache.org/jira/browse/MESOS-3343 > Project: Mesos > Issue Type: Task >Reporter: Anand Mazumdar > Labels: mesosphere > > We need to build rate limiting functionality for frameworks connecting via > the Scheduler HTTP API similar to the PID based frameworks. > Link to the rate-limiting section from design doc: > https://docs.google.com/document/d/1pnIY_HckimKNvpqhKRhbc9eSItWNFT-priXh_urR-T0/edit#heading=h.kzgdk4d5fmba > - This ticket deals with refactoring the existing PID based framework > functionality and extend it for HTTP frameworks. > - The second part of notifying the framework when rate-limiting is active > i.e. returning a status of 429 can be undertook as part of MESOS-1664 -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (MESOS-4031) slave crashed in cgroupstatistics()
[
https://issues.apache.org/jira/browse/MESOS-4031?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Benjamin Mahler updated MESOS-4031:
---
Component/s: (was: libprocess)
docker
> slave crashed in cgroupstatistics()
> ---
>
> Key: MESOS-4031
> URL: https://issues.apache.org/jira/browse/MESOS-4031
> Project: Mesos
> Issue Type: Bug
> Components: containerization, docker
>Affects Versions: 0.24.0
> Environment: Debian jessie
>Reporter: Steven
>Assignee: Timothy Chen
> Labels: mesosphere
> Fix For: 0.27.0
>
>
> Hi all,
> I have built a mesos cluster with three slaves. Any slave may sporadically
> crash when I get the summary through mesos master ui. Here is the stack
> trace.
> {code}
> slave.sh[13336]: I1201 11:54:12.827975 13338 slave.cpp:3926] Current disk
> usage 79.71%. Max allowed age: 17.279577136390834hrs
> slave.sh[13336]: I1201 11:55:12.829792 13342 slave.cpp:3926] Current disk
> usage 79.71%. Max allowed age: 17.279577136390834hrs
> slave.sh[13336]: I1201 11:55:38.389614 13342 http.cpp:189] HTTP GET for
> /slave(1)/state from 192.168.100.1:64870 with User-Agent='Mozilla/5.0 (X11;
> Ubuntu; Linux x86_64; rv:40.0) Gecko/20100101 Firefox/40.0'
> docker[8409]: time="2015-12-01T11:55:38.934148017+08:00" level=info msg="GET
> /v1.20/containers/mesos-b25be32d-41e1-4e14-9b84-d33d733cef51-S3.79c206a6-d6b5-487b-9390-e09292c5b53a/json"
> docker[8409]: time="2015-12-01T11:55:38.941489332+08:00" level=info msg="GET
> /v1.20/containers/mesos-b25be32d-41e1-4e14-9b84-d33d733cef51-S3.1e01a4b3-a76e-4bf6-8ce0-a4a937faf236/json"
> slave.sh[13336]: ABORT:
> (../../3rdparty/libprocess/3rdparty/stout/include/stout/result.hpp:110):
> Result::get() but state == NONE*** Aborted at 1448942139 (unix time) try
> "date -d @1448942139" if you are using GNU date ***
> slave.sh[13336]: PC: @ 0x7f295218a107 (unknown)
> slave.sh[13336]: *** SIGABRT (@0x3419) received by PID 13337 (TID
> 0x7f2948992700) from PID 13337; stack trace: ***
> slave.sh[13336]: @ 0x7f2952a2e8d0 (unknown)
> slave.sh[13336]: @ 0x7f295218a107 (unknown)
> slave.sh[13336]: @ 0x7f295218b4e8 (unknown)
> slave.sh[13336]: @ 0x43dc59 _Abort()
> slave.sh[13336]: @ 0x43dc87 _Abort()
> slave.sh[13336]: @ 0x7f2955e31c86 Result<>::get()
> slave.sh[13336]: @ 0x7f295637f017
> mesos::internal::slave::DockerContainerizerProcess::cgroupsStatistics()
> slave.sh[13336]: @ 0x7f295637dfea
> _ZZN5mesos8internal5slave26DockerContainerizerProcess5usageERKNS_11ContainerIDEENKUliE_clEi
> slave.sh[13336]: @ 0x7f295637e549
> _ZZN5mesos8internal5slave26DockerContainerizerProcess5usageERKNS_11ContainerIDEENKUlRKN6Docker9ContainerEE0_clES9_
> slave.sh[13336]: @ 0x7f295638453b
> ZN5mesos8internal5slave26DockerContainerizerProcess5usageERKNS1_11ContainerIDEEUlRKN6Docker9ContainerEE0_EcvSt8functionIFT_T0_EEINS_6FutureINS1_18ResourceStatisticsEEESB_EEvENKUlSB_E_clESB_ENKUlvE_clEv
> slave.sh[13336]: @ 0x7f295638751d
> FN7process6FutureIN5mesos18ResourceStatisticsEEEvEZZNKS0_9_DeferredIZNS2_8internal5slave26DockerContainerizerProcess5usageERKNS2_11ContainerIDEEUlRKN6Docker9ContainerEE0_EcvSt8functionIFT_T0_EEIS4_SG_EEvENKUlSG_E_clESG_EUlvE_E9_M_invoke
> slave.sh[13336]: @ 0x7f29563b53e7 std::function<>::operator()()
> slave.sh[13336]: @ 0x7f29563aa5dc
> _ZZN7process8dispatchIN5mesos18ResourceStatisticsEEENS_6FutureIT_EERKNS_4UPIDERKSt8functionIFS5_vEEENKUlPNS_11ProcessBaseEE_clESF_
> slave.sh[13336]: @ 0x7f29563bd667
> _ZNSt17_Function_handlerIFvPN7process11ProcessBaseEEZNS0_8dispatchIN5mesos18ResourceStatisticsEEENS0_6FutureIT_EERKNS0_4UPIDERKSt8functionIFS9_vEEEUlS2_E_E9_M_invokeERKSt9_Any_dataS2_
> slave.sh[13336]: @ 0x7f2956b893c3 std::function<>::operator()()
> slave.sh[13336]: @ 0x7f2956b72ab0 process::ProcessBase::visit()
> slave.sh[13336]: @ 0x7f2956b7588e process::DispatchEvent::visit()
> slave.sh[13336]: @ 0x7f2955d7f972 process::ProcessBase::serve()
> slave.sh[13336]: @ 0x7f2956b6ef8e process::ProcessManager::resume()
> slave.sh[13336]: @ 0x7f2956b63555 process::internal::schedule()
> slave.sh[13336]: @ 0x7f2956bc0839
> _ZNSt12_Bind_simpleIFPFvvEvEE9_M_invokeIJEEEvSt12_Index_tupleIJXspT_EEE
> slave.sh[13336]: @ 0x7f2956bc0781 std::_Bind_simple<>::operator()()
> slave.sh[13336]: @ 0x7f2956bc06fe std::thread::_Impl<>::_M_run()
> slave.sh[13336]: @ 0x7f29527ca970 (unknown)
> slave.sh[13336]: @ 0x7f2952a270a4 start_thread
> slave.sh[13336]: @ 0x7f295223b04d (unknown)
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (MESOS-4433) Implement a callback testing interface for the Executor Library
[
https://issues.apache.org/jira/browse/MESOS-4433?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Vinod Kone updated MESOS-4433:
--
Story Points: 3
> Implement a callback testing interface for the Executor Library
> ---
>
> Key: MESOS-4433
> URL: https://issues.apache.org/jira/browse/MESOS-4433
> Project: Mesos
> Issue Type: Task
>Reporter: Anand Mazumdar
>Assignee: Anand Mazumdar
> Labels: mesosphere
>
> Currently, we do not have a mocking based callback interface for the executor
> library. This should look similar to the ongoing work for MESOS-3339 i.e. the
> corresponding issue for the scheduler library.
> The interface should allow us to set expectations like we do for the driver.
> An example:
> {code}
> EXPECT_CALL(executor, connected())
> .Times(1)
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (MESOS-4457) Implement tests for the new Executor library
[
https://issues.apache.org/jira/browse/MESOS-4457?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15112997#comment-15112997
]
Anand Mazumdar commented on MESOS-4457:
---
Review Chain: https://reviews.apache.org/r/41290/
> Implement tests for the new Executor library
>
>
> Key: MESOS-4457
> URL: https://issues.apache.org/jira/browse/MESOS-4457
> Project: Mesos
> Issue Type: Task
>Reporter: Anand Mazumdar
> Labels: mesosphere
>
> We need to add tests for the executor library {{src/executor/executor.cpp}}.
> One possible approach would be to use the existing tests in
> {{src/tests/scheduler_tests.cpp}} and make them use the new executor library.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Created] (MESOS-4459) Implement AuthN handling on the scheduler library
Anand Mazumdar created MESOS-4459:
-
Summary: Implement AuthN handling on the scheduler library
Key: MESOS-4459
URL: https://issues.apache.org/jira/browse/MESOS-4459
Project: Mesos
Issue Type: Task
Reporter: Anand Mazumdar
Currently, we do not have the ability of passing {{Credentials}} via the
scheduler library. Once the master supports AuthN handling for the
{{/scheduler}} endpoint, we would need to add this support to the library.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (MESOS-4460) Enable Framework->Executor message optimization for HTTP API
[ https://issues.apache.org/jira/browse/MESOS-4460?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Anand Mazumdar updated MESOS-4460: -- Shepherd: Vinod Kone Labels: mesosphere (was: ) > Enable Framework->Executor message optimization for HTTP API > > > Key: MESOS-4460 > URL: https://issues.apache.org/jira/browse/MESOS-4460 > Project: Mesos > Issue Type: Task >Reporter: Anand Mazumdar > Labels: mesosphere > > Currently, we support sending framework->executor messages directly as an > optimization. This is not currently possible with using the Scheduler HTTP > API. We should think about exploring possible alternatives for supporting > this optimization. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (MESOS-4461) Enable Executor->Framework message optimization for HTTP API
Anand Mazumdar created MESOS-4461: - Summary: Enable Executor->Framework message optimization for HTTP API Key: MESOS-4461 URL: https://issues.apache.org/jira/browse/MESOS-4461 Project: Mesos Issue Type: Task Reporter: Anand Mazumdar Currently, we support sending executor->framework messages directly as an optimization. This is not currently possible with using the Scheduler HTTP API. We should think about exploring possible alternatives for supporting this optimization. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (MESOS-4457) Implement tests for the new Executor library
[
https://issues.apache.org/jira/browse/MESOS-4457?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Anand Mazumdar updated MESOS-4457:
--
Description: We need to add tests for the executor library
{{src/executor/executor.cpp}}. One possible approach would be to use the
existing tests in {{src/tests/scheduler_tests.cpp}} and make them use the new
executor library.
> Implement tests for the new Executor library
>
>
> Key: MESOS-4457
> URL: https://issues.apache.org/jira/browse/MESOS-4457
> Project: Mesos
> Issue Type: Task
>Reporter: Anand Mazumdar
> Labels: mesosphere
>
> We need to add tests for the executor library {{src/executor/executor.cpp}}.
> One possible approach would be to use the existing tests in
> {{src/tests/scheduler_tests.cpp}} and make them use the new executor library.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (MESOS-4459) Implement AuthN handling on the scheduler library
[
https://issues.apache.org/jira/browse/MESOS-4459?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Anand Mazumdar updated MESOS-4459:
--
Labels: mesosphere (was: )
> Implement AuthN handling on the scheduler library
> -
>
> Key: MESOS-4459
> URL: https://issues.apache.org/jira/browse/MESOS-4459
> Project: Mesos
> Issue Type: Task
>Reporter: Anand Mazumdar
> Labels: mesosphere
>
> Currently, we do not have the ability of passing {{Credentials}} via the
> scheduler library. Once the master supports AuthN handling for the
> {{/scheduler}} endpoint, we would need to add this support to the library.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (MESOS-2257) Version the Operator/Admin API
[
https://issues.apache.org/jira/browse/MESOS-2257?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Vinod Kone updated MESOS-2257:
--
Story Points: 13
> Version the Operator/Admin API
> --
>
> Key: MESOS-2257
> URL: https://issues.apache.org/jira/browse/MESOS-2257
> Project: Mesos
> Issue Type: Improvement
>Reporter: Sunil Shah
>Priority: Minor
> Labels: mesosphere
>
> As a consumer of the Mesos HTTP API, it is necessary for us to determine the
> current version of Mesos so that we can parse the JSON documents returned
> correctly (since they change from version to version).
> Currently we're doing this by fetching state.json, parsing it and pulling out
> the version field. A more idiomatic way to do this would be to filter on the
> content-type in the header itself.
> To give a more concrete example, currently the JSON documents returned by the
> HTTP API return the following headers:
> {code}
> HTTP/1.1 200 OK
> Date: Fri, 23 Jan 2015 21:31:37 GMT
> Content-Length: 9352
> Content-Type: application/json
> {code}
> Something like the following (e.g. for master/state.json) would be easy to
> switch upon:
> {code}
> HTTP/1.1 200 OK
> Date: Fri, 23 Jan 2015 21:31:37 GMT
> Content-Length: 9352
> Content-Type: application/vnd.mesos.master.state.v0.20.1+json; charset=utf-8
> {code}
> The vnd prefix is typically used for vendor specific file types (see:
> http://en.wikipedia.org/wiki/Internet_media_type#Prefix_vnd). Charset=utf-8
> is required for JSON documents and is currently being omitted.
> This content-type would change for each document type, for example:
> {code}
> application/vnd.mesos.master.state.v0.20.1+json; charset=utf-8
> application/vnd.mesos.master.stats.v0.20.1+json; charset=utf-8
> application/vnd.mesos.slave.state.v0.20.1+json; charset=utf-8
> application/vnd.mesos.slave.stats.v0.20.1+json; charset=utf-8
> {code}
> Alternatively, the version could be appended as an extra field:
> {code}
> application/vnd.mesos.master.state+json; charset=utf-8; version=v0.20.1
> application/vnd.mesos.master.stats+json; charset=utf-8; version=v0.20.1
> application/vnd.mesos.slave.state+json; charset=utf-8; version=v0.20.1
> application/vnd.mesos.slave.stats+json; charset=utf-8; version=v0.20.1
> {code}
> Thanks!
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (MESOS-4398) Synchronously handle AuthZ errors for the Scheduler endpoint.
[
https://issues.apache.org/jira/browse/MESOS-4398?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Vinod Kone updated MESOS-4398:
--
Story Points: 5
> Synchronously handle AuthZ errors for the Scheduler endpoint.
> -
>
> Key: MESOS-4398
> URL: https://issues.apache.org/jira/browse/MESOS-4398
> Project: Mesos
> Issue Type: Bug
>Affects Versions: 0.25.0
>Reporter: Anand Mazumdar
> Labels: mesosphere
>
> Currently, any AuthZ errors for the {{/scheduler}} endpoint are handled
> asynchronously as {{FrameworkErrorMessage}}. Here is an example:
> {code}
> if (authorizationError.isSome()) {
> LOG(INFO) << "Refusing subscription of framework"
> << " '" << frameworkInfo.name() << "'"
> << ": " << authorizationError.get().message;
> FrameworkErrorMessage message;
> message.set_message(authorizationError.get().message);
> http.send(message);
> http.close();
> return;
> }
> {code}
> We would like to handle such errors synchronously when the request is
> received similar to what other endpoints like {{/reserve}}/{{/quota}} do. We
> already have the relevant functions {{authorizeXXX}} etc in {{master.cpp}}.
> We should just make the requests pass through once the relevant {{Future}}
> from the {{authorizeXXX}} function is fulfilled.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (MESOS-920) Set GLOG_drop_log_memory=false in environment prior to logging initialization.
[
https://issues.apache.org/jira/browse/MESOS-920?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Benjamin Mahler updated MESOS-920:
--
Shepherd: Benjamin Mahler
> Set GLOG_drop_log_memory=false in environment prior to logging initialization.
> --
>
> Key: MESOS-920
> URL: https://issues.apache.org/jira/browse/MESOS-920
> Project: Mesos
> Issue Type: Improvement
> Components: technical debt
>Affects Versions: 0.15.0, 0.16.0
>Reporter: Benjamin Mahler
>Assignee: Kapil Arya
>
> We've observed issues where the masters are slow to respond. Two perf traces
> collected while the masters were slow to respond:
> {noformat}
> 25.84% [kernel][k] default_send_IPI_mask_sequence_phys
> 20.44% [kernel][k] native_write_msr_safe
> 4.54% [kernel][k] _raw_spin_lock
> 2.95% libc-2.5.so [.] _int_malloc
> 1.82% libc-2.5.so [.] malloc
> 1.55% [kernel][k] apic_timer_interrupt
> 1.36% libc-2.5.so [.] _int_free
> {noformat}
> {noformat}
> 29.03% [kernel][k] default_send_IPI_mask_sequence_phys
> 9.64% [kernel][k] _raw_spin_lock
> 7.38% [kernel][k] native_write_msr_safe
> 2.43% libc-2.5.so [.] _int_malloc
> 2.05% libc-2.5.so [.] _int_free
> 1.67% [kernel][k] apic_timer_interrupt
> 1.58% libc-2.5.so [.] malloc
> {noformat}
> These have been found to be attributed to the posix_fadvise calls made by
> glog. We can disable these via the environment:
> {noformat}
> GLOG_DEFINE_bool(drop_log_memory, true, "Drop in-memory buffers of log
> contents. "
> "Logs can grow very quickly and they are rarely read before
> they "
> "need to be evicted from memory. Instead, drop them from
> memory "
> "as soon as they are flushed to disk.");
> {noformat}
> {code}
> if (FLAGS_drop_log_memory) {
> if (file_length_ >= logging::kPageSize) {
> // don't evict the most recent page
> uint32 len = file_length_ & ~(logging::kPageSize - 1);
> posix_fadvise(fileno(file_), 0, len, POSIX_FADV_DONTNEED);
> }
> }
> {code}
> We should set GLOG_drop_log_memory=false prior to making our call to
> google::InitGoogleLogging, to avoid others running into this issue.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (MESOS-4455) Error on scrolling the page horizontally on website
[ https://issues.apache.org/jira/browse/MESOS-4455?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Disha Singh updated MESOS-4455: --- Description: When the page :http://mesos.apache.org/documentation/latest/architecture/ is scrolled horizontally the naval bar at the top discontinues creating a bad look. Also, this is occuring only because of the unadjusted size of the picture architecture3.jpg. This makes two finger-scrolling non-pleasant. one of the these things can be done: 1. Adjust the image's size. 2. Fix the naval bar on it's position by adding ":fixed" in the CSS class block itself to prevent any issues even in the future. was: When the page :http://mesos.apache.org/documentation/latest/architecture/ is scrolled horizontally the naval bar at the top discontinues creating a bad look. Also, this is occuring only because of the unadjusted size of the picture architecture3.jpg. This makes two finger-scrolling non-pleasant. one of the two things can be done: Either fix the image's size OR Fix the naval bar styling in the CSS file itself to prevent any future issues.(Better option) > Error on scrolling the page horizontally on website > --- > > Key: MESOS-4455 > URL: https://issues.apache.org/jira/browse/MESOS-4455 > Project: Mesos > Issue Type: Bug > Components: project website >Reporter: Disha Singh >Priority: Minor > Labels: newbie > > When the page :http://mesos.apache.org/documentation/latest/architecture/ > is scrolled horizontally the naval bar at the top discontinues creating a > bad look. > Also, this is occuring only because of the unadjusted size of the picture > architecture3.jpg. > This makes two finger-scrolling non-pleasant. > one of the these things can be done: > 1. Adjust the image's size. > 2. Fix the naval bar on it's position by adding ":fixed" in the CSS class > block itself to prevent any issues even in the future. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (MESOS-3583) Introduce sessions in HTTP Scheduler API Subscribed Responses
[
https://issues.apache.org/jira/browse/MESOS-3583?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Vinod Kone updated MESOS-3583:
--
Story Points: 13
> Introduce sessions in HTTP Scheduler API Subscribed Responses
> -
>
> Key: MESOS-3583
> URL: https://issues.apache.org/jira/browse/MESOS-3583
> Project: Mesos
> Issue Type: Task
>Reporter: Anand Mazumdar
> Labels: mesosphere, tech-debt
>
> Currently, the HTTP Scheduler API has no concept of Sessions aka
> {{SessionID}} or a {{TokenID}}. This is useful in some failure scenarios. As
> of now, if a framework fails over and then subscribes again with the same
> {{FrameworkID}} with the {{force}} option set. The Mesos master would
> subscribe it.
> If the previous instance of the framework/scheduler tries to send a Call ,
> e.g. {{Call::KILL}} with the same previous {{FrameworkID}} set, it would be
> still accepted by the master leading to erroneously killing a task.
> This is possible because we do not have a way currently of distinguishing
> connections. It used to work in the previous driver implementation due to the
> master also performing a {{UPID}} check to verify if they matched and only
> then allowing the call.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Created] (MESOS-4458) Document that TaskStatus.data is not stored at master
Neil Conway created MESOS-4458:
--
Summary: Document that TaskStatus.data is not stored at master
Key: MESOS-4458
URL: https://issues.apache.org/jira/browse/MESOS-4458
Project: Mesos
Issue Type: Documentation
Components: documentation
Reporter: Neil Conway
Priority: Minor
{noformat}
// Delete data (maybe very large since it's stored by on-top framework) we
// are not interested in to avoid OOM.
// For example: mesos-master is running on a machine with 4GB free memory,
// if every task stores 10MB data into TaskStatus, then mesos-master will be
// killed by OOM killer after have 400 tasks finished.
// MESOS-1746.
task->mutable_statuses(task->statuses_size() - 1)->clear_data();
{noformat}
We should document this behavior.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (MESOS-4418) Create a test macro to advance Clock for Future
[
https://issues.apache.org/jira/browse/MESOS-4418?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
haosdent updated MESOS-4418:
Description:
For speed up test, we offer use
{code}
Clock::pause();
Clock::advance();
Clock::settle();
Clock::resume();
{code}
when wait a {{Future}}
I think it would be helpful if we could provide a macro contains these steps
when wait a future done.
> Create a test macro to advance Clock for Future
> ---
>
> Key: MESOS-4418
> URL: https://issues.apache.org/jira/browse/MESOS-4418
> Project: Mesos
> Issue Type: Improvement
>Reporter: haosdent
>Assignee: haosdent
> Labels: test
>
> For speed up test, we offer use
> {code}
> Clock::pause();
> Clock::advance();
> Clock::settle();
> Clock::resume();
> {code}
> when wait a {{Future}}
> I think it would be helpful if we could provide a macro contains these steps
> when wait a future done.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (MESOS-4435) Update `Master::Http::stateSummary` to use `jsonify`.
[
https://issues.apache.org/jira/browse/MESOS-4435?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Timothy Chen updated MESOS-4435:
Target Version/s: 0.28.0 (was: 0.27.0)
> Update `Master::Http::stateSummary` to use `jsonify`.
> -
>
> Key: MESOS-4435
> URL: https://issues.apache.org/jira/browse/MESOS-4435
> Project: Mesos
> Issue Type: Task
> Components: master
>Reporter: Michael Park
>Assignee: Michael Park
>
> Update {{state-summary}} to use {{jsonify}} to stay consistent with {{state}}
> HTTP endpoint.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (MESOS-3834) slave upgrade framework checkpoint incompatibility
[
https://issues.apache.org/jira/browse/MESOS-3834?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Neil Conway updated MESOS-3834:
---
Fix Version/s: (was: 0.26.0)
0.27.0
> slave upgrade framework checkpoint incompatibility
> ---
>
> Key: MESOS-3834
> URL: https://issues.apache.org/jira/browse/MESOS-3834
> Project: Mesos
> Issue Type: Bug
>Affects Versions: 0.24.1
>Reporter: James Peach
>Assignee: James Peach
> Fix For: 0.27.0
>
>
> We are upgrading from 0.22 to 0.25 and experienced the following crash in the
> 0.24 slave:
> {code}
> F1104 05:20:49.162701 1153 slave.cpp:4175] Check failed:
> frameworkInfo.has_id()
> *** Check failure stack trace: ***
> @ 0x7fef9c294650 google::LogMessage::Fail()
> @ 0x7fef9c29459f google::LogMessage::SendToLog()
> @ 0x7fef9c293fb0 google::LogMessage::Flush()
> @ 0x7fef9c296ce4 google::LogMessageFatal::~LogMessageFatal()
> @ 0x7fef9b9a5492 mesos::internal::slave::Slave::recoverFramework()
> @ 0x7fef9b9a3314 mesos::internal::slave::Slave::recover()
> @ 0x7fef9b9d069c
> _ZZN7process8dispatchI7NothingN5mesos8internal5slave5SlaveERK6ResultINS4_5state5StateEES9_EENS_6FutureIT_EERKNS_3PIDIT0_EEMSG_FSE_T1_ET2_ENKUlPNS_11ProcessBaseEE_clESP_
> @ 0x7fef9ba039f4
> _ZNSt17_Function_handlerIFvPN7process11ProcessBaseEEZNS0_8dispatchI7NothingN5mesos8internal5slave5SlaveERK6ResultINS8_5state5StateEESD_EENS0_6FutureIT_EERKNS0_3PIDIT0_EEMSK_FSI_T1_ET2_EUlS2_E_E9_M_invokeERKSt9_Any_dataS2_
> {code}
> As near as I can tell, what happened was this:
> - 0.22 wrote {{framework.info}} without the FrameworkID
> - 0.23 had a compatibility check so it was ok with it
> - 0.24 removed the compatibility check in MESOS-2259
> - the framework checkpoint doesn't get rewritten during recovery so when the
> 0.24 slave starts it reads the 0.22 version
> - 0.24 asserts
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Created] (MESOS-4457) Implement tests for the new Executor library
Anand Mazumdar created MESOS-4457: - Summary: Implement tests for the new Executor library Key: MESOS-4457 URL: https://issues.apache.org/jira/browse/MESOS-4457 Project: Mesos Issue Type: Task Reporter: Anand Mazumdar -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (MESOS-3923) Implement AuthN handling in Master for the Scheduler endpoint
[
https://issues.apache.org/jira/browse/MESOS-3923?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Vinod Kone updated MESOS-3923:
--
Story Points: 5 (was: 3)
> Implement AuthN handling in Master for the Scheduler endpoint
> -
>
> Key: MESOS-3923
> URL: https://issues.apache.org/jira/browse/MESOS-3923
> Project: Mesos
> Issue Type: Bug
> Components: framework, HTTP API, master
>Affects Versions: 0.25.0
>Reporter: Ben Whitehead
> Labels: mesosphere
>
> If authentication(AuthN) is enabled on a master, frameworks attempting to use
> the HTTP Scheduler API can't register.
> {code}
> $ cat /tmp/subscribe-943257503176798091.bin | http --print=HhBb --stream
> --pretty=colors --auth verification:password1 POST :5050/api/v1/scheduler
> Accept:application/x-protobuf Content-Type:application/x-protobuf
> POST /api/v1/scheduler HTTP/1.1
> Connection: keep-alive
> Content-Type: application/x-protobuf
> Accept-Encoding: gzip, deflate
> Accept: application/x-protobuf
> Content-Length: 126
> User-Agent: HTTPie/0.9.0
> Host: localhost:5050
> Authorization: Basic dmVyaWZpY2F0aW9uOnBhc3N3b3JkMQ==
> +-+
> | NOTE: binary data not shown in terminal |
> +-+
> HTTP/1.1 401 Unauthorized
> Date: Fri, 13 Nov 2015 20:00:45 GMT
> WWW-authenticate: Basic realm="Mesos master"
> Content-Length: 65
> HTTP schedulers are not supported when authentication is required
> {code}
> Authorization(AuthZ) is already supported for HTTP based frameworks.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (MESOS-4418) Create a test macro to advance Clock for Future
[
https://issues.apache.org/jira/browse/MESOS-4418?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15112806#comment-15112806
]
haosdent commented on MESOS-4418:
-
Hi [~anandmazumdar] Thank you very much for your coments.
{quote}
Can we add some more context in the description? Also, we avoid JIRA Summary
that directly outlines the solution instead of the generic problem that led to
the issue being created in the first place (unless it's obvious).
{quote}
Sorry for not filling description.
{quote}
Can you also find a shepherd for this?
{quote}
Not yet, do you have any ideas about this?
> Create a test macro to advance Clock for Future
> ---
>
> Key: MESOS-4418
> URL: https://issues.apache.org/jira/browse/MESOS-4418
> Project: Mesos
> Issue Type: Improvement
>Reporter: haosdent
>Assignee: haosdent
> Labels: test
>
> For speed up test, we offer use
> {code}
> Clock::pause();
> Clock::advance();
> Clock::settle();
> Clock::resume();
> {code}
> when wait a {{Future}}
> I think it would be helpful if we could provide a macro contains these steps
> when wait a future done.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Created] (MESOS-4456) Document running framework schedulers using Marathon/Aurora
Neil Conway created MESOS-4456: -- Summary: Document running framework schedulers using Marathon/Aurora Key: MESOS-4456 URL: https://issues.apache.org/jira/browse/MESOS-4456 Project: Mesos Issue Type: Documentation Components: documentation Reporter: Neil Conway Priority: Minor We should document that this is possible, as well as: * why you would want to do something like this (and when you wouldn't) * HA configuration * tradeoffs and common gotchas -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (MESOS-3923) Implement AuthN handling in Master for the Scheduler endpoint
[
https://issues.apache.org/jira/browse/MESOS-3923?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Anand Mazumdar updated MESOS-3923:
--
Summary: Implement AuthN handling in Master for the Scheduler endpoint
(was: Implement AuthN handling for HTTP Scheduler API)
> Implement AuthN handling in Master for the Scheduler endpoint
> -
>
> Key: MESOS-3923
> URL: https://issues.apache.org/jira/browse/MESOS-3923
> Project: Mesos
> Issue Type: Bug
> Components: framework, HTTP API, master
>Affects Versions: 0.25.0
>Reporter: Ben Whitehead
> Labels: mesosphere
>
> If authentication(AuthN) is enabled on a master, frameworks attempting to use
> the HTTP Scheduler API can't register.
> {code}
> $ cat /tmp/subscribe-943257503176798091.bin | http --print=HhBb --stream
> --pretty=colors --auth verification:password1 POST :5050/api/v1/scheduler
> Accept:application/x-protobuf Content-Type:application/x-protobuf
> POST /api/v1/scheduler HTTP/1.1
> Connection: keep-alive
> Content-Type: application/x-protobuf
> Accept-Encoding: gzip, deflate
> Accept: application/x-protobuf
> Content-Length: 126
> User-Agent: HTTPie/0.9.0
> Host: localhost:5050
> Authorization: Basic dmVyaWZpY2F0aW9uOnBhc3N3b3JkMQ==
> +-+
> | NOTE: binary data not shown in terminal |
> +-+
> HTTP/1.1 401 Unauthorized
> Date: Fri, 13 Nov 2015 20:00:45 GMT
> WWW-authenticate: Basic realm="Mesos master"
> Content-Length: 65
> HTTP schedulers are not supported when authentication is required
> {code}
> Authorization(AuthZ) is already supported for HTTP based frameworks.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (MESOS-3976) C++ HTTP Scheduler Library does not work with SSL enabled
[ https://issues.apache.org/jira/browse/MESOS-3976?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vinod Kone updated MESOS-3976: -- Story Points: 3 (was: 2) > C++ HTTP Scheduler Library does not work with SSL enabled > - > > Key: MESOS-3976 > URL: https://issues.apache.org/jira/browse/MESOS-3976 > Project: Mesos > Issue Type: Bug > Components: framework, HTTP API >Reporter: Joseph Wu >Assignee: Anand Mazumdar > Labels: mesosphere, security > > The C++ HTTP scheduler library does not work against Mesos when SSL is > enabled (without downgrade). > The fix should be simple: > * The library should detect if SSL is enabled. > * If SSL is enabled, connections should be made with HTTPS instead of HTTP. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (MESOS-4156) Speed up FetcherCacheTest.* and FetcherCacheHttpTest.*
[
https://issues.apache.org/jira/browse/MESOS-4156?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15112113#comment-15112113
]
Bernd Mathiske commented on MESOS-4156:
---
Sure thing.
> Speed up FetcherCacheTest.* and FetcherCacheHttpTest.*
> --
>
> Key: MESOS-4156
> URL: https://issues.apache.org/jira/browse/MESOS-4156
> Project: Mesos
> Issue Type: Epic
> Components: technical debt, test
>Reporter: Alexander Rukletsov
>Assignee: haosdent
>Priority: Minor
> Labels: mesosphere, newbie++, tech-debt
>
> Execution times on Mac OS 10.10.4:
> {code}
> FetcherCacheTest.LocalUncached (2417 ms)
> FetcherCacheTest.LocalCached (2476 ms)
> FetcherCacheTest.LocalUncachedExtract (2496 ms)
> FetcherCacheTest.LocalCachedExtract (2471 ms)
> FetcherCacheTest.SimpleEviction (4451 ms)
> FetcherCacheTest.FallbackFromEviction (2483 ms)
> FetcherCacheTest.RemoveLRUCacheEntries (3422 ms)
> FetcherCacheHttpTest.HttpCachedSerialized (2490 ms)
> FetcherCacheHttpTest.HttpCachedConcurrent (1032 ms)
> FetcherCacheHttpTest.HttpMixed (1022 ms)
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (MESOS-3509) SlaveTest.TerminatingSlaveDoesNotReregister is flaky
[
https://issues.apache.org/jira/browse/MESOS-3509?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Adam B updated MESOS-3509:
--
Labels: flaky-test (was: )
> SlaveTest.TerminatingSlaveDoesNotReregister is flaky
>
>
> Key: MESOS-3509
> URL: https://issues.apache.org/jira/browse/MESOS-3509
> Project: Mesos
> Issue Type: Bug
>Affects Versions: 0.25.0
>Reporter: Jie Yu
>Assignee: Liqiang Lin
> Labels: flaky-test
>
> Observed on Apache CI
> {noformat}
> [ RUN ] SlaveTest.TerminatingSlaveDoesNotReregister
> Using temporary directory
> '/tmp/SlaveTest_TerminatingSlaveDoesNotReregister_PiT5jn'
> I0924 04:54:06.645386 29977 leveldb.cpp:176] Opened db in 112.347533ms
> I0924 04:54:06.665618 29977 leveldb.cpp:183] Compacted db in 20.158157ms
> I0924 04:54:06.665704 29977 leveldb.cpp:198] Created db iterator in 24721ns
> I0924 04:54:06.665727 29977 leveldb.cpp:204] Seeked to beginning of db in
> 3125ns
> I0924 04:54:06.665741 29977 leveldb.cpp:273] Iterated through 0 keys in the
> db in 256ns
> I0924 04:54:06.665799 29977 replica.cpp:744] Replica recovered with log
> positions 0 -> 0 with 1 holes and 0 unlearned
> I0924 04:54:06.666378 3 recover.cpp:449] Starting replica recovery
> I0924 04:54:06.666831 3 recover.cpp:475] Replica is in EMPTY status
> I0924 04:54:06.667945 30008 replica.cpp:641] Replica in EMPTY status received
> a broadcasted recover request
> I0924 04:54:06.668473 30005 recover.cpp:195] Received a recover response from
> a replica in EMPTY status
> I0924 04:54:06.669003 30007 recover.cpp:566] Updating replica status to
> STARTING
> I0924 04:54:06.669154 3 master.cpp:370] Master
> bd006350-cdbf-414f-9eef-25f03ccdc5fb (7c9c99874a2d) started on
> 172.17.1.154:55676
> I0924 04:54:06.669347 3 master.cpp:372] Flags at startup: --acls=""
> --allocation_interval="1secs" --allocator="HierarchicalDRF"
> --authenticate="true" --authenticate_slaves="true" --authenticators="crammd5"
> --authorizers="local"
> --credentials="/tmp/SlaveTest_TerminatingSlaveDoesNotReregister_PiT5jn/credentials"
> --framework_sorter="drf" --help="false" --initialize_driver_logging="true"
> --log_auto_initialize="true" --logbufsecs="0" --logging_level="INFO"
> --max_slave_ping_timeouts="5" --quiet="false"
> --recovery_slave_removal_limit="100%" --registry="replicated_log"
> --registry_fetch_timeout="1mins" --registry_store_timeout="25secs"
> --registry_strict="true" --root_submissions="true"
> --slave_ping_timeout="15secs" --slave_reregister_timeout="10mins"
> --user_sorter="drf" --version="false"
> --webui_dir="/mesos/mesos-0.25.0/_inst/share/mesos/webui"
> --work_dir="/tmp/SlaveTest_TerminatingSlaveDoesNotReregister_PiT5jn/master"
> --zk_session_timeout="10secs"
> I0924 04:54:06.669595 3 master.cpp:417] Master only allowing
> authenticated frameworks to register
> I0924 04:54:06.669605 3 master.cpp:422] Master only allowing
> authenticated slaves to register
> I0924 04:54:06.669613 3 credentials.hpp:37] Loading credentials for
> authentication from
> '/tmp/SlaveTest_TerminatingSlaveDoesNotReregister_PiT5jn/credentials'
> I0924 04:54:06.669874 3 master.cpp:461] Using default 'crammd5'
> authenticator
> I0924 04:54:06.670027 3 master.cpp:498] Authorization enabled
> I0924 04:54:06.670264 30005 hierarchical.hpp:468] Initialized hierarchical
> allocator process
> I0924 04:54:06.670320 30005 whitelist_watcher.cpp:79] No whitelist given
> I0924 04:54:06.671406 2 master.cpp:1597] The newly elected leader is
> master@172.17.1.154:55676 with id bd006350-cdbf-414f-9eef-25f03ccdc5fb
> I0924 04:54:06.671438 2 master.cpp:1610] Elected as the leading master!
> I0924 04:54:06.671461 2 master.cpp:1370] Recovering from registrar
> I0924 04:54:06.671612 30011 registrar.cpp:309] Recovering registrar
> I0924 04:54:06.704048 30002 leveldb.cpp:306] Persisting metadata (8 bytes) to
> leveldb took 34.707125ms
> I0924 04:54:06.704123 30002 replica.cpp:323] Persisted replica status to
> STARTING
> I0924 04:54:06.704504 29997 recover.cpp:475] Replica is in STARTING status
> I0924 04:54:06.705658 30002 replica.cpp:641] Replica in STARTING status
> received a broadcasted recover request
> I0924 04:54:06.706466 30007 recover.cpp:195] Received a recover response from
> a replica in STARTING status
> I0924 04:54:06.707064 30004 recover.cpp:566] Updating replica status to VOTING
> I0924 04:54:06.737488 30004 leveldb.cpp:306] Persisting metadata (8 bytes) to
> leveldb took 30.261425ms
> I0924 04:54:06.737560 30004 replica.cpp:323] Persisted replica status to
> VOTING
> I0924 04:54:06.737746 30004 recover.cpp:580] Successfully joined the Paxos
> group
> I0924 04:54:06.737932 30004 recover.cpp:464] Recover process terminated
> I0924 04:54:06.738535 30009 log.cpp:661]
[jira] [Commented] (MESOS-4449) SegFault on agent during executor startup
[ https://issues.apache.org/jira/browse/MESOS-4449?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15112194#comment-15112194 ] Philip Winder commented on MESOS-4449: -- Hi guys. Is there any chance of a point fix? Because this makes 0.26 unusable. Thanks, Phil > SegFault on agent during executor startup > - > > Key: MESOS-4449 > URL: https://issues.apache.org/jira/browse/MESOS-4449 > Project: Mesos > Issue Type: Bug >Affects Versions: 0.26.0 > Environment: Some setup details: > - Master and agents running in separate docker containers on the same host. > - Containers based upon Ubuntu 14.04 using Mesosphere produced Mesos deb > files. For more details see > (https://github.com/ContainerSolutions/minimesos-docker) > - This only occurs with 0.26, not with 0.25. >Reporter: Philip Winder >Assignee: Anand Mazumdar >Priority: Blocker > Labels: mesosphere > Attachments: agent.txt, master.txt > > > When repeatedly performing our system tests we have found that we get a > segfault on one of the agents. It probably occurs about one time in ten. I > have attached the full log from that agent. I've attached the log from the > agent that failed and the master (although I think this is less helpful). > To reproduce > - I have no idea. It seems to occur at certain times. E.g. like if a packet > is created right on a minute boundary or something. But I don't think it's > something caused by our code because the timestamps are stamped by mesos. I > was surprised not to find a bug already open. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (MESOS-4467) Implement `sleep` in Windows
Alex Clemmer created MESOS-4467: --- Summary: Implement `sleep` in Windows Key: MESOS-4467 URL: https://issues.apache.org/jira/browse/MESOS-4467 Project: Mesos Issue Type: Bug Components: stout Reporter: Alex Clemmer Assignee: Alex Clemmer -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (MESOS-4465) Implement pagesize facilities in Windows
Alex Clemmer created MESOS-4465: --- Summary: Implement pagesize facilities in Windows Key: MESOS-4465 URL: https://issues.apache.org/jira/browse/MESOS-4465 Project: Mesos Issue Type: Bug Components: cmake Reporter: Alex Clemmer Assignee: Alex Clemmer -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (MESOS-4468) Implement `loadavg` on Windows
Alex Clemmer created MESOS-4468: --- Summary: Implement `loadavg` on Windows Key: MESOS-4468 URL: https://issues.apache.org/jira/browse/MESOS-4468 Project: Mesos Issue Type: Bug Components: stout Reporter: Alex Clemmer Assignee: Alex Clemmer -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (MESOS-4464) Implement cpu count facilities on Windows
Alex Clemmer created MESOS-4464: --- Summary: Implement cpu count facilities on Windows Key: MESOS-4464 URL: https://issues.apache.org/jira/browse/MESOS-4464 Project: Mesos Issue Type: Bug Components: libprocess Reporter: Alex Clemmer Assignee: Alex Clemmer -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (MESOS-4466) Implement `waitpid` in Windows
Alex Clemmer created MESOS-4466: --- Summary: Implement `waitpid` in Windows Key: MESOS-4466 URL: https://issues.apache.org/jira/browse/MESOS-4466 Project: Mesos Issue Type: Bug Components: stout Reporter: Alex Clemmer Assignee: Alex Clemmer -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (MESOS-4471) Implement process querying/counting in Windows
[ https://issues.apache.org/jira/browse/MESOS-4471?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alex Clemmer updated MESOS-4471: Labels: mesosphere stout windows-mvp (was: mesosphere stout) > Implement process querying/counting in Windows > -- > > Key: MESOS-4471 > URL: https://issues.apache.org/jira/browse/MESOS-4471 > Project: Mesos > Issue Type: Bug > Components: stout >Reporter: Alex Clemmer >Assignee: Alex Clemmer > Labels: mesosphere, stout, windows-mvp > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (MESOS-4469) Implement memory querying in Windows
[ https://issues.apache.org/jira/browse/MESOS-4469?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alex Clemmer updated MESOS-4469: Labels: mesosphere stout windows-mvp (was: mesosphere stout) > Implement memory querying in Windows > > > Key: MESOS-4469 > URL: https://issues.apache.org/jira/browse/MESOS-4469 > Project: Mesos > Issue Type: Bug >Reporter: Alex Clemmer >Assignee: Alex Clemmer > Labels: mesosphere, stout, windows-mvp > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (MESOS-4471) Implement process querying/counting in Windows
Alex Clemmer created MESOS-4471: --- Summary: Implement process querying/counting in Windows Key: MESOS-4471 URL: https://issues.apache.org/jira/browse/MESOS-4471 Project: Mesos Issue Type: Bug Components: stout Reporter: Alex Clemmer Assignee: Alex Clemmer -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (MESOS-4472) Implement `getenv` in Windows
Alex Clemmer created MESOS-4472: --- Summary: Implement `getenv` in Windows Key: MESOS-4472 URL: https://issues.apache.org/jira/browse/MESOS-4472 Project: Mesos Issue Type: Bug Components: stout Reporter: Alex Clemmer Assignee: Alex Clemmer -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (MESOS-4473) Implement `shell` in Windows
Alex Clemmer created MESOS-4473: --- Summary: Implement `shell` in Windows Key: MESOS-4473 URL: https://issues.apache.org/jira/browse/MESOS-4473 Project: Mesos Issue Type: Bug Components: stout Reporter: Alex Clemmer Assignee: Alex Clemmer -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (MESOS-4463) Implement `hsterror`
[ https://issues.apache.org/jira/browse/MESOS-4463?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alex Clemmer updated MESOS-4463: Labels: mesosphere stout windows-mvp (was: mesosphere stout) > Implement `hsterror` > > > Key: MESOS-4463 > URL: https://issues.apache.org/jira/browse/MESOS-4463 > Project: Mesos > Issue Type: Bug > Components: stout >Reporter: Alex Clemmer >Assignee: Alex Clemmer > Labels: mesosphere, stout, windows-mvp > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (MESOS-4462) Port `gmtime_r`
[ https://issues.apache.org/jira/browse/MESOS-4462?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alex Clemmer updated MESOS-4462: Labels: cmake mesosphere windows-mvp (was: cmake mesosphere) > Port `gmtime_r` > --- > > Key: MESOS-4462 > URL: https://issues.apache.org/jira/browse/MESOS-4462 > Project: Mesos > Issue Type: Bug > Components: stout >Reporter: Alex Clemmer >Assignee: Alex Clemmer > Labels: cmake, mesosphere, windows-mvp > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (MESOS-4465) Implement pagesize facilities in Windows
[ https://issues.apache.org/jira/browse/MESOS-4465?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alex Clemmer updated MESOS-4465: Labels: mesosphere stout windows-mvp (was: mesosphere stout) > Implement pagesize facilities in Windows > > > Key: MESOS-4465 > URL: https://issues.apache.org/jira/browse/MESOS-4465 > Project: Mesos > Issue Type: Bug > Components: cmake >Reporter: Alex Clemmer >Assignee: Alex Clemmer > Labels: mesosphere, stout, windows-mvp > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (MESOS-4467) Implement `sleep` in Windows
[ https://issues.apache.org/jira/browse/MESOS-4467?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alex Clemmer updated MESOS-4467: Labels: mesosphere stout windows-mvp (was: mesosphere stout) > Implement `sleep` in Windows > > > Key: MESOS-4467 > URL: https://issues.apache.org/jira/browse/MESOS-4467 > Project: Mesos > Issue Type: Bug > Components: stout >Reporter: Alex Clemmer >Assignee: Alex Clemmer > Labels: mesosphere, stout, windows-mvp > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (MESOS-4464) Implement cpu count facilities on Windows
[ https://issues.apache.org/jira/browse/MESOS-4464?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alex Clemmer updated MESOS-4464: Labels: mesosphere stout windows-mvp (was: mesosphere stout) > Implement cpu count facilities on Windows > - > > Key: MESOS-4464 > URL: https://issues.apache.org/jira/browse/MESOS-4464 > Project: Mesos > Issue Type: Bug > Components: libprocess >Reporter: Alex Clemmer >Assignee: Alex Clemmer > Labels: mesosphere, stout, windows-mvp > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (MESOS-4466) Implement `waitpid` in Windows
[ https://issues.apache.org/jira/browse/MESOS-4466?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alex Clemmer updated MESOS-4466: Labels: mesosphere stout windows-mvp (was: mesosphere stout) > Implement `waitpid` in Windows > -- > > Key: MESOS-4466 > URL: https://issues.apache.org/jira/browse/MESOS-4466 > Project: Mesos > Issue Type: Bug > Components: stout >Reporter: Alex Clemmer >Assignee: Alex Clemmer > Labels: mesosphere, stout, windows-mvp > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (MESOS-4468) Implement `loadavg` on Windows
[ https://issues.apache.org/jira/browse/MESOS-4468?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alex Clemmer updated MESOS-4468: Labels: mesosphere stout windows-mvp (was: mesosphere stout) > Implement `loadavg` on Windows > -- > > Key: MESOS-4468 > URL: https://issues.apache.org/jira/browse/MESOS-4468 > Project: Mesos > Issue Type: Bug > Components: stout >Reporter: Alex Clemmer >Assignee: Alex Clemmer > Labels: mesosphere, stout, windows-mvp > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (MESOS-4470) Implement `uname` in Windows
Alex Clemmer created MESOS-4470: --- Summary: Implement `uname` in Windows Key: MESOS-4470 URL: https://issues.apache.org/jira/browse/MESOS-4470 Project: Mesos Issue Type: Bug Components: stout Reporter: Alex Clemmer Assignee: Alex Clemmer -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (MESOS-4470) Implement `uname` in Windows
[ https://issues.apache.org/jira/browse/MESOS-4470?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alex Clemmer updated MESOS-4470: Labels: mesosphere stout windows-mvp (was: mesosphere stout) > Implement `uname` in Windows > > > Key: MESOS-4470 > URL: https://issues.apache.org/jira/browse/MESOS-4470 > Project: Mesos > Issue Type: Bug > Components: stout >Reporter: Alex Clemmer >Assignee: Alex Clemmer > Labels: mesosphere, stout, windows-mvp > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Comment Edited] (MESOS-4005) Support workdir runtime configuration from image
[ https://issues.apache.org/jira/browse/MESOS-4005?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15113225#comment-15113225 ] Gilbert Song edited comment on MESOS-4005 at 1/22/16 10:20 PM: --- https://reviews.apache.org/r/42540/ was (Author: gilbert): https://reviews.apache.org/r/42538/ > Support workdir runtime configuration from image > - > > Key: MESOS-4005 > URL: https://issues.apache.org/jira/browse/MESOS-4005 > Project: Mesos > Issue Type: Improvement > Components: containerization >Reporter: Timothy Chen >Assignee: Gilbert Song > Labels: mesosphere, unified-containerizer-mvp > > We need to support workdir runtime configuration returned from image such as > Dockerfile. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (MESOS-4477) Document that TaskStatus.labels is not set in reconciliation results
Neil Conway created MESOS-4477: -- Summary: Document that TaskStatus.labels is not set in reconciliation results Key: MESOS-4477 URL: https://issues.apache.org/jira/browse/MESOS-4477 Project: Mesos Issue Type: Documentation Components: documentation Reporter: Neil Conway See https://mail-archives.apache.org/mod_mbox/mesos-user/201601.mbox/%3CCAEdQkn1beEBMmcH-41CPkKiy5mx2W-3id-L5uCmUm_5Ff0XNVA%40mail.gmail.com%3E -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (MESOS-4462) Port `gmtime_r`
Alex Clemmer created MESOS-4462: --- Summary: Port `gmtime_r` Key: MESOS-4462 URL: https://issues.apache.org/jira/browse/MESOS-4462 Project: Mesos Issue Type: Bug Components: stout Reporter: Alex Clemmer Assignee: Alex Clemmer -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (MESOS-4463) Implement `hsterror`
Alex Clemmer created MESOS-4463: --- Summary: Implement `hsterror` Key: MESOS-4463 URL: https://issues.apache.org/jira/browse/MESOS-4463 Project: Mesos Issue Type: Bug Components: stout Reporter: Alex Clemmer Assignee: Alex Clemmer -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (MESOS-3608) Optionally install test binaries.
[
https://issues.apache.org/jira/browse/MESOS-3608?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15113200#comment-15113200
]
James Peach commented on MESOS-3608:
[~tillt] This is complete and tested. All the tests pass when I run from an
installed version of the test suite (except as noted in the review).
> Optionally install test binaries.
> -
>
> Key: MESOS-3608
> URL: https://issues.apache.org/jira/browse/MESOS-3608
> Project: Mesos
> Issue Type: Improvement
> Components: build, test
>Reporter: James Peach
>Assignee: James Peach
>Priority: Minor
> Labels: mesosphere
>
> Many of the tests in Mesos could be described as integration tests, since
> they have external dependencies on kernel features, installed tools,
> permissions, etc. I'd like to be able to generate a {{mesos-tests}} RPM along
> with my {{mesos}} RPM so that I can run the same tests in different
> deployment environments.
> I propose a new configuration option named {{--enable-test-tools}} that will
> install the tests into {{libexec/mesos/tests}}. I'll also need to make some
> minor changes to tests so that helper tools can be found in this location as
> well as in the build directory.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Created] (MESOS-4475) Implement `pipe` in Windows
Alex Clemmer created MESOS-4475: --- Summary: Implement `pipe` in Windows Key: MESOS-4475 URL: https://issues.apache.org/jira/browse/MESOS-4475 Project: Mesos Issue Type: Bug Components: stout Reporter: Alex Clemmer Assignee: Alex Clemmer -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (MESOS-3622) Port slave/containerizer/launcher.cpp to Windows
[ https://issues.apache.org/jira/browse/MESOS-3622?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alex Clemmer updated MESOS-3622: Labels: mesosphere windows windows-mvp (was: mesosphere windows) > Port slave/containerizer/launcher.cpp to Windows > > > Key: MESOS-3622 > URL: https://issues.apache.org/jira/browse/MESOS-3622 > Project: Mesos > Issue Type: Task > Components: containerization >Reporter: Alex Clemmer >Assignee: Alex Clemmer > Labels: mesosphere, windows, windows-mvp > > Important subset of the dependency tree follows: > slave/containerizer/launcher.cpp: type_utils, collect, process, reap, launcher > type_utils.hpp: uuid.hpp > collect: future, defer, process > reap: future > launcher: isolator, future, usbprocess, flags > future.hpp: pid.hpp > defer.hpp: deferred.hpp, dispatch.hpp > deferred.hpp: dispatch.hpp, pid.hpp > dispatch.hpp: process.hpp > isolator: process > subprocess: os, future > flags.hpp: os.hpp, path.hpp, fetch.hpp > fetch.hpp: path.hpp -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (MESOS-3371) Implement process::subprocess on Windows
[ https://issues.apache.org/jira/browse/MESOS-3371?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alex Clemmer updated MESOS-3371: Labels: libprocess mesosphere windows-mvp (was: libprocess mesosphere) > Implement process::subprocess on Windows > > > Key: MESOS-3371 > URL: https://issues.apache.org/jira/browse/MESOS-3371 > Project: Mesos > Issue Type: Task > Components: libprocess >Reporter: Alex Clemmer >Assignee: Alex Clemmer > Labels: libprocess, mesosphere, windows-mvp > > From a discussion with mpark we (IIRC) concluded that even on Windows we call > this a couple times. We need to (1) confirm, and (2) do it. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (MESOS-4469) Implement memory querying in Windows
Alex Clemmer created MESOS-4469: --- Summary: Implement memory querying in Windows Key: MESOS-4469 URL: https://issues.apache.org/jira/browse/MESOS-4469 Project: Mesos Issue Type: Bug Reporter: Alex Clemmer Assignee: Alex Clemmer -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (MESOS-920) Set GLOG_drop_log_memory=false in environment prior to logging initialization.
[
https://issues.apache.org/jira/browse/MESOS-920?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Kapil Arya updated MESOS-920:
-
Target Version/s: 0.27.0
Priority: Blocker (was: Major)
> Set GLOG_drop_log_memory=false in environment prior to logging initialization.
> --
>
> Key: MESOS-920
> URL: https://issues.apache.org/jira/browse/MESOS-920
> Project: Mesos
> Issue Type: Improvement
> Components: technical debt
>Affects Versions: 0.15.0, 0.16.0
>Reporter: Benjamin Mahler
>Assignee: Kapil Arya
>Priority: Blocker
> Labels: mesosphere
>
> We've observed issues where the masters are slow to respond. Two perf traces
> collected while the masters were slow to respond:
> {noformat}
> 25.84% [kernel][k] default_send_IPI_mask_sequence_phys
> 20.44% [kernel][k] native_write_msr_safe
> 4.54% [kernel][k] _raw_spin_lock
> 2.95% libc-2.5.so [.] _int_malloc
> 1.82% libc-2.5.so [.] malloc
> 1.55% [kernel][k] apic_timer_interrupt
> 1.36% libc-2.5.so [.] _int_free
> {noformat}
> {noformat}
> 29.03% [kernel][k] default_send_IPI_mask_sequence_phys
> 9.64% [kernel][k] _raw_spin_lock
> 7.38% [kernel][k] native_write_msr_safe
> 2.43% libc-2.5.so [.] _int_malloc
> 2.05% libc-2.5.so [.] _int_free
> 1.67% [kernel][k] apic_timer_interrupt
> 1.58% libc-2.5.so [.] malloc
> {noformat}
> These have been found to be attributed to the posix_fadvise calls made by
> glog. We can disable these via the environment:
> {noformat}
> GLOG_DEFINE_bool(drop_log_memory, true, "Drop in-memory buffers of log
> contents. "
> "Logs can grow very quickly and they are rarely read before
> they "
> "need to be evicted from memory. Instead, drop them from
> memory "
> "as soon as they are flushed to disk.");
> {noformat}
> {code}
> if (FLAGS_drop_log_memory) {
> if (file_length_ >= logging::kPageSize) {
> // don't evict the most recent page
> uint32 len = file_length_ & ~(logging::kPageSize - 1);
> posix_fadvise(fileno(file_), 0, len, POSIX_FADV_DONTNEED);
> }
> }
> {code}
> We should set GLOG_drop_log_memory=false prior to making our call to
> google::InitGoogleLogging, to avoid others running into this issue.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Created] (MESOS-4476) Set ReservationInfo for static reservations
Neil Conway created MESOS-4476:
--
Summary: Set ReservationInfo for static reservations
Key: MESOS-4476
URL: https://issues.apache.org/jira/browse/MESOS-4476
Project: Mesos
Issue Type: Improvement
Components: master
Reporter: Neil Conway
Currently, we do not set {{ReservationInfo}} for static reservations. Moreover,
we suggest that frameworks determine if a resource offer contains dynamically
reserved resources by checking whether the {{ReservationInfo}} field is set.
This means that if we want to add new reservation-specific information (e.g.,
labels), we can't put those fields into {{ReservationInfo}} if we want them to
be supported by static reservations.
Proposed plan:
* Continue to add reservation-specific information to {{ReservationInfo}},
which means it won't be supported for static reservations
* Set {{ReservationInfo}} for both static and dynamic reservations
* Introduce a new enum to describe the type of the reservation, and encourage
frameworks to use this field to check for whether a resource offer has a
reservation.
The tricky part is the backward compatibility story.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Created] (MESOS-4478) ReviewBot seemed to be crashing ReviewBoard server when posting large reviews
Vinod Kone created MESOS-4478: - Summary: ReviewBot seemed to be crashing ReviewBoard server when posting large reviews Key: MESOS-4478 URL: https://issues.apache.org/jira/browse/MESOS-4478 Project: Mesos Issue Type: Bug Reporter: Vinod Kone Assignee: Vinod Kone The bot is currently tripping on this review https://reviews.apache.org/r/42506/ (see builds #10973 to #10978). [~jfarrell] looked at the server logs and said he saw 'MySQL going away' message when the mesos bot was making these requests. I think that error is a bit misleading because it happens only for this review (which has a huge error log due to bad patch). The bot has successfully posted reviews for other review requests which had no error log (good patch). One way to fix this would be to just post a tail of the error log (and perhaps link to Jenkins Console or some other service for the longer error text). -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (MESOS-4453) CMAKE: include directores rules' bug
kreats created MESOS-4453: - Summary: CMAKE: include directores rules' bug Key: MESOS-4453 URL: https://issues.apache.org/jira/browse/MESOS-4453 Project: Mesos Issue Type: Bug Components: master Affects Versions: 0.27.0 Reporter: kreats -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (MESOS-4156) Speed up FetcherCacheTest.* and FetcherCacheHttpTest.*
[
https://issues.apache.org/jira/browse/MESOS-4156?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Bernd Mathiske updated MESOS-4156:
--
Shepherd: Bernd Mathiske
> Speed up FetcherCacheTest.* and FetcherCacheHttpTest.*
> --
>
> Key: MESOS-4156
> URL: https://issues.apache.org/jira/browse/MESOS-4156
> Project: Mesos
> Issue Type: Epic
> Components: technical debt, test
>Reporter: Alexander Rukletsov
>Assignee: haosdent
>Priority: Minor
> Labels: mesosphere, newbie++, tech-debt
>
> Execution times on Mac OS 10.10.4:
> {code}
> FetcherCacheTest.LocalUncached (2417 ms)
> FetcherCacheTest.LocalCached (2476 ms)
> FetcherCacheTest.LocalUncachedExtract (2496 ms)
> FetcherCacheTest.LocalCachedExtract (2471 ms)
> FetcherCacheTest.SimpleEviction (4451 ms)
> FetcherCacheTest.FallbackFromEviction (2483 ms)
> FetcherCacheTest.RemoveLRUCacheEntries (3422 ms)
> FetcherCacheHttpTest.HttpCachedSerialized (2490 ms)
> FetcherCacheHttpTest.HttpCachedConcurrent (1032 ms)
> FetcherCacheHttpTest.HttpMixed (1022 ms)
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (MESOS-3945) Add operator documentation for /weight endpoint
[ https://issues.apache.org/jira/browse/MESOS-3945?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15112099#comment-15112099 ] Adam B commented on MESOS-3945: --- We need this done before we can really consider the Dynamic Weights feature complete (and so users will actually know how to use it). > Add operator documentation for /weight endpoint > --- > > Key: MESOS-3945 > URL: https://issues.apache.org/jira/browse/MESOS-3945 > Project: Mesos > Issue Type: Task >Reporter: James Wang > > This JIRA ticket will update the related doc to apply to dynamic weights, and > add an new operator guide for dynamic weights which describes basic usage of > the /weights endpoint. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (MESOS-4453) CMAKE: include directores rules' bug
[
https://issues.apache.org/jira/browse/MESOS-4453?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15112106#comment-15112106
]
kreats commented on MESOS-4453:
---
in mesos/src/uri/fetcher.cpp file, line 23:
```
#include "uri/fetcher.hpp"
```
It should use local directory file "fetcher.hpp",
there is a file with the same at "/mesos/include/mesos/uri/fetcher.hpp",
however, their contents are different.
and in the CMAKE file "mesos/src/slave/cmake/SlaveConfigure.cmake" line 34:
```
set(AGENT_INCLUDE_DIRS
${AGENT_INCLUDE_DIRS}
${MESOS_PUBLIC_INCLUDE_DIR}
# Contains (e.g.) compiled *.pb.h files.
${MESOS_BIN_INCLUDE_DIR}
${MESOS_BIN_INCLUDE_DIR}/mesos
${MESOS_BIN_SRC_DIR}
${MESOS_SRC_DIR}
)
```
It sets include searching path should begin from ""/mesos/include/" first, this
will occur an error.
we may put "${MESOS_SRC_DIR}" before ${MESOS_PUBLIC_INCLUDE_DIR}, but i an not
sure whether it's a good solution or not.
> CMAKE: include directores rules' bug
>
>
> Key: MESOS-4453
> URL: https://issues.apache.org/jira/browse/MESOS-4453
> Project: Mesos
> Issue Type: Bug
> Components: master
>Affects Versions: 0.27.0
>Reporter: kreats
>
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (MESOS-4444) Design doc for reservation labels
[ https://issues.apache.org/jira/browse/MESOS-?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15113326#comment-15113326 ] Neil Conway commented on MESOS-: The design doc for reservation labels can be found here: https://docs.google.com/document/d/1HdS4TxmfMkMR_2mvOHZR-LLmyLNdyqRrPBdiGCp6-w8/edit# > Design doc for reservation labels > - > > Key: MESOS- > URL: https://issues.apache.org/jira/browse/MESOS- > Project: Mesos > Issue Type: Bug > Components: general >Reporter: Neil Conway >Assignee: Neil Conway > Labels: mesosphere, reservations > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (MESOS-4480) Update the mesos architecture doc.
[ https://issues.apache.org/jira/browse/MESOS-4480?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Anand Mazumdar updated MESOS-4480: -- Description: We currently have an architecture doc located [here|http://mesos.apache.org/documentation/latest/architecture/]. This document is pretty outdated. It does not list the following things among others: - Mesos containerizer. - Master registry. - Slave checkpointed state. - Log replicas. It would be a good idea to update the document to capture these. Also, we can update the various images to reflect these new components. was: We currently have an architecture doc located [here] (http://mesos.apache.org/documentation/latest/architecture/). This document is pretty outdated. It does not list the following things among others: - Mesos containerizer. - Master registry. - Slave checkpointed state. - Log replicas. It would be a good idea to update the document to capture these. Also, we can update the various images to reflect these new components. > Update the mesos architecture doc. > -- > > Key: MESOS-4480 > URL: https://issues.apache.org/jira/browse/MESOS-4480 > Project: Mesos > Issue Type: Task >Reporter: Anand Mazumdar > Labels: documentation, mesosphere > > We currently have an architecture doc located > [here|http://mesos.apache.org/documentation/latest/architecture/]. This > document is pretty outdated. It does not list the following things among > others: > - Mesos containerizer. > - Master registry. > - Slave checkpointed state. > - Log replicas. > It would be a good idea to update the document to capture these. Also, we can > update the various images to reflect these new components. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (MESOS-4476) Set ReservationInfo for static reservations
[
https://issues.apache.org/jira/browse/MESOS-4476?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15113617#comment-15113617
]
Guangya Liu commented on MESOS-4476:
Then in this ticket, you mean that both static and dynamic reservation can set
ReservationInfo, and introduce a new enum to distinguish for static and dynamic
reservation, right?
> Set ReservationInfo for static reservations
> ---
>
> Key: MESOS-4476
> URL: https://issues.apache.org/jira/browse/MESOS-4476
> Project: Mesos
> Issue Type: Improvement
> Components: master
>Reporter: Neil Conway
> Labels: mesosphere, reservations
>
> Currently, we do not set {{ReservationInfo}} for static reservations.
> Moreover, we suggest that frameworks determine if a resource offer contains
> dynamically reserved resources by checking whether the {{ReservationInfo}}
> field is set. This means that if we want to add new reservation-specific
> information (e.g., labels), we can't put those fields into
> {{ReservationInfo}} if we want them to be supported by static reservations.
> Proposed plan:
> * Continue to add reservation-specific information to {{ReservationInfo}},
> which means it won't be supported for static reservations
> * Set {{ReservationInfo}} for both static and dynamic reservations
> * Introduce a new enum to describe the type of the reservation, and encourage
> frameworks to use this field to check for whether a resource offer has a
> reservation.
> The tricky part is the backward compatibility story.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (MESOS-4476) Set ReservationInfo for static reservations
[
https://issues.apache.org/jira/browse/MESOS-4476?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15113611#comment-15113611
]
Neil Conway commented on MESOS-4476:
{{principal}} in {{ReservationInfo}} will be optional in 0.27+ anyway, so I
think that shouldn't be a problem.
> Set ReservationInfo for static reservations
> ---
>
> Key: MESOS-4476
> URL: https://issues.apache.org/jira/browse/MESOS-4476
> Project: Mesos
> Issue Type: Improvement
> Components: master
>Reporter: Neil Conway
> Labels: mesosphere, reservations
>
> Currently, we do not set {{ReservationInfo}} for static reservations.
> Moreover, we suggest that frameworks determine if a resource offer contains
> dynamically reserved resources by checking whether the {{ReservationInfo}}
> field is set. This means that if we want to add new reservation-specific
> information (e.g., labels), we can't put those fields into
> {{ReservationInfo}} if we want them to be supported by static reservations.
> Proposed plan:
> * Continue to add reservation-specific information to {{ReservationInfo}},
> which means it won't be supported for static reservations
> * Set {{ReservationInfo}} for both static and dynamic reservations
> * Introduce a new enum to describe the type of the reservation, and encourage
> frameworks to use this field to check for whether a resource offer has a
> reservation.
> The tricky part is the backward compatibility story.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (MESOS-4476) Set ReservationInfo for static reservations
[
https://issues.apache.org/jira/browse/MESOS-4476?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15113608#comment-15113608
]
Guangya Liu commented on MESOS-4476:
There is a patch doing similar thing as what you request:
https://reviews.apache.org/r/40375/
The background for this patch is that the mesos now support only one type of
revocable resources: the oversubscribed resources. But in MESOS-1607 we are
introducing a new type of revocable resources named as {{allocation slack}} and
rename the old oversubscribed resources as {{usage slack}}, the patch also kept
the backward compatibility issue.
One question for {{Set ReservationInfo for both static and dynamic
reservations}}, the static reservation do not request {{principal}}, so what
will be set for {{ReservationInfo}} wit static reservation?
> Set ReservationInfo for static reservations
> ---
>
> Key: MESOS-4476
> URL: https://issues.apache.org/jira/browse/MESOS-4476
> Project: Mesos
> Issue Type: Improvement
> Components: master
>Reporter: Neil Conway
> Labels: mesosphere, reservations
>
> Currently, we do not set {{ReservationInfo}} for static reservations.
> Moreover, we suggest that frameworks determine if a resource offer contains
> dynamically reserved resources by checking whether the {{ReservationInfo}}
> field is set. This means that if we want to add new reservation-specific
> information (e.g., labels), we can't put those fields into
> {{ReservationInfo}} if we want them to be supported by static reservations.
> Proposed plan:
> * Continue to add reservation-specific information to {{ReservationInfo}},
> which means it won't be supported for static reservations
> * Set {{ReservationInfo}} for both static and dynamic reservations
> * Introduce a new enum to describe the type of the reservation, and encourage
> frameworks to use this field to check for whether a resource offer has a
> reservation.
> The tricky part is the backward compatibility story.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (MESOS-4418) Create a test macro to advance Clock for Future
[
https://issues.apache.org/jira/browse/MESOS-4418?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15112683#comment-15112683
]
Anand Mazumdar commented on MESOS-4418:
---
[~haosd...@gmail.com] Thanks for filing the issue and working on this. Two
minor points:
- Can we add some more context in the description? Also, we avoid JIRA
{{Summary}} that directly outlines the solution instead of the generic problem
that led to the issue being created in the first place.
- Can you also find a shepherd for this?
> Create a test macro to advance Clock for Future
> ---
>
> Key: MESOS-4418
> URL: https://issues.apache.org/jira/browse/MESOS-4418
> Project: Mesos
> Issue Type: Improvement
>Reporter: haosdent
>Assignee: haosdent
> Labels: test
>
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Comment Edited] (MESOS-4418) Create a test macro to advance Clock for Future
[
https://issues.apache.org/jira/browse/MESOS-4418?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15112683#comment-15112683
]
Anand Mazumdar edited comment on MESOS-4418 at 1/22/16 5:03 PM:
[~haosd...@gmail.com] Thanks for filing the issue and working on this. Two
minor points:
- Can we add some more context in the description? Also, we avoid JIRA
{{Summary}} that directly outlines the solution instead of the generic problem
that led to the issue being created in the first place (unless it's obvious).
- Can you also find a shepherd for this?
was (Author: anandmazumdar):
[~haosd...@gmail.com] Thanks for filing the issue and working on this. Two
minor points:
- Can we add some more context in the description? Also, we avoid JIRA
{{Summary}} that directly outlines the solution instead of the generic problem
that led to the issue being created in the first place.
- Can you also find a shepherd for this?
> Create a test macro to advance Clock for Future
> ---
>
> Key: MESOS-4418
> URL: https://issues.apache.org/jira/browse/MESOS-4418
> Project: Mesos
> Issue Type: Improvement
>Reporter: haosdent
>Assignee: haosdent
> Labels: test
>
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (MESOS-4446) Please add an ability to set Docker labels based on TaskStatus labels
[ https://issues.apache.org/jira/browse/MESOS-4446?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15112401#comment-15112401 ] Abhishek Dasgupta commented on MESOS-4446: -- Hi Gennady, Those labels can be passed also with label parameters while creating a docker container(Atlease marathon works this way). Can you be specific if you want anything else? > Please add an ability to set Docker labels based on TaskStatus labels > - > > Key: MESOS-4446 > URL: https://issues.apache.org/jira/browse/MESOS-4446 > Project: Mesos > Issue Type: Story > Components: docker >Reporter: Gennady Feldman > > So looks like MESOS-3076 added support for Labels to TaskStatus. Would it be > possible to pass those onto the docker container? > This would really help with doing "docker inspect" on the mesos-slave nodes > as well as allow us to better collect docker metrics about the > tasks/containers that are currently running on the slave. > docker supports labels out of the box. See here: > https://docs.docker.com/engine/userguide/labels-custom-metadata/ -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (MESOS-4446) Please add an ability to set Docker labels based on TaskStatus labels
[ https://issues.apache.org/jira/browse/MESOS-4446?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15112491#comment-15112491 ] Gennady Feldman commented on MESOS-4446: Hi Abhishek, This is actually what I am trying to get working. It's not working for me. In Marathon i set labels (in the labels section, docker section doesn't have configuration for this). When I actually login to the Mesos Slave and do "docker inspect" the Labels are empty. I am using Mesos 0.25 and Marathon 0.13. Looking through the code here: https://github.com/apache/mesos/blob/master/src/docker/docker.cpp#L471 you notice that labels are not actually passed to docker. > Please add an ability to set Docker labels based on TaskStatus labels > - > > Key: MESOS-4446 > URL: https://issues.apache.org/jira/browse/MESOS-4446 > Project: Mesos > Issue Type: Story > Components: docker >Reporter: Gennady Feldman > > So looks like MESOS-3076 added support for Labels to TaskStatus. Would it be > possible to pass those onto the docker container? > This would really help with doing "docker inspect" on the mesos-slave nodes > as well as allow us to better collect docker metrics about the > tasks/containers that are currently running on the slave. > docker supports labels out of the box. See here: > https://docs.docker.com/engine/userguide/labels-custom-metadata/ -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (MESOS-4446) Please add an ability to set Docker labels based on TaskStatus labels
[ https://issues.apache.org/jira/browse/MESOS-4446?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15112506#comment-15112506 ] Abhishek Dasgupta commented on MESOS-4446: -- Exactly. The label section in marathon are to set the label for marathon app (be it docker or any other standalone app). If you want to put a docker label, in the parameter section of docker container settings in marathon(Right below "Port Mapping" section), put "label" as key and "com.something.something=something" as value. Then you create the app and do a docker inspect, you will see the label there. > Please add an ability to set Docker labels based on TaskStatus labels > - > > Key: MESOS-4446 > URL: https://issues.apache.org/jira/browse/MESOS-4446 > Project: Mesos > Issue Type: Story > Components: docker >Reporter: Gennady Feldman > > So looks like MESOS-3076 added support for Labels to TaskStatus. Would it be > possible to pass those onto the docker container? > This would really help with doing "docker inspect" on the mesos-slave nodes > as well as allow us to better collect docker metrics about the > tasks/containers that are currently running on the slave. > docker supports labels out of the box. See here: > https://docs.docker.com/engine/userguide/labels-custom-metadata/ -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (MESOS-4454) Create common sha512 compute utility function.
Jojy Varghese created MESOS-4454: Summary: Create common sha512 compute utility function. Key: MESOS-4454 URL: https://issues.apache.org/jira/browse/MESOS-4454 Project: Mesos Issue Type: Bug Components: containerization Reporter: Jojy Varghese Assignee: Jojy Varghese Add common utility function for computing digests. Start with `sha512` since its immediately needed by appc image fetcher. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (MESOS-4455) Error on scrolling the page horizontally on website
Disha Singh created MESOS-4455: -- Summary: Error on scrolling the page horizontally on website Key: MESOS-4455 URL: https://issues.apache.org/jira/browse/MESOS-4455 Project: Mesos Issue Type: Bug Components: project website Reporter: Disha Singh Priority: Minor When the page :http://mesos.apache.org/documentation/latest/architecture/ is scrolled horizontally the naval bar at the top discontinues creating a bad look. Also, this is occuring only because of the unadjusted size of the picture architecture3.jpg. This makes two finger-scrolling non-pleasant. one of the two things can be done: Either fix the image's size OR Fix the naval bar styling in the CSS file itself to prevent any future issues.(Better option) -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (MESOS-4481) Update MESOS-MAVEN_README
Disha Singh created MESOS-4481: -- Summary: Update MESOS-MAVEN_README Key: MESOS-4481 URL: https://issues.apache.org/jira/browse/MESOS-4481 Project: Mesos Issue Type: Documentation Components: build Reporter: Disha Singh Priority: Critical https://github.com/apache/mesos/blob/master/src/java/MESOS-MAVEN-README is outdated and still mentions version-0.19.0 Also, maven causes error while building the project when run on proxy. Clearly include how to fix that issue , if it occurs. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (MESOS-4479) Implement reservation labels
Neil Conway created MESOS-4479: -- Summary: Implement reservation labels Key: MESOS-4479 URL: https://issues.apache.org/jira/browse/MESOS-4479 Project: Mesos Issue Type: Improvement Components: master Reporter: Neil Conway Assignee: Neil Conway -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (MESOS-4480) Update the mesos architecture doc.
Anand Mazumdar created MESOS-4480: - Summary: Update the mesos architecture doc. Key: MESOS-4480 URL: https://issues.apache.org/jira/browse/MESOS-4480 Project: Mesos Issue Type: Task Reporter: Anand Mazumdar We currently have an architecture doc located [here] (http://mesos.apache.org/documentation/latest/architecture/). This document is pretty outdated. It does not list the following things among others: - Mesos containerizer. - Master registry. - Slave checkpointed state. - Log replicas. It would be a good idea to update the document to capture these. Also, we can update the various images to reflect these new components. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (MESOS-4478) ReviewBot seemed to be crashing ReviewBoard server when posting large reviews
[ https://issues.apache.org/jira/browse/MESOS-4478?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vinod Kone updated MESOS-4478: -- Story Points: 2 (was: 3) > ReviewBot seemed to be crashing ReviewBoard server when posting large reviews > - > > Key: MESOS-4478 > URL: https://issues.apache.org/jira/browse/MESOS-4478 > Project: Mesos > Issue Type: Bug >Reporter: Vinod Kone >Assignee: Vinod Kone > Fix For: 0.27.0 > > > The bot is currently tripping on this review > https://reviews.apache.org/r/42506/ (see builds #10973 to #10978). > [~jfarrell] looked at the server logs and said he saw 'MySQL going away' > message when the mesos bot was making these requests. I think that error is a > bit misleading because it happens only for this review (which has a huge > error log due to bad patch). The bot has successfully posted reviews for > other review requests which had no error log (good patch). > One way to fix this would be to just post a tail of the error log (and > perhaps link to Jenkins Console or some other service for the longer error > text). -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (MESOS-3413) Docker containerizer does not symlink persistent volumes into sandbox
[
https://issues.apache.org/jira/browse/MESOS-3413?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Adam B updated MESOS-3413:
--
Labels: docker mesosphere persistent-volumes (was: )
> Docker containerizer does not symlink persistent volumes into sandbox
> -
>
> Key: MESOS-3413
> URL: https://issues.apache.org/jira/browse/MESOS-3413
> Project: Mesos
> Issue Type: Bug
> Components: containerization, docker, slave
>Affects Versions: 0.23.0
>Reporter: Max Neunhöffer
>Assignee: Zhitao Li
> Labels: docker, mesosphere, persistent-volumes
> Original Estimate: 1h
> Remaining Estimate: 1h
>
> For the ArangoDB framework I am trying to use the persistent primitives.
> nearly all is working, but I am missing a crucial piece at the end: I have
> successfully created a persistent disk resource and have set the persistence
> and volume information in the DiskInfo message. However, I do not see any way
> to find out what directory on the host the mesos slave has reserved for us. I
> know it is ${MESOS_SLAVE_WORKDIR}/volumes/roles//_ but we
> have no way to query this information anywhere. The docker containerizer does
> not automatically mount this directory into our docker container, or symlinks
> it into our sandbox. Therefore, I have essentially no access to it. Note that
> the mesos containerizer (which I cannot use for other reasons) seems to
> create a symlink in the sandbox to the actual path for the persistent volume.
> With that, I could mount the volume into our docker container and all would
> be well.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (MESOS-2444) Update mesos presentations documentation
[ https://issues.apache.org/jira/browse/MESOS-2444?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15113501#comment-15113501 ] Disha Singh commented on MESOS-2444: https://reviews.apache.org/r/42490/ > Update mesos presentations documentation > > > Key: MESOS-2444 > URL: https://issues.apache.org/jira/browse/MESOS-2444 > Project: Mesos > Issue Type: Task > Components: documentation, project website >Reporter: Dave Lester >Assignee: Disha Singh > Labels: newbie > > The list of Mesos presentations in `docs/mesos-presentations.md` only > reflects presentations as of mid-2014 and could be more-comprehensive. It > would be great to include additional presentations (both slides and videos) > on this page. > Optionally, the display of content on this page could be improved -- > potentially using a table and generating thumbnails for each video/slideshow > to make it more visual. If this route is taken, images can be added to > docs/images; ideally within a subfolder to organize them. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (MESOS-3843) Audit `src/CMakelists.txt` to make sure we're compiling everything we need to build the agent binary.
[ https://issues.apache.org/jira/browse/MESOS-3843?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Artem Harutyunyan updated MESOS-3843: - Labels: mesosphere windows-mvp (was: ) > Audit `src/CMakelists.txt` to make sure we're compiling everything we need to > build the agent binary. > - > > Key: MESOS-3843 > URL: https://issues.apache.org/jira/browse/MESOS-3843 > Project: Mesos > Issue Type: Task > Components: cmake >Reporter: Alex Clemmer >Assignee: Diana Arroyo > Labels: mesosphere, windows-mvp > > `src/CMakeLists.txt` has fallen into some state of disrepair. There are some > source files that seem to be missing (e.g., the `src/launcher/` and > `src/linux`/ directories), so the first step is to audit the source file to > make sure everything we need is there. Likely this will mean looking at the > corresponding `src/Makefile.am` to see that's missing. > Once we understand the limitations of the current build, we can fan out more > tickets or proceed to generating the agent binary, as well as the master. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
