brooklyn-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Martin Harris (JIRA)" <>
Subject [jira] [Created] (BROOKLYN-171) Mapping propagated sensor causes excessive CPU load
Date Thu, 10 Sep 2015 13:01:46 GMT
Martin Harris created BROOKLYN-171:

             Summary: Mapping propagated sensor causes excessive CPU load
                 Key: BROOKLYN-171
             Project: Brooklyn
          Issue Type: Bug
            Reporter: Martin Harris

Mapping a propagated sensor using a second propagator will cause excessive CPU load, and the
sensor will fail to propagate. This can be demonstrated using the following YAML:

location: localhost
- type: org.apache.brooklyn.entity.stock.BasicApplication
  - type:
    id: childid

  - type: org.apache.brooklyn.enricher.stock.Propagator
      producer: $brooklyn:component("child", "childid")
      - $brooklyn:sensor("")
  - type: org.apache.brooklyn.enricher.stock.Propagator
        $brooklyn:sensor(""): $brooklyn:sensor("host")

Running this YAML will cause CPU load on my machine to run to around 600% CPU, and cause the
Brooklyn console to become unresponsive. The specs of my machine are as follows:

  Model Name:	MacBook Pro
  Model Identifier:	MacBookPro11,3
  Processor Name:	Intel Core i7
  Processor Speed:	2.8 GHz
  Number of Processors:	1
  Total Number of Cores:	4
  L2 Cache (per Core):	256 KB
  L3 Cache:	6 MB
  Memory:	16 GB

Context (aka 'Why would you ever want to do this??'):

The Redis cluster propagates the hostname of the master RedisStore up to the cluster level
[1]. We then added (in the YAML) a propagator with `sensorMapping` to map the sensor ``
to `host` in order for it to be consumed by a third party application (CloudFoundry via the

In this scenario (i.e. Redis, deploying to AWS from a rBrooklyn server), the server web interface
becomes completely unresponsive until the Brooklyn process is terminated and restarted


This message was sent by Atlassian JIRA

View raw message