brooklyn-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From aledsage <...@git.apache.org>
Subject [GitHub] incubator-brooklyn pull request: PostgreSQL lifecycle improvements
Date Mon, 17 Aug 2015 12:17:58 GMT
Github user aledsage commented on the pull request:

    https://github.com/apache/incubator-brooklyn/pull/792#issuecomment-131797684
  
    Background context for others... A Brooklyn user has a number of entities in the dev/test
environment, including `PostgreSqlNode`. For each, they stopped the process (e.g. using the
`stop` effector with `stopProcessMode=ALWAYS` and `stopMachineMode=NEVER`). They then called
the `start` effector, expecting that to restart the process. For most types of entities it
worked (because the `install` and `customize` phases were idempotent. However, for `PostgreSqlNode`
the customize phase executed `initdb` (which you don't want to do on an existing database).
    
    The user should have called the `restart` effector with parameters `restartMachine=false`.
This would have just done the `launch` phase.
    
    However, the `restart` effector has the downside of first stopping the process (if it
is currently running). What the user really wants is an effector for "launch to process if
it's not already running; if it is running then do nothing".


---
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 infrastructure@apache.org or file a JIRA ticket
with INFRA.
---

Mime
View raw message