[COMPASS-5374] Compass performance tab - hottest collections - DATA UNAVAILABLE Created: 17/Dec/21 Updated: 09/Aug/22 |
|
| Status: | Open |
| Project: | Compass |
| Component/s: | None |
| Affects Version/s: | 1.29.5 |
| Fix Version/s: | None |
| Type: | Bug | Priority: | Minor - P4 |
| Reporter: | Joel J | Assignee: | Unassigned |
| Resolution: | Unresolved | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Environment: |
Windows 10 64 bits |
||
| Attachments: |
|
| Story Points: | 3 |
| Description |
| Comments |
| Comment by Joel J [ 17/Dec/21 ] |
|
Now that you say it, i've seen such a message, but not everytime. But it doesn't work for a standalone mongod instance neither. It writes the same thing: "DATA UNAVAILABLE". It doesn't work on the individual shards neither, and neither on the config server. I always see "DATA UNAVAILABLE". It has never worked. Does it work for you? On which kind of instance? |
| Comment by Anna Henningsen [ 17/Dec/21 ] |
|
bonjourjoel@gmail.com For this log file specifically, it seems that the cause is that you are running it against a sharded cluster, where it is expected that the command would not work (you should be able to run it against each shard individually, though). I don’t know why it doesn’t show that error for you, it should usually display one on the top of the page (“Top command is not available in mongos”). How does it fail for the standalone mongod instance? |
| Comment by Joel J [ 17/Dec/21 ] |
|
compass_61bc80edd033558418a39600_log.txt
Hi, here is the log. I have a problem with "Hottest collections", even connected with user root. But for "Slowest operations", I found out it's because i had a user without the privilege " |
| Comment by Anna Henningsen [ 17/Dec/21 ] |
|
Hello bonjourjoel@gmail.com! Can you share a log file for these sessions (Help → Open Log File → Extract and open as .txt)? |