brooklyn-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From neykov <>
Subject [GitHub] brooklyn-server pull request #520: Limit parallelism of start/stop steps on ...
Date Mon, 16 Jan 2017 16:50:57 GMT
GitHub user neykov opened a pull request:

    Limit parallelism of start/stop steps on SoftwareProcess

    Setting a `ReleaseableLatch` as the latch of a `SoftwareProcess` allows for controlling
the behaviour of the start/stop effector.
    When `ReleaseableLatch.Factory.maxConcurrency(int)` is used as the value of the latch
(either directly or by referncing a `MaxConcurrencySensor`) only the specified maximum number
of threads will be able to execute the immediate step the latch is guarding.
    It's very similar to `DynamicCluster.MAX_CONCURRENT_CHILD_COMMANDS` but allows for finer-grained
control (though is specific to `SoftwareProcess`).

You can merge this pull request into a Git repository by running:

    $ git pull max-concurrency

Alternatively you can review and apply these changes as the patch at:

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

    This closes #520
commit 112269ae484dcc5283d9cabc8de2e987f013e79f
Author: Svetoslav Neykov <>
Date:   2017-01-16T16:37:46Z

    Add iterator to ValueResolver
    Resolves the initial object iteratively until either failure or object can't be resolved
any more.

commit b7b5ab25a0c483b9c97d03404db2cad40a5485a4
Author: Svetoslav Neykov <>
Date:   2017-01-16T16:40:55Z

    Let latches limit the paralellism for the step they guard


If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at or file a JIRA ticket
with INFRA.

View raw message