Mailing-List: contact issues-help@ignite.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@ignite.apache.org
Date: Fri, 28 Oct 2016 22:22:58 +0000 (UTC)
From: "Denis Magda (JIRA)" <jira@apache.org>
To: issues@ignite.apache.org
Message-ID: <JIRA.13016288.1477693249000.122767.1477693378571@Atlassian.JIRA>
In-Reply-To: <JIRA.13016288.1477693249000@Atlassian.JIRA>
References: <JIRA.13016288.1477693249000@Atlassian.JIRA> <JIRA.13016288.1477693249598@arcas>
Subject: [jira] [Updated] (IGNITE-4152) Make ignite-shmem lib optional
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit
archived-at: Fri, 28 Oct 2016 22:23:00 -0000


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

Denis Magda updated IGNITE-4152:
--------------------------------
    Description: 
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.

  was:
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


> Make ignite-shmem lib optional
> ------------------------------
>
>                 Key: IGNITE-4152
>                 URL: https://issues.apache.org/jira/browse/IGNITE-4152
>             Project: Ignite
>          Issue Type: Bug
>            Reporter: Denis Magda
>             Fix For: 1.8
>
>
> 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.


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