[jira] [Updated] (IGNITE-679) shmem communication does not work if Ignite node and Hadoop client running on behalf of different users

["Ivan Veselovsky (JIRA)" <ji...@apache.org>]

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

Ivan Veselovsky updated IGNITE-679:
-----------------------------------
    Attachment: IGNITE-679--a.patch

> shmem communication does not work if Ignite node and Hadoop client running on behalf of different users
> -------------------------------------------------------------------------------------------------------
>
>                 Key: IGNITE-679
>                 URL: https://issues.apache.org/jira/browse/IGNITE-679
>             Project: Ignite
>          Issue Type: Bug
>          Components: hadoop
>    Affects Versions: sprint-3
>            Reporter: Ivan Veselovsky
>            Assignee: Ivan Veselovsky
>             Fix For: sprint-3
>
>         Attachments: IGNITE-679--a.patch
>
>
> problem is that shmem native library loader uses global file lock /tmp/igniteshmem.lock . Upon Ignite node start this lock is created by the Ignite service user ("ignite"). When client starts, it tries to get "rws" lock on this file, but fails because that file is typically not writable for the client user. This permanently prevents the client from loading the native shmem library, and, ans a consequence, shmem communication from working.



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