Skip to main content
Question

Best practices for qlist usage

  • 9 September 2024
  • 2 replies
  • 25 views

Forum|alt.badge.img+1

Hello! 

We want to use qlist command for Commvault jobs monitoring for telegraf. When we are using it from single host - it completed after 1-2 sec. When we are using it at one time from 10 hosts - we are waiting to 15 sec, and after 50 hosts - to 2-3 min. How does Commcerve handle such requests? Multistream or singlestream? 

 

We are usung whish request

qlist jobhistory -c $CLIENT_NAME -a $AGENT_TYPE -st "$d2" -et "$d1" -js Completed -dispJobTimeUnix -tf /etc/telegraf/plugins.d/dbms/pgtf
!--endfragment>

 

2 replies

Hi,

This is not about the single or multistream. It is about user authorization and running queries per each client. Much easier (meaning: more efficient) way would be running one command and parse the results per client, but I suspect this is not the option here, for client centric requests.


Forum|alt.badge.img+7

@bdn 

there is no queue on the server for this command. So the only thing i suspect is server overload when you run it simultaenously from multiple machines

 


Cookie policy

We use cookies to enhance and personalize your experience. If you accept you agree to our full cookie policy. Learn more about our cookies.

 
Cookie settings