hadoop-hdfs-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Chen Liang (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (HDFS-11582) Block Storage : add SCSI target access daemon
Date Tue, 28 Mar 2017 00:02:41 GMT

     [ https://issues.apache.org/jira/browse/HDFS-11582?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel

Chen Liang updated HDFS-11582:
    Attachment: HDFS-11582-HDFS-7240.003.patch

Thanks [~anu] for the review and the comments! addressed in v003 patch.

bq. who ensures that we don't have race condition that is two volumeNames from 2 different
CBlock servers are not racing here ? I understand that it is a pretty far fetched scenerio
and I was wondering if the jscsi target server does any kind of concurrency control.

This was written to make sure that mounting a volume twice or more would not reset the in-memory
metadata. But just like you mentioned, jscsi code, or even system iscsi might already handled
this scenario. This code is more like doing a safety check without assuming it will be handled.

> Block Storage : add SCSI target access daemon
> ---------------------------------------------
>                 Key: HDFS-11582
>                 URL: https://issues.apache.org/jira/browse/HDFS-11582
>             Project: Hadoop HDFS
>          Issue Type: Sub-task
>          Components: hdfs
>            Reporter: Chen Liang
>            Assignee: Chen Liang
>         Attachments: HDFS-11582-HDFS-7240.001.patch, HDFS-11582-HDFS-7240.002.patch,
> This JIRA adds the daemon process that exposes SCSI target access. More specifically,
with this daemon process running, any OS with SCSI can talk to this daemon process and treat
CBlock volumes as SCSI targets, in this way the user can mount the volume just like the POSIX

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