brooklyn-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "ASF GitHub Bot (JIRA)" <>
Subject [jira] [Commented] (BROOKLYN-356) The sensor Transformer enricher fails to resolve its targetValue indeterministically.
Date Wed, 12 Oct 2016 13:41:21 GMT


ASF GitHub Bot commented on BROOKLYN-356:

GitHub user aledsage opened a pull request:

    BROOKLYN-356: workaround, by increasing timeout

    @neykov can you take a look please?

You can merge this pull request into a Git repository by running:

    $ git pull BROOKLYN-356-increase-timeout

Alternatively you can review and apply these changes as the patch at:

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

    This closes #381
commit c45777f33402b1326e637b8bd5314c295608d9a7
Author: Aled Sage <>
Date:   2016-10-12T13:16:52Z

    JcloudsByonLocationResolverStubbedRebindTest: avoid taking 5 minutes

commit 0edce9879670560c245f2f6f4df3eae9fd2c27a8
Author: Aled Sage <>
Date:   2016-10-12T13:17:01Z

    BROOKLYN-356: workaround, by increasing timeout


> The sensor Transformer enricher fails to resolve its targetValue indeterministically.
> -------------------------------------------------------------------------------------
>                 Key: BROOKLYN-356
>                 URL:
>             Project: Brooklyn
>          Issue Type: Bug
>            Reporter: Svetoslav Neykov
> The sensor {{Transformer}} enricher fails to resolve its {{targetValue}} indeterministically,
especially so on loaded systems. This is especially problematic if sourceSensor/triggerSensors
change infrequently or do not change ever (when using default values).
> Bueprints using the {{Transformer}} behave perfectly fine during development and on test
setups, but will fail on production machines (i.e. under load).
> The code [doing the value resolving|]
tries to do so in a non-blocking fashion by spinning a thread to try to resolve and cancelling
it after a short while without guarantees it ever got scheduled to run. It's more likely to
fail when nesting DSLs, for example nesting several levels of {{$brooklyn:formatString}} and
ending with a {{$brooklyn:attributeWhenRready}}. It's a common pattern in moderately complex
blueprints. It needs to schedule a thread for each nesting level thus maximizing the chance
that the value will not be resolved in the allotted time even if resolvabe. This is especially
bad for sensors which don't get updated, for example {{PortAttributeSensorAndConfigKey} set
only when initializing the entity or any config values which are always resolvable.

This message was sent by Atlassian JIRA

View raw message