[SERVER-45073] Check profiler before logs in comment_field.js Created: 11/Dec/19 Updated: 29/Oct/23 Resolved: 14/Dec/19 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Testing Infrastructure |
| Affects Version/s: | None |
| Fix Version/s: | 4.3.3 |
| Type: | Improvement | Priority: | Major - P3 |
| Reporter: | Bernard Gorman | Assignee: | Bernard Gorman |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||
| Backwards Compatibility: | Fully Compatible | ||||
| Sprint: | Query 2019-12-30 | ||||
| Participants: | |||||
| Linked BF Score: | 11 | ||||
| Description |
|
We saw a single BF incident for comment_field.js where the createIndexes command was unexpectedly logged on only one of two shards, and mongoS. We should move the profiler check before the logging check such that, if this failure occurs again, we will be able to tell whether the entry was correctly profiled and then failed to log, or whether it vanished altogether. |
| Comments |
| Comment by Githook User [ 14/Dec/19 ] |
|
Author: {'name': 'Bernard Gorman', 'email': 'bernard.gorman@mongodb.com', 'username': 'gormanb'}Message: |