[SERVER-34034] Test mongos slow query log format Created: 21/Mar/18 Updated: 29/Oct/23 Resolved: 04/Apr/18 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Querying, Sharding |
| Affects Version/s: | None |
| Fix Version/s: | 3.7.4 |
| Type: | Task | Priority: | Major - P3 |
| Reporter: | David Storch | Assignee: | Bernard Gorman |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Backwards Compatibility: | Fully Compatible |
| Sprint: | Query 2018-03-26, Query 2018-04-09 |
| Participants: |
| Description |
|
This can work with a test in the core suite that is also eligible for the mongos passthroughs. There are some existing tests using getLog that we can probably update to be more thorough. |
| Comments |
| Comment by Githook User [ 04/Apr/18 ] |
|
Author: {'email': 'bernard.gorman@gmail.com', 'name': 'Bernard Gorman', 'username': 'gormanb'}Message: |
| Comment by David Storch [ 21/Mar/18 ] |
|
bernard.gorman, as part of this ticket, I think we should include an integration test which verifies that slowms and sampleRate configuration have the expected effect on mongos. |