Mailing-List: contact dev-help@gearpump.incubator.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@gearpump.incubator.apache.org
Date: Wed, 4 May 2016 12:36:12 +0000 (UTC)
From: "Manu Zhang (JIRA)" <jira@apache.org>
To: dev@gearpump.incubator.apache.org
Message-ID: <JIRA.12960215.1461127135000.107639.1462365372861@Atlassian.JIRA>
In-Reply-To: <JIRA.12960215.1461127135000@Atlassian.JIRA>
References: <JIRA.12960215.1461127135000@Atlassian.JIRA> <JIRA.12960215.1461127135259@arcas>
Subject: [jira] [Updated] (GEARPUMP-47) display task location on dashboard
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit
archived-at: Wed, 04 May 2016 12:36:19 -0000


     [ https://issues.apache.org/jira/browse/GEARPUMP-47?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Manu Zhang updated GEARPUMP-47:
-------------------------------
    Description: 
moved from [https://github.com/gearpump/gearpump/issues/1987]. The usage is to trace the problems of abnormal tasks (e.g. exceptions, low throughput, high latency) to its containing executors (e.g. wrong configuration) and running machines (e.g. bad network). 

It's impractical to return the mapping of executor to task list in processor summary. A better idea is to add a rest call which returns the executor for a task on user demand (e.g. click a display location button)


  was:
moved from [https://github.com/gearpump/gearpump/issues/1987]. We already have task lists in the "ExecutorSummary" and executor location is available. It won't be hard to display task location on dashboard. That will help users to locate task logs on exceptions. 

{code}
  case class ExecutorSummary(
    id: Int,
    workerId: Int,
    actorPath: String,
    logFile: String,
    status: String,
    taskCount: Int,
    tasks: Map[ProcessorId, List[TaskId]],
    jvmName: String
  )
{code}


> display task location on dashboard
> ----------------------------------
>
>                 Key: GEARPUMP-47
>                 URL: https://issues.apache.org/jira/browse/GEARPUMP-47
>             Project: Apache Gearpump
>          Issue Type: Improvement
>          Components: Dashboard
>            Reporter: Manu Zhang
>            Assignee: Manu Zhang
>            Priority: Minor
>
> moved from [https://github.com/gearpump/gearpump/issues/1987]. The usage is to trace the problems of abnormal tasks (e.g. exceptions, low throughput, high latency) to its containing executors (e.g. wrong configuration) and running machines (e.g. bad network). 
> It's impractical to return the mapping of executor to task list in processor summary. A better idea is to add a rest call which returns the executor for a task on user demand (e.g. click a display location button)


--
This message was sent by Atlassian JIRA
(v6.3.4#6332)