[SERVER-21159] cursor manager messages improvement Created: 27/Oct/15 Updated: 06/Dec/22 Resolved: 03/Dec/21 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Querying, Shell |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Improvement | Priority: | Major - P3 |
| Reporter: | Eric Milkie | Assignee: | Backlog - Server Tooling and Methods (STM) (Inactive) |
| Resolution: | Won't Fix | Votes: | 0 |
| Labels: | move-stm | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Assigned Teams: |
Server Tooling & Methods
|
| Participants: |
| Description |
|
If you open a cursor in the shell (say, you do a find() query and get the "type it for more" message), and then shut the underlying server down, and then attempt to exit the shell, you will get a Frankenmessage like this:
|
| Comments |
| Comment by Brooke Miller [ 03/Dec/21 ] |
|
The shell is deprecated to external users, so please feel free to re-open if you are a core-db contributor and would like this feature for correctness testing purposes. |
| Comment by J Rassi [ 03/Nov/15 ] |
|
I agree that this message should be suppressed in this case. CursorHandleInfo::finalize() should either special-case the error handling for socket exceptions, or the log message should be removed entirely. There's also an argument for leaving the message in when the shell is run in non-interactive mode. |