[
https://issues.apache.org/jira/browse/DISPATCH-556?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15732348#comment-15732348
]
Ganesh Murthy commented on DISPATCH-556:
----------------------------------------
Now the "limit" option can be used to limit the number of rows being obtained
by qdstat. The default for the limit is set to 1000 rows, so if you don't
specify limit, you will get back only 1000 rows. If you want more rows, specify
a limit and if qdstat times out use the "timeout" option to increase the
timeout.
For example, if you run -
{noformat}
qdstat -c
{noformat}
Only a maximum of 1000 rows will be returned. If you want 5000 rows run this
{noformat}
qdstat -c --limit 5000
{noformat}
This way the router will not be burdened when there are hundreds of thousands
of connections to be returned by qdstat.
If you want to see only the count of connections, use
{noformat}
qdstat -g
{noformat}
> qdstat fails at high scale
> --------------------------
>
> Key: DISPATCH-556
> URL: https://issues.apache.org/jira/browse/DISPATCH-556
> Project: Qpid Dispatch
> Issue Type: Bug
> Components: Tools
> Affects Versions: 0.7.0
> Reporter: Ted Ross
> Assignee: Ganesh Murthy
> Fix For: 0.8.0
>
>
> qdstat times out waiting for a response when there are very large numbers of
> management entities. It needs a way to provide summary counts and it needs
> to take advantage of pagination for large results.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
