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: membership tracking policy defaul...
Date Wed, 16 Jul 2014 15:26:30 GMT
Github user aledsage commented on the pull request:

    https://github.com/apache/incubator-brooklyn/pull/73#issuecomment-49182163
  
    Background for this change... originally the AbstractMembershipTrackingPolicy was not
configurable. It would not notify of duplicates for serviceUp, but would for other attributes.
    
    This was changed a while back so it was configurable, but trying to preserve original
behaviour. However, there was a bug: serviceUp duplicates were being sent through, resulting
in 1000s of effector calls in some entities trying to respond to the change!
    
    Given the event is "entityChanged" it makes sense for the default to be false. For places
where it is important to get the duplicate (e.g. where timestamps are important for recording
workload etc) then one can configure the policy accordingly.


---
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