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

Chris Nauroth commented on HDFS-9062:
-------------------------------------

Hi [~James Clampffer].

I'm curious if you've tried to get a setup working by controlling the path in 
configuration with {{dfs.domain.socket.path}} pointed to a more appropriate 
location for your environment, such as /tmp.  On the Java side of things, an 
example of this is {{TestShortCircuitLocalRead}}, which uses helper class 
{{TemporarySocketDirectory}} to grab a temp location and then set that location 
in {{Configuration}} as {{dfs.domain.socket.path}} before booting the 
mini-cluster.

libhdfs takes a similar approach too.  An example is in test_libhdfs_zerocopy.c.

There is also the static method {{DomainSocket#disableBindPathValidation}}, 
which is a method intended only for tests to use for skipping the security 
checks.

Do any of these existing mechanisms help solve the current problem?

> Add a parameter to MiniDFSCluster to turn off security checks on the domain 
> socked path
> ---------------------------------------------------------------------------------------
>
>                 Key: HDFS-9062
>                 URL: https://issues.apache.org/jira/browse/HDFS-9062
>             Project: Hadoop HDFS
>          Issue Type: Sub-task
>          Components: hdfs-client
>            Reporter: James Clampffer
>            Assignee: James Clampffer
>            Priority: Blocker
>
> I'd like to add a command line parameter that allows the permission checks on 
> dfs.domain.socket.path to be turned off.
> Right now a blocker, or at least major inconvenience, for short circuit 
> reader development is getting the domain socket path set up with the correct 
> permissions.  I'm working on shared test machines where messing with things 
> in /var/lib is discouraged.
> This should also make it easier to write tests for short circuit reads once 
> completed.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Reply via email to