[
https://issues.apache.org/jira/browse/HDFS-10746?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16410443#comment-16410443
]
Hudson commented on HDFS-10746:
-------------------------------
SUCCESS: Integrated in Jenkins build Hadoop-trunk-Commit #13869 (See
[https://builds.apache.org/job/Hadoop-trunk-Commit/13869/])
HDFS-10746: libhdfs++: synchronize access to working_directory and
(james.clampffer: rev b9cf0e932d8a56eadc9c23912590722a5d846dec)
* (edit)
hadoop-hdfs-project/hadoop-hdfs-native-client/src/main/native/libhdfspp/lib/fs/filehandle.h
* (edit)
hadoop-hdfs-project/hadoop-hdfs-native-client/src/main/native/libhdfspp/lib/fs/filehandle.cc
* (edit)
hadoop-hdfs-project/hadoop-hdfs-native-client/src/main/native/libhdfspp/lib/bindings/c/hdfs.cc
> libhdfs++: synchronize access to working_directory and bytes_read_.
> -------------------------------------------------------------------
>
> Key: HDFS-10746
> URL: https://issues.apache.org/jira/browse/HDFS-10746
> Project: Hadoop HDFS
> Issue Type: Sub-task
> Components: hdfs-client
> Reporter: Anatoli Shein
> Assignee: Anatoli Shein
> Priority: Major
> Attachments: HDFS-10746.HDFS-8707.000.patch,
> HDFS-10746.HDFS-8707.001.patch
>
>
> std::string working_directory is located in hdfs.cc and access to it should
> be synchronized with locks.
> uint64_t bytes_read_; is located in filehandle.h and it should be made atomic
> in order to be thread safe when multithreading becomes available.
--
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
