[
https://issues.apache.org/jira/browse/HDFS-4698?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13640762#comment-13640762
]
Aaron T. Myers commented on HDFS-4698:
--------------------------------------
bq. I think it would not be too difficult to update the stats after every read,
rather than just after close. That will make it a lot more useful, I think.
I think this is a good idea, if only to make the interface more easily
understood. Though not a bug per se, it's a little odd to continue to be
accessing an (Input|Output)Stream after having called close on it.
bq. I think the tl;dr is that we should think about that later.
Makes sense to me. Thanks for thinking about it.
> provide client-side metrics for remote reads, local reads, and short-circuit
> reads
> ----------------------------------------------------------------------------------
>
> Key: HDFS-4698
> URL: https://issues.apache.org/jira/browse/HDFS-4698
> Project: Hadoop HDFS
> Issue Type: Improvement
> Components: hdfs-client
> Affects Versions: 2.0.4-alpha
> Reporter: Colin Patrick McCabe
> Assignee: Colin Patrick McCabe
> Priority: Minor
> Attachments: HDFS-4698.001.patch
>
>
> We should provide metrics to let clients know how many bytes of data they
> have read remotely, versus locally or via short-circuit local reads. This
> will allow clients to know how well they're doing at bringing the computation
> to the data, which will be useful in evaluating placement policies and
> cluster configurations.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
