[
https://issues.apache.org/jira/browse/HDFS-13403?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16466343#comment-16466343
]
Bibin A Chundatt commented on HDFS-13403:
-----------------------------------------
[~James C]
For version gcc 7 native compilation fails
[https://bugzilla.redhat.com/show_bug.cgi?id=1417383]
{code}
For reference, the <future>, <mutex>, and <regex> headers used to include the
whole of <functional> (thousands of lines), but now they don't. This is a Good
Thing™.
I'll make a note of this in the GCC 7 "porting to" doc.
{code}
Seems we have to explicitly include <functional>
> 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
(v7.6.3#76005)
---------------------------------------------------------------------
To unsubscribe, e-mail: hdfs-issues-unsubscr...@hadoop.apache.org
For additional commands, e-mail: hdfs-issues-h...@hadoop.apache.org
