brooklyn-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Graeme Miller (JIRA)" <j...@apache.org>
Subject [jira] [Created] (BROOKLYN-208) Config resolution on shutdown
Date Tue, 22 Dec 2015 17:47:47 GMT
Graeme Miller created BROOKLYN-208:
--------------------------------------

             Summary: Config resolution on shutdown
                 Key: BROOKLYN-208
                 URL: https://issues.apache.org/jira/browse/BROOKLYN-208
             Project: Brooklyn
          Issue Type: Bug
    Affects Versions: 0.9.0
            Reporter: Graeme Miller
            Priority: Minor


Consider a blueprint that has two entities, Entity1 and Entity2. Entity1 has a brooklyn.config
value Conf1. Entity2 has a brookyln.config value Conf2, which uses attributeWhenReady to get
the value of Conf1.

When Entity2 is shutting down, it attempts to get Conf2 (for example because it is a 'shell.env'
parameter). Brooklyn then creates a task to get the value of Conf1 to populate it, however,
Entity1 has already shutdown. Entity2 now waits for the value until a timeout and then cancels
resolving Conf2.

To fix this situation, I would like to suggest that config values should be immutable, I.E.
should be resolved once before the entity starts and never again.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Mime
View raw message