[SERVER-27002] Double counting of uassert when non-ssl connection attempted on sslMode required Created: 11/Nov/16 Updated: 08/May/18 Resolved: 03/May/18 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Logging, Networking |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Bug | Priority: | Minor - P4 |
| Reporter: | Daniel Pasette (Inactive) | Assignee: | Mira Carey |
| Resolution: | Done | Votes: | 0 |
| Labels: | dogfooding | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Operating System: | ALL |
| Participants: |
| Description |
|
| Comments |
| Comment by Mira Carey [ 03/May/18 ] |
|
This is gone away as of 3.6 (gone for both transport layer asio as well as legacy). |
| Comment by Daniel Pasette (Inactive) [ 13/Nov/16 ] |
|
this is a minor issue. it would be better to not register two uasserts for the same error during one operation in general, but the cost does not seem to outweigh the benefit. |
| Comment by Mira Carey [ 11/Nov/16 ] |
|
These log lines come out this way because we:
So this isn't indicative of any bugs in the code. Are we hoping for a pervasive fix, or just not double logging in this particular case? A pervasive solution is going to be somewhat complicated (do we want to avoid uasserting the same message twice? Or more than once per client operation?). The specific case is a bit easier, but hacky (we can check the status code at the second uassert location and throw instead of uasserting if it has that code) |