[
https://issues.apache.org/jira/browse/BROOKLYN-175?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14958846#comment-14958846
]
ASF GitHub Bot commented on BROOKLYN-175:
-----------------------------------------
Github user sjcorbett commented on the pull request:
https://github.com/apache/incubator-brooklyn/pull/956#issuecomment-148376357
Looks fine. Will run integration tests and merge.
> 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)
