[SERVER-45673] Implement poolResetCounter logic Created: 21/Jan/20 Updated: 06/Dec/22 Resolved: 05/May/20 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | New Feature | Priority: | Major - P3 |
| Reporter: | Lamont Nelson | Assignee: | Backlog - Service Architecture |
| Resolution: | Won't Fix | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Assigned Teams: |
Service Arch
|
| Sprint: | Service Arch 2020-01-27 |
| Participants: |
| Description |
|
poolResetCounter is used to guard against processing stale messages in drivers spec. When we have a problem when contacting a monitored host, the "failedHost" method of RSM will be called to notify the sdam subsystem. If this problem is a network timeout, or timeout, we should increment the poolResetCounter for the associated ServerDescription. There is already a _generation member variable on the connection pool that is used for the same purpose as poolResetCounter. We should determine if we want to use this value or track this separately in the rsm code. Either way, the sdam system needs to be modified to ignore messages coming from connections associated with older versions of poolResetCounter.
|
| Comments |
| Comment by Janna Golden [ 05/May/20 ] |
|
This is not necessary for the server client implementation side of this project. |
| Comment by Haley Connelly [ 03/Mar/20 ] |
|
Sorry, was not. Moved back to open! |
| Comment by Kelly Lewis [ 03/Mar/20 ] |
|
Hi haley.connelly, is this actively being investigated or should it be moved back to Open? |