[jira] [Assigned] (MESOS-6649) Mesos build fails when run configure with network-isolator
[ https://issues.apache.org/jira/browse/MESOS-6649?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] haosdent reassigned MESOS-6649: --- Assignee: haosdent > Mesos build fails when run configure with network-isolator > --- > > Key: MESOS-6649 > URL: https://issues.apache.org/jira/browse/MESOS-6649 > Project: Mesos > Issue Type: Bug >Reporter: Lax >Assignee: haosdent > > '../configure --with-network-isolator' is failing with error(s) on Centos > 7.2 distributions. > Issues seen in order > 1. Please install libnl3 (version 3.2.26 or higher ) > Issue is there is none rpms available with version > 3.2.21 for Centos 7 > distribution. Only workaround was to download libnl3 from > https://github.com/thom311/libnl and install it manually > 2. After the above fix, ran into 'We need CRAM-MD5 support for SASL > authentication' on rerunning the configure with network isolatoer. However > the issue was not seen if just configure was run -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (MESOS-6649) Mesos build fails when run configure with network-isolator
Lax created MESOS-6649: -- Summary: Mesos build fails when run configure with network-isolator Key: MESOS-6649 URL: https://issues.apache.org/jira/browse/MESOS-6649 Project: Mesos Issue Type: Bug Reporter: Lax '../configure --with-network-isolator' is failing with error(s) on Centos 7.2 distributions. Issues seen in order 1. Please install libnl3 (version 3.2.26 or higher ) Issue is there is none rpms available with version > 3.2.21 for Centos 7 distribution. Only workaround was to download libnl3 from https://github.com/thom311/libnl and install it manually 2. After the above fix, ran into 'We need CRAM-MD5 support for SASL authentication' on rerunning the configure with network isolatoer. However the issue was not seen if just configure was run -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (MESOS-5994) Add Windows support for modules
[
https://issues.apache.org/jira/browse/MESOS-5994?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15703667#comment-15703667
]
Joseph Wu commented on MESOS-5994:
--
{code}
commit 58f63747f185995d7f9cbfca9d240e2d60053184
Author: Joseph Wu
Date: Mon Nov 28 15:37:26 2016 -0800
Windows: Disable modules tests and related helpers.
Building and linking modules has some extra challenges on Windows
(see MESOS-5994).
This patch #ifdef's some module-specific tests on Windows.
NOTE: Most module tests are already parameterized to run the same code,
once as a built-in class and once as a module.
Review: https://reviews.apache.org/r/50827/
{code}
> Add Windows support for modules
>
>
> Key: MESOS-5994
> URL: https://issues.apache.org/jira/browse/MESOS-5994
> Project: Mesos
> Issue Type: Improvement
> Components: modules
> Environment: Windows
>Reporter: Joseph Wu
>Priority: Minor
> Labels: agent, master, mesos, mesosphere, windows
>
> Modules are currently not supported on Windows due to a couple limitations:
> * GCC and Clang export all symbols to shared libraries by default. MSVC has
> the opposite behavior and does not export any symbols by default. To
> properly create a shared library on Windows, one must
> {{__declspec(dllexport)}} every single exposed function/class.
> * CMake 3.4+ has utilities for auto-generating exports, but upgrading the
> CMake requirement has other version incompatibilities.
> * We can't load a statically linked module due to a runtime check in the
> protobuf library.
> For now, module-related code is not compiled on Windows.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Comment Edited] (MESOS-6473) Build support for ATTACH_CONTAINER_OUTPUT into the Agent API in Mesos
[ https://issues.apache.org/jira/browse/MESOS-6473?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15692583#comment-15692583 ] Vinod Kone edited comment on MESOS-6473 at 11/28/16 10:20 PM: -- https://reviews.apache.org/r/54093/ https://reviews.apache.org/r/54039/ https://reviews.apache.org/r/53994/ https://reviews.apache.org/r/54049/ https://reviews.apache.org/r/53995/ was (Author: adam-mesos): https://reviews.apache.org/r/53995/ > Build support for ATTACH_CONTAINER_OUTPUT into the Agent API in Mesos > - > > Key: MESOS-6473 > URL: https://issues.apache.org/jira/browse/MESOS-6473 > Project: Mesos > Issue Type: Task >Reporter: Kevin Klues >Assignee: Vinod Kone > Labels: debugging, mesosphere > > Coupled with the ATTACH_CONTAINER_INPUT call, this call will attach a remote > client to the the input/output of the entrypoint of a container. All > input/output data will be packed into I/O messages and interleaved with > control messages sent between a client and the agent. A single chunked > request will be used to stream messages to the agent over the input stream, > and a single chunked response will be used to stream messages to the client > over the output stream. > This call will integrate with the I/O switchboard to stream data between the > container and the HTTP stream. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (MESOS-6648) MesosContainerizer launch helper should take ContainerLaunchInfo.
[ https://issues.apache.org/jira/browse/MESOS-6648?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kevin Klues updated MESOS-6648: --- Labels: mesosphere (was: ) > MesosContainerizer launch helper should take ContainerLaunchInfo. > - > > Key: MESOS-6648 > URL: https://issues.apache.org/jira/browse/MESOS-6648 > Project: Mesos > Issue Type: Improvement >Reporter: Jie Yu >Assignee: Jie Yu > Labels: mesosphere > > Currently, the launch helper takes various flags from MesosContainerizer to > launch the container. This makes it very hard to add more parameters to the > launch helper. To simplify that, MesosContainerizer can pass > 'ContainerLaunchInfo' to the launch helper instead. 'ContainerLaunchInfo' is > also the protobuf message returned by isolators during 'prepare()'. This > makes it very easy to merge them and send it to the launch helper. More > importantly, this makes it very easy to add more parameters to the launch > helper in the future. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (MESOS-6625) Expose container id in ContainerStatus in DockerContainerizer.
[ https://issues.apache.org/jira/browse/MESOS-6625?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kevin Klues updated MESOS-6625: --- Labels: debugging mesosphere (was: ) > Expose container id in ContainerStatus in DockerContainerizer. > -- > > Key: MESOS-6625 > URL: https://issues.apache.org/jira/browse/MESOS-6625 > Project: Mesos > Issue Type: Bug >Reporter: Jie Yu >Assignee: Jie Yu > Labels: debugging, mesosphere > Fix For: 1.2.0 > > > Currently, the container id is only exposed for MesosContainerizer. We should > make it consistent in DockerContainerizer. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (MESOS-6640) mesos-local doesn't hande --work_dir correctly.
[
https://issues.apache.org/jira/browse/MESOS-6640?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15702918#comment-15702918
]
Artem Harutyunyan commented on MESOS-6640:
--
Thanks [~haosd...@gmail.com]!
> mesos-local doesn't hande --work_dir correctly.
> ---
>
> Key: MESOS-6640
> URL: https://issues.apache.org/jira/browse/MESOS-6640
> Project: Mesos
> Issue Type: Bug
>Reporter: Artem Harutyunyan
> Labels: beginner, newbie
> Fix For: 1.2.0
>
>
> After {{work_dir}} became a required command line flag for {{mesos-agent}}
> it's only possible to launch {{mesos-local}} if {{MESOS_WORK_DIR}}
> environment variable is set. Using {{work_dir}} that {{mesos-local}}
> presumably allows to set does not work:
> {code}
> ~/src/mesos-install $ ./bin/mesos-local --work_dir=/tmp/foo
> I1124 13:26:42.609170 2103623680 replica.cpp:776] Replica recovered with log
> positions 0 -> 0 with 1 holes and 0 unlearned
> I1124 13:26:42.610047 1601536 recover.cpp:451] Starting replica recovery
> I1124 13:26:42.610213 1601536 recover.cpp:477] Replica is in EMPTY status
> I1124 13:26:42.615016 2138112 replica.cpp:673] Replica in EMPTY status
> received a broadcasted recover request from __req_res__(1)@10.204.3.193:5050
> I1124 13:26:42.617058 1064960 master.cpp:380] Master
> 73762f1c-314b-4e7c-a7e9-b820bfd9dde7 (xkcd2358.railnet.train) started on
> 10.204.3.193:5050
> I1124 13:26:42.617082 1064960 master.cpp:382] Flags at startup:
> --agent_ping_timeout="15secs" --agent_reregister_timeout="10mins"
> --allocation_interval="1secs" --allocator="HierarchicalDRF"
> --authenticate_agents="false" --authenticate_frameworks="false"
> --authenticate_http_frameworks="false" --authenticate_http_readonly="false"
> --authenticate_http_readwrite="false" --authenticators="crammd5"
> --authorizers="local" --framework_sorter="drf" --help="false"
> --hostname_lookup="true" --http_authenticators="basic"
> --initialize_driver_logging="true" --log_auto_initialize="true"
> --logbufsecs="0" --logging_level="INFO" --max_agent_ping_timeouts="5"
> --max_completed_frameworks="50" --max_completed_tasks_per_framework="1000"
> --quiet="false" --recovery_agent_removal_limit="100%"
> --registry="replicated_log" --registry_fetch_timeout="1mins"
> --registry_gc_interval="15mins" --registry_max_agent_age="2weeks"
> --registry_max_agent_count="102400" --registry_store_timeout="20secs"
> --registry_strict="false" --root_submissions="true" --user_sorter="drf"
> --version="false"
> --webui_dir="/Users/xkcd2358/src/mesos-install/share/mesos/webui"
> --work_dir="/tmp/foo" --zk_session_timeout="10secs"
> I1124 13:26:42.617246 2138112 recover.cpp:197] Received a recover response
> from a replica in EMPTY status
> I1124 13:26:42.617292 1064960 master.cpp:434] Master allowing unauthenticated
> frameworks to register
> I1124 13:26:42.617301 1064960 master.cpp:448] Master allowing unauthenticated
> agents to register
> I1124 13:26:42.617306 1064960 master.cpp:462] Master allowing HTTP frameworks
> to register without authentication
> I1124 13:26:42.617316 1064960 master.cpp:504] Using default 'crammd5'
> authenticator
> W1124 13:26:42.617328 1064960 authenticator.cpp:512] No credentials provided,
> authentication requests will be refused
> I1124 13:26:42.617334 1064960 authenticator.cpp:519] Initializing server SASL
> Failed to start a local cluster while loading agent flags from the
> environment: Flag 'work_dir' is required, but it was not provided
> ~/src/mesos-install $
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (MESOS-5368) Consider introducing persistent agent ID
[
https://issues.apache.org/jira/browse/MESOS-5368?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15702916#comment-15702916
]
Deshi Xiao commented on MESOS-5368:
---
this issue MESOS-1739
> Consider introducing persistent agent ID
>
>
> Key: MESOS-5368
> URL: https://issues.apache.org/jira/browse/MESOS-5368
> Project: Mesos
> Issue Type: Improvement
>Reporter: Neil Conway
> Labels: mesosphere
>
> Currently, agent IDs identify a single "session" by an agent: that is, an
> agent receives an agent ID when it registers with the master; it reuses that
> agent ID if it disconnects and successfully reregisters; if the agent shuts
> down and restarts, it registers anew and receives a new agent ID.
> It would be convenient to have a "persistent agent ID" that remains the same
> for the duration of a given agent {{work_dir}}. This would mean that a given
> persistent volume would not migrate between different persistent agent IDs
> over time, for example (see MESOS-4894). If we supported permanently removing
> an agent from the cluster (i.e., the {{work_dir}} and any volumes used by the
> agent will never be reused), we could use the persistent agent ID to report
> which agent has been removed.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Assigned] (MESOS-6569) MesosContainerizer/DefaultExecutorTest.KillTask/0 failing on ASF CI
[
https://issues.apache.org/jira/browse/MESOS-6569?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Benjamin Bannier reassigned MESOS-6569:
---
Assignee: Benjamin Bannier
> MesosContainerizer/DefaultExecutorTest.KillTask/0 failing on ASF CI
> ---
>
> Key: MESOS-6569
> URL: https://issues.apache.org/jira/browse/MESOS-6569
> Project: Mesos
> Issue Type: Bug
>Affects Versions: 1.1.0
> Environment:
> https://builds.apache.org/job/Mesos/BUILDTOOL=autotools,COMPILER=gcc,CONFIGURATION=--verbose,ENVIRONMENT=GLOG_v=1%20MESOS_VERBOSE=1,OS=ubuntu:14.04,label_exp=(docker%7C%7CHadoop)&&(!ubuntu-us1)&&(!ubuntu-6)&&(!ubuntu-eu2)/
>Reporter: Yan Xu
>Assignee: Benjamin Bannier
> Labels: flaky, newbie
>
> {noformat:title=}
> [ RUN ] MesosContainerizer/DefaultExecutorTest.KillTask/0
> I1110 01:20:11.482097 29700 cluster.cpp:158] Creating default 'local'
> authorizer
> I1110 01:20:11.485241 29700 leveldb.cpp:174] Opened db in 2.774513ms
> I1110 01:20:11.486237 29700 leveldb.cpp:181] Compacted db in 953614ns
> I1110 01:20:11.486299 29700 leveldb.cpp:196] Created db iterator in 24739ns
> I1110 01:20:11.486325 29700 leveldb.cpp:202] Seeked to beginning of db in
> 2300ns
> I1110 01:20:11.486344 29700 leveldb.cpp:271] Iterated through 0 keys in the
> db in 378ns
> I1110 01:20:11.486399 29700 replica.cpp:776] Replica recovered with log
> positions 0 -> 0 with 1 holes and 0 unlearned
> I1110 01:20:11.486933 29733 recover.cpp:451] Starting replica recovery
> I1110 01:20:11.487289 29733 recover.cpp:477] Replica is in EMPTY status
> I1110 01:20:11.488503 29721 replica.cpp:673] Replica in EMPTY status received
> a broadcasted recover request from __req_res__(7318)@172.17.0.3:52462
> I1110 01:20:11.488855 29727 recover.cpp:197] Received a recover response from
> a replica in EMPTY status
> I1110 01:20:11.489398 29729 recover.cpp:568] Updating replica status to
> STARTING
> I1110 01:20:11.490223 29723 leveldb.cpp:304] Persisting metadata (8 bytes) to
> leveldb took 575135ns
> I1110 01:20:11.490284 29732 master.cpp:380] Master
> d28fbae1-c3dc-45fa-8384-32ab9395a975 (3a31be8bf679) started on
> 172.17.0.3:52462
> I1110 01:20:11.490317 29732 master.cpp:382] Flags at startup: --acls=""
> --agent_ping_timeout="15secs" --agent_reregister_timeout="10mins"
> --allocation_interval="1secs" --allocator="HierarchicalDRF"
> --authenticate_agents="true" --authenticate_frameworks="true"
> --authenticate_http_frameworks="true" --authenticate_http_readonly="true"
> --authenticate_http_readwrite="true" --authenticators="crammd5"
> --authorizers="local" --credentials="/tmp/k50x7x/credentials"
> --framework_sorter="drf" --help="false" --hostname_lookup="true"
> --http_authenticators="basic" --http_framework_authenticators="basic"
> --initialize_driver_logging="true" --log_auto_initialize="true"
> --logbufsecs="0" --logging_level="INFO" --max_agent_ping_timeouts="5"
> --max_completed_frameworks="50" --max_completed_tasks_per_framework="1000"
> --quiet="false" --recovery_agent_removal_limit="100%"
> --registry="replicated_log" --registry_fetch_timeout="1mins"
> --registry_gc_interval="15mins" --registry_max_agent_age="2weeks"
> --registry_max_agent_count="102400" --registry_store_timeout="100secs"
> --registry_strict="false" --root_submissions="true" --user_sorter="drf"
> --version="false" --webui_dir="/mesos/mesos-1.2.0/_inst/share/mesos/webui"
> --work_dir="/tmp/k50x7x/master" --zk_session_timeout="10secs"
> I1110 01:20:11.490696 29732 master.cpp:432] Master only allowing
> authenticated frameworks to register
> I1110 01:20:11.490712 29732 master.cpp:446] Master only allowing
> authenticated agents to register
> I1110 01:20:11.490720 29732 master.cpp:459] Master only allowing
> authenticated HTTP frameworks to register
> I1110 01:20:11.490730 29732 credentials.hpp:37] Loading credentials for
> authentication from '/tmp/k50x7x/credentials'
> I1110 01:20:11.490281 29723 replica.cpp:320] Persisted replica status to
> STARTING
> I1110 01:20:11.491210 29732 master.cpp:504] Using default 'crammd5'
> authenticator
> I1110 01:20:11.491225 29720 recover.cpp:477] Replica is in STARTING status
> I1110 01:20:11.491394 29732 http.cpp:895] Using default 'basic' HTTP
> authenticator for realm 'mesos-master-readonly'
> I1110 01:20:11.491621 29732 http.cpp:895] Using default 'basic' HTTP
> authenticator for realm 'mesos-master-readwrite'
> I1110 01:20:11.491770 29732 http.cpp:895] Using default 'basic' HTTP
> authenticator for realm 'mesos-master-scheduler'
> I1110 01:20:11.491937 29732 master.cpp:584] Authorization enabled
> I1110 01:20:11.492276 29725 whitelist_watcher.cpp:77] No whitelist given
> I1110 01:20:11.492310 29723 hierarchical.cpp:149] Initialized hierarchical
> allocator process
> I1110
