community-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Aaron Fabbri (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (COMDEV-191) Add HTrace distributed tracing for s3 and other alternative Hadoop FS implementations
Date Sat, 19 Mar 2016 00:56:33 GMT

    [ https://issues.apache.org/jira/browse/COMDEV-191?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15202433#comment-15202433
] 

Aaron Fabbri commented on COMDEV-191:
-------------------------------------

+1  This would be pretty cool.  Would love to see, eventually, latency histograms of the major
cloud storage implementations.

> 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 Patrick McCabe
>              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
(v6.3.4#6332)

Mime
View raw message