[SERVER-34660] mongostat shard discovery test fails on 3.7 nightlies Created: 24/Apr/18 Updated: 27/Oct/23 Resolved: 18/May/18 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Sharding |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | David Golden | Assignee: | David Golden |
| Resolution: | Works as Designed | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||||||
| Operating System: | ALL | ||||||||||||
| Participants: | |||||||||||||
| Description |
|
mongostat has a js test called stat_discover_shard.js that has been passing on 3.6 and failing on 3.7 nightlies. Here is an example build with a failure: https://evergreen.mongodb.com/task/mongo_tools_ubuntu1404_qa_tests_unstable_b4547e48d74081c6ed3b607b9ea5e6acdb7b00cf_18_04_13_15_47_28 The symptom seems to be that the test is expecting mongostat to discover 3 shards and it only discovers 2 shards in the allowed timeframe. mongostat does discovery by querying config.shards I suspect that another test, stat_mixed_storage_engine.js is experiencing the same issue, as it also does a discovery test. |
| Comments |
| Comment by David Golden [ 18/May/18 ] |
|
Looks like the ShardingTest fixture output changed format and the tools tests were looking for the ports in old place. We'll add version-specific inspection of the ShardingTest fixture on the tools side. |
| Comment by Misha Tyulenev [ 17/May/18 ] |
|
david.golden The query seems to return the correct number of shards. Its 2 shards in the test: https://github.com/mongodb/mongo-tools/blob/master/test/qa-tests/jstests/stat/stat_discover_shard.js#L4 and the query returns correct nResults: [https://logkeeper.mongodb.org/lobster/build/75821a5c146b5577b02bde5b35b43686/test/5ad0d711f84ae83c3d490830?bookmarks=1641
|