[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: PNG File compass-performance-tab-data-unavailable.png     Text File compass_61bc80edd033558418a39600_log.txt    
Story Points: 3

 Description   

Problem Statement/Rationale

In compass, I can't see the labels "hottest collections" and "slowest operations" of the tab performance.

Steps to Reproduce

I am not sure. It doesn't work for me. It says "DATA UNAVAILABLE" instead of the 2 informations.

Expected Results

To see the 2 informations

Actual Results

"DATA UNAVAILABLE"

Additional Notes

In compass, I can't see the labels "hottest collections" and "slowest operations" of the tab performance. What can cause this? Is it an expected behaviour?

I am running compass on windows 10 64 bits with mongodb community server. It happens even if i connect with a user with root privilege. I have set up mongodb tools in the windows system path. It happens on a sharded cluster as well as on a standalone mongod. I happens if i connect to a localhost database, as well if i connect online to a debian mongodb cluster. To make it short, i can never make it work.



 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 "
inprog". So i withdraw this half of my request.
Thanks.

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)?

Generated at Wed Feb 07 22:39:20 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.