[
https://issues.apache.org/jira/browse/HDDS-2070?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Marton Elek updated HDDS-2070:
------------------------------
Description:
Wit the first implementation of ozone insight tool we had a demo insight-point
to debug Ratis pipelines. It was not stable enough to include in the first
patch, this patch is about fixing it.
The goal is to implement a new insight point (eg. datanode.pipeline) which can
show information about one pipeline.
It can be done with retrieving the hosts of the pipeline and generate the
loggers metrics (InsightPoint.getRelatedLoggers and InsightPoint.getMetrics)
based on the pipeline information (same loggers should be displayed from all
the three datanodes.
The pipeline id can be defined as a filter parameter which (in this case)
should be required.
was:
During the first demo of ozone insight tool we had a demo insight point to
debug Ratis pipelines. It was not stable enough to include in the first patch
but here we can add it.
The goal is to implement a new insight point (eg. datanode.pipeline) which can
show information about one pipeline.
It can be done with retrieving the hosts of the pipeline and generate the
loggers metrics (InsightPoint.getRelatedLoggers and InsightPoint.getMetrics)
based on the pipeline information (same loggers should be displayed from all
the three datanodes.
The pipeline id can be defined as a filter parameter which (in this case)
should be required.
> Create insight point to debug one specific pipeline
> ---------------------------------------------------
>
> Key: HDDS-2070
> URL: https://issues.apache.org/jira/browse/HDDS-2070
> Project: Hadoop Distributed Data Store
> Issue Type: Sub-task
> Reporter: Marton Elek
> Assignee: Marton Elek
> Priority: Major
> Labels: pull-request-available
> Time Spent: 20m
> Remaining Estimate: 0h
>
> Wit the first implementation of ozone insight tool we had a demo
> insight-point to debug Ratis pipelines. It was not stable enough to include
> in the first patch, this patch is about fixing it.
> The goal is to implement a new insight point (eg. datanode.pipeline) which
> can show information about one pipeline.
> It can be done with retrieving the hosts of the pipeline and generate the
> loggers metrics (InsightPoint.getRelatedLoggers and InsightPoint.getMetrics)
> based on the pipeline information (same loggers should be displayed from all
> the three datanodes.
> The pipeline id can be defined as a filter parameter which (in this case)
> should be required.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
---------------------------------------------------------------------
To unsubscribe, e-mail: ozone-issues-unsubscr...@hadoop.apache.org
For additional commands, e-mail: ozone-issues-h...@hadoop.apache.org
