You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@ignite.apache.org by "Vladimir Ozerov (JIRA)" <ji...@apache.org> on 2017/07/10 07:58:01 UTC

[jira] [Updated] (IGNITE-4152) Make ignite-shmem lib optional

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

Vladimir Ozerov updated IGNITE-4152:
------------------------------------
    Fix Version/s:     (was: 2.1)
                   2.2

> Make ignite-shmem lib optional
> ------------------------------
>
>                 Key: IGNITE-4152
>                 URL: https://issues.apache.org/jira/browse/IGNITE-4152
>             Project: Ignite
>          Issue Type: Bug
>    Affects Versions: 1.7
>            Reporter: Denis Magda
>            Assignee: Denis Magda
>             Fix For: 2.2
>
>
> Presently, if someone starts up a cluster and has at least two nodes running on a single Unix machine then those nodes will be communicating over the shared memory (shmem) by default.
> This approach sounds absolutely reasonable but the shmem library is not ideal at the moment. There are many situations when a cluster may hang in the production or during long running tests due to some unclear issues in shmem internals. Even from Ignite community side we have the following shmem related issues 
> https://issues.apache.org/jira/browse/IGNITE-1578
> https://issues.apache.org/jira/browse/IGNITE-1294
> Let's make the shmem lib optional by putting it into "{{ignite-release/libs/optional}}" folder and removing any explicit reference we may have in a pom.xml file.
> Refer to this discussion for more details:
> http://apache-ignite-developers.2346864.n4.nabble.com/Making-Ignite-shmem-library-optional-td11874.html



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)