[DRIVERS-2711] Publish TopologyDescriptionChangedEvent on topology close Created: 30/Aug/23  Updated: 11/Jan/24

Status: In Progress
Project: Drivers
Component/s: Logging, SDAM
Fix Version/s: None

Type: Task Priority: Minor - P4
Reporter: Boris Dogadov Assignee: Warren James
Resolution: Unresolved Votes: 0
Labels: alex+, jeff+, leads-triage, rachelle+
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Depends
is depended on by GODRIVER-2967 Sync SDAM "Topology Lifecycle" with f... Backlog
is depended on by JAVA-4770 Add log messages to SDAM spec Backlog
is depended on by DRIVERS-1670 Add log messages to SDAM spec Implementing
Issue split
split to CDRIVER-4757 Publish TopologyDescriptionChangedEve... Blocked
split to CSHARP-4830 Publish TopologyDescriptionChangedEve... Blocked
split to CXX-2780 Publish TopologyDescriptionChangedEve... Blocked
split to GODRIVER-3035 Publish TopologyDescriptionChangedEve... Blocked
split to JAVA-5229 Publish TopologyDescriptionChangedEve... Blocked
split to MOTOR-1205 Publish TopologyDescriptionChangedEve... Blocked
split to NODE-5723 Publish TopologyDescriptionChangedEve... Blocked
split to PHPLIB-1300 Publish TopologyDescriptionChangedEve... Blocked
split to PYTHON-4021 Publish TopologyDescriptionChangedEve... Blocked
split to RUBY-3344 Publish TopologyDescriptionChangedEve... Blocked
split to RUST-1791 Publish TopologyDescriptionChangedEve... Blocked
Driver Changes: Needed
Quarter: FY24Q4
Engineering Lead: Shane Harvey Shane Harvey
Start date:
Driver Compliance:
Key Status/Resolution FixVersion
CDRIVER-4757 Blocked
CXX-2780 Blocked
CSHARP-4830 Blocked
GODRIVER-3035 Blocked
JAVA-5229 Blocked
NODE-5723 Blocked
MOTOR-1205 Blocked
PYTHON-4021 Blocked
PHPLIB-1300 Blocked
RUBY-3344 Blocked
RUST-1791 Blocked

 Description   

Summary

Currently .NET and Rust drivers (maybe other drivers as well) set topology description to Unknown and emit TopologyDescriptionChangedEvent on closing (before TopologyClosedEvent).
The SDAM logs tests account for that.

The question is whether when TopologyClosedEvent if emitted, should the topology be in up to date state, which Unknown state (all servers are removed by then).
Consider adding this behaviour to SDAM specification for a better topology state management.

For events consistency across all drivers, it would be useful to clarify the desired behaviour on topology close.

If decided that TopologyDescriptionChangedEvent should not be published on topology close, SDAM logging tests need to be updated accordingly.

Motivation

Who is the affected end user?

Drivers

How does this affect the end user?

No known affect

How likely is it that this problem or use case will occur?

Main path

If the problem does occur, what are the consequences and how severe are they?

Events consistency among drivers.

Is this issue urgent?

No

Is this ticket required by a downstream team?

No

Is this ticket only for tests?

Yes, logging tests

Acceptance Criteria

What specific requirements must be met to consider the design phase complete?


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