[jira] [Updated] (MESOS-4157) Speed up ZooKeeper-related tests
[
https://issues.apache.org/jira/browse/MESOS-4157?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Alexander Rukletsov updated MESOS-4157:
---
Priority: Minor (was: Major)
> Speed up ZooKeeper-related tests
>
>
> Key: MESOS-4157
> URL: https://issues.apache.org/jira/browse/MESOS-4157
> Project: Mesos
> Issue Type: Epic
> Components: technical debt, test
>Reporter: Alexander Rukletsov
>Priority: Minor
> Labels: mesosphere, tech-debt
>
> Execution times on Mac OS 10.10.4:
> {code}
> ZooKeeperTest.Auth (6688 ms)
> ZooKeeperTest.Create (6690 ms)
> ZooKeeperTest.LeaderContender (3385 ms)
> MasterZooKeeperTest.MasterInfoAddress (11282 ms)
> ZooKeeperMasterContenderDetectorTest.NonRetryableFrrors (10053 ms)
> ZooKeeperMasterContenderDetectorTest.ContenderDetectorShutdownNetwork (3390
> ms)
> ZooKeeperMasterContenderDetectorTest.MasterDetectorExpireSlaveZKSession (3358
> ms)
> ZooKeeperMasterContenderDetectorTest.MasterDetectorExpireSlaveZKSessionNewMaster
> (3359 ms)
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (MESOS-4171) OversubscriptionTest.RemoveCapabilitiesOnSchedulerFailover is slow
[
https://issues.apache.org/jira/browse/MESOS-4171?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Alexander Rukletsov updated MESOS-4171:
---
Labels: mesosphere newbie++ tech-debt (was: mesosphere tech-debt)
> OversubscriptionTest.RemoveCapabilitiesOnSchedulerFailover is slow
> --
>
> Key: MESOS-4171
> URL: https://issues.apache.org/jira/browse/MESOS-4171
> Project: Mesos
> Issue Type: Improvement
> Components: technical debt, test
>Reporter: Alexander Rukletsov
>Priority: Minor
> Labels: mesosphere, newbie++, tech-debt
>
> The {{OversubscriptionTest.RemoveCapabilitiesOnSchedulerFailover}} test takes
> more than {{1s}} to finish on my Mac OS 10.10.4:
> {code}
> OversubscriptionTest.RemoveCapabilitiesOnSchedulerFailover (1018 ms)
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (MESOS-4160) Log recover tests are slow
[
https://issues.apache.org/jira/browse/MESOS-4160?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Alexander Rukletsov updated MESOS-4160:
---
Labels: mesosphere newbie++ tech-debt (was: mesosphere tech-debt)
> Log recover tests are slow
> --
>
> Key: MESOS-4160
> URL: https://issues.apache.org/jira/browse/MESOS-4160
> Project: Mesos
> Issue Type: Improvement
> Components: technical debt, test
>Reporter: Alexander Rukletsov
>Priority: Minor
> Labels: mesosphere, newbie++, tech-debt
>
> On Mac OS 10.10.4, some tests take longer than {{1s}} to finish:
> {code}
> RecoverTest.AutoInitialization (1003 ms)
> RecoverTest.AutoInitializationRetry (1000 ms)
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (MESOS-4162) SlaveTest.MetricsSlaveLaunchErrors is slow
[
https://issues.apache.org/jira/browse/MESOS-4162?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Alexander Rukletsov updated MESOS-4162:
---
Description:
The {{SlaveTest.MetricsSlaveLaunchErrors}} test takes around {{1s}} to finish
on my Mac OS 10.10.4:
{code}
SlaveTest.MetricsSlaveLaunchErrors (1009 ms)
{code}
was:
The {{SlaveTest.MetricsSlaveLaunchErrors}} test takes around {{1s}} on my Mac
OS 10.10.4 to finish:
{code}
SlaveTest.MetricsSlaveLaunchErrors (1009 ms)
{code}
> SlaveTest.MetricsSlaveLaunchErrors is slow
> --
>
> Key: MESOS-4162
> URL: https://issues.apache.org/jira/browse/MESOS-4162
> Project: Mesos
> Issue Type: Improvement
> Components: technical debt, test
>Reporter: Alexander Rukletsov
>Priority: Minor
> Labels: mesosphere, tech-debt
>
> The {{SlaveTest.MetricsSlaveLaunchErrors}} test takes around {{1s}} to finish
> on my Mac OS 10.10.4:
> {code}
> SlaveTest.MetricsSlaveLaunchErrors (1009 ms)
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (MESOS-4172) GarbageCollectorIntegrationTest.Restart is slow
[
https://issues.apache.org/jira/browse/MESOS-4172?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Alexander Rukletsov updated MESOS-4172:
---
Labels: mesosphere newbie++ tech-debt (was: mesosphere tech-debt)
> GarbageCollectorIntegrationTest.Restart is slow
> ---
>
> Key: MESOS-4172
> URL: https://issues.apache.org/jira/browse/MESOS-4172
> Project: Mesos
> Issue Type: Improvement
> Components: technical debt, test
>Reporter: Alexander Rukletsov
>Priority: Minor
> Labels: mesosphere, newbie++, tech-debt
>
> The {{GarbageCollectorIntegrationTest.Restart}} test takes more than {{5s}}
> to finish on my Mac OS 10.10.4:
> {code}
> GarbageCollectorIntegrationTest.Restart (5102 ms)
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (MESOS-4173) HealthCheckTest.CheckCommandTimeout is slow
[
https://issues.apache.org/jira/browse/MESOS-4173?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Alexander Rukletsov updated MESOS-4173:
---
Labels: mesosphere newbie++ tech-debt (was: mesosphere tech-debt)
> HealthCheckTest.CheckCommandTimeout is slow
> ---
>
> Key: MESOS-4173
> URL: https://issues.apache.org/jira/browse/MESOS-4173
> Project: Mesos
> Issue Type: Improvement
> Components: technical debt, test
>Reporter: Alexander Rukletsov
>Priority: Minor
> Labels: mesosphere, newbie++, tech-debt
>
> The {{HealthCheckTest.CheckCommandTimeout}} test takes more than {{15s}}! to
> finish on my Mac OS 10.10.4:
> {code}
> HealthCheckTest.CheckCommandTimeout (15483 ms)
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (MESOS-1757) Speed up the tests
[ https://issues.apache.org/jira/browse/MESOS-1757?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alexander Rukletsov updated MESOS-1757: --- Summary: Speed up the tests (was: Speed up the tests.) > Speed up the tests > -- > > Key: MESOS-1757 > URL: https://issues.apache.org/jira/browse/MESOS-1757 > Project: Mesos > Issue Type: Epic > Components: technical debt, test >Reporter: Benjamin Mahler >Assignee: haosdent > Labels: mesosphere, tech-debt, twitter > > The full test suite is exceeding the 9 minute mark (581 seconds on my > machine), this epic is to track techniques to improve this: > # Now that the master and the slave have to perform sync'ed disk writes, > consider using tmpfs (e.g. under /dev/shm) to speed up the disk writes. For > the master, we could also consider defaulting to in-memory state rather than > the replicated log for most tests. > # -The reaper takes a full second to reap an exited process (MESOS-1199), > this adds a second to each slave recovery test, and possibly more for things > that rely on Subprocess.- > # The command executor sleeps for a second when shutting down (MESOS-442), > this adds a second to every test that uses the command executor. > A big improvement will come from running the tests in parallel, a few options: > # Use automake's parallel test harness to compile tests separately and run > tests in parallel (see > [here|http://www.gnu.org/software/automake/manual/html_node/Parallel-Test-Harness.html]). > # Continue to use one test binary, but leverage google test's ability to > shard tests across processes/machines (see > [here|https://code.google.com/p/googletest/wiki/AdvancedGuide#Distributing_Test_Functions_to_Multiple_Machines]). > This entails writing our own test wrapper script in support to decide many > workers to use, etc. > [gtest-parallel|https://github.com/google/gtest-parallel/blob/master/gtest-parallel] > is an example of a parallel runner, but does not leverage the sharding > ability. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (MESOS-4161) SlaveTest.CommandExecutorWithOverride is slow
[
https://issues.apache.org/jira/browse/MESOS-4161?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Alexander Rukletsov updated MESOS-4161:
---
Description:
The {{SlaveTest.CommandExecutorWithOverride}} takes around `1.3s` on my Mac OS
10.10.4 to finish:
{code}
SlaveTest.CommandExecutorWithOverride (1311 ms)
{code}
was:
The {{SlaveTest.CommandExecutorWithOverride}} takes around 1.3s on my Mac OS
10.10.4 to finish:
{code}
SlaveTest.CommandExecutorWithOverride (1311 ms)
{code}
> SlaveTest.CommandExecutorWithOverride is slow
> -
>
> Key: MESOS-4161
> URL: https://issues.apache.org/jira/browse/MESOS-4161
> Project: Mesos
> Issue Type: Improvement
> Components: technical debt, test
>Reporter: Alexander Rukletsov
>Priority: Minor
> Labels: mesosphere, tech-debt
>
> The {{SlaveTest.CommandExecutorWithOverride}} takes around `1.3s` on my Mac
> OS 10.10.4 to finish:
> {code}
> SlaveTest.CommandExecutorWithOverride (1311 ms)
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Created] (MESOS-4165) MasterTest.MasterInfoOnReElection is slow
Alexander Rukletsov created MESOS-4165:
--
Summary: MasterTest.MasterInfoOnReElection is slow
Key: MESOS-4165
URL: https://issues.apache.org/jira/browse/MESOS-4165
Project: Mesos
Issue Type: Improvement
Components: technical debt, test
Reporter: Alexander Rukletsov
Priority: Minor
The {{MasterTest.MasterInfoOnReElection}} test takes more than {{1s}} to finish
on my Mac OS 10.10.4:
{code}
MasterTest.MasterInfoOnReElection (1024 ms)
{code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Created] (MESOS-4164) MasterTest.RecoverResources is slow
Alexander Rukletsov created MESOS-4164:
--
Summary: MasterTest.RecoverResources is slow
Key: MESOS-4164
URL: https://issues.apache.org/jira/browse/MESOS-4164
Project: Mesos
Issue Type: Improvement
Components: technical debt, test
Reporter: Alexander Rukletsov
Priority: Minor
The {{MasterTest.RecoverResources}} test takes more than {{1s}} to finish on my
Mac OS 10.10.4:
{code}
MasterTest.RecoverResources (1018 ms)
{code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (MESOS-4155) Speed up ExamplesTest.*
[
https://issues.apache.org/jira/browse/MESOS-4155?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Alexander Rukletsov updated MESOS-4155:
---
Summary: Speed up ExamplesTest.* (was: Speedup ExamplesTest.*)
> Speed up ExamplesTest.*
> ---
>
> Key: MESOS-4155
> URL: https://issues.apache.org/jira/browse/MESOS-4155
> Project: Mesos
> Issue Type: Epic
> Components: technical debt, test
>Reporter: Alexander Rukletsov
>Priority: Minor
> Labels: mesosphere, tech-debt
>
> Execution times on Mac OS 10.10.4:
> {code}
> ExamplesTest.TestFramework (5225 ms)
> ExamplesTest.NoExecutorFramework (5387 ms)
> ExamplesTest.EventCallFramework (1238 ms)
> ExamplesTest.PersistentVolumeFramework (3380 ms)
> ExamplesTest.JavaFramework (6159 ms)
> ExamplesTest.JavaException (1 ms)
> ExamplesTest.JavaLog (1174 ms)
> ExamplesTest.PythonFramework (7126 ms)
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (MESOS-4160) Log recover tests are slow
[
https://issues.apache.org/jira/browse/MESOS-4160?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Alexander Rukletsov updated MESOS-4160:
---
Labels: mesosphere tech-debt (was: mesosphere)
> Log recover tests are slow
> --
>
> Key: MESOS-4160
> URL: https://issues.apache.org/jira/browse/MESOS-4160
> Project: Mesos
> Issue Type: Improvement
> Components: technical debt, test
>Reporter: Alexander Rukletsov
>Priority: Minor
> Labels: mesosphere, tech-debt
>
> On Mac OS 10.10.4, some tests take longer than 1s to finish:
> {code}
> RecoverTest.AutoInitialization (1003 ms)
> RecoverTest.AutoInitializationRetry (1000 ms)
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Created] (MESOS-4168) MasterMaintenanceTest.EnterMaintenanceMode is slow
Alexander Rukletsov created MESOS-4168:
--
Summary: MasterMaintenanceTest.EnterMaintenanceMode is slow
Key: MESOS-4168
URL: https://issues.apache.org/jira/browse/MESOS-4168
Project: Mesos
Issue Type: Improvement
Components: technical debt, test
Reporter: Alexander Rukletsov
Priority: Minor
The {{MasterMaintenanceTest.EnterMaintenanceMode}} test takes more than {{5s}}
to finish on my Mac OS 10.10.4:
{code}
MasterMaintenanceTest.EnterMaintenanceMode (5087 ms)
{code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Created] (MESOS-4161) SlaveTest.CommandExecutorWithOverride is slow
Alexander Rukletsov created MESOS-4161:
--
Summary: SlaveTest.CommandExecutorWithOverride is slow
Key: MESOS-4161
URL: https://issues.apache.org/jira/browse/MESOS-4161
Project: Mesos
Issue Type: Improvement
Components: technical debt, test
Reporter: Alexander Rukletsov
Priority: Minor
The {{SlaveTest.CommandExecutorWithOverride}} takes around 1.3s on my Mac OS
10.10.4 to finish:
{code}
SlaveTest.CommandExecutorWithOverride (1311 ms)
{code}
--
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
]
Alexander Rukletsov updated MESOS-4156:
---
Summary: Speed up FetcherCacheTest.* and FetcherCacheHttpTest.* (was:
Speedup FetcherCacheTest.* and FetcherCacheHttpTest.*)
> 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
>Priority: Minor
> Labels: mesosphere, 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] [Created] (MESOS-4170) OversubscriptionTest.UpdateAllocatorOnSchedulerFailover is slow
Alexander Rukletsov created MESOS-4170:
--
Summary: OversubscriptionTest.UpdateAllocatorOnSchedulerFailover
is slow
Key: MESOS-4170
URL: https://issues.apache.org/jira/browse/MESOS-4170
Project: Mesos
Issue Type: Improvement
Components: technical debt, test
Reporter: Alexander Rukletsov
Priority: Minor
The {{OversubscriptionTest.UpdateAllocatorOnSchedulerFailover}} test takes more
than {{1s}} to finish on my Mac OS 10.10.4:
{code}
OversubscriptionTest.UpdateAllocatorOnSchedulerFailover (1018 ms)
{code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Created] (MESOS-4174) HookTest.VerifySlaveLaunchExecutorHook is slow
Alexander Rukletsov created MESOS-4174:
--
Summary: HookTest.VerifySlaveLaunchExecutorHook is slow
Key: MESOS-4174
URL: https://issues.apache.org/jira/browse/MESOS-4174
Project: Mesos
Issue Type: Improvement
Components: technical debt, test
Reporter: Alexander Rukletsov
Priority: Minor
The {{HookTest.VerifySlaveLaunchExecutorHook}} test takes more than {{5s}} to
finish on my Mac OS 10.10.4:
{code}
HookTest.VerifySlaveLaunchExecutorHook (5061 ms)
{code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (MESOS-4174) HookTest.VerifySlaveLaunchExecutorHook is slow
[
https://issues.apache.org/jira/browse/MESOS-4174?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Alexander Rukletsov updated MESOS-4174:
---
Labels: mesosphere newbie++ tech-debt (was: mesosphere tech-debt)
> HookTest.VerifySlaveLaunchExecutorHook is slow
> --
>
> Key: MESOS-4174
> URL: https://issues.apache.org/jira/browse/MESOS-4174
> Project: Mesos
> Issue Type: Improvement
> Components: technical debt, test
>Reporter: Alexander Rukletsov
>Priority: Minor
> Labels: mesosphere, newbie++, tech-debt
>
> The {{HookTest.VerifySlaveLaunchExecutorHook}} test takes more than {{5s}} to
> finish on my Mac OS 10.10.4:
> {code}
> HookTest.VerifySlaveLaunchExecutorHook (5061 ms)
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (MESOS-3775) MasterAllocatorTest.SlaveLost is slow
[
https://issues.apache.org/jira/browse/MESOS-3775?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Alexander Rukletsov updated MESOS-3775:
---
Labels: mesosphere newbie++ tech-debt (was: mesosphere tech-debt)
> MasterAllocatorTest.SlaveLost is slow
> -
>
> Key: MESOS-3775
> URL: https://issues.apache.org/jira/browse/MESOS-3775
> Project: Mesos
> Issue Type: Improvement
> Components: technical debt, test
>Reporter: Alexander Rukletsov
>Priority: Minor
> Labels: mesosphere, newbie++, tech-debt
>
> The {{MasterAllocatorTest.SlaveLost}} takes more that {{5s}} to complete. A
> brief look into the code hints that the stopped agent does not quit
> immediately (and hence its resources are not released by the allocator)
> because [it waits for the executor to
> terminate|https://github.com/apache/mesos/blob/master/src/tests/master_allocator_tests.cpp#L717].
> {{5s}} timeout comes from {{EXECUTOR_SHUTDOWN_GRACE_PERIOD}} agent constant.
> Possible solutions:
> * Do not wait until the stopped agent quits (can be flaky, needs deeper
> analysis).
> * Decrease the agent's {{executor_shutdown_grace_period}} flag.
> * Terminate the executor faster (this may require some refactoring since the
> executor driver is created in the {{TestContainerizer}} and we do not have
> direct access to it.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (MESOS-4173) HealthCheckTest.CheckCommandTimeout is slow
[
https://issues.apache.org/jira/browse/MESOS-4173?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15058468#comment-15058468
]
haosdent commented on MESOS-4173:
-
[~tnachen]] have a patch to fix this. https://reviews.apache.org/r/40956/
> HealthCheckTest.CheckCommandTimeout is slow
> ---
>
> Key: MESOS-4173
> URL: https://issues.apache.org/jira/browse/MESOS-4173
> Project: Mesos
> Issue Type: Improvement
> Components: technical debt, test
>Reporter: Alexander Rukletsov
>Priority: Minor
> Labels: mesosphere, newbie++, tech-debt
>
> The {{HealthCheckTest.CheckCommandTimeout}} test takes more than {{15s}}! to
> finish on my Mac OS 10.10.4:
> {code}
> HealthCheckTest.CheckCommandTimeout (15483 ms)
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (MESOS-1757) Speed up the tests.
[ https://issues.apache.org/jira/browse/MESOS-1757?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alexander Rukletsov updated MESOS-1757: --- Labels: mesosphere tech-debt tech-debt-test twitter (was: twitter) > Speed up the tests. > --- > > Key: MESOS-1757 > URL: https://issues.apache.org/jira/browse/MESOS-1757 > Project: Mesos > Issue Type: Epic > Components: technical debt, test >Reporter: Benjamin Mahler >Assignee: haosdent > Labels: mesosphere, tech-debt, tech-debt-test, twitter > > The full test suite is exceeding the 9 minute mark (581 seconds on my > machine), this epic is to track techniques to improve this: > # Now that the master and the slave have to perform sync'ed disk writes, > consider using tmpfs (e.g. under /dev/shm) to speed up the disk writes. For > the master, we could also consider defaulting to in-memory state rather than > the replicated log for most tests. > # -The reaper takes a full second to reap an exited process (MESOS-1199), > this adds a second to each slave recovery test, and possibly more for things > that rely on Subprocess.- > # The command executor sleeps for a second when shutting down (MESOS-442), > this adds a second to every test that uses the command executor. > A big improvement will come from running the tests in parallel, a few options: > # Use automake's parallel test harness to compile tests separately and run > tests in parallel (see > [here|http://www.gnu.org/software/automake/manual/html_node/Parallel-Test-Harness.html]). > # Continue to use one test binary, but leverage google test's ability to > shard tests across processes/machines (see > [here|https://code.google.com/p/googletest/wiki/AdvancedGuide#Distributing_Test_Functions_to_Multiple_Machines]). > This entails writing our own test wrapper script in support to decide many > workers to use, etc. > [gtest-parallel|https://github.com/google/gtest-parallel/blob/master/gtest-parallel] > is an example of a parallel runner, but does not leverage the sharding > ability. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (MESOS-4155) Speedup ExamplesTest.*
Alexander Rukletsov created MESOS-4155:
--
Summary: Speedup ExamplesTest.*
Key: MESOS-4155
URL: https://issues.apache.org/jira/browse/MESOS-4155
Project: Mesos
Issue Type: Epic
Components: technical debt, test
Reporter: Alexander Rukletsov
Priority: Minor
Execution times on Mac OS 10.10.4:
{code}
ExamplesTest.TestFramework (5225 ms)
ExamplesTest.NoExecutorFramework (5387 ms)
ExamplesTest.EventCallFramework (1238 ms)
ExamplesTest.PersistentVolumeFramework (3380 ms)
ExamplesTest.JavaFramework (6159 ms)
ExamplesTest.JavaException (1 ms)
ExamplesTest.JavaLog (1174 ms)
ExamplesTest.PythonFramework (7126 ms)
{code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (MESOS-4173) HealthCheckTest.CheckCommandTimeout is slow
[
https://issues.apache.org/jira/browse/MESOS-4173?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Alexander Rukletsov updated MESOS-4173:
---
Description:
The {{HealthCheckTest.CheckCommandTimeout{}} test takes more than {{15s}}! to
finish on my Mac OS 10.10.4:
{code}
HealthCheckTest.CheckCommandTimeout (15483 ms)
{code}
was:
The {HealthCheckTest.CheckCommandTimeout{}} test takes more than {{15s}}! to
finish on my Mac OS 10.10.4:
{code}
HealthCheckTest.CheckCommandTimeout (15483 ms)
{code}
> HealthCheckTest.CheckCommandTimeout is slow
> ---
>
> Key: MESOS-4173
> URL: https://issues.apache.org/jira/browse/MESOS-4173
> Project: Mesos
> Issue Type: Improvement
> Components: technical debt, test
>Reporter: Alexander Rukletsov
>Priority: Minor
> Labels: mesosphere, tech-debt
>
> The {{HealthCheckTest.CheckCommandTimeout{}} test takes more than {{15s}}! to
> finish on my Mac OS 10.10.4:
> {code}
> HealthCheckTest.CheckCommandTimeout (15483 ms)
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Created] (MESOS-4160) Log recover tests are slow
Alexander Rukletsov created MESOS-4160:
--
Summary: Log recover tests are slow
Key: MESOS-4160
URL: https://issues.apache.org/jira/browse/MESOS-4160
Project: Mesos
Issue Type: Improvement
Components: technical debt, test
Reporter: Alexander Rukletsov
Priority: Minor
On Mac OS 10.10.4, some tests take longer than 1s to finish:
{code}
RecoverTest.AutoInitialization (1003 ms)
RecoverTest.AutoInitializationRetry (1000 ms)
{code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (MESOS-4162) SlaveTest.MetricsSlaveLaunchErrors is slow
[
https://issues.apache.org/jira/browse/MESOS-4162?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Alexander Rukletsov updated MESOS-4162:
---
Labels: mesosphere newbie++ tech-debt (was: mesosphere tech-debt)
> SlaveTest.MetricsSlaveLaunchErrors is slow
> --
>
> Key: MESOS-4162
> URL: https://issues.apache.org/jira/browse/MESOS-4162
> Project: Mesos
> Issue Type: Improvement
> Components: technical debt, test
>Reporter: Alexander Rukletsov
>Priority: Minor
> Labels: mesosphere, newbie++, tech-debt
>
> The {{SlaveTest.MetricsSlaveLaunchErrors}} test takes around {{1s}} to finish
> on my Mac OS 10.10.4:
> {code}
> SlaveTest.MetricsSlaveLaunchErrors (1009 ms)
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (MESOS-4161) SlaveTest.CommandExecutorWithOverride is slow
[
https://issues.apache.org/jira/browse/MESOS-4161?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Alexander Rukletsov updated MESOS-4161:
---
Labels: mesosphere newbie++ tech-debt (was: mesosphere tech-debt)
> SlaveTest.CommandExecutorWithOverride is slow
> -
>
> Key: MESOS-4161
> URL: https://issues.apache.org/jira/browse/MESOS-4161
> Project: Mesos
> Issue Type: Improvement
> Components: technical debt, test
>Reporter: Alexander Rukletsov
>Priority: Minor
> Labels: mesosphere, newbie++, tech-debt
>
> The {{SlaveTest.CommandExecutorWithOverride}} test takes around {{1.3s}} to
> finish on my Mac OS 10.10.4:
> {code}
> SlaveTest.CommandExecutorWithOverride (1311 ms)
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (MESOS-4167) MasterTest.OfferTimeout is slow
[
https://issues.apache.org/jira/browse/MESOS-4167?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Alexander Rukletsov updated MESOS-4167:
---
Labels: mesosphere newbie++ tech-debt (was: mesosphere tech-debt)
> MasterTest.OfferTimeout is slow
> ---
>
> Key: MESOS-4167
> URL: https://issues.apache.org/jira/browse/MESOS-4167
> Project: Mesos
> Issue Type: Improvement
> Components: technical debt, test
>Reporter: Alexander Rukletsov
>Priority: Minor
> Labels: mesosphere, newbie++, tech-debt
>
> The {{MasterTest.OfferTimeout}} test takes more than {{1s}} to finish on my
> Mac OS 10.10.4:
> {code}
> MasterTest.OfferTimeout (1053 ms)
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (MESOS-4163) SlaveTest.HTTPSchedulerSlaveRestart is slow
[
https://issues.apache.org/jira/browse/MESOS-4163?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Alexander Rukletsov updated MESOS-4163:
---
Labels: mesosphere newbie++ tech-debt (was: mesosphere tech-debt)
> SlaveTest.HTTPSchedulerSlaveRestart is slow
> ---
>
> Key: MESOS-4163
> URL: https://issues.apache.org/jira/browse/MESOS-4163
> Project: Mesos
> Issue Type: Improvement
> Components: technical debt, test
>Reporter: Alexander Rukletsov
>Priority: Minor
> Labels: mesosphere, newbie++, tech-debt
>
> The {{SlaveTest.HTTPSchedulerSlaveRestart}} test takes more than {{2s}} to
> finish on my Mac OS 10.10.4:
> {code}
> SlaveTest.HTTPSchedulerSlaveRestart (2307 ms)
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (MESOS-4166) MasterTest.LaunchCombinedOfferTest is slow
[
https://issues.apache.org/jira/browse/MESOS-4166?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Alexander Rukletsov updated MESOS-4166:
---
Labels: mesosphere newbie++ tech-debt (was: mesosphere tech-debt)
> MasterTest.LaunchCombinedOfferTest is slow
> --
>
> Key: MESOS-4166
> URL: https://issues.apache.org/jira/browse/MESOS-4166
> Project: Mesos
> Issue Type: Improvement
> Components: technical debt, test
>Reporter: Alexander Rukletsov
>Priority: Minor
> Labels: mesosphere, newbie++, tech-debt
>
> The {{MasterTest.LaunchCombinedOfferTest}} test takes more than {{2s}} to
> finish on my Mac OS 10.10.4:
> {code}
> MasterTest.LaunchCombinedOfferTest (2023 ms)
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (MESOS-4158) Speed up SlaveRecoveryTest.*
[
https://issues.apache.org/jira/browse/MESOS-4158?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Alexander Rukletsov updated MESOS-4158:
---
Labels: mesosphere newbie++ tech-debt (was: mesosphere tech-debt)
> Speed up SlaveRecoveryTest.*
>
>
> Key: MESOS-4158
> URL: https://issues.apache.org/jira/browse/MESOS-4158
> Project: Mesos
> Issue Type: Epic
> Components: technical debt, test
>Reporter: Alexander Rukletsov
>Priority: Minor
> Labels: mesosphere, newbie++, tech-debt
>
> Execution times on Mac OS 10.10.4:
> {code}
> SlaveRecoveryTest/0.RecoverStatusUpdateManager (2260 ms)
> SlaveRecoveryTest/0.ReconnectExecutor (2261 ms)
> SlaveRecoveryTest/0.RecoverCompletedExecutor (1288 ms)
> SlaveRecoveryTest/0.CleanupExecutor (1290 ms)
> SlaveRecoveryTest/0.Reboot (1360 ms)
> SlaveRecoveryTest/0.ShutdownSlave (1321 ms)
> SlaveRecoveryTest/0.ShutdownSlaveSIGUSR1 (1360 ms)
> SlaveRecoveryTest/0.ReconcileKillTask (3123 ms)
> SlaveRecoveryTest/0.ReconcileShutdownFramework (3353 ms)
> SlaveRecoveryTest/0.MasterFailover (1355 ms)
> SlaveRecoveryTest/0.MultipleFrameworks (1555 ms)
> SlaveRecoveryTest/0.MultipleSlaves (1444 ms)
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (MESOS-2059) improve performance of expensive tests
[
https://issues.apache.org/jira/browse/MESOS-2059?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Alexander Rukletsov updated MESOS-2059:
---
Labels: tech-debt (was: )
> improve performance of expensive tests
> --
>
> Key: MESOS-2059
> URL: https://issues.apache.org/jira/browse/MESOS-2059
> Project: Mesos
> Issue Type: Improvement
> Components: technical debt, test
>Reporter: Dominic Hamon
>Priority: Minor
> Labels: tech-debt
>
> Many of our tests take a long time to run which has an impact on the
> developer compile-test cycle. Improving the performance of the worst cases
> can lead to a significant improvement in developer workflow.
> A quick test shows that focusing on a few key test fixtures might be
> worthwhile:
> {noformat}
> $ egrep '\(.* ms\)$' test.log | cut -d\ -f10- | cut -d\ -f1-2 | sed 's/(//'
> | sort -k2 -rn | head -n 30
> ZooKeeperMasterContenderDetectorTest.NonRetryableFrrors 15107
> ZooKeeperMasterContenderDetectorTest.MasterDetectorExpireMasterZKSession 13473
> ZooKeeperMasterContenderDetectorTest.MasterDetectorExpireSlaveZKSessionNewMaster
> 13434
> ZooKeeperMasterContenderDetectorTest.MasterContenders 10089
> ZooKeeperMasterContenderDetectorTest.MasterDetectorTimedoutSession 10081
> ZooKeeperMasterContenderDetectorTest.ContenderDetectorShutdownNetwork 8459
> ZooKeeperMasterContenderDetectorTest.MasterDetectorExpireSlaveZKSession 8424
> ZooKeeperMasterContenderDetectorTest.MasterContender 8397
> SlaveRecoveryTest/0.MultipleFrameworks 7971
> ExamplesTest.PythonFramework 7326
> HealthCheckTest.GracePeriod 6552
> SlaveRecoveryTest/0.ReconcileKillTask 6150
> ExamplesTest.LowLevelSchedulerPthread 6113
> ExamplesTest.JavaFramework 5543
> ExamplesTest.NoExecutorFramework 5391
> ExamplesTest.TestFramework 5282
> ExamplesTest.LowLevelSchedulerLibprocess 5282
> ExamplesTest.JavaException 5177
> ZooKeeperMasterContenderDetectorTest.ContenderPendingElection 5046
> BasicMasterContenderDetectorTest.Detector 5010
> BasicMasterContenderDetectorTest.Contender 5004
> SlaveRecoveryTest/0.MultipleSlaves 4845
> SlaveRecoveryTest/0.MasterFailover 4736
> SlaveRecoveryTest/0.ShutdownSlave 4517
> SlaveRecoveryTest/0.ShutdownSlaveSIGUSR1 4482
> SlaveRecoveryTest/0.Reboot 4481
> SlaveRecoveryTest/0.KillTask 3600
> SlaveRecoveryTest/0.SchedulerFailover 3542
> SlaveRecoveryTest/0.ReconcileShutdownFramework 3534
> GroupTest.GroupJoinWithDisconnect 3384
> {noformat}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (MESOS-1757) Speed up the tests.
[ https://issues.apache.org/jira/browse/MESOS-1757?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alexander Rukletsov updated MESOS-1757: --- Labels: mesosphere tech-debt twitter (was: mesosphere tech-debt tech-debt-test twitter) > Speed up the tests. > --- > > Key: MESOS-1757 > URL: https://issues.apache.org/jira/browse/MESOS-1757 > Project: Mesos > Issue Type: Epic > Components: technical debt, test >Reporter: Benjamin Mahler >Assignee: haosdent > Labels: mesosphere, tech-debt, twitter > > The full test suite is exceeding the 9 minute mark (581 seconds on my > machine), this epic is to track techniques to improve this: > # Now that the master and the slave have to perform sync'ed disk writes, > consider using tmpfs (e.g. under /dev/shm) to speed up the disk writes. For > the master, we could also consider defaulting to in-memory state rather than > the replicated log for most tests. > # -The reaper takes a full second to reap an exited process (MESOS-1199), > this adds a second to each slave recovery test, and possibly more for things > that rely on Subprocess.- > # The command executor sleeps for a second when shutting down (MESOS-442), > this adds a second to every test that uses the command executor. > A big improvement will come from running the tests in parallel, a few options: > # Use automake's parallel test harness to compile tests separately and run > tests in parallel (see > [here|http://www.gnu.org/software/automake/manual/html_node/Parallel-Test-Harness.html]). > # Continue to use one test binary, but leverage google test's ability to > shard tests across processes/machines (see > [here|https://code.google.com/p/googletest/wiki/AdvancedGuide#Distributing_Test_Functions_to_Multiple_Machines]). > This entails writing our own test wrapper script in support to decide many > workers to use, etc. > [gtest-parallel|https://github.com/google/gtest-parallel/blob/master/gtest-parallel] > is an example of a parallel runner, but does not leverage the sharding > ability. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (MESOS-4156) Speedup FetcherCacheTest.* and FetcherCacheHttpTest.*
[
https://issues.apache.org/jira/browse/MESOS-4156?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Alexander Rukletsov updated MESOS-4156:
---
Priority: Minor (was: Major)
> Speedup 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
>Priority: Minor
> Labels: mesosphere, 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-4160) Log recover tests are slow
[
https://issues.apache.org/jira/browse/MESOS-4160?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Alexander Rukletsov updated MESOS-4160:
---
Description:
On Mac OS 10.10.4, some tests take longer than {{1s}} to finish:
{code}
RecoverTest.AutoInitialization (1003 ms)
RecoverTest.AutoInitializationRetry (1000 ms)
{code}
was:
On Mac OS 10.10.4, some tests take longer than 1s to finish:
{code}
RecoverTest.AutoInitialization (1003 ms)
RecoverTest.AutoInitializationRetry (1000 ms)
{code}
> Log recover tests are slow
> --
>
> Key: MESOS-4160
> URL: https://issues.apache.org/jira/browse/MESOS-4160
> Project: Mesos
> Issue Type: Improvement
> Components: technical debt, test
>Reporter: Alexander Rukletsov
>Priority: Minor
> Labels: mesosphere, tech-debt
>
> On Mac OS 10.10.4, some tests take longer than {{1s}} to finish:
> {code}
> RecoverTest.AutoInitialization (1003 ms)
> RecoverTest.AutoInitializationRetry (1000 ms)
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Created] (MESOS-4171) OversubscriptionTest.RemoveCapabilitiesOnSchedulerFailover is slow
Alexander Rukletsov created MESOS-4171:
--
Summary:
OversubscriptionTest.RemoveCapabilitiesOnSchedulerFailover is slow
Key: MESOS-4171
URL: https://issues.apache.org/jira/browse/MESOS-4171
Project: Mesos
Issue Type: Improvement
Components: technical debt, test
Reporter: Alexander Rukletsov
Priority: Minor
The {{OversubscriptionTest.RemoveCapabilitiesOnSchedulerFailover}} test takes
more than {{1s}} to finish on my Mac OS 10.10.4:
{code}
OversubscriptionTest.RemoveCapabilitiesOnSchedulerFailover (1018 ms)
{code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (MESOS-4157) Speed up ZooKeeper-related tests
[
https://issues.apache.org/jira/browse/MESOS-4157?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Alexander Rukletsov updated MESOS-4157:
---
Labels: mesosphere newbie++ tech-debt (was: mesosphere tech-debt)
> Speed up ZooKeeper-related tests
>
>
> Key: MESOS-4157
> URL: https://issues.apache.org/jira/browse/MESOS-4157
> Project: Mesos
> Issue Type: Epic
> Components: technical debt, test
>Reporter: Alexander Rukletsov
>Priority: Minor
> Labels: mesosphere, newbie++, tech-debt
>
> Execution times on Mac OS 10.10.4:
> {code}
> ZooKeeperTest.Auth (6688 ms)
> ZooKeeperTest.Create (6690 ms)
> ZooKeeperTest.LeaderContender (3385 ms)
> MasterZooKeeperTest.MasterInfoAddress (11282 ms)
> ZooKeeperMasterContenderDetectorTest.NonRetryableFrrors (10053 ms)
> ZooKeeperMasterContenderDetectorTest.ContenderDetectorShutdownNetwork (3390
> ms)
> ZooKeeperMasterContenderDetectorTest.MasterDetectorExpireSlaveZKSession (3358
> ms)
> ZooKeeperMasterContenderDetectorTest.MasterDetectorExpireSlaveZKSessionNewMaster
> (3359 ms)
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (MESOS-3775) MasterAllocatorTest.SlaveLost is slow
[
https://issues.apache.org/jira/browse/MESOS-3775?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Alexander Rukletsov updated MESOS-3775:
---
Issue Type: Improvement (was: Bug)
> MasterAllocatorTest.SlaveLost is slow
> -
>
> Key: MESOS-3775
> URL: https://issues.apache.org/jira/browse/MESOS-3775
> Project: Mesos
> Issue Type: Improvement
> Components: technical debt, test
>Reporter: Alexander Rukletsov
>Priority: Minor
> Labels: mesosphere, tech-debt
>
> The {{MasterAllocatorTest.SlaveLost}} takes more that {{5s}} to complete. A
> brief look into the code hints that the stopped agent does not quit
> immediately (and hence its resources are not released by the allocator)
> because [it waits for the executor to
> terminate|https://github.com/apache/mesos/blob/master/src/tests/master_allocator_tests.cpp#L717].
> {{5s}} timeout comes from {{EXECUTOR_SHUTDOWN_GRACE_PERIOD}} agent constant.
> Possible solutions:
> * Do not wait until the stopped agent quits (can be flaky, needs deeper
> analysis).
> * Decrease the agent's {{executor_shutdown_grace_period}} flag.
> * Terminate the executor faster (this may require some refactoring since the
> executor driver is created in the {{TestContainerizer}} and we do not have
> direct access to it.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Comment Edited] (MESOS-4137) Modularize plain-file logging for executor/task logs launched with the Docker Containerizer
[
https://issues.apache.org/jira/browse/MESOS-4137?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15057100#comment-15057100
]
Joseph Wu edited comment on MESOS-4137 at 12/15/15 5:22 PM:
|| Reviews || Summary ||
| https://reviews.apache.org/r/41294/ | Add {{ContainerLogger}} to
{{DockerContainerizer}} |
| https://reviews.apache.org/r/41369/ | Add {{ContainerLogger}} to
{{mesos-docker-executor}} |
| https://reviews.apache.org/r/41370/ | Update {{MesosTest}} |
| https://reviews.apache.org/r/41378/ | Update {{DockerContainerizer}} tests |
was (Author: kaysoky):
|| Reviews || Summary ||
| https://reviews.apache.org/r/41294/ | Add {{ContainerLogger}} to
{{DockerContainerizer}} |
| https://reviews.apache.org/r/41369/ | Add {{ContainerLogger}} to
{{mesos-docker-executor}} |
| https://reviews.apache.org/r/41370/ | Update {{MesosTest}} |
| https://reviews.apache.org/r/41378/ | Update {{DockerContainerizer}} tests |
| https://reviews.apache.org/r/41386/ | Add regression test |
> Modularize plain-file logging for executor/task logs launched with the Docker
> Containerizer
> ---
>
> Key: MESOS-4137
> URL: https://issues.apache.org/jira/browse/MESOS-4137
> Project: Mesos
> Issue Type: Task
> Components: docker, modules
>Reporter: Joseph Wu
>Assignee: Joseph Wu
> Labels: logging, mesosphere
>
> Adding a hook inside the Docker containerizer is slightly more involved than
> the Mesos containerizer.
> Docker executors/tasks perform plain-file logging in different places
> depending on whether the agent is in a Docker container itself
> || Agent || Code ||
> | Not in container | {{DockerContainerizerProcess::launchExecutorProcess}} |
> | In container | {{Docker::run}} in a {{mesos-docker-executor}} process |
> This means a {{ContainerLogger}} will need to be loaded or hooked into the
> {{mesos-docker-executor}}.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (MESOS-4161) SlaveTest.CommandExecutorWithOverride is slow
[
https://issues.apache.org/jira/browse/MESOS-4161?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Alexander Rukletsov updated MESOS-4161:
---
Description:
The {{SlaveTest.CommandExecutorWithOverride}} takes around {{1.3s}} on my Mac
OS 10.10.4 to finish:
{code}
SlaveTest.CommandExecutorWithOverride (1311 ms)
{code}
was:
The {{SlaveTest.CommandExecutorWithOverride}} takes around `1.3s` on my Mac OS
10.10.4 to finish:
{code}
SlaveTest.CommandExecutorWithOverride (1311 ms)
{code}
> SlaveTest.CommandExecutorWithOverride is slow
> -
>
> Key: MESOS-4161
> URL: https://issues.apache.org/jira/browse/MESOS-4161
> Project: Mesos
> Issue Type: Improvement
> Components: technical debt, test
>Reporter: Alexander Rukletsov
>Priority: Minor
> Labels: mesosphere, tech-debt
>
> The {{SlaveTest.CommandExecutorWithOverride}} takes around {{1.3s}} on my Mac
> OS 10.10.4 to finish:
> {code}
> SlaveTest.CommandExecutorWithOverride (1311 ms)
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Created] (MESOS-4162) SlaveTest.MetricsSlaveLaunchErrors is slow
Alexander Rukletsov created MESOS-4162:
--
Summary: SlaveTest.MetricsSlaveLaunchErrors is slow
Key: MESOS-4162
URL: https://issues.apache.org/jira/browse/MESOS-4162
Project: Mesos
Issue Type: Improvement
Components: technical debt, test
Reporter: Alexander Rukletsov
Priority: Minor
The {{SlaveTest.MetricsSlaveLaunchErrors}} test takes around {{1s}} on my Mac
OS 10.10.4 to finish:
{code}
SlaveTest.MetricsSlaveLaunchErrors (1009 ms)
{code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (MESOS-4155) Speed up ExamplesTest.*
[
https://issues.apache.org/jira/browse/MESOS-4155?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Alexander Rukletsov updated MESOS-4155:
---
Labels: mesosphere newbie++ tech-debt (was: mesosphere tech-debt)
> Speed up ExamplesTest.*
> ---
>
> Key: MESOS-4155
> URL: https://issues.apache.org/jira/browse/MESOS-4155
> Project: Mesos
> Issue Type: Epic
> Components: technical debt, test
>Reporter: Alexander Rukletsov
>Priority: Minor
> Labels: mesosphere, newbie++, tech-debt
>
> Execution times on Mac OS 10.10.4:
> {code}
> ExamplesTest.TestFramework (5225 ms)
> ExamplesTest.NoExecutorFramework (5387 ms)
> ExamplesTest.EventCallFramework (1238 ms)
> ExamplesTest.PersistentVolumeFramework (3380 ms)
> ExamplesTest.JavaFramework (6159 ms)
> ExamplesTest.JavaException (1 ms)
> ExamplesTest.JavaLog (1174 ms)
> ExamplesTest.PythonFramework (7126 ms)
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (MESOS-3732) Speed up FaultToleranceTest.FrameworkReregister test
[
https://issues.apache.org/jira/browse/MESOS-3732?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Alexander Rukletsov updated MESOS-3732:
---
Labels: mesosphere newbie tech-debt (was: mesosphere newbie)
> Speed up FaultToleranceTest.FrameworkReregister test
>
>
> Key: MESOS-3732
> URL: https://issues.apache.org/jira/browse/MESOS-3732
> Project: Mesos
> Issue Type: Improvement
> Components: test
>Reporter: Alexander Rukletsov
>Assignee: Alexander Rukletsov
> Labels: mesosphere, newbie, tech-debt
>
> FaultToleranceTest.FrameworkReregister test takes more than one second to
> complete:
> {code}
> [ RUN ] FaultToleranceTest.FrameworkReregister
> [ OK ] FaultToleranceTest.FrameworkReregister (1056 ms)
> {code}
> There must be a {{1s}} timeout somewhere which we should mitigate via
> {{Clock::advance()}}.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Created] (MESOS-4158) Speed up SlaveRecoveryTest.*
Alexander Rukletsov created MESOS-4158:
--
Summary: Speed up SlaveRecoveryTest.*
Key: MESOS-4158
URL: https://issues.apache.org/jira/browse/MESOS-4158
Project: Mesos
Issue Type: Epic
Components: technical debt, test
Reporter: Alexander Rukletsov
Priority: Minor
Execution times on Mac OS 10.10.4:
{code}
SlaveRecoveryTest/0.RecoverStatusUpdateManager (2260 ms)
SlaveRecoveryTest/0.ReconnectExecutor (2261 ms)
SlaveRecoveryTest/0.RecoverCompletedExecutor (1288 ms)
SlaveRecoveryTest/0.CleanupExecutor (1290 ms)
SlaveRecoveryTest/0.Reboot (1360 ms)
SlaveRecoveryTest/0.ShutdownSlave (1321 ms)
SlaveRecoveryTest/0.ShutdownSlaveSIGUSR1 (1360 ms)
SlaveRecoveryTest/0.ReconcileKillTask (3123 ms)
SlaveRecoveryTest/0.ReconcileShutdownFramework (3353 ms)
SlaveRecoveryTest/0.MasterFailover (1355 ms)
SlaveRecoveryTest/0.MultipleFrameworks (1555 ms)
SlaveRecoveryTest/0.MultipleSlaves (1444 ms)
{code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Created] (MESOS-4159) Speed up GroupTest.*
Alexander Rukletsov created MESOS-4159:
--
Summary: Speed up GroupTest.*
Key: MESOS-4159
URL: https://issues.apache.org/jira/browse/MESOS-4159
Project: Mesos
Issue Type: Epic
Components: technical debt, test
Reporter: Alexander Rukletsov
Priority: Minor
Execution times on Mac OS 10.10.4:
{code}
GroupTest.GroupJoinWithDisconnect (3352 ms)
GroupTest.GroupDataWithDisconnect (3350 ms)
GroupTest.GroupCancelWithDisconnect (2013 ms)
GroupTest.GroupPathWithRestrictivePerms (13368 ms)
GroupTest.RetryableErrors (26720 ms)
{code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (MESOS-4161) SlaveTest.CommandExecutorWithOverride is slow
[
https://issues.apache.org/jira/browse/MESOS-4161?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Alexander Rukletsov updated MESOS-4161:
---
Description:
The {{SlaveTest.CommandExecutorWithOverride}} test takes around {{1.3s}} on my
Mac OS 10.10.4 to finish:
{code}
SlaveTest.CommandExecutorWithOverride (1311 ms)
{code}
was:
The {{SlaveTest.CommandExecutorWithOverride}} takes around {{1.3s}} on my Mac
OS 10.10.4 to finish:
{code}
SlaveTest.CommandExecutorWithOverride (1311 ms)
{code}
> SlaveTest.CommandExecutorWithOverride is slow
> -
>
> Key: MESOS-4161
> URL: https://issues.apache.org/jira/browse/MESOS-4161
> Project: Mesos
> Issue Type: Improvement
> Components: technical debt, test
>Reporter: Alexander Rukletsov
>Priority: Minor
> Labels: mesosphere, tech-debt
>
> The {{SlaveTest.CommandExecutorWithOverride}} test takes around {{1.3s}} on
> my Mac OS 10.10.4 to finish:
> {code}
> SlaveTest.CommandExecutorWithOverride (1311 ms)
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Created] (MESOS-4163) SlaveTest.HTTPSchedulerSlaveRestart is slow
Alexander Rukletsov created MESOS-4163:
--
Summary: SlaveTest.HTTPSchedulerSlaveRestart is slow
Key: MESOS-4163
URL: https://issues.apache.org/jira/browse/MESOS-4163
Project: Mesos
Issue Type: Improvement
Components: technical debt, test
Reporter: Alexander Rukletsov
Priority: Minor
The {{SlaveTest.HTTPSchedulerSlaveRestart}} test takes more than {{2s}} to
finish on my Mac OS 10.10.4:
{code}
SlaveTest.HTTPSchedulerSlaveRestart (2307 ms)
{code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Created] (MESOS-4176) Support CMake build on FreeBSD
David Forsythe created MESOS-4176: - Summary: Support CMake build on FreeBSD Key: MESOS-4176 URL: https://issues.apache.org/jira/browse/MESOS-4176 Project: Mesos Issue Type: Task Reporter: David Forsythe Assignee: David Forsythe As noted on [39634|https://reviews.apache.org/r/39634/], a few changes may be be needed to enable a FreeBSD CMake build. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (MESOS-4173) HealthCheckTest.CheckCommandTimeout is slow
[
https://issues.apache.org/jira/browse/MESOS-4173?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Alexander Rukletsov updated MESOS-4173:
---
Description:
The {{HealthCheckTest.CheckCommandTimeout}} test takes more than {{15s}}! to
finish on my Mac OS 10.10.4:
{code}
HealthCheckTest.CheckCommandTimeout (15483 ms)
{code}
was:
The {{HealthCheckTest.CheckCommandTimeout{}} test takes more than {{15s}}! to
finish on my Mac OS 10.10.4:
{code}
HealthCheckTest.CheckCommandTimeout (15483 ms)
{code}
> HealthCheckTest.CheckCommandTimeout is slow
> ---
>
> Key: MESOS-4173
> URL: https://issues.apache.org/jira/browse/MESOS-4173
> Project: Mesos
> Issue Type: Improvement
> Components: technical debt, test
>Reporter: Alexander Rukletsov
>Priority: Minor
> Labels: mesosphere, tech-debt
>
> The {{HealthCheckTest.CheckCommandTimeout}} test takes more than {{15s}}! to
> finish on my Mac OS 10.10.4:
> {code}
> HealthCheckTest.CheckCommandTimeout (15483 ms)
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Created] (MESOS-4172) GarbageCollectorIntegrationTest.Restart is slow
Alexander Rukletsov created MESOS-4172:
--
Summary: GarbageCollectorIntegrationTest.Restart is slow
Key: MESOS-4172
URL: https://issues.apache.org/jira/browse/MESOS-4172
Project: Mesos
Issue Type: Improvement
Components: technical debt, test
Reporter: Alexander Rukletsov
Priority: Minor
The {{GarbageCollectorIntegrationTest.Restart}} test takes more than {{5s}} to
finish on my Mac OS 10.10.4:
{code}
GarbageCollectorIntegrationTest.Restart (5102 ms)
{code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Created] (MESOS-4166) MasterTest.LaunchCombinedOfferTest is slow
Alexander Rukletsov created MESOS-4166:
--
Summary: MasterTest.LaunchCombinedOfferTest is slow
Key: MESOS-4166
URL: https://issues.apache.org/jira/browse/MESOS-4166
Project: Mesos
Issue Type: Improvement
Components: technical debt, test
Reporter: Alexander Rukletsov
Priority: Minor
The {{MasterTest.LaunchCombinedOfferTest}} test takes more than {{2s}} to
finish on my Mac OS 10.10.4:
{code}
MasterTest.LaunchCombinedOfferTest (2023 ms)
{code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Created] (MESOS-4157) Speed up ZooKeeper-related tests
Alexander Rukletsov created MESOS-4157:
--
Summary: Speed up ZooKeeper-related tests
Key: MESOS-4157
URL: https://issues.apache.org/jira/browse/MESOS-4157
Project: Mesos
Issue Type: Epic
Components: technical debt, test
Reporter: Alexander Rukletsov
Execution times on Mac OS 10.10.4:
{code}
ZooKeeperTest.Auth (6688 ms)
ZooKeeperTest.Create (6690 ms)
ZooKeeperTest.LeaderContender (3385 ms)
MasterZooKeeperTest.MasterInfoAddress (11282 ms)
ZooKeeperMasterContenderDetectorTest.NonRetryableFrrors (10053 ms)
ZooKeeperMasterContenderDetectorTest.ContenderDetectorShutdownNetwork (3390 ms)
ZooKeeperMasterContenderDetectorTest.MasterDetectorExpireSlaveZKSession (3358
ms)
ZooKeeperMasterContenderDetectorTest.MasterDetectorExpireSlaveZKSessionNewMaster
(3359 ms)
{code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (MESOS-3153) Add tests for HTTPS SSL socket communication
[ https://issues.apache.org/jira/browse/MESOS-3153?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15058570#comment-15058570 ] Jojy Varghese commented on MESOS-3153: -- [~kaysoky][~jvanremoortere] Is this ticket still valid? > Add tests for HTTPS SSL socket communication > > > Key: MESOS-3153 > URL: https://issues.apache.org/jira/browse/MESOS-3153 > Project: Mesos > Issue Type: Bug >Reporter: Jojy Varghese >Assignee: Jojy Varghese >Priority: Minor > Labels: mesosphere > > Unit tests are lacking for the following cases: > 1. HTTPS Post with "None" payload. > 2. Verification of HTTPS payload on the SSL socket(maybe decode to a Request > object) > 3. http -> ssl socket > 4. https -> raw socket. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (MESOS-4156) Speedup FetcherCacheTest.* and FetcherCacheHttpTest.*
Alexander Rukletsov created MESOS-4156:
--
Summary: Speedup 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
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] [Created] (MESOS-4177) Create a user doc for Executor HTTP API
Anand Mazumdar created MESOS-4177: - Summary: Create a user doc for Executor HTTP API Key: MESOS-4177 URL: https://issues.apache.org/jira/browse/MESOS-4177 Project: Mesos Issue Type: Bug Reporter: Anand Mazumdar Assignee: Anand Mazumdar We need a user doc similar to the corresponding one for the Scheduler HTTP API. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (MESOS-4175) ContentType/SchedulerTest.Decline is slow
Alexander Rukletsov created MESOS-4175:
--
Summary: ContentType/SchedulerTest.Decline is slow
Key: MESOS-4175
URL: https://issues.apache.org/jira/browse/MESOS-4175
Project: Mesos
Issue Type: Improvement
Components: technical debt, test
Reporter: Alexander Rukletsov
Priority: Minor
The {{ContentType/SchedulerTest.Decline}} test takes more than {{1s}} to finish
on my Mac OS 10.10.4:
{code}
ContentType/SchedulerTest.Decline/0 (1022 ms)
{code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (MESOS-4169) MasterMaintenanceTest.InverseOffers is slow
[
https://issues.apache.org/jira/browse/MESOS-4169?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Alexander Rukletsov updated MESOS-4169:
---
Labels: mesosphere newbie++ tech-debt (was: mesosphere tech-debt)
> MasterMaintenanceTest.InverseOffers is slow
> ---
>
> Key: MESOS-4169
> URL: https://issues.apache.org/jira/browse/MESOS-4169
> Project: Mesos
> Issue Type: Improvement
> Components: technical debt, test
>Reporter: Alexander Rukletsov
>Priority: Minor
> Labels: mesosphere, newbie++, tech-debt
>
> The {{MasterMaintenanceTest.InverseOffers}} test takes more than {{2s}} to
> finish on my Mac OS 10.10.4:
> {code}
> MasterMaintenanceTest.InverseOffers (2027 ms)
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (MESOS-4173) HealthCheckTest.CheckCommandTimeout is slow
[
https://issues.apache.org/jira/browse/MESOS-4173?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15058475#comment-15058475
]
Alexander Rukletsov commented on MESOS-4173:
Great! [~tnachen], could you please link the ticket in the review?
> HealthCheckTest.CheckCommandTimeout is slow
> ---
>
> Key: MESOS-4173
> URL: https://issues.apache.org/jira/browse/MESOS-4173
> Project: Mesos
> Issue Type: Improvement
> Components: technical debt, test
>Reporter: Alexander Rukletsov
>Priority: Minor
> Labels: mesosphere, newbie++, tech-debt
>
> The {{HealthCheckTest.CheckCommandTimeout}} test takes more than {{15s}}! to
> finish on my Mac OS 10.10.4:
> {code}
> HealthCheckTest.CheckCommandTimeout (15483 ms)
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (MESOS-2465) Add links to libprocess readme
[ https://issues.apache.org/jira/browse/MESOS-2465?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15058605#comment-15058605 ] Neil Conway commented on MESOS-2465: I'm fine closing this. I think it is phrased a little wrong: we definitely need to improve the libprocess docs, but just adding links is not necessarily the right way to do that. > Add links to libprocess readme > -- > > Key: MESOS-2465 > URL: https://issues.apache.org/jira/browse/MESOS-2465 > Project: Mesos > Issue Type: Documentation > Components: libprocess >Reporter: Aidan Hobson Sayers >Assignee: Jojy Varghese >Priority: Minor > > There's not much documentation on libprocess at the moment. > It'd be good if a link to > https://www.dropbox.com/s/50buds6t0vizr4w/libprocess.pdf (link found > [here|http://mail-archives.apache.org/mod_mbox/mesos-dev/201307.mbox/%3CCAPXBsRD2e4XxR9cHm3thendDWEijFW7wEx1Z+XEu+oQEmC=9...@mail.gmail.com%3E]) > could be added to the readme as a start. > I also found this [mailing list > post|http://mail-archives.apache.org/mod_mbox/mesos-dev/201404.mbox/%3CCAFeOQnVn=2uGMbq5vTQ-Q0e=Bz=u0Bo49p2=gsk1wsxtuuw...@mail.gmail.com%3E] > very helpful, so maybe it could be added as well? -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (MESOS-3836) `--executor-environment-variables` may not apply to docker containers
[
https://issues.apache.org/jira/browse/MESOS-3836?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15058581#comment-15058581
]
Jojy Varghese commented on MESOS-3836:
--
~[~jieyu]
Since we are moving in the direction of not sharing env variables between agent
and containerizer, we should pack this ticket also along with the others that
address this issue in a broader perspective.
> `--executor-environment-variables` may not apply to docker containers
> -
>
> Key: MESOS-3836
> URL: https://issues.apache.org/jira/browse/MESOS-3836
> Project: Mesos
> Issue Type: Bug
> Components: containerization, slave
>Affects Versions: 0.25.0
> Environment: Mesos 0.25.0 configured with
> --executor-environment-variables
>Reporter: Cody Maloney
>Assignee: Jojy Varghese
>Priority: Minor
> Labels: mesosphere
>
> In our use case we set {{PATH}} as part of the
> {{\-\-executor_environment_variables}} in order to limit what binaries all
> tasks which are launched via Mesos have readily available to them, making it
> much harder for people launching tasks on mesos to accidentally depend on
> something which isn't part of the "guaranteed" environment / platform.
> Docker containers can be used as executors, and have a fully isolated
> filesystem. For executors which run in docker containers setting {{PATH}} to
> our path on the host filesystem may potentially break the docker container.
> The previous code of only copying across environment variables when
> {{includeOsEnvironment}} is set dealt with this
> (https://github.com/apache/mesos/blob/56510afe149758a69a5a714dfaab16111dd0d9c3/src/slave/containerizer/containerizer.cpp#L267)
> if {{includeOsEnvironment}} is set than we should copy across the current
> {{\-\-executor_environment_variables}}. If it isn't, then
> {{\-\-executor_environment_variables}} shouldn't be used at all.
> Another option which could be useful is to make it so that there are two sets
> of "Executor Environment Variables". One for when {{includeOsEnvironment}} is
> set, and one for when it is not.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (MESOS-4164) MasterTest.RecoverResources is slow
[
https://issues.apache.org/jira/browse/MESOS-4164?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Alexander Rukletsov updated MESOS-4164:
---
Labels: mesosphere newbie++ tech-debt (was: mesosphere tech-debt)
> MasterTest.RecoverResources is slow
> ---
>
> Key: MESOS-4164
> URL: https://issues.apache.org/jira/browse/MESOS-4164
> Project: Mesos
> Issue Type: Improvement
> Components: technical debt, test
>Reporter: Alexander Rukletsov
>Priority: Minor
> Labels: mesosphere, newbie++, tech-debt
>
> The {{MasterTest.RecoverResources}} test takes more than {{1s}} to finish on
> my Mac OS 10.10.4:
> {code}
> MasterTest.RecoverResources (1018 ms)
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (MESOS-2465) Add links to libprocess readme
[ https://issues.apache.org/jira/browse/MESOS-2465?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15058608#comment-15058608 ] Jojy Varghese commented on MESOS-2465: -- Ok will close it and maybe mark it duplicate. > Add links to libprocess readme > -- > > Key: MESOS-2465 > URL: https://issues.apache.org/jira/browse/MESOS-2465 > Project: Mesos > Issue Type: Documentation > Components: libprocess >Reporter: Aidan Hobson Sayers >Assignee: Jojy Varghese >Priority: Minor > > There's not much documentation on libprocess at the moment. > It'd be good if a link to > https://www.dropbox.com/s/50buds6t0vizr4w/libprocess.pdf (link found > [here|http://mail-archives.apache.org/mod_mbox/mesos-dev/201307.mbox/%3CCAPXBsRD2e4XxR9cHm3thendDWEijFW7wEx1Z+XEu+oQEmC=9...@mail.gmail.com%3E]) > could be added to the readme as a start. > I also found this [mailing list > post|http://mail-archives.apache.org/mod_mbox/mesos-dev/201404.mbox/%3CCAFeOQnVn=2uGMbq5vTQ-Q0e=Bz=u0Bo49p2=gsk1wsxtuuw...@mail.gmail.com%3E] > very helpful, so maybe it could be added as well? -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (MESOS-4167) MasterTest.OfferTimeout is slow
Alexander Rukletsov created MESOS-4167:
--
Summary: MasterTest.OfferTimeout is slow
Key: MESOS-4167
URL: https://issues.apache.org/jira/browse/MESOS-4167
Project: Mesos
Issue Type: Improvement
Components: technical debt, test
Reporter: Alexander Rukletsov
Priority: Minor
The {{MasterTest.OfferTimeout}} test takes more than {{1s}} to finish on my Mac
OS 10.10.4:
{code}
MasterTest.OfferTimeout (1053 ms)
{code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Created] (MESOS-4173) HealthCheckTest.CheckCommandTimeout is slow
Alexander Rukletsov created MESOS-4173:
--
Summary: HealthCheckTest.CheckCommandTimeout is slow
Key: MESOS-4173
URL: https://issues.apache.org/jira/browse/MESOS-4173
Project: Mesos
Issue Type: Improvement
Components: technical debt, test
Reporter: Alexander Rukletsov
Priority: Minor
The {HealthCheckTest.CheckCommandTimeout{}} test takes more than {{15s}}! to
finish on my Mac OS 10.10.4:
{code}
HealthCheckTest.CheckCommandTimeout (15483 ms)
{code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (MESOS-4159) Speed up GroupTest.*
[
https://issues.apache.org/jira/browse/MESOS-4159?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Alexander Rukletsov updated MESOS-4159:
---
Labels: mesosphere newbie++ tech-debt (was: mesosphere tech-debt)
> Speed up GroupTest.*
>
>
> Key: MESOS-4159
> URL: https://issues.apache.org/jira/browse/MESOS-4159
> Project: Mesos
> Issue Type: Epic
> Components: technical debt, test
>Reporter: Alexander Rukletsov
>Priority: Minor
> Labels: mesosphere, newbie++, tech-debt
>
> Execution times on Mac OS 10.10.4:
> {code}
> GroupTest.GroupJoinWithDisconnect (3352 ms)
> GroupTest.GroupDataWithDisconnect (3350 ms)
> GroupTest.GroupCancelWithDisconnect (2013 ms)
> GroupTest.GroupPathWithRestrictivePerms (13368 ms)
> GroupTest.RetryableErrors (26720 ms)
> {code}
--
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
]
Alexander Rukletsov updated MESOS-4156:
---
Labels: mesosphere newbie++ tech-debt (was: mesosphere tech-debt)
> 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
>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-4170) OversubscriptionTest.UpdateAllocatorOnSchedulerFailover is slow
[
https://issues.apache.org/jira/browse/MESOS-4170?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Alexander Rukletsov updated MESOS-4170:
---
Labels: mesosphere newbie++ tech-debt (was: mesosphere tech-debt)
> OversubscriptionTest.UpdateAllocatorOnSchedulerFailover is slow
> ---
>
> Key: MESOS-4170
> URL: https://issues.apache.org/jira/browse/MESOS-4170
> Project: Mesos
> Issue Type: Improvement
> Components: technical debt, test
>Reporter: Alexander Rukletsov
>Priority: Minor
> Labels: mesosphere, newbie++, tech-debt
>
> The {{OversubscriptionTest.UpdateAllocatorOnSchedulerFailover}} test takes
> more than {{1s}} to finish on my Mac OS 10.10.4:
> {code}
> OversubscriptionTest.UpdateAllocatorOnSchedulerFailover (1018 ms)
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (MESOS-1563) Failed to configure on FreeBSD
[ https://issues.apache.org/jira/browse/MESOS-1563?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15058485#comment-15058485 ] David Forsythe commented on MESOS-1563: --- [MESOS-4176|https://issues.apache.org/jira/browse/MESOS-4176] > Failed to configure on FreeBSD > -- > > Key: MESOS-1563 > URL: https://issues.apache.org/jira/browse/MESOS-1563 > Project: Mesos > Issue Type: Bug >Affects Versions: 0.19.0 > Environment: FreeBSD-10/stable >Reporter: Dmitry Sivachenko >Assignee: David Forsythe > > When trying to configure mesos on FreeBSD, I get the following error: > configure: Setting up build environment for x86_64 freebsd10.0 > configure: error: "Mesos is currently unsupported on your platform." > Why? Is there anything really Linux-specific inside? It's written in Java > after all. > And MacOS is supported, but it is rather close to FreeBSD. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (MESOS-4165) MasterTest.MasterInfoOnReElection is slow
[
https://issues.apache.org/jira/browse/MESOS-4165?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Alexander Rukletsov updated MESOS-4165:
---
Labels: mesosphere newbie++ tech-debt (was: mesosphere tech-debt)
> MasterTest.MasterInfoOnReElection is slow
> -
>
> Key: MESOS-4165
> URL: https://issues.apache.org/jira/browse/MESOS-4165
> Project: Mesos
> Issue Type: Improvement
> Components: technical debt, test
>Reporter: Alexander Rukletsov
>Priority: Minor
> Labels: mesosphere, newbie++, tech-debt
>
> The {{MasterTest.MasterInfoOnReElection}} test takes more than {{1s}} to
> finish on my Mac OS 10.10.4:
> {code}
> MasterTest.MasterInfoOnReElection (1024 ms)
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (MESOS-3951) Make HDFS tool wrappers asynchronous.
[ https://issues.apache.org/jira/browse/MESOS-3951?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jie Yu updated MESOS-3951: -- Fix Version/s: 0.27.0 > Make HDFS tool wrappers asynchronous. > - > > Key: MESOS-3951 > URL: https://issues.apache.org/jira/browse/MESOS-3951 > Project: Mesos > Issue Type: Task >Reporter: Jie Yu >Assignee: Jie Yu > Labels: mesosphere, twitter > Fix For: 0.27.0 > > > The existing HDFS tool wrappers (src/hdfs/hdfs.hpp) are synchronous. They use > os::shell to shell out the 'hadoop' commands. This makes it very hard to be > reused at other locations in the code base. > The URI fetcher HDFS plugin will try to re-use the existing HDFS tool > wrappers. In order to do that, we need to make it asynchronous first. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (MESOS-4161) SlaveTest.CommandExecutorWithOverride is slow
[
https://issues.apache.org/jira/browse/MESOS-4161?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Alexander Rukletsov updated MESOS-4161:
---
Description:
The {{SlaveTest.CommandExecutorWithOverride}} test takes around {{1.3s}} to
finish on my Mac OS 10.10.4:
{code}
SlaveTest.CommandExecutorWithOverride (1311 ms)
{code}
was:
The {{SlaveTest.CommandExecutorWithOverride}} test takes around {{1.3s}} on my
Mac OS 10.10.4 to finish:
{code}
SlaveTest.CommandExecutorWithOverride (1311 ms)
{code}
> SlaveTest.CommandExecutorWithOverride is slow
> -
>
> Key: MESOS-4161
> URL: https://issues.apache.org/jira/browse/MESOS-4161
> Project: Mesos
> Issue Type: Improvement
> Components: technical debt, test
>Reporter: Alexander Rukletsov
>Priority: Minor
> Labels: mesosphere, tech-debt
>
> The {{SlaveTest.CommandExecutorWithOverride}} test takes around {{1.3s}} to
> finish on my Mac OS 10.10.4:
> {code}
> SlaveTest.CommandExecutorWithOverride (1311 ms)
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Created] (MESOS-4169) MasterMaintenanceTest.InverseOffers is slow
Alexander Rukletsov created MESOS-4169:
--
Summary: MasterMaintenanceTest.InverseOffers is slow
Key: MESOS-4169
URL: https://issues.apache.org/jira/browse/MESOS-4169
Project: Mesos
Issue Type: Improvement
Components: technical debt, test
Reporter: Alexander Rukletsov
Priority: Minor
The {{MasterMaintenanceTest.InverseOffers}} test takes more than {{2s}} to
finish on my Mac OS 10.10.4:
{code}
MasterMaintenanceTest.InverseOffers (2027 ms)
{code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (MESOS-4178) Add persistent volume support to the Authorizer
[
https://issues.apache.org/jira/browse/MESOS-4178?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Greg Mann updated MESOS-4178:
-
Description:
This ticket is the first in a series that adds authorization support for
persistent volume creation and destruction.
Persistent volumes should be authorized with the {{principal}} of the reserving
entity (framework or master). The idea is to introduce {{Create}} and
{{Destroy}} into the ACL.
{code}
message Create {
// Subjects.
required Entity principals = 1;
// Objects? Perhaps the kind of volume? allowed permissions?
}
message Destroy {
// Subjects.
required Entity principals = 1;
// Objects.
required Entity creator_principals = 2;
}
{code}
ACLs for volume creation and destruction must be added to {{authorizer.proto}},
and the appropriate function overloads must be added to the Authorizer.
was:
This ticket is the first in a series that adds authorization support for
persistent volume creation and destruction.
ACLs for volume creation and destruction must be added to {{authorizer.proto}},
and the appropriate function overloads must be added to the Authorizer.
> Add persistent volume support to the Authorizer
> ---
>
> Key: MESOS-4178
> URL: https://issues.apache.org/jira/browse/MESOS-4178
> Project: Mesos
> Issue Type: Bug
>Reporter: Greg Mann
>Assignee: Greg Mann
> Labels: mesosphere, persistent-volumes
>
> This ticket is the first in a series that adds authorization support for
> persistent volume creation and destruction.
> Persistent volumes should be authorized with the {{principal}} of the
> reserving entity (framework or master). The idea is to introduce {{Create}}
> and {{Destroy}} into the ACL.
> {code}
> message Create {
> // Subjects.
> required Entity principals = 1;
> // Objects? Perhaps the kind of volume? allowed permissions?
> }
> message Destroy {
> // Subjects.
> required Entity principals = 1;
> // Objects.
> required Entity creator_principals = 2;
> }
> {code}
> ACLs for volume creation and destruction must be added to
> {{authorizer.proto}}, and the appropriate function overloads must be added to
> the Authorizer.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Created] (MESOS-4179) Extend `Master` to authorize persistent volumes
Greg Mann created MESOS-4179:
Summary: Extend `Master` to authorize persistent volumes
Key: MESOS-4179
URL: https://issues.apache.org/jira/browse/MESOS-4179
Project: Mesos
Issue Type: Bug
Reporter: Greg Mann
Assignee: Greg Mann
This ticket is the second in a series that adds authorization support for
persistent volumes.
Methods {{Master::authorizeCreateVolume()}} and
{{Master::authorizeDestroyVolume}} must be added to allow the Master to
authorize these operations.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (MESOS-3903) Add authorization for '/create-volume' and '/destroy-volume' HTTP endpoints
[
https://issues.apache.org/jira/browse/MESOS-3903?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Greg Mann updated MESOS-3903:
-
Description:
This is the fourth in a series of tickets that adds authorization support for
persistent volumes.
We need to add ACL authorization for the '/create-volume' and '/destroy-volume'
HTTP endpoints. In other complementary work, authorization for frameworks
performing {{CREATE}} and {{DESTROY}} operations is being added by MESOS-3065.
This will consist of adding authorization calls into the HTTP endpoint code in
{{src/master/http.cpp}}, as well as tests for both failed & successful calls to
'/create-volume' and '/destroy-volume' with authorization. We also must ensure
that the {{principal}} field of {{Resource.DiskInfo.Persistence}} is being
populated correctly.
was:
We need to add ACL authorization for the '/create-volume' and '/destroy-volume'
HTTP endpoints. In other complementary work, authorization for frameworks
performing {{CREATE}} and {{DESTROY}} operations is being added by MESOS-3065.
This will consist of adding authorization calls into the HTTP endpoint code in
{{src/master/http.cpp}}, as well as tests for both failed & successful calls to
'/create-volume' and '/destroy-volume' with authorization. We also must ensure
that the {{principal}} field of {{Resource.DiskInfo.Persistence}} is being
populated correctly.
> Add authorization for '/create-volume' and '/destroy-volume' HTTP endpoints
> ---
>
> Key: MESOS-3903
> URL: https://issues.apache.org/jira/browse/MESOS-3903
> Project: Mesos
> Issue Type: Improvement
>Reporter: Greg Mann
>Assignee: Greg Mann
> Labels: mesosphere, persistent-volumes
>
> This is the fourth in a series of tickets that adds authorization support for
> persistent volumes.
> We need to add ACL authorization for the '/create-volume' and
> '/destroy-volume' HTTP endpoints. In other complementary work, authorization
> for frameworks performing {{CREATE}} and {{DESTROY}} operations is being
> added by MESOS-3065.
> This will consist of adding authorization calls into the HTTP endpoint code
> in {{src/master/http.cpp}}, as well as tests for both failed & successful
> calls to '/create-volume' and '/destroy-volume' with authorization. We also
> must ensure that the {{principal}} field of {{Resource.DiskInfo.Persistence}}
> is being populated correctly.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (MESOS-3065) Add framework authorization for persistent volume
[ https://issues.apache.org/jira/browse/MESOS-3065?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15058838#comment-15058838 ] Greg Mann commented on MESOS-3065: -- This ticket has been split into pieces to help us complete some of this work on a short timescale. The review requests which are now applicable to this particular ticket are: https://reviews.apache.org/r/40255/ https://reviews.apache.org/r/40256/ https://reviews.apache.org/r/40271/ > Add framework authorization for persistent volume > - > > Key: MESOS-3065 > URL: https://issues.apache.org/jira/browse/MESOS-3065 > Project: Mesos > Issue Type: Task >Reporter: Michael Park >Assignee: Greg Mann > Labels: mesosphere, persistent-volumes > > This is the third in a series of tickets that adds authorization support to > persistent volumes. > When a framework creates a persistent volume, "create" ACLs are checked to > see if the framework (FrameworkInfo.principal) or the operator > (Credential.user) is authorized to create persistent volumes. If not > authorized, the create operation is rejected. > When a framework destroys a persistent volume, "destroy" ACLs are checked to > see if the framework (FrameworkInfo.principal) or the operator > (Credential.user) is authorized to destroy the persistent volume created by a > framework or operator (Resource.DiskInfo.principal). If not authorized, the > destroy operation is rejected. > A separate ticket will use the structures created here to enable > authorization of the "/create" and "/destroy" HTTP endpoints: > https://issues.apache.org/jira/browse/MESOS-3903 -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (MESOS-4180) Add flags to post_reviews.py to update summary and description.
[ https://issues.apache.org/jira/browse/MESOS-4180?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15058935#comment-15058935 ] Kevin Klues commented on MESOS-4180: https://reviews.apache.org/r/41411/ > Add flags to post_reviews.py to update summary and description. > --- > > Key: MESOS-4180 > URL: https://issues.apache.org/jira/browse/MESOS-4180 > Project: Mesos > Issue Type: Improvement > Components: general >Reporter: Kevin Klues >Assignee: Kevin Klues >Priority: Minor > Labels: reviewboard > > If you amend a commit message and post it to reviewboard via the > support/post_reviews.py script, then the summary / description on reviewboard > does not get updated between subsequent revisions. The only way to update > these is to modify them directly on the webpage. However, with some simple > flags to the 'rbt' command we can force the review's summary / description to > be updated to the text in the commit message. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (MESOS-4180) Add flags to post_reviews.py to update summary and description.
[ https://issues.apache.org/jira/browse/MESOS-4180?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kevin Klues updated MESOS-4180: --- Description: If you amend a commit message and post it to reviewboard via the support/post_reviews.py script, then the summary / description on reviewboard does not get updated between subsequent revisions. The only way to update these is to modify them directly on the webpage. However, with a simple directive in the .reviewboardrc file we can force the review's summary / description to be updated to the text in the commit message. (was: If you amend a commit message and post it to reviewboard via the support/post_reviews.py script, then the summary / description on reviewboard does not get updated between subsequent revisions. The only way to update these is to modify them directly on the webpage. However, with some simple flags to the 'rbt' command we can force the review's summary / description to be updated to the text in the commit message. ) > Add flags to post_reviews.py to update summary and description. > --- > > Key: MESOS-4180 > URL: https://issues.apache.org/jira/browse/MESOS-4180 > Project: Mesos > Issue Type: Improvement > Components: general >Reporter: Kevin Klues >Assignee: Kevin Klues >Priority: Minor > Labels: reviewboard > > If you amend a commit message and post it to reviewboard via the > support/post_reviews.py script, then the summary / description on reviewboard > does not get updated between subsequent revisions. The only way to update > these is to modify them directly on the webpage. However, with a simple > directive in the .reviewboardrc file we can force the review's summary / > description to be updated to the text in the commit message. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (MESOS-4178) Add persistent volume support to the Authorizer
[
https://issues.apache.org/jira/browse/MESOS-4178?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15058830#comment-15058830
]
Greg Mann commented on MESOS-4178:
--
Reviews here:
https://reviews.apache.org/r/40167/
https://reviews.apache.org/r/40168/
> Add persistent volume support to the Authorizer
> ---
>
> Key: MESOS-4178
> URL: https://issues.apache.org/jira/browse/MESOS-4178
> Project: Mesos
> Issue Type: Bug
>Reporter: Greg Mann
>Assignee: Greg Mann
> Labels: mesosphere, persistent-volumes
>
> This ticket is the first in a series that adds authorization support for
> persistent volume creation and destruction.
> Persistent volumes should be authorized with the {{principal}} of the
> reserving entity (framework or master). The idea is to introduce {{Create}}
> and {{Destroy}} into the ACL.
> {code}
> message Create {
> // Subjects.
> required Entity principals = 1;
> // Objects? Perhaps the kind of volume? allowed permissions?
> }
> message Destroy {
> // Subjects.
> required Entity principals = 1;
> // Objects.
> required Entity creator_principals = 2;
> }
> {code}
> ACLs for volume creation and destruction must be added to
> {{authorizer.proto}}, and the appropriate function overloads must be added to
> the Authorizer.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (MESOS-4180) Add flags to post_reviews.py to update summary and description.
[ https://issues.apache.org/jira/browse/MESOS-4180?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kevin Klues updated MESOS-4180: --- Summary: Add flags to post_reviews.py to update summary and description. (was: Added flags to post_reviews.py to update summary and description.) > Add flags to post_reviews.py to update summary and description. > --- > > Key: MESOS-4180 > URL: https://issues.apache.org/jira/browse/MESOS-4180 > Project: Mesos > Issue Type: Improvement > Components: general >Reporter: Kevin Klues >Assignee: Kevin Klues >Priority: Minor > Labels: reviewboard > > If you amend a commit message and post it to reviewboard via the > support/post_reviews.py script, then the summary / description on reviewboard > does not get updated between subsequent revisions. The only way to update > these is to modify them directly on the webpage. However, with some simple > flags to the 'rbt' command we can force the review's summary / description to > be updated to the text in the commit message. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (MESOS-4180) Added flags to post_reviews.py to update summary and description.
Kevin Klues created MESOS-4180: -- Summary: Added flags to post_reviews.py to update summary and description. Key: MESOS-4180 URL: https://issues.apache.org/jira/browse/MESOS-4180 Project: Mesos Issue Type: Improvement Components: general Reporter: Kevin Klues Assignee: Kevin Klues Priority: Minor If you amend a commit message and post it to reviewboard via the support/post_reviews.py script, then the summary / description on reviewboard does not get updated between subsequent revisions. The only way to update these is to modify them directly on the webpage. However, with some simple flags to the 'rbt' command we can force the review's summary / description to be updated to the text in the commit message. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (MESOS-3065) Add framework authorization for persistent volume
[
https://issues.apache.org/jira/browse/MESOS-3065?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Greg Mann updated MESOS-3065:
-
Description:
This is the third in a series of tickets that adds authorization support to
persistent volumes.
When a framework creates a persistent volume, "create" ACLs are checked to see
if the framework (FrameworkInfo.principal) or the operator (Credential.user) is
authorized to create persistent volumes. If not authorized, the create
operation is rejected.
When a framework destroys a persistent volume, "destroy" ACLs are checked to
see if the framework (FrameworkInfo.principal) or the operator
(Credential.user) is authorized to destroy the persistent volume created by a
framework or operator (Resource.DiskInfo.principal). If not authorized, the
destroy operation is rejected.
A separate ticket will use the structures created here to enable authorization
of the "/create" and "/destroy" HTTP endpoints:
https://issues.apache.org/jira/browse/MESOS-3903
was:
Persistent volume should be authorized with the {{principal}} of the reserving
entity (framework or master). The idea is to introduce {{Create}} and
{{Destroy}} into the ACL.
{code}
message Create {
// Subjects.
required Entity principals = 1;
// Objects? Perhaps the kind of volume? allowed permissions?
}
message Destroy {
// Subjects.
required Entity principals = 1;
// Objects.
required Entity creator_principals = 2;
}
{code}
When a framework creates a persistent volume, "create" ACLs are checked to see
if the framework (FrameworkInfo.principal) or the operator (Credential.user) is
authorized to create persistent volumes. If not authorized, the create
operation is rejected.
When a framework destroys a persistent volume, "destroy" ACLs are checked to
see if the framework (FrameworkInfo.principal) or the operator
(Credential.user) is authorized to destroy the persistent volume created by a
framework or operator (Resource.DiskInfo.principal). If not authorized, the
destroy operation is rejected.
A separate ticket will use the structures created here to enable authorization
of the "/create" and "/destroy" HTTP endpoints:
https://issues.apache.org/jira/browse/MESOS-3903
> Add framework authorization for persistent volume
> -
>
> Key: MESOS-3065
> URL: https://issues.apache.org/jira/browse/MESOS-3065
> Project: Mesos
> Issue Type: Task
>Reporter: Michael Park
>Assignee: Greg Mann
> Labels: mesosphere, persistent-volumes
>
> This is the third in a series of tickets that adds authorization support to
> persistent volumes.
> When a framework creates a persistent volume, "create" ACLs are checked to
> see if the framework (FrameworkInfo.principal) or the operator
> (Credential.user) is authorized to create persistent volumes. If not
> authorized, the create operation is rejected.
> When a framework destroys a persistent volume, "destroy" ACLs are checked to
> see if the framework (FrameworkInfo.principal) or the operator
> (Credential.user) is authorized to destroy the persistent volume created by a
> framework or operator (Resource.DiskInfo.principal). If not authorized, the
> destroy operation is rejected.
> A separate ticket will use the structures created here to enable
> authorization of the "/create" and "/destroy" HTTP endpoints:
> https://issues.apache.org/jira/browse/MESOS-3903
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (MESOS-4179) Extend `Master` to authorize persistent volumes
[
https://issues.apache.org/jira/browse/MESOS-4179?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15058826#comment-15058826
]
Greg Mann commented on MESOS-4179:
--
Review here: https://reviews.apache.org/r/40169/
> Extend `Master` to authorize persistent volumes
> ---
>
> Key: MESOS-4179
> URL: https://issues.apache.org/jira/browse/MESOS-4179
> Project: Mesos
> Issue Type: Bug
>Reporter: Greg Mann
>Assignee: Greg Mann
> Labels: persistent-volumes
>
> This ticket is the second in a series that adds authorization support for
> persistent volumes.
> Methods {{Master::authorizeCreateVolume()}} and
> {{Master::authorizeDestroyVolume}} must be added to allow the Master to
> authorize these operations.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (MESOS-4180) Add flags to update summary and description in updated patches for review.
[ https://issues.apache.org/jira/browse/MESOS-4180?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kevin Klues updated MESOS-4180: --- Summary: Add flags to update summary and description in updated patches for review. (was: Add flags to post_reviews.py to update summary and description.) > Add flags to update summary and description in updated patches for review. > -- > > Key: MESOS-4180 > URL: https://issues.apache.org/jira/browse/MESOS-4180 > Project: Mesos > Issue Type: Improvement > Components: general >Reporter: Kevin Klues >Assignee: Kevin Klues >Priority: Minor > Labels: reviewboard > > If you amend a commit message and post it to reviewboard via the > support/post_reviews.py script, then the summary / description on reviewboard > does not get updated between subsequent revisions. The only way to update > these is to modify them directly on the webpage. However, with a simple > directive in the .reviewboardrc file we can force the review's summary / > description to be updated to the text in the commit message. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (MESOS-4181) Don't log port ranges
Cody Maloney created MESOS-4181:
---
Summary: Don't log port ranges
Key: MESOS-4181
URL: https://issues.apache.org/jira/browse/MESOS-4181
Project: Mesos
Issue Type: Bug
Components: master
Affects Versions: 0.25.0
Reporter: Cody Maloney
Transforming from mesos' internal port range representation -> text is
non-linear in the number of bytest output. We end up with a massive amount of
log data like the following:
{noformat}
Dec 15 23:54:08 ip-10-0-7-60.us-west-2.compute.internal mesos-master[15919]:
I1215 23:51:58.891165 15925 hierarchical.hpp:1103] Recovered cpus(*):1e-05;
mem(*):10; ports(*):[5565-5565] (total: ports(*):[1025-2180, 2182-3887,
3889-5049, 5052-8079, 8082-8180, 8182-32000]; cpus(*):4; mem(*):14019;
disk(*):32541, allocated: cpus(*):0.01815; ports(*):[1050-1050, 1092-1092,
1094-1094, 1129-1129, 1132-1132, 1140-1140, 1177-1178, 1180-1180, 1192-1192,
1205-1205, 1221-1221, 1308-1308, 1311-1311, 1323-1323, 1326-1326, 1335-1335,
1365-1365, 1404-1404, 1412-1412, 1436-1436, 1455-1455, 1459-1459, 1472-1472,
1477-1477, 1482-1482, 1491-1491, 1510-1510, 1551-1551, 1553-1553, 1559-1559,
1573-1573, 1590-1590, 1592-1592, 1619-1619, 1635-1636, 1678-1678, 1738-1738,
1742-1742, 1752-1752, 1770-1770, 1780-1782, 1790-1790, 1792-1792, 1799-1799,
1804-1804, 1844-1844, 1852-1852, 1867-1867, 1899-1899, 1936-1936, 1945-1945,
1954-1954, 2046-2046, 2055-2055, 2063-2063, 2070-2070, 2089-2089, 2104-2104,
2117-2117, 2132-2132, 2173-2173, 2178-2178, 2188-2188, 2200-2200, 2218-2218,
2223-2223, 2244-2244, 2248-2248, 2250-2250, 2270-2270, 2286-2286, 2302-2302,
2332-2332, 2377-2377, 2397-2397, 2423-2423, 2435-2435, 2442-2442, 2448-2448,
2477-2477, 2482-2482, 2522-2522, 2586-2586, 2594-2594, 2600-2600, 2602-2602,
2643-2643, 2648-2648, 2659-2659, 2691-2691, 2716-2716, 2739-2739, 2794-2794,
2802-2802, 2823-2823, 2831-2831, 2840-2840, 2848-2848, 2876-2876, 2894-2895,
2900-2900, 2904-2904, 2912-2912, 2983-2983, 2991-2991, 2999-2999, 3011-3011,
3025-3025, 3036-3036, 3041-3041, 3051-3051, 3074-3074, 3097-3097, 3107-3107,
3121-3121, 3171-3171, 3176-3176, 3195-3195, 3197-3197, 3210-3210, 3221-3221,
3234-3234, 3245-3245, 3250-3251, 3255-3255, 3270-3270, 3293-3293, 3298-3298,
3312-3312, 3318-3318, 3325-3325, 3368-3368, 3379-3379, 3391-3391, 3412-3412,
3414-3414, 3420-3420, 3492-3492, 3501-3501, 3538-3538, 3579-3579, 3631-3631,
3680-3680, 3684-3684, 3695-3695, 3699-3699, 3738-3738, 3758-3758, 3793-3793,
3808-3808, 3817-3817, 3854-3854, 3856-3856, 3900-3900, 3906-3906, 3909-3909,
3912-3912, 3946-3946, 3956-3956, 3959-3959, 3963-3963, 3974-
Dec 15 23:54:09 ip-10-0-7-60.us-west-2.compute.internal mesos-master[15919]:
3974, 3981-3981, 3985-3985, 4134-4134, 4178-4178, 4206-4206, 4223-4223,
4239-4239, 4245-4245, 4251-4251, 4262-4263, 4271-4271, 4308-4308, 4323-4323,
4329-4329, 4368-4368, 4385-4385, 4404-4404, 4419-4419, 4430-4430, 4448-4448,
4464-4464, 4481-4481, 4494-4494, 4499-4499, 4510-4510, 4534-4534, 4543-4543,
4555-4555, 4561-4562, 4577-4577, 4601-4601, 4675-4675, 4722-4722, 4739-4739,
4748-4748, 4752-4752, 4764-4764, 4771-4771, 4787-4787, 4827-4827, 4830-4830,
4837-4837, 4848-4848, 4853-4853, 4879-4879, 4883-4883, 4897-4897, 4902-4902,
4911-4911, 4940-4940, 4946-4946, 4957-4957, 4994-4994, 4996-4996, 5008-5008,
5019-5019, 5043-5043, 5059-5059, 5109-5109, 5134-5135, 5157-5157, 5172-5172,
5192-5192, 5211-5211, 5215-5215, 5234-5234, 5237-5237, 5246-5246, 5255-5255,
5268-5268, 5311-5311, 5314-5314, 5316-5316, 5348-5348, 5391-5391, 5407-5407,
5433-5433, 5446-5447, 5454-5454, 5456-5456, 5482-5482, 5514-5515, 5517-5517,
5525-5525, 5542-5542, 5554-5554, 5581-5581, 5624-5624, 5647-5647, 5695-5695,
5700-5700, 5703-5703, 5743-5743, 5747-5747, 5793-5793, 5850-5850, 5856-5856,
5858-5858, 5899-5899, 5901-5901, 5940-5940, 5958-5958, 5962-5962, 5974-5974,
5995-5995, 6000-6001, 6037-6037, 6053-6053, 6066-6066, 6078-6078, 6129-6129,
6139-6139, 6160-6160, 6174-6174, 6193-6193, 6234-6234, 6263-6263, 6276-6276,
6287-6287, 6292-6292, 6294-6294, 6296-6296, 6306-6307, 6333-6333, 6343-6343,
6349-6349, 6377-6377, 6418-6418, 6454-6454, 6484-6484, 6496-6496, 6504-6504,
6518-6518, 6589-6589, 6592-6592, 6606-6606, 6640-6640, 6713-6713, 6717-6717,
6738-6738, 6757-6757, 6765-6765, 6778-6778, 6792-6792, 6798-6798, 6811-6811,
6815-6815, 6828-6828, 6838-6839, 6856-6856, 6868-6868, 6877-6877, 6892-6892,
6903-6903, 6908-6908, 6943-6943, 6973-6973, 6977-6977, 7003-7003, 7019-7019,
7021-7021, 7031-7031, 7034-7034, 7038-7038, 7052-7052, 7060-7060, 7097-7097,
7124-7124, 7151-7152, 7169-7169, 7171-7171, 7200-7200, 7204-7204, 7246-7246,
7250-7250, 7292-7292, 7326-7326, 7347-7347, 7363-7363, 7369-7369, 7401-7401,
7407-7407, 7421-7421, 7436-7436, 7447-7447, 7458-74
Dec 15 23:54:09 ip-10-0-7-60.us-west-2.compute.internal mesos-master[15919]:
58, 7475-7475, 7477-7477, 7502-7502, 7531-7531,
[jira] [Commented] (MESOS-3909) isolator module headers depend on picojson headers
[
https://issues.apache.org/jira/browse/MESOS-3909?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15059164#comment-15059164
]
James Peach commented on MESOS-3909:
https://reviews.apache.org/r/41424/
https://reviews.apache.org/r/41425/
[~benjaminhindman], [~nnielsen] are you able to help shepherd this?
> isolator module headers depend on picojson headers
> --
>
> Key: MESOS-3909
> URL: https://issues.apache.org/jira/browse/MESOS-3909
> Project: Mesos
> Issue Type: Bug
> Components: c++ api, modules
>Reporter: James Peach
>Assignee: James Peach
>
> When trying to build an isolator module, stout headers end up depending on
> {{picojson.hpp}} which is not installed.
> {code}
> In file included from /opt/mesos/include/mesos/module/isolator.hpp:25:
> In file included from /opt/mesos/include/mesos/slave/isolator.hpp:30:
> In file included from /opt/mesos/include/process/dispatch.hpp:22:
> In file included from /opt/mesos/include/process/process.hpp:26:
> In file included from /opt/mesos/include/process/event.hpp:21:
> In file included from /opt/mesos/include/process/http.hpp:39:
> /opt/mesos/include/stout/json.hpp:23:10: fatal error: 'picojson.h' file not
> found
> #include
> ^
> 8 warnings and 1 error generated.
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Assigned] (MESOS-4161) SlaveTest.CommandExecutorWithOverride is slow
[
https://issues.apache.org/jira/browse/MESOS-4161?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jian Qiu reassigned MESOS-4161:
---
Assignee: Jian Qiu
> SlaveTest.CommandExecutorWithOverride is slow
> -
>
> Key: MESOS-4161
> URL: https://issues.apache.org/jira/browse/MESOS-4161
> Project: Mesos
> Issue Type: Improvement
> Components: technical debt, test
>Reporter: Alexander Rukletsov
>Assignee: Jian Qiu
>Priority: Minor
> Labels: mesosphere, newbie++, tech-debt
>
> The {{SlaveTest.CommandExecutorWithOverride}} test takes around {{1.3s}} to
> finish on my Mac OS 10.10.4:
> {code}
> SlaveTest.CommandExecutorWithOverride (1311 ms)
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Created] (MESOS-4178) Add persistent volume support to the Authorizer
Greg Mann created MESOS-4178:
Summary: Add persistent volume support to the Authorizer
Key: MESOS-4178
URL: https://issues.apache.org/jira/browse/MESOS-4178
Project: Mesos
Issue Type: Bug
Reporter: Greg Mann
Assignee: Greg Mann
This ticket is the first in a series that adds authorization support for
persistent volume creation and destruction.
ACLs for volume creation and destruction must be added to {{authorizer.proto}},
and the appropriate function overloads must be added to the Authorizer.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (MESOS-3892) Add a helper function to the Agent to retrieve the list of executors that are using optimistically offered, revocable resources.
[
https://issues.apache.org/jira/browse/MESOS-3892?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15059415#comment-15059415
]
Klaus Ma commented on MESOS-3892:
-
RR: https://reviews.apache.org/r/41345/
> Add a helper function to the Agent to retrieve the list of executors that are
> using optimistically offered, revocable resources.
>
>
> Key: MESOS-3892
> URL: https://issues.apache.org/jira/browse/MESOS-3892
> Project: Mesos
> Issue Type: Bug
>Reporter: Artem Harutyunyan
>Assignee: Klaus Ma
> Labels: mesosphere
>
> {noformat}
> class Slave {
> ...
> // How the master currently keeps track of executors.
> hashmap> executors;
> ...
> // Returns the list of executors that are using optimistically-
> // offered, revocable resources.
> list getEvictableExecutors() { ... }
> ...
> }
> {noformat}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (MESOS-3892) Add a helper function to the Agent to retrieve the list of executors that are using optimistically offered, revocable resources.
[
https://issues.apache.org/jira/browse/MESOS-3892?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Klaus Ma updated MESOS-3892:
Description:
In the agent, add a helper function to get the list of the exeuctor using
ALLOCATION_SLACK.
It's short term solution which is different the design document, because master
did not have executor for command line executor. Send evicatble executors from
master to slave will addess in post-MVP after MESOS-1718.
{noformat}
class Slave {
...
// If the executor used revocable resources, add it into `evictableExecutors`
// list.
void addEvictableExecutor(Executor* executor);
// If the executor used revocable resources, remove it from
// `evictableExecutors` list.
void removeEvictableExecutor(Executor* executor);
// Get evictable executor ID list by `Resource::RevocableInfo::Type`.
std::list getEvictableExecutors(
Resource::RevocableInfo::Type type);
...
// The map of evictable executor list. If there's not enough resources,
// the evictable executor will be terminated by slave to release resources.
hashmap
evictableExecutors;
...
}
{noformat}
was:
{noformat}
class Slave {
...
// How the master currently keeps track of executors.
hashmap> executors;
...
// Returns the list of executors that are using optimistically-
// offered, revocable resources.
list getEvictableExecutors() { ... }
...
}
{noformat}
> Add a helper function to the Agent to retrieve the list of executors that are
> using optimistically offered, revocable resources.
>
>
> Key: MESOS-3892
> URL: https://issues.apache.org/jira/browse/MESOS-3892
> Project: Mesos
> Issue Type: Bug
>Reporter: Artem Harutyunyan
>Assignee: Klaus Ma
> Labels: mesosphere
>
> In the agent, add a helper function to get the list of the exeuctor using
> ALLOCATION_SLACK.
> It's short term solution which is different the design document, because
> master did not have executor for command line executor. Send evicatble
> executors from master to slave will addess in post-MVP after MESOS-1718.
> {noformat}
> class Slave {
> ...
> // If the executor used revocable resources, add it into
> `evictableExecutors`
> // list.
> void addEvictableExecutor(Executor* executor);
> // If the executor used revocable resources, remove it from
> // `evictableExecutors` list.
> void removeEvictableExecutor(Executor* executor);
> // Get evictable executor ID list by `Resource::RevocableInfo::Type`.
> std::list getEvictableExecutors(
> Resource::RevocableInfo::Type type);
> ...
> // The map of evictable executor list. If there's not enough resources,
> // the evictable executor will be terminated by slave to release resources.
> hashmap
> evictableExecutors;
> ...
> }
> {noformat}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Issue Comment Deleted] (MESOS-2857) FetcherCacheTest.LocalCachedExtract is flaky.
[
https://issues.apache.org/jira/browse/MESOS-2857?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Benjamin Bannier updated MESOS-2857:
Comment: was deleted
(was: Comparing with the original log in this report, this appears to be a
different issue.
>From the log it appears as if everything happened as expected, only that the
>test ran into our default timeout when waiting for a status update; without
>verbose libprocess logs I am tempted to attribute this issue to very high
>system load.)
> FetcherCacheTest.LocalCachedExtract is flaky.
> -
>
> Key: MESOS-2857
> URL: https://issues.apache.org/jira/browse/MESOS-2857
> Project: Mesos
> Issue Type: Bug
> Components: fetcher, test
>Reporter: Benjamin Mahler
>Assignee: Benjamin Bannier
> Labels: flaky-test, mesosphere
>
> From jenkins:
> {noformat}
> [ RUN ] FetcherCacheTest.LocalCachedExtract
> Using temporary directory '/tmp/FetcherCacheTest_LocalCachedExtract_Cwdcdj'
> I0610 20:04:48.591573 24561 leveldb.cpp:176] Opened db in 3.512525ms
> I0610 20:04:48.592456 24561 leveldb.cpp:183] Compacted db in 828630ns
> I0610 20:04:48.592512 24561 leveldb.cpp:198] Created db iterator in 32992ns
> I0610 20:04:48.592531 24561 leveldb.cpp:204] Seeked to beginning of db in
> 8967ns
> I0610 20:04:48.592545 24561 leveldb.cpp:273] Iterated through 0 keys in the
> db in 7762ns
> I0610 20:04:48.592604 24561 replica.cpp:744] Replica recovered with log
> positions 0 -> 0 with 1 holes and 0 unlearned
> I0610 20:04:48.593438 24587 recover.cpp:449] Starting replica recovery
> I0610 20:04:48.593698 24587 recover.cpp:475] Replica is in EMPTY status
> I0610 20:04:48.595641 24580 replica.cpp:641] Replica in EMPTY status received
> a broadcasted recover request
> I0610 20:04:48.596086 24590 recover.cpp:195] Received a recover response from
> a replica in EMPTY status
> I0610 20:04:48.596607 24590 recover.cpp:566] Updating replica status to
> STARTING
> I0610 20:04:48.597507 24590 leveldb.cpp:306] Persisting metadata (8 bytes) to
> leveldb took 717888ns
> I0610 20:04:48.597535 24590 replica.cpp:323] Persisted replica status to
> STARTING
> I0610 20:04:48.597697 24590 recover.cpp:475] Replica is in STARTING status
> I0610 20:04:48.599165 24584 replica.cpp:641] Replica in STARTING status
> received a broadcasted recover request
> I0610 20:04:48.599434 24584 recover.cpp:195] Received a recover response from
> a replica in STARTING status
> I0610 20:04:48.599915 24590 recover.cpp:566] Updating replica status to VOTING
> I0610 20:04:48.600545 24590 leveldb.cpp:306] Persisting metadata (8 bytes) to
> leveldb took 432335ns
> I0610 20:04:48.600574 24590 replica.cpp:323] Persisted replica status to
> VOTING
> I0610 20:04:48.600659 24590 recover.cpp:580] Successfully joined the Paxos
> group
> I0610 20:04:48.600797 24590 recover.cpp:464] Recover process terminated
> I0610 20:04:48.602905 24594 master.cpp:363] Master
> 20150610-200448-3875541420-32907-24561 (dbade881e927) started on
> 172.17.0.231:32907
> I0610 20:04:48.602957 24594 master.cpp:365] Flags at startup: --acls=""
> --allocation_interval="1secs" --allocator="HierarchicalDRF"
> --authenticate="true" --authenticate_slaves="true" --authenticators="crammd5"
> --credentials="/tmp/FetcherCacheTest_LocalCachedExtract_Cwdcdj/credentials"
> --framework_sorter="drf" --help="false" --initialize_driver_logging="true"
> --log_auto_initialize="true" --logbufsecs="0" --logging_level="INFO"
> --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_reregister_timeout="10mins"
> --user_sorter="drf" --version="false"
> --webui_dir="/mesos/mesos-0.23.0/_inst/share/mesos/webui"
> --work_dir="/tmp/FetcherCacheTest_LocalCachedExtract_Cwdcdj/master"
> --zk_session_timeout="10secs"
> I0610 20:04:48.603374 24594 master.cpp:410] Master only allowing
> authenticated frameworks to register
> I0610 20:04:48.603392 24594 master.cpp:415] Master only allowing
> authenticated slaves to register
> I0610 20:04:48.603404 24594 credentials.hpp:37] Loading credentials for
> authentication from
> '/tmp/FetcherCacheTest_LocalCachedExtract_Cwdcdj/credentials'
> I0610 20:04:48.603751 24594 master.cpp:454] Using default 'crammd5'
> authenticator
> I0610 20:04:48.604928 24594 master.cpp:491] Authorization enabled
> I0610 20:04:48.606034 24593 hierarchical.hpp:309] Initialized hierarchical
> allocator process
> I0610 20:04:48.606106 24593 whitelist_watcher.cpp:79] No whitelist given
> I0610 20:04:48.607430 24594 master.cpp:1476] The newly elected leader is
> master@172.17.0.231:32907 with id 20150610-200448-3875541420-32907-24561
> I0610 20:04:48.607466 24594
[jira] [Updated] (MESOS-4151) GMock warning in SlaveTest.ContainerizerUsageFailure
[
https://issues.apache.org/jira/browse/MESOS-4151?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Till Toenshoff updated MESOS-4151:
--
Shepherd: Till Toenshoff
> GMock warning in SlaveTest.ContainerizerUsageFailure
>
>
> Key: MESOS-4151
> URL: https://issues.apache.org/jira/browse/MESOS-4151
> Project: Mesos
> Issue Type: Bug
>Reporter: Neil Conway
>Assignee: Benjamin Bannier
> Labels: mesosphere, tech-debt
> Attachments: gmock_warning_containerizer.txt
>
>
> {noformat}
> [ RUN ] SlaveTest.ContainerizerUsageFailure
> GMOCK WARNING:
> Uninteresting mock function call - returning directly.
> Function call: shutdown(0x7f920271dfd0)
> Stack trace:
> [ OK ] SlaveTest.ContainerizerUsageFailure (94 ms)
> [--] 1 test from SlaveTest (95 ms total)
> {noformat}
> Occurs deterministically for me on OSX 10.10
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (MESOS-4151) GMock warning in SlaveTest.ContainerizerUsageFailure
[
https://issues.apache.org/jira/browse/MESOS-4151?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Benjamin Bannier updated MESOS-4151:
Sprint: Mesosphere Sprint 24
> GMock warning in SlaveTest.ContainerizerUsageFailure
>
>
> Key: MESOS-4151
> URL: https://issues.apache.org/jira/browse/MESOS-4151
> Project: Mesos
> Issue Type: Bug
>Reporter: Neil Conway
>Assignee: Benjamin Bannier
> Labels: mesosphere, tech-debt
> Attachments: gmock_warning_containerizer.txt
>
>
> {noformat}
> [ RUN ] SlaveTest.ContainerizerUsageFailure
> GMOCK WARNING:
> Uninteresting mock function call - returning directly.
> Function call: shutdown(0x7f920271dfd0)
> Stack trace:
> [ OK ] SlaveTest.ContainerizerUsageFailure (94 ms)
> [--] 1 test from SlaveTest (95 ms total)
> {noformat}
> Occurs deterministically for me on OSX 10.10
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Assigned] (MESOS-4151) GMock warning in SlaveTest.ContainerizerUsageFailure
[
https://issues.apache.org/jira/browse/MESOS-4151?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Benjamin Bannier reassigned MESOS-4151:
---
Assignee: Benjamin Bannier
> GMock warning in SlaveTest.ContainerizerUsageFailure
>
>
> Key: MESOS-4151
> URL: https://issues.apache.org/jira/browse/MESOS-4151
> Project: Mesos
> Issue Type: Bug
>Reporter: Neil Conway
>Assignee: Benjamin Bannier
> Labels: mesosphere, tech-debt
> Attachments: gmock_warning_containerizer.txt
>
>
> {noformat}
> [ RUN ] SlaveTest.ContainerizerUsageFailure
> GMOCK WARNING:
> Uninteresting mock function call - returning directly.
> Function call: shutdown(0x7f920271dfd0)
> Stack trace:
> [ OK ] SlaveTest.ContainerizerUsageFailure (94 ms)
> [--] 1 test from SlaveTest (95 ms total)
> {noformat}
> Occurs deterministically for me on OSX 10.10
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Issue Comment Deleted] (MESOS-2857) FetcherCacheTest.LocalCachedExtract is flaky.
[
https://issues.apache.org/jira/browse/MESOS-2857?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Benjamin Bannier updated MESOS-2857:
Comment: was deleted
(was: Comparing with the original log in this report, this appears to be a
different issue.
>From the log it appears as if everything happened as expected, only that the
>test ran into our default timeout when waiting for a status update; without
>verbose libprocess logs I am tempted to attribute this issue to very high
>system load.)
> FetcherCacheTest.LocalCachedExtract is flaky.
> -
>
> Key: MESOS-2857
> URL: https://issues.apache.org/jira/browse/MESOS-2857
> Project: Mesos
> Issue Type: Bug
> Components: fetcher, test
>Reporter: Benjamin Mahler
>Assignee: Benjamin Bannier
> Labels: flaky-test, mesosphere
>
> From jenkins:
> {noformat}
> [ RUN ] FetcherCacheTest.LocalCachedExtract
> Using temporary directory '/tmp/FetcherCacheTest_LocalCachedExtract_Cwdcdj'
> I0610 20:04:48.591573 24561 leveldb.cpp:176] Opened db in 3.512525ms
> I0610 20:04:48.592456 24561 leveldb.cpp:183] Compacted db in 828630ns
> I0610 20:04:48.592512 24561 leveldb.cpp:198] Created db iterator in 32992ns
> I0610 20:04:48.592531 24561 leveldb.cpp:204] Seeked to beginning of db in
> 8967ns
> I0610 20:04:48.592545 24561 leveldb.cpp:273] Iterated through 0 keys in the
> db in 7762ns
> I0610 20:04:48.592604 24561 replica.cpp:744] Replica recovered with log
> positions 0 -> 0 with 1 holes and 0 unlearned
> I0610 20:04:48.593438 24587 recover.cpp:449] Starting replica recovery
> I0610 20:04:48.593698 24587 recover.cpp:475] Replica is in EMPTY status
> I0610 20:04:48.595641 24580 replica.cpp:641] Replica in EMPTY status received
> a broadcasted recover request
> I0610 20:04:48.596086 24590 recover.cpp:195] Received a recover response from
> a replica in EMPTY status
> I0610 20:04:48.596607 24590 recover.cpp:566] Updating replica status to
> STARTING
> I0610 20:04:48.597507 24590 leveldb.cpp:306] Persisting metadata (8 bytes) to
> leveldb took 717888ns
> I0610 20:04:48.597535 24590 replica.cpp:323] Persisted replica status to
> STARTING
> I0610 20:04:48.597697 24590 recover.cpp:475] Replica is in STARTING status
> I0610 20:04:48.599165 24584 replica.cpp:641] Replica in STARTING status
> received a broadcasted recover request
> I0610 20:04:48.599434 24584 recover.cpp:195] Received a recover response from
> a replica in STARTING status
> I0610 20:04:48.599915 24590 recover.cpp:566] Updating replica status to VOTING
> I0610 20:04:48.600545 24590 leveldb.cpp:306] Persisting metadata (8 bytes) to
> leveldb took 432335ns
> I0610 20:04:48.600574 24590 replica.cpp:323] Persisted replica status to
> VOTING
> I0610 20:04:48.600659 24590 recover.cpp:580] Successfully joined the Paxos
> group
> I0610 20:04:48.600797 24590 recover.cpp:464] Recover process terminated
> I0610 20:04:48.602905 24594 master.cpp:363] Master
> 20150610-200448-3875541420-32907-24561 (dbade881e927) started on
> 172.17.0.231:32907
> I0610 20:04:48.602957 24594 master.cpp:365] Flags at startup: --acls=""
> --allocation_interval="1secs" --allocator="HierarchicalDRF"
> --authenticate="true" --authenticate_slaves="true" --authenticators="crammd5"
> --credentials="/tmp/FetcherCacheTest_LocalCachedExtract_Cwdcdj/credentials"
> --framework_sorter="drf" --help="false" --initialize_driver_logging="true"
> --log_auto_initialize="true" --logbufsecs="0" --logging_level="INFO"
> --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_reregister_timeout="10mins"
> --user_sorter="drf" --version="false"
> --webui_dir="/mesos/mesos-0.23.0/_inst/share/mesos/webui"
> --work_dir="/tmp/FetcherCacheTest_LocalCachedExtract_Cwdcdj/master"
> --zk_session_timeout="10secs"
> I0610 20:04:48.603374 24594 master.cpp:410] Master only allowing
> authenticated frameworks to register
> I0610 20:04:48.603392 24594 master.cpp:415] Master only allowing
> authenticated slaves to register
> I0610 20:04:48.603404 24594 credentials.hpp:37] Loading credentials for
> authentication from
> '/tmp/FetcherCacheTest_LocalCachedExtract_Cwdcdj/credentials'
> I0610 20:04:48.603751 24594 master.cpp:454] Using default 'crammd5'
> authenticator
> I0610 20:04:48.604928 24594 master.cpp:491] Authorization enabled
> I0610 20:04:48.606034 24593 hierarchical.hpp:309] Initialized hierarchical
> allocator process
> I0610 20:04:48.606106 24593 whitelist_watcher.cpp:79] No whitelist given
> I0610 20:04:48.607430 24594 master.cpp:1476] The newly elected leader is
> master@172.17.0.231:32907 with id 20150610-200448-3875541420-32907-24561
> I0610 20:04:48.607466 24594
[jira] [Created] (MESOS-4182) Add Qunar to the "Powered by" page.
Lei Xu created MESOS-4182: - Summary: Add Qunar to the "Powered by" page. Key: MESOS-4182 URL: https://issues.apache.org/jira/browse/MESOS-4182 Project: Mesos Issue Type: Wish Components: documentation Reporter: Lei Xu Priority: Trivial Hi, We use Mesos and Marathon to support the log analyize programs, such as ELK, Spark. It is a great resource manager to hold thousands of applications to deal with 6~8 billion lines text per day, thanks very much! https://github.com/apache/mesos/pull/83 We'd love if you could merge it. :) -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (MESOS-4155) Speed up ExamplesTest.*
[
https://issues.apache.org/jira/browse/MESOS-4155?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15059606#comment-15059606
]
Jian Qiu commented on MESOS-4155:
-
One of the problem comes from authentication time out
{code}
W1216 15:02:52.761855 162168832 sched.cpp:429] Authentication timed out
I1216 15:02:52.762025 162168832 sched.cpp:387] Failed to authenticate with
master master@192.168.99.1:54409: Authentication discarded
I1216 15:02:52.762082 162168832 sched.cpp:318] Authenticating with master
master@192.168.99.1:54409
I1216 15:02:52.762097 162168832 sched.cpp:325] Using default CRAM-MD5
authenticatee
{code}
> Speed up ExamplesTest.*
> ---
>
> Key: MESOS-4155
> URL: https://issues.apache.org/jira/browse/MESOS-4155
> Project: Mesos
> Issue Type: Epic
> Components: technical debt, test
>Reporter: Alexander Rukletsov
>Priority: Minor
> Labels: mesosphere, newbie++, tech-debt
>
> Execution times on Mac OS 10.10.4:
> {code}
> ExamplesTest.TestFramework (5225 ms)
> ExamplesTest.NoExecutorFramework (5387 ms)
> ExamplesTest.EventCallFramework (1238 ms)
> ExamplesTest.PersistentVolumeFramework (3380 ms)
> ExamplesTest.JavaFramework (6159 ms)
> ExamplesTest.JavaException (1 ms)
> ExamplesTest.JavaLog (1174 ms)
> ExamplesTest.PythonFramework (7126 ms)
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
