[
https://issues.apache.org/jira/browse/IGNITE-679?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14394933#comment-14394933
]
Konstantin Boudnik commented on IGNITE-679:
-------------------------------------------
Looks like a potential fix for multi-tenancy issue and IGNITE-218??
> 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: Vladimir Ozerov
> 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.
> WORKAROUND for old GG/Ignite builds: manually create file
> /tmp/igniteshmem.lock of 0666 permission mode. This will make any user able
> to get "rws" lock on that file.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
