GitHub user aledsage opened a pull request:
https://github.com/apache/brooklyn-server/pull/789
Adds DynamicCluster.START_TIMEOUT
Similar to `SoftwareProcess`, this allows a dynamic cluster to wait for
`service.isUp` before returning from `start()`. It defaults to not waiting
(for backwards compatibility).
Previously, it would return as soon as all the initial memberâs start()
effectors had finished executing.
---
Note that the new test `testReportsServiceUpAsSoonAsQuorumSize()` just
demonstrates existing behaviour - this PR does not change that behaviour.
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/aledsage/brooklyn-server
DynamicCluster-waitForServiceUp
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/brooklyn-server/pull/789.patch
To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:
This closes #789
----
commit 64d9862443c6bf2ed018ab717b43930914872484
Author: Aled Sage <[email protected]>
Date: 2017-08-03T13:37:48Z
Adds DynamicCluster.START_TIMEOUT
Similar to SoftwareProcess, this allows a dynamic cluster to wait for
service.isUp before returning from `start`. It defaults to not waiting
(for backwards compatibility).
Previously, it would return as soon as all the initial memberâs start()
effectors had finished executing.
----
---
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 [email protected] or file a JIRA ticket
with INFRA.
---
