[JAVA-3485] Stop firing duplicate server and cluster description events Created: 28/Oct/19  Updated: 28/Oct/23  Resolved: 02/Sep/20

Status: Closed
Project: Java Driver
Component/s: Monitoring
Affects Version/s: None
Fix Version/s: 4.2.0

Type: Improvement Priority: Major - P3
Reporter: PM Bot Assignee: Jeffrey Yemin
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Depends
is depended on by DRIVERS-760 Add SDAM test for debouncing topology... Implementing
Backwards Compatibility: Minor Change

 Description   

See DRIVERS-760 for details.



 Comments   
Comment by Jeffrey Yemin [ 02/Sep/20 ]

This introduces a minor behavioral change, in that the driver will no longer generate consecutive duplicate server and cluster description events.

Comment by Githook User [ 02/Sep/20 ]

Author:

{'name': 'Jeff Yemin', 'email': 'jeff.yemin@mongodb.com', 'username': 'jyemin'}

Message: Suppress firing of consecutive duplicate server and cluster events

Don't fire server or cluster description changed events when the description hasn't changed
from the previously fired event.

JAVA-3485
Branch: master
https://github.com/mongodb/mongo-java-driver/commit/b165880c659b82ae2436b3cb2689b95ebc19d642

Comment by Githook User [ 02/Sep/20 ]

Author:

{'name': 'Jeff Yemin', 'email': 'jeff.yemin@mongodb.com', 'username': 'jyemin'}

Message: Refactor to enable event suppression

The monitoring specification requires that duplicate server
events are not sent. This refactoring separates server listeners
registered by the application, to which this rule applies, from
the one registered by Cluster implementation, to which this rule
does not apply.

JAVA-3485
Branch: master
https://github.com/mongodb/mongo-java-driver/commit/6f100b8c4bedbb32187529dace92c331b214344b

Generated at Thu Feb 08 08:59:43 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.