[
https://issues.apache.org/jira/browse/BROOKLYN-175?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14957551#comment-14957551
]
ASF GitHub Bot commented on BROOKLYN-175:
-----------------------------------------
GitHub user ygy opened a pull request:
https://github.com/apache/incubator-brooklyn/pull/956
BROOKLYN-175 Fixing MongoDB restart() phase
- isRunning() check uses ping() during the restart phase
- ping() must complete in a reasonable amount of time since
it is invoked against stopped entities too
- lowering the MongoClient timeouts, because default values are too
high when used inside ping()
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/ygy/incubator-brooklyn fix/mongodb-restart
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/incubator-brooklyn/pull/956.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 #956
----
commit 87be92257b6f44ec9966e41795c856a5eced3afd
Author: Yavor Yanchev <[email protected]>
Date: 2015-10-14T18:44:14Z
BROOKLYN-175 Fixing MongoDB restart() phase
- isRunning() check uses ping() during the restart phase
- ping() must complete in a reasonable amount of time since
it is invoked against stopped entities too
- lowering the MongoClient timeouts, because default values are too
high when used inside ping()
----
> MongoDB process restart() very slow for phase "stop (best effort)"
> ------------------------------------------------------------------
>
> Key: BROOKLYN-175
> URL: https://issues.apache.org/jira/browse/BROOKLYN-175
> Project: Brooklyn
> Issue Type: Bug
> Affects Versions: 0.9.0
> Reporter: Aled Sage
>
> On a private vcloud-director cloud, I had an app with a single MongoDB
> instance (where access to the various ports was over NAT).
> I stopped just the process (via the stop effector on the MongoDB entity). I
> then called restart() on the mongoDB entity. After 5 minutes, finally the
> “stop (best effort)” completed. Then the process restarted quickly.
> Why did it take 5 minute for “stop (best effort)”?!
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
