You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@community.apache.org by "Isabel Drost-Fromm (JIRA)" <ji...@apache.org> on 2018/01/24 08:57:00 UTC

[jira] [Closed] (COMDEV-191) Add HTrace distributed tracing for s3 and other alternative Hadoop FS implementations

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

Isabel Drost-Fromm closed COMDEV-191.
-------------------------------------
    Resolution: Won't Fix

Hasn't been touched in years. Please reopen if still needed

> Add HTrace distributed tracing for s3 and other alternative Hadoop FS implementations
> -------------------------------------------------------------------------------------
>
>                 Key: COMDEV-191
>                 URL: https://issues.apache.org/jira/browse/COMDEV-191
>             Project: Community Development
>          Issue Type: New Feature
>            Reporter: Colin P. McCabe
>            Priority: Major
>              Labels: gsoc, gsoc2016, mentor
>
> The Apache HTrace distributed tracing framework allows developers and system administrators to get an end-to-end view of system performance, in a manner similar to XTrace or Dapper.  See http://htrace.incubator.apache.org/
> s3, GCS, WASB, and other cloud blob stores are becoming increasingly important in Hadoop.  But we don't have distributed tracing for these yet.  It would be interesting to add distributed tracing here.  It would enable collecting really interesting data like probability distributions of PUT and GET requests to s3 and their impact on MR jobs, etc.  We should add HTrace distributed tracing for s3 and other alternative Hadoop FS implementations.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@community.apache.org
For additional commands, e-mail: dev-help@community.apache.org