-
Type: Bug
-
Resolution: Unresolved
-
Priority: Minor - P4
-
None
-
Affects Version/s: 3.4.7
-
Component/s: mongostat
-
None
-
Environment:Ubuntu 14.04.5 LTS (GNU/Linux 4.4.0-93-generic x86_64)
-
1,876
-
Needed
-
Need to explain that when querying multiple hosts, due to asynchronous timing issues, some reports may show 'no data' messages (or apparently omit messages) if stats data wasn't received by the time mongostat was scheduled to show results.
Running mongostat across two clusters will frequently produce "no data received" error.
- is duplicated by
-
TOOLS-2681 [replica set][mongostat] "no data received" error when using --discover
- Closed