[SERVER-75293] Different return types for the connectionId Created: 26/Mar/23 Updated: 21/Apr/23 Resolved: 21/Apr/23 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | None |
| Affects Version/s: | 4.4.18 |
| Fix Version/s: | None |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | Vinicius Grippa | Assignee: | Dianna Hohensee (Inactive) |
| Resolution: | Won't Do | Votes: | 1 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||||||||||||||
| Assigned Teams: |
Storage Execution
|
||||||||||||||||||||
| Operating System: | ALL | ||||||||||||||||||||
| Sprint: | Execution Team 2023-05-01 | ||||||||||||||||||||
| Participants: | |||||||||||||||||||||
| Description |
|
This issue started affecting several drivers when connectionId was implemented in the return of the hello() command. The general ticket of the driver issue is this: The problem with connectioId is that the type returned can change, causing exceptions on the driver side. An example is the following ticket: When looking at Mongo code we can see that appendNumber function:
If we look at the appendNumber: We can see:
So, Mongo needs to decide where to fix this issue. If this is expected behavior then this fix needs to be accepted: Otherwise, if it is a server issue, the upstream code needs to provide a single type to return the connectionId to avoid these driver exceptions. From what I see in this bug, it gives the impression no one was expecting Mongo running for so long without the need to be restarted. |
| Comments |
| Comment by Dianna Hohensee (Inactive) [ 21/Apr/23 ] |
|
In master the cluster_hello_cmd.cpp uses appendNumber, which as Chris Kelly noted can only return int or LL as of It looks like the Driver issue in DRIVERS-2503 is being fixed independently of any server changes, since Drivers must support all versions. It won't be helpful to Drivers to backport |
| Comment by Chris Kelly [ 29/Mar/23 ] |
|
Thanks for your report! I think this may have been fixed in |