[JAVA-5185] Fix the ClusterListener, ServerListener, ServerMonitorListener API docs relevant to thread-safety Created: 28/Sep/23 Updated: 04/Oct/23 Resolved: 04/Oct/23 |
|
| Status: | Closed |
| Project: | Java Driver |
| Component/s: | Documentation |
| Affects Version/s: | None |
| Fix Version/s: | 4.11.0 |
| Type: | Improvement | Priority: | Unknown |
| Reporter: | Valentin Kavalenka | Assignee: | Valentin Kavalenka |
| Resolution: | Done | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||||||
| Backwards Compatibility: | Fully Compatible | ||||||||||||
| Documentation Changes: | Needed | ||||||||||||
| Documentation Changes Summary: | Let's mention in What's new that we fixed the documentation of ClusterListener, ServerListener, ServerMonitorListener. Users should not take the guarantee provided by these listeners as something that automatically spares them from synchronizing memory accesses. |
||||||||||||
| Description |
|
While the events are delivered to ClusterListener/ServerListener/ServerMonitorListener in a total order consistent with HB, these listeners still have to synchronize writes to shared memory with reads from it if the listeners write to shared memory. For a listener to be of any use, it has to write to shared memory, unless the only activity it does is logging or terminating the process. |
| Comments |
| Comment by Githook User [ 04/Oct/23 ] |
|
Author: {'name': 'Valentin Kovalenko', 'email': 'valentin.kovalenko@mongodb.com', 'username': 'stIncMale'}Message: Fix the `ClusterListener`, `ServerListener`, `ServerMonitorListener` API docs relevant to thread-safety (#1208)
|