[SERVER-49050] Cannot differentiate logs from different shards with python fixtures Created: 23/Jun/20 Updated: 29/Oct/23 Resolved: 24/Jun/20 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Sharding, Testing Infrastructure |
| Affects Version/s: | None |
| Fix Version/s: | 4.7.0 |
| Type: | Bug | Priority: | Critical - P2 |
| Reporter: | Judah Schvimer | Assignee: | Raiden Worley (Inactive) |
| Resolution: | Fixed | Votes: | 2 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||
| Backwards Compatibility: | Fully Compatible | ||||||||
| Sprint: | STM 2020-06-29 | ||||||||
| Participants: | |||||||||
| Description |
|
A log line looks like:
But I do not think there's a way to really know which shard/csrs it belongs to. We just know it's a primary on in some replica set. The test fixture knows its replica set name, so we just need to include it in the log. |
| Comments |
| Comment by Githook User [ 24/Jun/20 ] | |
|
Author: {'name': 'Carl Raiden Worley', 'email': 'carl.worley@10gen.com', 'username': 'aggrand'}Message: | |
| Comment by Max Hirschhorn [ 23/Jun/20 ] | |
|
The log format for sharded clusters spawned by resmoke.py prior to the changes from c81a9f3 as part of
|