[jira] [Updated] (MESOS-7541) Cannot compile without pre-compiled headers on Windows

2017-05-22 Thread Joseph Wu (JIRA) 

 [ 
https://issues.apache.org/jira/browse/MESOS-7541?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Joseph Wu updated MESOS-7541:
-
Description: 
Looks like we messed up an include at some point:

{noformat}
"C:\Users\andschwa\src\mesos\build\src\tests\mesos-tests.vcxproj" (default 
target) (1) ->
"C:\Users\andschwa\src\mesos\build\src\mesos-1.4.0.vcxproj" (default target) 
(4) ->
(ClCompile target) ->
  C:\Users\andschwa\src\mesos\3rdparty\stout\include\stout/ip.hpp(104): error 
C2065: 'AF_INET6': undeclared identifier (compiling source file 
C:\Users\andschwa\src\mesos\src\zookeeper\group.cpp) 
[C:\Users\andschwa\src\mesos\build\src\mesos-1.4.0.vcxproj]
  C:\Users\andschwa\src\mesos\3rdparty\stout\include\stout/ip.hpp(138): error 
C2065: 'AF_INET6': undeclared identifier (compiling source file 
C:\Users\andschwa\src\mesos\src\zookeeper\group.cpp) 
[C:\Users\andschwa\src\mesos\build\src\mesos-1.4.0.vcxproj]
  C:\Users\andschwa\src\mesos\3rdparty\stout\include\stout/ip.hpp(151): error 
C2065: 'AF_INET6': undeclared identifier (compiling source file 
C:\Users\andschwa\src\mesos\src\zookeeper\group.cpp) 
[C:\Users\andschwa\src\mesos\build\src\mesos-1.4.0.vcxproj]
  C:\Users\andschwa\src\mesos\3rdparty\stout\include\stout/ip.hpp(151): error 
C2131: expression did not evaluate to a constant (compiling source file 
C:\Users\andschwa\src\mesos\src\zookeeper\group.cpp) 
[C:\Users\andschwa\src\mesos\build\src\mesos-1.4.0.vcxproj]
  C:\Users\andschwa\src\mesos\3rdparty\stout\include\stout/ip.hpp(151): error 
C2051: case expression not constant (compiling source file 
C:\Users\andschwa\src\mesos\src\zookeeper\group.cpp) 
[C:\Users\andschwa\src\mesos\build\src\mesos-1.4.0.vcxproj]
  C:\Users\andschwa\src\mesos\3rdparty\stout\include\stout/ip.hpp(164): error 
C2065: 'AF_INET6': undeclared identifier (compiling source file 
C:\Users\andschwa\src\mesos\src\zookeeper\group.cpp) 
[C:\Users\andschwa\src\mesos\build\src\mesos-1.4.0.vcxproj]
  C:\Users\andschwa\src\mesos\3rdparty\stout\include\stout/ip.hpp(164): error 
C2131: expression did not evaluate to a constant (compiling source file 
C:\Users\andschwa\src\mesos\src\zookeeper\group.cpp) 
[C:\Users\andschwa\src\mesos\build\src\mesos-1.4.0.vcxproj]
  C:\Users\andschwa\src\mesos\3rdparty\stout\include\stout/ip.hpp(164): error 
C2051: case expression not constant (compiling source file 
C:\Users\andschwa\src\mesos\src\zookeeper\group.cpp) 
[C:\Users\andschwa\src\mesos\build\src\mesos-1.4.0.vcxproj]
  C:\Users\andschwa\src\mesos\3rdparty\stout\include\stout/ip.hpp(233): error 
C2065: 'AF_INET6': undeclared identifier (compiling source file 
C:\Users\andschwa\src\mesos\src\zookeeper\group.cpp) 
[C:\Users\andschwa\src\mesos\build\src\mesos-1.4.0.vcxproj]
  C:\Users\andschwa\src\mesos\3rdparty\stout\include\stout/ip.hpp(233): error 
C2131: expression did not evaluate to a constant (compiling source file 
C:\Users\andschwa\src\mesos\src\zookeeper\group.cpp) 
[C:\Users\andschwa\src\mesos\build\src\mesos-1.4.0.vcxproj]
  C:\Users\andschwa\src\mesos\3rdparty\stout\include\stout/ip.hpp(234): error 
C2065: 'AF_INET6': undeclared identifier (compiling source file 
C:\Users\andschwa\src\mesos\src\zookeeper\group.cpp) 
[C:\Users\andschwa\src\mesos\build\src\mesos-1.4.0.vcxproj]
  C:\Users\andschwa\src\mesos\3rdparty\stout\include\stout/ip.hpp(246): error 
C2065: 'AF_INET6': undeclared identifier (compiling source file 
C:\Users\andschwa\src\mesos\src\zookeeper\group.cpp) 
[C:\Users\andschwa\src\mesos\build\src\mesos-1.4.0.vcxproj]
  C:\Users\andschwa\src\mesos\3rdparty\stout\include\stout/ip.hpp(246): error 
C2512: 'Try': no appropriate default constructor available 
(compiling source file C:\Users\andschwa\src\mesos\src\zookeeper\group.cpp) 
[C:\Users\andschwa\src\mesos\build\src\mesos-1.4.0.vcxproj]
  C:\Users\andschwa\src\mesos\3rdparty\stout\include\stout/ip.hpp(233): error 
C2051: case expression not constant (compiling source file 
C:\Users\andschwa\src\mesos\src\zookeeper\group.cpp) 
[C:\Users\andschwa\src\mesos\build\src\mesos-1.4.0.vcxproj]
  C:\Users\andschwa\src\mesos\3rdparty\stout\include\stout/ip.hpp(293): error 
C2065: 'AF_INET6': undeclared identifier (compiling source file 
C:\Users\andschwa\src\mesos\src\zookeeper\group.cpp) 
[C:\Users\andschwa\src\mesos\build\src\mesos-1.4.0.vcxproj]
  C:\Users\andschwa\src\mesos\3rdparty\stout\include\stout/ip.hpp(293): error 
C2131: expression did not evaluate to a constant (compiling source file 
C:\Users\andschwa\src\mesos\src\zookeeper\group.cpp) 
[C:\Users\andschwa\src\mesos\build\src\mesos-1.4.0.vcxproj]
  C:\Users\andschwa\src\mesos\3rdparty\stout\include\stout/ip.hpp(293): error 
C2051: case expression not constant (compiling source file 
C:\Users\andschwa\src\mesos\src\zookeeper\group.cpp) 
[C:\Users\andschwa\src\mesos\build\src\mesos-1.4.0.vcxproj]
  C:\Users\andschwa\src\mesos\3rdparty\stout\include\stout/ip.hpp(322): error 
C2065: 'AF_INET6': undeclared identifi

[jira] [Comment Edited] (MESOS-7540) Add an agent flag for executor re-register timeout

2017-05-22 Thread Greg Mann (JIRA) 

[ 
https://issues.apache.org/jira/browse/MESOS-7540?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16020001#comment-16020001
 ] 

Greg Mann edited comment on MESOS-7540 at 5/22/17 9:18 PM:
---

Reviews here:
https://reviews.apache.org/r/59460/
https://reviews.apache.org/r/59461/
https://reviews.apache.org/r/59463/


was (Author: greggomann):
Reviews here:
https://reviews.apache.org/r/59460/
https://reviews.apache.org/r/59461/

> Add an agent flag for executor re-register timeout
> --
>
> Key: MESOS-7540
> URL: https://issues.apache.org/jira/browse/MESOS-7540
> Project: Mesos
>  Issue Type: Improvement
>  Components: agent
>Reporter: Greg Mann
>Assignee: Greg Mann
>  Labels: mesosphere
>
> Currently, the executor re-register timeout is hard-coded at 2 seconds. It 
> would be beneficial to allow operators to specify this value.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Updated] (MESOS-7540) Add an agent flag for executor re-register timeout

2017-05-22 Thread Greg Mann (JIRA) 

 [ 
https://issues.apache.org/jira/browse/MESOS-7540?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Greg Mann updated MESOS-7540:
-
Shepherd: Benjamin Mahler

> Add an agent flag for executor re-register timeout
> --
>
> Key: MESOS-7540
> URL: https://issues.apache.org/jira/browse/MESOS-7540
> Project: Mesos
>  Issue Type: Improvement
>  Components: agent
>Reporter: Greg Mann
>Assignee: Greg Mann
>  Labels: mesosphere
>
> Currently, the executor re-register timeout is hard-coded at 2 seconds. It 
> would be beneficial to allow operators to specify this value.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Created] (MESOS-7542) Add executor reconnection retry logic to the agent

2017-05-22 Thread Greg Mann (JIRA) 
Greg Mann created MESOS-7542:


 Summary: Add executor reconnection retry logic to the agent
 Key: MESOS-7542
 URL: https://issues.apache.org/jira/browse/MESOS-7542
 Project: Mesos
  Issue Type: Improvement
  Components: agent, executor
Reporter: Greg Mann


Currently, the agent sends a single {{ReconnectExecutorMessage}} to PID-based 
executors during recovery. It would be more robust to have the agent retry 
these messages until {{executor_reregister_timeout}} has elapsed.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Assigned] (MESOS-7542) Add executor reconnection retry logic to the agent

2017-05-22 Thread Greg Mann (JIRA) 

 [ 
https://issues.apache.org/jira/browse/MESOS-7542?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Greg Mann reassigned MESOS-7542:


Assignee: Greg Mann

> Add executor reconnection retry logic to the agent
> --
>
> Key: MESOS-7542
> URL: https://issues.apache.org/jira/browse/MESOS-7542
> Project: Mesos
>  Issue Type: Improvement
>  Components: agent, executor
>Reporter: Greg Mann
>Assignee: Greg Mann
>  Labels: mesosphere
>
> Currently, the agent sends a single {{ReconnectExecutorMessage}} to PID-based 
> executors during recovery. It would be more robust to have the agent retry 
> these messages until {{executor_reregister_timeout}} has elapsed.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Updated] (MESOS-7418) Add support for file-based secrets

2017-05-22 Thread Kapil Arya (JIRA) 

 [ 
https://issues.apache.org/jira/browse/MESOS-7418?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Kapil Arya updated MESOS-7418:
--
Fix Version/s: 1.4.0

> Add support for file-based secrets
> --
>
> Key: MESOS-7418
> URL: https://issues.apache.org/jira/browse/MESOS-7418
> Project: Mesos
>  Issue Type: Improvement
>  Components: modules, security
>Reporter: Kapil Arya
>Assignee: Kapil Arya
>  Labels: mesosphere
> Fix For: 1.4.0
>
>
> The goal is to allow users to populate files within a task's environment with 
> contents fetched from a backend secret store. A new secret fetching module 
> interface is proposed to allow interaction with arbitrary third-party secret 
> stores.
> Further details are covered in the attached design doc



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Comment Edited] (MESOS-7418) Add support for file-based secrets

2017-05-22 Thread Kapil Arya (JIRA) 

[ 
https://issues.apache.org/jira/browse/MESOS-7418?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16020244#comment-16020244
 ] 

Kapil Arya edited comment on MESOS-7418 at 5/22/17 9:40 PM:


{code}
commit 1c7ffbeb505b3f5ab759202195f0b946a20cb803
Author: Kapil Arya 
Date:   Wed May 3 03:05:17 2017 -0400

Added volume secret isolator.

Review: https://reviews.apache.org/r/59001

commit e9e9e739d4d120c7c7dc9f366b0b1f7d2f1d3154
Author: Kapil Arya 
Date:   Mon May 1 18:51:22 2017 -0400

Added environment secret isolator.

Review: https://reviews.apache.org/r/59000

commit 5a630d82c1f59fc0156ffbe5356c3f1b3ac87489
Author: Kapil Arya 
Date:   Mon May 1 18:23:51 2017 -0400

Added --secret_resolver flag to agent.

Updated Containerizer to accept SecretResolver.

Review: https://reviews.apache.org/r/58999

commit d284a9ed561ec4f8967114953febd5dd84c92006
Author: Kapil Arya 
Date:   Wed Apr 26 10:59:01 2017 -0400

Added default secret resolver module.

Review: https://reviews.apache.org/r/58760

commit 9430a3b33b3d5d9955c3a2aed459e66106307bcb
Author: Kapil Arya 
Date:   Wed Apr 26 10:55:57 2017 -0400

Introduced SecretResolver module interface.

Review: https://reviews.apache.org/r/58759
{code}


was (Author: karya):
{code>
commit 1c7ffbeb505b3f5ab759202195f0b946a20cb803
Author: Kapil Arya 
Date:   Wed May 3 03:05:17 2017 -0400

Added volume secret isolator.

Review: https://reviews.apache.org/r/59001

commit e9e9e739d4d120c7c7dc9f366b0b1f7d2f1d3154
Author: Kapil Arya 
Date:   Mon May 1 18:51:22 2017 -0400

Added environment secret isolator.

Review: https://reviews.apache.org/r/59000

commit 5a630d82c1f59fc0156ffbe5356c3f1b3ac87489
Author: Kapil Arya 
Date:   Mon May 1 18:23:51 2017 -0400

Added --secret_resolver flag to agent.

Updated Containerizer to accept SecretResolver.

Review: https://reviews.apache.org/r/58999

commit d284a9ed561ec4f8967114953febd5dd84c92006
Author: Kapil Arya 
Date:   Wed Apr 26 10:59:01 2017 -0400

Added default secret resolver module.

Review: https://reviews.apache.org/r/58760

commit 9430a3b33b3d5d9955c3a2aed459e66106307bcb
Author: Kapil Arya 
Date:   Wed Apr 26 10:55:57 2017 -0400

Introduced SecretResolver module interface.

Review: https://reviews.apache.org/r/58759
{code}

> Add support for file-based secrets
> --
>
> Key: MESOS-7418
> URL: https://issues.apache.org/jira/browse/MESOS-7418
> Project: Mesos
>  Issue Type: Improvement
>  Components: modules, security
>Reporter: Kapil Arya
>Assignee: Kapil Arya
>  Labels: mesosphere
> Fix For: 1.4.0
>
>
> The goal is to allow users to populate files within a task's environment with 
> contents fetched from a backend secret store. A new secret fetching module 
> interface is proposed to allow interaction with arbitrary third-party secret 
> stores.
> Further details are covered in the attached design doc



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Created] (MESOS-7543) Allow isolators to specify secret environment

2017-05-22 Thread Kapil Arya (JIRA) 
Kapil Arya created MESOS-7543:
-

 Summary: Allow isolators to specify secret environment
 Key: MESOS-7543
 URL: https://issues.apache.org/jira/browse/MESOS-7543
 Project: Mesos
  Issue Type: Bug
  Components: containerization, security
Reporter: Kapil Arya






--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Created] (MESOS-7544) Incremental builds on Windows are broken

2017-05-22 Thread Andrew Schwartzmeyer (JIRA) 
Andrew Schwartzmeyer created MESOS-7544:
---

 Summary: Incremental builds on Windows are broken
 Key: MESOS-7544
 URL: https://issues.apache.org/jira/browse/MESOS-7544
 Project: Mesos
  Issue Type: Bug
 Environment: Windows 10
Reporter: Andrew Schwartzmeyer
Assignee: Andrew Schwartzmeyer


Cannot incrementally rebuild, say, mesos-tests after changing a test source 
file. Everything rebuilds. At least as recent as 0edb2ee96.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Assigned] (MESOS-5158) Provide XFS quota support for persistent volumes.

2017-05-22 Thread James Peach (JIRA) 

 [ 
https://issues.apache.org/jira/browse/MESOS-5158?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

James Peach reassigned MESOS-5158:
--

Assignee: (was: James Peach)

> Provide XFS quota support for persistent volumes.
> -
>
> Key: MESOS-5158
> URL: https://issues.apache.org/jira/browse/MESOS-5158
> Project: Mesos
>  Issue Type: Improvement
>  Components: containerization
>Reporter: Yan Xu
>
> Given that the lifecycle of persistent volumes is managed outside of the 
> isolator, we may need to further abstract out the quota management 
> functionality to do it outside the XFS isolator.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Assigned] (MESOS-4828) XFS disk quota isolator

2017-05-22 Thread James Peach (JIRA) 

 [ 
https://issues.apache.org/jira/browse/MESOS-4828?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

James Peach reassigned MESOS-4828:
--

Assignee: Yan Xu  (was: James Peach)

> XFS disk quota isolator
> ---
>
> Key: MESOS-4828
> URL: https://issues.apache.org/jira/browse/MESOS-4828
> Project: Mesos
>  Issue Type: Epic
>  Components: containerization
>Reporter: James Peach
>Assignee: Yan Xu
>
> Implement a disk resource isolator using XFS project quotas. Compared to the 
> {{posix/disk}} isolator, this doesn't need to scan the filesystem 
> periodically, and applications receive a {{EDQUOT}} error instead of being 
> summarily killed.
> This initial implementation only isolates sandbox directory resources, since 
> isolation doesn't have any visibility into the the lifecycle of volumes, 
> which is needed to assign and track project IDs.
> The build dependencies for this are XFS header (from xfsprogs-devel) and 
> libblkid. We need libblkid or the equivalent to map filesystem paths to block 
> devices in order to apply quota.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Updated] (MESOS-7545) Volume secret isolator breaks Windows build

2017-05-22 Thread Andrew Schwartzmeyer (JIRA) 

 [ 
https://issues.apache.org/jira/browse/MESOS-7545?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Andrew Schwartzmeyer updated MESOS-7545:

Summary: Volume secret isolator breaks Windows build  (was: Volume secrete 
isolator breaks Windows build)

> Volume secret isolator breaks Windows build
> ---
>
> Key: MESOS-7545
> URL: https://issues.apache.org/jira/browse/MESOS-7545
> Project: Mesos
>  Issue Type: Bug
> Environment: Windows 10
>Reporter: Andrew Schwartzmeyer
>Assignee: Kapil Arya
>
> commit 1c7ffbeb5 
> Review: https://reviews.apache.org/r/59001
> Doesn't build on Windows:
> "C:\Users\andschwa\src\mesos-master\build\src\tests\mesos-tests.vcxproj" 
> (default target) (1) ->
> "C:\Users\andschwa\src\mesos-master\build\mesos-and-binaries.vcxproj" 
> (default target) (20) ->
> "C:\Users\andschwa\src\mesos-master\build\src\slave\mesos-agent.vcxproj" 
> (default target) (23) ->
> (Link target) ->
>   mesos-1.4.0.lib(containerizer.cpp.obj) : error LNK2019: unresolved external 
> symbol "public: static class Try sos::slave::Isolator *,class Error> __cdecl 
> mesos::internal::slave::EnvironmentSecretIsolatorProcess::create(class meso
> s::internal::slave::Flags const &,class mesos::SecretResolver *)" 
> (?create@EnvironmentSecretIsolatorProcess@slave@inter
> nal@mesos@@SA?AV?$Try@PEAVIsolator@slave@mesos@@VErrorAEBVFlags@234@PEAVSecretResolver@4@@Z)
>  referenced in function
>  "public: class Try __cdecl 
> ::oper
> ator()(class mesos::internal::slave::Flags const &)const " 
> (??R@@QEBA?AV?$Try@
> PEAVIsolator@slave@mesos@@VErrorAEBVFlags@slave@internal@mesos@@@Z) 
> [C:\Users\andschwa\src\mesos-master\build\src\s
> lave\mesos-agent.vcxproj]
>   C:\Users\andschwa\src\mesos-master\build\src\mesos-agent.exe : fatal error 
> LNK1120: 1 unresolved externals [C:\Users\
> andschwa\src\mesos-master\build\src\slave\mesos-agent.vcxproj]



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Created] (MESOS-7545) Volume secrete isolator breaks Windows build

2017-05-22 Thread Andrew Schwartzmeyer (JIRA) 
Andrew Schwartzmeyer created MESOS-7545:
---

 Summary: Volume secrete isolator breaks Windows build
 Key: MESOS-7545
 URL: https://issues.apache.org/jira/browse/MESOS-7545
 Project: Mesos
  Issue Type: Bug
 Environment: Windows 10
Reporter: Andrew Schwartzmeyer
Assignee: Kapil Arya


commit 1c7ffbeb5 
Review: https://reviews.apache.org/r/59001

Doesn't build on Windows:

"C:\Users\andschwa\src\mesos-master\build\src\tests\mesos-tests.vcxproj" 
(default target) (1) ->
"C:\Users\andschwa\src\mesos-master\build\mesos-and-binaries.vcxproj" (default 
target) (20) ->
"C:\Users\andschwa\src\mesos-master\build\src\slave\mesos-agent.vcxproj" 
(default target) (23) ->
(Link target) ->
  mesos-1.4.0.lib(containerizer.cpp.obj) : error LNK2019: unresolved external 
symbol "public: static class Try __cdecl 
mesos::internal::slave::EnvironmentSecretIsolatorProcess::create(class meso
s::internal::slave::Flags const &,class mesos::SecretResolver *)" 
(?create@EnvironmentSecretIsolatorProcess@slave@inter
nal@mesos@@SA?AV?$Try@PEAVIsolator@slave@mesos@@VErrorAEBVFlags@234@PEAVSecretResolver@4@@Z)
 referenced in function
 "public: class Try __cdecl 
::oper
ator()(class mesos::internal::slave::Flags const &)const " 
(??R@@QEBA?AV?$Try@
PEAVIsolator@slave@mesos@@VErrorAEBVFlags@slave@internal@mesos@@@Z) 
[C:\Users\andschwa\src\mesos-master\build\src\s
lave\mesos-agent.vcxproj]
  C:\Users\andschwa\src\mesos-master\build\src\mesos-agent.exe : fatal error 
LNK1120: 1 unresolved externals [C:\Users\
andschwa\src\mesos-master\build\src\slave\mesos-agent.vcxproj]



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Created] (MESOS-7546) WAIT_NESTED_CONTAINER sometimes returns 404

2017-05-22 Thread JIRA 
Gastón Kleiman created MESOS-7546:
-

 Summary: WAIT_NESTED_CONTAINER sometimes returns 404
 Key: MESOS-7546
 URL: https://issues.apache.org/jira/browse/MESOS-7546
 Project: Mesos
  Issue Type: Bug
  Components: containerization
Reporter: Gastón Kleiman


{{WAIT_NESTED_CONTAINER}} sometimes returns 404s even though the nested 
container has already exited and the parent task/executor is still running.

This happens when an agent uses more than one containerizer (e.g.,
 {{docker,mesos}}, {{WAIT_NESTED_CONTAINER}} and the exit status of the nested 
container has already been checkpointed.

The root cause of this is a bug in the {{ComposingContainerizer}} in the 
following lines: 
https://github.com/apache/mesos/blob/1c7ffbeb505b3f5ab759202195f0b946a20cb803/src/slave/containerizer/composing.cpp#L620-L628





--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Assigned] (MESOS-5903) `GTEST_IS_THREADSAFE` guards prevent many tests from being run on Windows.

2017-05-22 Thread Neil Conway (JIRA) 

 [ 
https://issues.apache.org/jira/browse/MESOS-5903?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Neil Conway reassigned MESOS-5903:
--

Shepherd: Neil Conway
Assignee: Jan Schlicht  (was: Andrew Schwartzmeyer)

> `GTEST_IS_THREADSAFE` guards prevent many tests from being run on Windows.
> --
>
> Key: MESOS-5903
> URL: https://issues.apache.org/jira/browse/MESOS-5903
> Project: Mesos
>  Issue Type: Bug
>  Components: libprocess
>Reporter: Alex Clemmer
>Assignee: Jan Schlicht
>  Labels: libprocess, mesosphere
>
> In many tests, there is an assertion about the thread-safety of GTest, like: 
> `ASSERT_TRUE(GTEST_IS_THREADSAFE)`.
> This prevents probably a dozen tests from getting run on Windows. In 
> libprocess alone:
> * FutureTest: Select,
> * LimiterTest: Acquire
> * MetricsTest: Gauge, Snapshot, SnapshotTimeout, SnapshotAuthenticationEnabled
> * ProcessTest: Spawn, Dispatch, Defer1, Defer2, Defer3, Handlers, Expect, 
> Action, Inheritance, Thunk, Delegate, Delay, Order, Donate, Settle, Pid, 
> Listener, Executor, Remote, Async, 



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Updated] (MESOS-7527) Enable ProcessTest.THREADSAFE_Http2 on Windows.

2017-05-22 Thread Neil Conway (JIRA) 

 [ 
https://issues.apache.org/jira/browse/MESOS-7527?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Neil Conway updated MESOS-7527:
---
Summary: Enable ProcessTest.THREADSAFE_Http2 on Windows.  (was: Unit test 
ProcessTest.THREADSAFE_Http2 failing)

> Enable ProcessTest.THREADSAFE_Http2 on Windows.
> ---
>
> Key: MESOS-7527
> URL: https://issues.apache.org/jira/browse/MESOS-7527
> Project: Mesos
>  Issue Type: Bug
>  Components: libprocess
> Environment: Windows
>Reporter: Andrew Schwartzmeyer
>Assignee: Jan Schlicht
>
> TEST(ProcessTest, THREADSAFE_Http2) enabled in 
> https://github.com/apache/mesos/commit/82f3ab1a0da9e85e5354d8feeb88bf4a8f1ec6f8
> Appears to be this line:
> https://github.com/apache/mesos/blob/master/3rdparty/libprocess/src/tests/process_tests.cpp#L1380
> "Does not actually create a socket connection since the libprocess sender is 
> equal to the local OS process." - Joseph
> Unfortunately causing CI tests to fail.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Assigned] (MESOS-7527) Enable ProcessTest.THREADSAFE_Http2 on Windows.

2017-05-22 Thread Neil Conway (JIRA) 

 [ 
https://issues.apache.org/jira/browse/MESOS-7527?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Neil Conway reassigned MESOS-7527:
--

Assignee: (was: Jan Schlicht)

> Enable ProcessTest.THREADSAFE_Http2 on Windows.
> ---
>
> Key: MESOS-7527
> URL: https://issues.apache.org/jira/browse/MESOS-7527
> Project: Mesos
>  Issue Type: Bug
>  Components: libprocess
> Environment: Windows
>Reporter: Andrew Schwartzmeyer
>
> TEST(ProcessTest, THREADSAFE_Http2) enabled in 
> https://github.com/apache/mesos/commit/82f3ab1a0da9e85e5354d8feeb88bf4a8f1ec6f8
> Appears to be this line:
> https://github.com/apache/mesos/blob/master/3rdparty/libprocess/src/tests/process_tests.cpp#L1380
> "Does not actually create a socket connection since the libprocess sender is 
> equal to the local OS process." - Joseph
> Unfortunately causing CI tests to fail.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Updated] (MESOS-7527) Enable ProcessTest.THREADSAFE_Http2 on Windows.

2017-05-22 Thread Neil Conway (JIRA) 

 [ 
https://issues.apache.org/jira/browse/MESOS-7527?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Neil Conway updated MESOS-7527:
---
Shepherd:   (was: Neil Conway)

> Enable ProcessTest.THREADSAFE_Http2 on Windows.
> ---
>
> Key: MESOS-7527
> URL: https://issues.apache.org/jira/browse/MESOS-7527
> Project: Mesos
>  Issue Type: Bug
>  Components: libprocess
> Environment: Windows
>Reporter: Andrew Schwartzmeyer
>
> TEST(ProcessTest, THREADSAFE_Http2) enabled in 
> https://github.com/apache/mesos/commit/82f3ab1a0da9e85e5354d8feeb88bf4a8f1ec6f8
> Appears to be this line:
> https://github.com/apache/mesos/blob/master/3rdparty/libprocess/src/tests/process_tests.cpp#L1380
> "Does not actually create a socket connection since the libprocess sender is 
> equal to the local OS process." - Joseph
> Unfortunately causing CI tests to fail.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Commented] (MESOS-7530) HTTP authenticators modules never get the realm they are registered for

2017-05-22 Thread chenhaijiang (JIRA) 

[ 
https://issues.apache.org/jira/browse/MESOS-7530?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16020484#comment-16020484
 ] 

chenhaijiang commented on MESOS-7530:
-

Add a little more detail, Mesos agent also use the same authenticator module(no 
matter it is built-in or customize module).

Thanks,
Haijiang

> HTTP authenticators modules never get the realm they are registered for
> ---
>
> Key: MESOS-7530
> URL: https://issues.apache.org/jira/browse/MESOS-7530
> Project: Mesos
>  Issue Type: Bug
>  Components: modules, security
>Affects Versions: 1.3.0
>Reporter: Alexander Rojas
>  Labels: mesosphere
>
> When someone creates a module to provide HTTP Authenticator, only in the 
> master it can be register for one of three realms:
> * {{READONLY_HTTP_AUTHENTICATION_REALM}} 
> * {{READWRITE_HTTP_AUTHENTICATION_REALM}}
> * {{DEFAULT_HTTP_FRAMEWORK_AUTHENTICATION_REALM}}
> These realms are passed to the HTTP basic authenticator when it is 
> constructed:
> {code}
> Result 
> createBasicAuthenticator(
> const string& realm,
> const string& authenticatorName,
> const Option& credentials)
> {
>   if (credentials.isNone()) {
> return Error(
> "No credentials provided for the default '" +
> string(internal::DEFAULT_BASIC_HTTP_AUTHENTICATOR) +
> "' HTTP authenticator for realm '" + realm + "'");
>   }
>   LOG(INFO) << "Creating default '"
> << internal::DEFAULT_BASIC_HTTP_AUTHENTICATOR
> << "' HTTP authenticator for realm '" << realm << "'";
>   return BasicAuthenticatorFactory::create(realm, credentials.get());
> }
> {code}
> However modules don't get to configure their configured realm at construction 
> and the API doesn't allow to change that afterwards:
> {code}
> Result 
> createCustomAuthenticator(
> const string& realm,
> const string& authenticatorName)
> {
>   if (!modules::ModuleManager::contains<
> process::http::authentication::Authenticator>(authenticatorName)) {
> return Error(
> "HTTP authenticator '" + authenticatorName + "' not found. "
> "Check the spelling (compare to '" +
> string(internal::DEFAULT_BASIC_HTTP_AUTHENTICATOR) +
> "') or verify that the authenticator was loaded "
> "successfully (see --modules)");
>   }
>   LOG(INFO) << "Creating '" << authenticatorName << "' HTTP authenticator "
> << "for realm '" << realm << "'";
>   return modules::ModuleManager::create<
>   process::http::authentication::Authenticator>(authenticatorName);
> }
> {code}
> Since the same authenticator module is used for all the realms, it is 
> impossible to provide one authenticator per realm if using modules.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Updated] (MESOS-7538) Don't validate re-registrations that are going to be dropped.

2017-05-22 Thread Neil Conway (JIRA) 

 [ 
https://issues.apache.org/jira/browse/MESOS-7538?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Neil Conway updated MESOS-7538:
---
Target Version/s: 1.3.0, 1.4.0

> Don't validate re-registrations that are going to be dropped.
> -
>
> Key: MESOS-7538
> URL: https://issues.apache.org/jira/browse/MESOS-7538
> Project: Mesos
>  Issue Type: Bug
>  Components: master
>Reporter: James Peach
>Assignee: James Peach
>
> If there is already a re-registration in flight, we don't need to validate 
> the re-registration message since we are going to drop it anyway. Validation 
> can be expensive and we should aim to minimize the cost.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Updated] (MESOS-7538) Don't validate re-registrations that are going to be dropped.

2017-05-22 Thread Neil Conway (JIRA) 

 [ 
https://issues.apache.org/jira/browse/MESOS-7538?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Neil Conway updated MESOS-7538:
---
Shepherd: Neil Conway

> Don't validate re-registrations that are going to be dropped.
> -
>
> Key: MESOS-7538
> URL: https://issues.apache.org/jira/browse/MESOS-7538
> Project: Mesos
>  Issue Type: Bug
>  Components: master
>Reporter: James Peach
>Assignee: James Peach
> Fix For: 1.4.0
>
>
> If there is already a re-registration in flight, we don't need to validate 
> the re-registration message since we are going to drop it anyway. Validation 
> can be expensive and we should aim to minimize the cost.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Updated] (MESOS-7349) Document Mesos "check" feature.

2017-05-22 Thread Alexander Rukletsov (JIRA) 

 [ 
https://issues.apache.org/jira/browse/MESOS-7349?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Alexander Rukletsov updated MESOS-7349:
---
Sprint: Mesosphere Sprint 54, Mesosphere Sprint 55, Mesosphere Sprint 56  
(was: Mesosphere Sprint 54, Mesosphere Sprint 55, Mesosphere Sprint 56, 
Mesosphere Sprint 57)

> Document Mesos "check" feature.
> ---
>
> Key: MESOS-7349
> URL: https://issues.apache.org/jira/browse/MESOS-7349
> Project: Mesos
>  Issue Type: Documentation
>  Components: documentation
>Reporter: Alexander Rukletsov
>Assignee: Alexander Rukletsov
>  Labels: documentaion, mesosphere
>
> This should include framework authors recommendations about how and when to 
> use general checks as well as comparison with health checks.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Created] (MESOS-7529) Realm names defined for tests are used in production code

2017-05-22 Thread Jan Schlicht (JIRA) 
Jan Schlicht created MESOS-7529:
---

 Summary: Realm names defined for tests are used in production code
 Key: MESOS-7529
 URL: https://issues.apache.org/jira/browse/MESOS-7529
 Project: Mesos
  Issue Type: Bug
  Components: libprocess, technical debt
Reporter: Jan Schlicht
Priority: Minor


In {{process/gtest.hpp}} the realms {{READONLY_HTTP_AUTHENTICATION_REALM}} and 
{{READWRITE_HTTP_AUTHENTICATION_REALM}} are defined. These are then used in 
{{master/main.cpp}} and {{slave/main.cpp}}. I'd expect that these would only be 
used in tests or these realms should be defined elsewhere.
Also the concept of having these two realms seems specific to Mesos, not 
libprocess, hence it would make sense to define them somewhere in Mesos.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Updated] (MESOS-7529) Realm names defined for tests are used in main Mesos code

2017-05-22 Thread Jan Schlicht (JIRA) 

 [ 
https://issues.apache.org/jira/browse/MESOS-7529?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Jan Schlicht updated MESOS-7529:

Summary: Realm names defined for tests are used in main Mesos code  (was: 
Realm names defined for tests are used in production code)

> Realm names defined for tests are used in main Mesos code
> -
>
> Key: MESOS-7529
> URL: https://issues.apache.org/jira/browse/MESOS-7529
> Project: Mesos
>  Issue Type: Bug
>  Components: libprocess, technical debt
>Reporter: Jan Schlicht
>Priority: Minor
>  Labels: easy-fix, libprocess, tech-debt
>
> In {{process/gtest.hpp}} the realms {{READONLY_HTTP_AUTHENTICATION_REALM}} 
> and {{READWRITE_HTTP_AUTHENTICATION_REALM}} are defined. These are then used 
> in {{master/main.cpp}} and {{slave/main.cpp}}. I'd expect that these would 
> only be used in tests or these realms should be defined elsewhere.
> Also the concept of having these two realms seems specific to Mesos, not 
> libprocess, hence it would make sense to define them somewhere in Mesos.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Created] (MESOS-7530) HTTP authenticators modules never get the realm they are registered for

2017-05-22 Thread Alexander Rojas (JIRA) 
Alexander Rojas created MESOS-7530:
--

 Summary: HTTP authenticators modules never get the realm they are 
registered for
 Key: MESOS-7530
 URL: https://issues.apache.org/jira/browse/MESOS-7530
 Project: Mesos
  Issue Type: Bug
  Components: modules, security
Affects Versions: 1.3.0
Reporter: Alexander Rojas


When someone creates a module to provide HTTP Authenticator, only in the master 
it can be register for one of three realms:

* {{READONLY_HTTP_AUTHENTICATION_REALM}} 
* {{READWRITE_HTTP_AUTHENTICATION_REALM}}
* {{DEFAULT_HTTP_FRAMEWORK_AUTHENTICATION_REALM}}

These realms are passed to the HTTP basic authenticator when it is constructed:

{code}
Result createBasicAuthenticator(
const string& realm,
const string& authenticatorName,
const Option& credentials)
{
  if (credentials.isNone()) {
return Error(
"No credentials provided for the default '" +
string(internal::DEFAULT_BASIC_HTTP_AUTHENTICATOR) +
"' HTTP authenticator for realm '" + realm + "'");
  }

  LOG(INFO) << "Creating default '"
<< internal::DEFAULT_BASIC_HTTP_AUTHENTICATOR
<< "' HTTP authenticator for realm '" << realm << "'";

  return BasicAuthenticatorFactory::create(realm, credentials.get());
}
{code}

However modules don't get to configure their configured realm at construction 
and the API doesn't allow to change that afterwards:

{code}
Result createCustomAuthenticator(
const string& realm,
const string& authenticatorName)
{
  if (!modules::ModuleManager::contains<
process::http::authentication::Authenticator>(authenticatorName)) {
return Error(
"HTTP authenticator '" + authenticatorName + "' not found. "
"Check the spelling (compare to '" +
string(internal::DEFAULT_BASIC_HTTP_AUTHENTICATOR) +
"') or verify that the authenticator was loaded "
"successfully (see --modules)");
  }

  LOG(INFO) << "Creating '" << authenticatorName << "' HTTP authenticator "
<< "for realm '" << realm << "'";

  return modules::ModuleManager::create<
  process::http::authentication::Authenticator>(authenticatorName);
}
{code}

Since the same authenticator module is used for all the realms, it is 
impossible to provide one authenticator per realm if using modules.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Created] (MESOS-7531) Handle maintenance for local resource providers

2017-05-22 Thread Jan Schlicht (JIRA) 
Jan Schlicht created MESOS-7531:
---

 Summary: Handle maintenance for local resource providers
 Key: MESOS-7531
 URL: https://issues.apache.org/jira/browse/MESOS-7531
 Project: Mesos
  Issue Type: Task
Reporter: Jan Schlicht


Local resource providers are closely tied to the agents they're running on. As 
the machines the agents are running on, might be scheduled for maintenance, we 
need to make sure that local resource providers running on that machine are 
affected as well. I.e. if a machine is set to the {{DOWN}} maintenance state, 
find out which resource providers are running on that machine and change their 
{{availability}} state in the allocator.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Created] (MESOS-7532) Test maintenance handling of local resource providers

2017-05-22 Thread Jan Schlicht (JIRA) 
Jan Schlicht created MESOS-7532:
---

 Summary: Test maintenance handling of local resource providers
 Key: MESOS-7532
 URL: https://issues.apache.org/jira/browse/MESOS-7532
 Project: Mesos
  Issue Type: Task
Reporter: Jan Schlicht


Test the maintenance behavior described in MESOS-7531, i.e. start a master and 
an agent that provides a local resource provider, schedule that agent for 
maintenance (setting the machine's state to {{DOWN}}) and check that no 
resources from the local resource provider are offered afterwards.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Created] (MESOS-7533) Add a function stub for resource provider re-registration

2017-05-22 Thread Jan Schlicht (JIRA) 
Jan Schlicht created MESOS-7533:
---

 Summary: Add a function stub for resource provider re-registration
 Key: MESOS-7533
 URL: https://issues.apache.org/jira/browse/MESOS-7533
 Project: Mesos
  Issue Type: Task
Reporter: Jan Schlicht


In case there is a resource provider failover it is expected that a resource 
provider will re-register with the master using its ID that was provided by the 
master. A function needs to be added to the master to support this. I.e. if a 
resource provider {{SUBSCRIBE}}s using a {{ResourceProviderInfo}} that contains 
an ID, check if that was already registered. A later task would be to implement 
resource reconciliation.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Created] (MESOS-7534) Notify resource providers if they've been re-registered.

2017-05-22 Thread Jan Schlicht (JIRA) 
Jan Schlicht created MESOS-7534:
---

 Summary: Notify resource providers if they've been re-registered.
 Key: MESOS-7534
 URL: https://issues.apache.org/jira/browse/MESOS-7534
 Project: Mesos
  Issue Type: Task
Reporter: Jan Schlicht


Send a {{SUBSCRIBED}} event to the resource provider.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Created] (MESOS-7535) Distinguish between active and inactive resource providers in the master

2017-05-22 Thread Jan Schlicht (JIRA) 
Jan Schlicht created MESOS-7535:
---

 Summary: Distinguish between active and inactive resource 
providers in the master
 Key: MESOS-7535
 URL: https://issues.apache.org/jira/browse/MESOS-7535
 Project: Mesos
  Issue Type: Task
Reporter: Jan Schlicht


To support re-registration with the master after a resource provider failover, 
the master should be able to distinguish between active and inactive resource 
providers. In the case that a resource provider disconnects (handled in a 
different ticket), it would be marked as inactive until it re-registers. While 
being inactive, resource of it won't be offered.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Created] (MESOS-7536) Test that a resource provider failover results in a re-registration with the master

2017-05-22 Thread Jan Schlicht (JIRA) 
Jan Schlicht created MESOS-7536:
---

 Summary: Test that a resource provider failover results in a 
re-registration with the master
 Key: MESOS-7536
 URL: https://issues.apache.org/jira/browse/MESOS-7536
 Project: Mesos
  Issue Type: Task
Reporter: Jan Schlicht


Multiple scenarios need to be tested:
* A failover of a local resource provider will lead to a re-registration
* A failover of an agent that a running a local resource provider will lead to 
a re-registration of the local resource provider (following a re-registration 
of the agent) 



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Created] (MESOS-7537) Add functionality to disconnect resource providers in the master

2017-05-22 Thread Jan Schlicht (JIRA) 
Jan Schlicht created MESOS-7537:
---

 Summary: Add functionality to disconnect resource providers in the 
master
 Key: MESOS-7537
 URL: https://issues.apache.org/jira/browse/MESOS-7537
 Project: Mesos
  Issue Type: Task
Reporter: Jan Schlicht


Similar to the existing {{disconnect}} methods for frameworks and agents, a 
similar function has to be added to the master.
It needs to be called in {{Master::exited}}, i.e. when it detects that a 
resource provider is no longer reachable.
For local resource providers this also has to be called when the agent 
disconnects where these are running on.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Created] (MESOS-7538) Don't validate re-registrations that are going to be dropped.

2017-05-22 Thread James Peach (JIRA) 
James Peach created MESOS-7538:
--

 Summary: Don't validate re-registrations that are going to be 
dropped.
 Key: MESOS-7538
 URL: https://issues.apache.org/jira/browse/MESOS-7538
 Project: Mesos
  Issue Type: Bug
  Components: master
Reporter: James Peach


If there is already a re-registration in flight, we don't need to validate the 
re-registration message since we are going to drop it anyway. Validation can be 
expensive and we should aim to minimize the cost.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Updated] (MESOS-7530) HTTP authenticators modules never get the realm they are registered for

2017-05-22 Thread Adam B (JIRA) 

 [ 
https://issues.apache.org/jira/browse/MESOS-7530?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Adam B updated MESOS-7530:
--
Labels: mesosphere  (was: )

> HTTP authenticators modules never get the realm they are registered for
> ---
>
> Key: MESOS-7530
> URL: https://issues.apache.org/jira/browse/MESOS-7530
> Project: Mesos
>  Issue Type: Bug
>  Components: modules, security
>Affects Versions: 1.3.0
>Reporter: Alexander Rojas
>  Labels: mesosphere
>
> When someone creates a module to provide HTTP Authenticator, only in the 
> master it can be register for one of three realms:
> * {{READONLY_HTTP_AUTHENTICATION_REALM}} 
> * {{READWRITE_HTTP_AUTHENTICATION_REALM}}
> * {{DEFAULT_HTTP_FRAMEWORK_AUTHENTICATION_REALM}}
> These realms are passed to the HTTP basic authenticator when it is 
> constructed:
> {code}
> Result 
> createBasicAuthenticator(
> const string& realm,
> const string& authenticatorName,
> const Option& credentials)
> {
>   if (credentials.isNone()) {
> return Error(
> "No credentials provided for the default '" +
> string(internal::DEFAULT_BASIC_HTTP_AUTHENTICATOR) +
> "' HTTP authenticator for realm '" + realm + "'");
>   }
>   LOG(INFO) << "Creating default '"
> << internal::DEFAULT_BASIC_HTTP_AUTHENTICATOR
> << "' HTTP authenticator for realm '" << realm << "'";
>   return BasicAuthenticatorFactory::create(realm, credentials.get());
> }
> {code}
> However modules don't get to configure their configured realm at construction 
> and the API doesn't allow to change that afterwards:
> {code}
> Result 
> createCustomAuthenticator(
> const string& realm,
> const string& authenticatorName)
> {
>   if (!modules::ModuleManager::contains<
> process::http::authentication::Authenticator>(authenticatorName)) {
> return Error(
> "HTTP authenticator '" + authenticatorName + "' not found. "
> "Check the spelling (compare to '" +
> string(internal::DEFAULT_BASIC_HTTP_AUTHENTICATOR) +
> "') or verify that the authenticator was loaded "
> "successfully (see --modules)");
>   }
>   LOG(INFO) << "Creating '" << authenticatorName << "' HTTP authenticator "
> << "for realm '" << realm << "'";
>   return modules::ModuleManager::create<
>   process::http::authentication::Authenticator>(authenticatorName);
> }
> {code}
> Since the same authenticator module is used for all the realms, it is 
> impossible to provide one authenticator per realm if using modules.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Assigned] (MESOS-7538) Don't validate re-registrations that are going to be dropped.

2017-05-22 Thread James Peach (JIRA) 

 [ 
https://issues.apache.org/jira/browse/MESOS-7538?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

James Peach reassigned MESOS-7538:
--

Assignee: James Peach

| [https://reviews.apache.org/r/59458/|https://reviews.apache.org/r/59458/] | 
Belay the reregistration validation if it is already in flight.|

> Don't validate re-registrations that are going to be dropped.
> -
>
> Key: MESOS-7538
> URL: https://issues.apache.org/jira/browse/MESOS-7538
> Project: Mesos
>  Issue Type: Bug
>  Components: master
>Reporter: James Peach
>Assignee: James Peach
>
> If there is already a re-registration in flight, we don't need to validate 
> the re-registration message since we are going to drop it anyway. Validation 
> can be expensive and we should aim to minimize the cost.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Created] (MESOS-7539) Allow agent to complete recovery before executor reregister timeout has elapsed

2017-05-22 Thread Greg Mann (JIRA) 
Greg Mann created MESOS-7539:


 Summary: Allow agent to complete recovery before executor 
reregister timeout has elapsed
 Key: MESOS-7539
 URL: https://issues.apache.org/jira/browse/MESOS-7539
 Project: Mesos
  Issue Type: Improvement
  Components: agent
Reporter: Greg Mann


Once the executor reregister timeout is made configurable via an agent flag, it 
would be beneficial to allow the agent to complete recovery before this timeout 
elapses if all executors have successfully re-registered.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Created] (MESOS-7540) Add an agent flag for executor re-register timeout

2017-05-22 Thread Greg Mann (JIRA) 
Greg Mann created MESOS-7540:


 Summary: Add an agent flag for executor re-register timeout
 Key: MESOS-7540
 URL: https://issues.apache.org/jira/browse/MESOS-7540
 Project: Mesos
  Issue Type: Improvement
  Components: agent
Reporter: Greg Mann


Currently, the executor re-register timeout is hard-coded at 2 seconds. It 
would be beneficial to allow operators to specify this value.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Assigned] (MESOS-7540) Add an agent flag for executor re-register timeout

2017-05-22 Thread Greg Mann (JIRA) 

 [ 
https://issues.apache.org/jira/browse/MESOS-7540?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Greg Mann reassigned MESOS-7540:


Assignee: Greg Mann

> Add an agent flag for executor re-register timeout
> --
>
> Key: MESOS-7540
> URL: https://issues.apache.org/jira/browse/MESOS-7540
> Project: Mesos
>  Issue Type: Improvement
>  Components: agent
>Reporter: Greg Mann
>Assignee: Greg Mann
>  Labels: mesosphere
>
> Currently, the executor re-register timeout is hard-coded at 2 seconds. It 
> would be beneficial to allow operators to specify this value.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Commented] (MESOS-7539) Allow agent to complete recovery before executor reregister timeout has elapsed

2017-05-22 Thread Greg Mann (JIRA) 

[ 
https://issues.apache.org/jira/browse/MESOS-7539?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=1602#comment-1602
 ] 

Greg Mann commented on MESOS-7539:
--

Reviews here:
https://reviews.apache.org/r/59460/
https://reviews.apache.org/r/59461/

> Allow agent to complete recovery before executor reregister timeout has 
> elapsed
> ---
>
> Key: MESOS-7539
> URL: https://issues.apache.org/jira/browse/MESOS-7539
> Project: Mesos
>  Issue Type: Improvement
>  Components: agent
>Reporter: Greg Mann
>  Labels: mesosphere, recovery
>
> Once the executor reregister timeout is made configurable via an agent flag, 
> it would be beneficial to allow the agent to complete recovery before this 
> timeout elapses if all executors have successfully re-registered.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Commented] (MESOS-7540) Add an agent flag for executor re-register timeout

2017-05-22 Thread Greg Mann (JIRA) 

[ 
https://issues.apache.org/jira/browse/MESOS-7540?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16020001#comment-16020001
 ] 

Greg Mann commented on MESOS-7540:
--

Reviews here:
https://reviews.apache.org/r/59460/
https://reviews.apache.org/r/59461/

> Add an agent flag for executor re-register timeout
> --
>
> Key: MESOS-7540
> URL: https://issues.apache.org/jira/browse/MESOS-7540
> Project: Mesos
>  Issue Type: Improvement
>  Components: agent
>Reporter: Greg Mann
>Assignee: Greg Mann
>  Labels: mesosphere
>
> Currently, the executor re-register timeout is hard-coded at 2 seconds. It 
> would be beneficial to allow operators to specify this value.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Issue Comment Deleted] (MESOS-7539) Allow agent to complete recovery before executor reregister timeout has elapsed

2017-05-22 Thread Greg Mann (JIRA) 

 [ 
https://issues.apache.org/jira/browse/MESOS-7539?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Greg Mann updated MESOS-7539:
-
Comment: was deleted

(was: Reviews here:
https://reviews.apache.org/r/59460/
https://reviews.apache.org/r/59461/)

> Allow agent to complete recovery before executor reregister timeout has 
> elapsed
> ---
>
> Key: MESOS-7539
> URL: https://issues.apache.org/jira/browse/MESOS-7539
> Project: Mesos
>  Issue Type: Improvement
>  Components: agent
>Reporter: Greg Mann
>  Labels: mesosphere, recovery
>
> Once the executor reregister timeout is made configurable via an agent flag, 
> it would be beneficial to allow the agent to complete recovery before this 
> timeout elapses if all executors have successfully re-registered.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Created] (MESOS-7541) Cannot compile without pre-compiled headers on Windows

2017-05-22 Thread Andrew Schwartzmeyer (JIRA) 
Andrew Schwartzmeyer created MESOS-7541:
---

 Summary: Cannot compile without pre-compiled headers on Windows
 Key: MESOS-7541
 URL: https://issues.apache.org/jira/browse/MESOS-7541
 Project: Mesos
  Issue Type: Bug
 Environment: Windows 10 with  -DENABLE_PRECOMPILED_HEADERS=0
Reporter: Andrew Schwartzmeyer
Assignee: Jeff Coffler


Looks like we messed up an include at some point:

"C:\Users\andschwa\src\mesos\build\src\tests\mesos-tests.vcxproj" (default 
target) (1) ->
"C:\Users\andschwa\src\mesos\build\src\mesos-1.4.0.vcxproj" (default target) 
(4) ->
(ClCompile target) ->
  C:\Users\andschwa\src\mesos\3rdparty\stout\include\stout/ip.hpp(104): error 
C2065: 'AF_INET6': undeclared identifier (compiling source file 
C:\Users\andschwa\src\mesos\src\zookeeper\group.cpp) 
[C:\Users\andschwa\src\mesos\build\src\mesos-1.4.0.vcxproj]
  C:\Users\andschwa\src\mesos\3rdparty\stout\include\stout/ip.hpp(138): error 
C2065: 'AF_INET6': undeclared identifier (compiling source file 
C:\Users\andschwa\src\mesos\src\zookeeper\group.cpp) 
[C:\Users\andschwa\src\mesos\build\src\mesos-1.4.0.vcxproj]
  C:\Users\andschwa\src\mesos\3rdparty\stout\include\stout/ip.hpp(151): error 
C2065: 'AF_INET6': undeclared identifier (compiling source file 
C:\Users\andschwa\src\mesos\src\zookeeper\group.cpp) 
[C:\Users\andschwa\src\mesos\build\src\mesos-1.4.0.vcxproj]
  C:\Users\andschwa\src\mesos\3rdparty\stout\include\stout/ip.hpp(151): error 
C2131: expression did not evaluate to a constant (compiling source file 
C:\Users\andschwa\src\mesos\src\zookeeper\group.cpp) 
[C:\Users\andschwa\src\mesos\build\src\mesos-1.4.0.vcxproj]
  C:\Users\andschwa\src\mesos\3rdparty\stout\include\stout/ip.hpp(151): error 
C2051: case expression not constant (compiling source file 
C:\Users\andschwa\src\mesos\src\zookeeper\group.cpp) 
[C:\Users\andschwa\src\mesos\build\src\mesos-1.4.0.vcxproj]
  C:\Users\andschwa\src\mesos\3rdparty\stout\include\stout/ip.hpp(164): error 
C2065: 'AF_INET6': undeclared identifier (compiling source file 
C:\Users\andschwa\src\mesos\src\zookeeper\group.cpp) 
[C:\Users\andschwa\src\mesos\build\src\mesos-1.4.0.vcxproj]
  C:\Users\andschwa\src\mesos\3rdparty\stout\include\stout/ip.hpp(164): error 
C2131: expression did not evaluate to a constant (compiling source file 
C:\Users\andschwa\src\mesos\src\zookeeper\group.cpp) 
[C:\Users\andschwa\src\mesos\build\src\mesos-1.4.0.vcxproj]
  C:\Users\andschwa\src\mesos\3rdparty\stout\include\stout/ip.hpp(164): error 
C2051: case expression not constant (compiling source file 
C:\Users\andschwa\src\mesos\src\zookeeper\group.cpp) 
[C:\Users\andschwa\src\mesos\build\src\mesos-1.4.0.vcxproj]
  C:\Users\andschwa\src\mesos\3rdparty\stout\include\stout/ip.hpp(233): error 
C2065: 'AF_INET6': undeclared identifier (compiling source file 
C:\Users\andschwa\src\mesos\src\zookeeper\group.cpp) 
[C:\Users\andschwa\src\mesos\build\src\mesos-1.4.0.vcxproj]
  C:\Users\andschwa\src\mesos\3rdparty\stout\include\stout/ip.hpp(233): error 
C2131: expression did not evaluate to a constant (compiling source file 
C:\Users\andschwa\src\mesos\src\zookeeper\group.cpp) 
[C:\Users\andschwa\src\mesos\build\src\mesos-1.4.0.vcxproj]
  C:\Users\andschwa\src\mesos\3rdparty\stout\include\stout/ip.hpp(234): error 
C2065: 'AF_INET6': undeclared identifier (compiling source file 
C:\Users\andschwa\src\mesos\src\zookeeper\group.cpp) 
[C:\Users\andschwa\src\mesos\build\src\mesos-1.4.0.vcxproj]
  C:\Users\andschwa\src\mesos\3rdparty\stout\include\stout/ip.hpp(246): error 
C2065: 'AF_INET6': undeclared identifier (compiling source file 
C:\Users\andschwa\src\mesos\src\zookeeper\group.cpp) 
[C:\Users\andschwa\src\mesos\build\src\mesos-1.4.0.vcxproj]
  C:\Users\andschwa\src\mesos\3rdparty\stout\include\stout/ip.hpp(246): error 
C2512: 'Try': no appropriate default constructor available 
(compiling source file C:\Users\andschwa\src\mesos\src\zookeeper\group.cpp) 
[C:\Users\andschwa\src\mesos\build\src\mes
os-1.4.0.vcxproj]
  C:\Users\andschwa\src\mesos\3rdparty\stout\include\stout/ip.hpp(233): error 
C2051: case expression not constant (compiling source file 
C:\Users\andschwa\src\mesos\src\zookeeper\group.cpp) 
[C:\Users\andschwa\src\mesos\build\src\mesos-1.4.0.vcxproj]
  C:\Users\andschwa\src\mesos\3rdparty\stout\include\stout/ip.hpp(293): error 
C2065: 'AF_INET6': undeclared identifier (compiling source file 
C:\Users\andschwa\src\mesos\src\zookeeper\group.cpp) 
[C:\Users\andschwa\src\mesos\build\src\mesos-1.4.0.vcxproj]
  C:\Users\andschwa\src\mesos\3rdparty\stout\include\stout/ip.hpp(293): error 
C2131: expression did not evaluate to a constant (compiling source file 
C:\Users\andschwa\src\mesos\src\zookeeper\group.cpp) 
[C:\Users\andschwa\src\mesos\build\src\mesos-1.4.0.vcxproj]
  C:\Users\andschwa\src\mesos\3rdparty\stout\include\stout/ip.hpp(293): error 
C2051: case expression not constant

[jira] [Updated] (MESOS-7541) Cannot compile without pre-compiled headers on Windows

2017-05-22 Thread Joseph Wu (JIRA) 

 [ 
https://issues.apache.org/jira/browse/MESOS-7541?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Joseph Wu updated MESOS-7541:
-
Description: 
Looks like we messed up an include at some point:

{noformat}
"C:\Users\andschwa\src\mesos\build\src\tests\mesos-tests.vcxproj" (default 
target) (1) ->
"C:\Users\andschwa\src\mesos\build\src\mesos-1.4.0.vcxproj" (default target) 
(4) ->
(ClCompile target) ->
  C:\Users\andschwa\src\mesos\3rdparty\stout\include\stout/ip.hpp(104): error 
C2065: 'AF_INET6': undeclared identifier (compiling source file 
C:\Users\andschwa\src\mesos\src\zookeeper\group.cpp) 
[C:\Users\andschwa\src\mesos\build\src\mesos-1.4.0.vcxproj]
  C:\Users\andschwa\src\mesos\3rdparty\stout\include\stout/ip.hpp(138): error 
C2065: 'AF_INET6': undeclared identifier (compiling source file 
C:\Users\andschwa\src\mesos\src\zookeeper\group.cpp) 
[C:\Users\andschwa\src\mesos\build\src\mesos-1.4.0.vcxproj]
  C:\Users\andschwa\src\mesos\3rdparty\stout\include\stout/ip.hpp(151): error 
C2065: 'AF_INET6': undeclared identifier (compiling source file 
C:\Users\andschwa\src\mesos\src\zookeeper\group.cpp) 
[C:\Users\andschwa\src\mesos\build\src\mesos-1.4.0.vcxproj]
  C:\Users\andschwa\src\mesos\3rdparty\stout\include\stout/ip.hpp(151): error 
C2131: expression did not evaluate to a constant (compiling source file 
C:\Users\andschwa\src\mesos\src\zookeeper\group.cpp) 
[C:\Users\andschwa\src\mesos\build\src\mesos-1.4.0.vcxproj]
  C:\Users\andschwa\src\mesos\3rdparty\stout\include\stout/ip.hpp(151): error 
C2051: case expression not constant (compiling source file 
C:\Users\andschwa\src\mesos\src\zookeeper\group.cpp) 
[C:\Users\andschwa\src\mesos\build\src\mesos-1.4.0.vcxproj]
  C:\Users\andschwa\src\mesos\3rdparty\stout\include\stout/ip.hpp(164): error 
C2065: 'AF_INET6': undeclared identifier (compiling source file 
C:\Users\andschwa\src\mesos\src\zookeeper\group.cpp) 
[C:\Users\andschwa\src\mesos\build\src\mesos-1.4.0.vcxproj]
  C:\Users\andschwa\src\mesos\3rdparty\stout\include\stout/ip.hpp(164): error 
C2131: expression did not evaluate to a constant (compiling source file 
C:\Users\andschwa\src\mesos\src\zookeeper\group.cpp) 
[C:\Users\andschwa\src\mesos\build\src\mesos-1.4.0.vcxproj]
  C:\Users\andschwa\src\mesos\3rdparty\stout\include\stout/ip.hpp(164): error 
C2051: case expression not constant (compiling source file 
C:\Users\andschwa\src\mesos\src\zookeeper\group.cpp) 
[C:\Users\andschwa\src\mesos\build\src\mesos-1.4.0.vcxproj]
  C:\Users\andschwa\src\mesos\3rdparty\stout\include\stout/ip.hpp(233): error 
C2065: 'AF_INET6': undeclared identifier (compiling source file 
C:\Users\andschwa\src\mesos\src\zookeeper\group.cpp) 
[C:\Users\andschwa\src\mesos\build\src\mesos-1.4.0.vcxproj]
  C:\Users\andschwa\src\mesos\3rdparty\stout\include\stout/ip.hpp(233): error 
C2131: expression did not evaluate to a constant (compiling source file 
C:\Users\andschwa\src\mesos\src\zookeeper\group.cpp) 
[C:\Users\andschwa\src\mesos\build\src\mesos-1.4.0.vcxproj]
  C:\Users\andschwa\src\mesos\3rdparty\stout\include\stout/ip.hpp(234): error 
C2065: 'AF_INET6': undeclared identifier (compiling source file 
C:\Users\andschwa\src\mesos\src\zookeeper\group.cpp) 
[C:\Users\andschwa\src\mesos\build\src\mesos-1.4.0.vcxproj]
  C:\Users\andschwa\src\mesos\3rdparty\stout\include\stout/ip.hpp(246): error 
C2065: 'AF_INET6': undeclared identifier (compiling source file 
C:\Users\andschwa\src\mesos\src\zookeeper\group.cpp) 
[C:\Users\andschwa\src\mesos\build\src\mesos-1.4.0.vcxproj]
  C:\Users\andschwa\src\mesos\3rdparty\stout\include\stout/ip.hpp(246): error 
C2512: 'Try': no appropriate default constructor available 
(compiling source file C:\Users\andschwa\src\mesos\src\zookeeper\group.cpp) 
[C:\Users\andschwa\src\mesos\build\src\mes
os-1.4.0.vcxproj]
  C:\Users\andschwa\src\mesos\3rdparty\stout\include\stout/ip.hpp(233): error 
C2051: case expression not constant (compiling source file 
C:\Users\andschwa\src\mesos\src\zookeeper\group.cpp) 
[C:\Users\andschwa\src\mesos\build\src\mesos-1.4.0.vcxproj]
  C:\Users\andschwa\src\mesos\3rdparty\stout\include\stout/ip.hpp(293): error 
C2065: 'AF_INET6': undeclared identifier (compiling source file 
C:\Users\andschwa\src\mesos\src\zookeeper\group.cpp) 
[C:\Users\andschwa\src\mesos\build\src\mesos-1.4.0.vcxproj]
  C:\Users\andschwa\src\mesos\3rdparty\stout\include\stout/ip.hpp(293): error 
C2131: expression did not evaluate to a constant (compiling source file 
C:\Users\andschwa\src\mesos\src\zookeeper\group.cpp) 
[C:\Users\andschwa\src\mesos\build\src\mesos-1.4.0.vcxproj]
  C:\Users\andschwa\src\mesos\3rdparty\stout\include\stout/ip.hpp(293): error 
C2051: case expression not constant (compiling source file 
C:\Users\andschwa\src\mesos\src\zookeeper\group.cpp) 
[C:\Users\andschwa\src\mesos\build\src\mesos-1.4.0.vcxproj]
  C:\Users\andschwa\src\mesos\3rdparty\stout\include\stout/ip.hpp(322): error 
C2065: 'AF_INET6': undeclared identif