[
https://issues.apache.org/jira/browse/HDFS-11130?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16450539#comment-16450539
]
Hudson commented on HDFS-11130:
-------------------------------
SUCCESS: Integrated in Jenkins build Hadoop-trunk-Commit #14057 (See
[https://builds.apache.org/job/Hadoop-trunk-Commit/14057/])
HDFS-11130. Block Storage : Add storage client to server protocol. (aengineer:
rev 23eba154094b383ed9a9be1b293f318788bdfecc)
* (edit) hadoop-hdfs-project/hadoop-hdfs/pom.xml
* (add)
hadoop-hdfs-project/hadoop-hdfs/src/main/proto/CBlockClientServerProtocol.proto
> Block Storage : add storage client to server protocol
> -----------------------------------------------------
>
> Key: HDFS-11130
> URL: https://issues.apache.org/jira/browse/HDFS-11130
> Project: Hadoop HDFS
> Issue Type: Sub-task
> Components: hdfs
> Reporter: Chen Liang
> Assignee: Chen Liang
> Priority: Major
> Attachments: HDFS-11130-HDFS-7240.001.patch,
> HDFS-11130-HDFS-7240.002.patch
>
>
> This JIRA adds the protocol between block storage client side and server
> side. For now, the only operation is mount volume. More specifically, when
> user mount a volume on client side, client checks with server to verify
> whether it is a valid volume to mount. On valid mount request, server will
> also piggyback meta information about the volume back to client.
> Note that the actual read/write on the volume will never go through server,
> as long as volume is mounted on client, it is all client's job to communicate
> with the underly storage layer (SCM in this case)
--
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
