[SERVER-50559] Don't log waiting change stream getMores as slow queries Created: 26/Aug/20 Updated: 29/Oct/23 Resolved: 05/Jul/21 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | None |
| Affects Version/s: | 4.0.19, 4.4.1 |
| Fix Version/s: | 5.1.0-rc0 |
| Type: | Improvement | Priority: | Major - P3 |
| Reporter: | Jing Wu | Assignee: | Denis Grebennicov |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | qexec-team | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||
| Backwards Compatibility: | Minor Change | ||||||||
| Sprint: | Query 2020-11-30, Query Execution 2021-05-31, Query Execution 2021-06-14, Query Execution 2021-06-28, Query Execution 2021-07-12 | ||||||||
| Participants: | |||||||||
| Description |
|
This messages show up every second even there is no traffic form application to this mongos:
Thanks, Jing |
| Comments |
| Comment by Vivian Ge (Inactive) [ 06/Oct/21 ] |
|
Updating the fixversion since branching activities occurred yesterday. This ticket will be in rc0 when it’s been triggered. For more active release information, please keep an eye on #server-release. Thank you! |
| Comment by Githook User [ 05/Jul/21 ] |
|
Author: {'name': 'Denis Grebennicov', 'email': 'denis.grebennicov@mongodb.com', 'username': 'denis631'}Message: |
| Comment by Bernard Gorman [ 30/Nov/20 ] |
|
I'm going to add this ticket to our upcoming Quick Wins bucket. |
| Comment by Eric Sedor [ 09/Sep/20 ] |
|
Hi Jing, thanks for your patience. Since these messages make idle mongos logs very noisy and aren't reporting operations that are slow for a problematic reason, it makes sense to avoid logging them if possible. I'm going to pass this on to an appropriate team for further consideration. Currently, you can influence these messages if necessary, but only with side effects.
|
| Comment by Jing Wu [ 09/Sep/20 ] |
|
Eric, |
| Comment by Jing Wu [ 07/Sep/20 ] |
|
Hi Eric, |
| Comment by Jing Wu [ 28/Aug/20 ] |
|
Hi Eric, Yes, the message is showing up every second in mongos.log. Is it new behaviour in 4.0 mongos ? How can I suppress such messages if it's not a bug ? Thanks |
| Comment by Eric Sedor [ 27/Aug/20 ] |
|
jing66wu@yahoo.com on the surface, this looks like the client is polling for new change events and finding none (which is why these log lines show nreturned:0). Do I understand correctly that you have a client opening a changeStream on the "altconfig-b2b-perf.oplog" collection, and you are asking just about a difference in log behavior between 3.6 and 4.0? |
| Comment by Jing Wu [ 26/Aug/20 ] |
|
The message is in mongos log. |