You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@hbase.apache.org by "Ted Yu (JIRA)" <ji...@apache.org> on 2016/11/22 21:30:59 UTC
[jira] [Updated] (HBASE-17064) Add TaskMonitor#getTasks() variant
which accepts type selection
[ https://issues.apache.org/jira/browse/HBASE-17064?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Ted Yu updated HBASE-17064:
---------------------------
Labels: ui (was: )
> Add TaskMonitor#getTasks() variant which accepts type selection
> ---------------------------------------------------------------
>
> Key: HBASE-17064
> URL: https://issues.apache.org/jira/browse/HBASE-17064
> Project: HBase
> Issue Type: Improvement
> Reporter: Ted Yu
> Priority: Minor
> Labels: ui
>
> In TaskMonitorTmpl.jamon :
> {code}
> List<? extends MonitoredTask> tasks = taskMonitor.getTasks();
> Iterator<? extends MonitoredTask> iter = tasks.iterator();
> // apply requested filter
> while (iter.hasNext()) {
> MonitoredTask t = iter.next();
> if (filter.equals("general")) {
> if (t instanceof MonitoredRPCHandler)
> iter.remove();
> {code}
> This means when user refreshes rs-status page, regardless of the type of filter, we always traverse and clone MonitoredTask's.
> getTasks() is synchronized :
> {code}
> public synchronized List<MonitoredTask> getTasks() {
> {code}
> A variant of getTasks() can be added which takes the type of filter so that unnecessary cloning is avoided.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)