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 [email protected] or file a JIRA ticket
with INFRA.
---
