[DRIVERS-944] SDAM spec and monitoring spec tests are inconsistent in topology description definition Created: 06/Feb/20  Updated: 31/Mar/22

Status: Backlog
Project: Drivers
Component/s: SDAM
Fix Version/s: None

Type: Spec Change Priority: Major - P3
Reporter: Oleg Pudeyev (Inactive) Assignee: Unassigned
Resolution: Unresolved Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Related
related to CDRIVER-3527 Store server_description_t hostname f... Backlog

 Description   

SDAM spec defines topology description in https://github.com/mongodb/specifications/blob/master/source/server-discovery-and-monitoring/server-discovery-and-monitoring.rst#topologydescription. This definition contains a list of fields that must be included in topology description, and notably does not include server descriptions or server addresses.

SDAM Monitoring spec in https://github.com/mongodb/specifications/blob/master/source/server-discovery-and-monitoring/server-discovery-and-monitoring-monitoring.rst#events specifies that topology description changed event must be published when:

> When the old topology description is not equal to the new topology description.

At the same time, sdam monitoring spec tests such as https://github.com/mongodb/specifications/blob/master/source/server-discovery-and-monitoring/tests/monitoring/replica_set_with_no_primary.yml#L25 require that a topology description event is published when none of the fields enumerated in the topology description definition change.

It appears that the monitoring spec tests contradict the language in the sdam/monitoring specifications.



 Comments   
Comment by Jeffrey Yemin [ 11/Feb/20 ]

The language is incorrect/imprecise. The tests are correct.

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