hadoop-hdfs-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Istvan Fajth (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HDFS-13403) libhdfs++: Use hdfs::IoService object rather than asio::io_service
Date Sun, 06 May 2018 08:53:00 GMT

    [ https://issues.apache.org/jira/browse/HDFS-13403?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16465026#comment-16465026

Istvan Fajth commented on HDFS-13403:

Hi [~James C],

I am wondering if the build_fixes.patch can be committed to the trunk? As I see it is still
missing, I just ran into it again :)

Thank you in advance!

> libhdfs++: Use hdfs::IoService object rather than asio::io_service
> ------------------------------------------------------------------
>                 Key: HDFS-13403
>                 URL: https://issues.apache.org/jira/browse/HDFS-13403
>             Project: Hadoop HDFS
>          Issue Type: Task
>            Reporter: James Clampffer
>            Assignee: James Clampffer
>            Priority: Critical
>         Attachments: HDFS-13403.000.patch, build_fixes.patch
> At the moment the hdfs::IoService is a simple wrapper over asio's io_service object.
 I'd like to make this smarter and have it do things like track which tasks are queued, validate
that dependencies of tasks exist, and monitor ioservice throughput and contention.  In order
to get there we need to use have all components in the library to go through the hdfs::IoService
rather than directly interacting with the asio::io_service.  The only time the asio::io_service
should be used is when calling things like asio::async_write that need an io_service&.
 HDFS-11884 will be able get rid of those remaining instances once this work is in place.

This message was sent by Atlassian JIRA

To unsubscribe, e-mail: hdfs-issues-unsubscribe@hadoop.apache.org
For additional commands, e-mail: hdfs-issues-help@hadoop.apache.org

View raw message