[SERVER-20180] Provide mechanism to determine which kind of process is logging a message during test output Created: 28/Aug/15 Updated: 07/Oct/15 Resolved: 22/Sep/15 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Sharding, Testing Infrastructure |
| Affects Version/s: | 3.1.7 |
| Fix Version/s: | 3.1.9 |
| Type: | Improvement | Priority: | Major - P3 |
| Reporter: | Charlie Swanson | Assignee: | Charlie Swanson |
| Resolution: | Done | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Backwards Compatibility: | Fully Compatible |
| Sprint: | QuInt A (10/12/15) |
| Participants: |
| Description |
|
Currently in the logs of our test output, mongod or mongos processes started by the test have log lines with the following format:
For example:
Engineers that have experience with ReplSetTest and ShardingTest can tell which nodes are likely to be a mongos, a primary node, or a config server based on the port it's running on. (e.g 30999 for mongos, 29000-29002 for config servers, 31000+ for regular mongod's) We should move away from this special association of ports with certain types of nodes/processes. Instead, the
part of the log message should include the information about which kind of process it is. Something like:
This will make the logic of allocating ports for parallel testing much simpler, and hopefully will make reading the logs easier. Even with this information, it would still be nice to group nodes of a replica set to have similar ports, or mongos's for the same cluster. |
| Comments |
| Comment by Githook User [ 22/Sep/15 ] |
|
Author: {u'username': u'cswanson310', u'name': u'Charlie Swanson', u'email': u'charlie.swanson@mongodb.com'}Message: |
| Comment by Charlie Swanson [ 10/Sep/15 ] |
|
Appears to have made the noPassthrough suite unresponsive, so reverting until we can figure out why |
| Comment by Githook User [ 10/Sep/15 ] |
|
Author: {u'username': u'cswanson310', u'name': u'Charlie Swanson', u'email': u'charlie.swanson@mongodb.com'}Message: Revert " This reverts commit ed3c15504d8d5b6afaac95a6f5bbf4742fe51092. |
| Comment by Githook User [ 09/Sep/15 ] |
|
Author: {u'username': u'cswanson310', u'name': u'Charlie Swanson', u'email': u'charlie.swanson@mongodb.com'}Message: Mostly applicable for tests that use ShardingTest |
| Comment by Spencer Brody (Inactive) [ 28/Aug/15 ] |
|
This is a great idea. I would consider this a prerequisite for |