Github user zd-project commented on the issue:
https://github.com/apache/storm/pull/2754
One thing that is worthy of noticing: Storm UI currently interweaves
different search API regarding searching functionalities and it's kind of
confusing.
Specifically:
1. For the search button at the homepage it uses a single deep search API
to search for all ports (server side process), both archived and non-archived.
2. For non-archived search at a specific topology page, it invokes search
API on each port inside a loop (client side process).
3. For archived search at a specific topology page, it invokes deep search
API (search-archived=on) on each port inside a loop (client side process)
As a result, metrics for these APIs may not accurately reflect how many
searches are invoked from client's perspective.
---
