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

ASF GitHub Bot commented on IGNITE-2650:
----------------------------------------

GitHub user ruskim opened a pull request:

    https://github.com/apache/ignite/pull/502

    fix IGNITE-2650

    - Added checkClient to to IgniteSpiConsistencyChecked annotation with 
default value true.
    If it's false, than spi consistency will not be checked for client nodes.
    
    - Added IgniteSpiConsistencyChecked to NoopSwapSpaceSpi and 
FileSwapSpaceSpi. That guaranties, that all nodes in grid will have the same 
swap space provider. Client nodes ignore this check, because clients don't have 
any data.
    
    - Cache with swap creation will fail, if nodes in grid have 
NoopSwapSpaceSpi 

You can merge this pull request into a Git repository by running:

    $ git pull https://github.com/ruskim/ignite ignite-2650

Alternatively you can review and apply these changes as the patch at:

    https://github.com/apache/ignite/pull/502.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

    This closes #502
    
----
commit 4b7996ad92d452ecd0ff11e1181754e712009da0
Author: ruskim <[email protected]>
Date:   2016-02-19T12:26:37Z

    fix IGNITE-2650

----


> Ignite should throw an exception on start of dynamic cache with swap if 
> Ignite uses NoopSwapSpaceSpi
> ----------------------------------------------------------------------------------------------------
>
>                 Key: IGNITE-2650
>                 URL: https://issues.apache.org/jira/browse/IGNITE-2650
>             Project: Ignite
>          Issue Type: Bug
>            Reporter: Artem Shutak
>            Assignee: Konstantin Margorin
>              Labels: newbie
>             Fix For: 1.6
>
>
> Ignite should throw an exception on start of dynamic cache with enabled swap 
> if Ignite uses NoopSwapSpaceSpi.



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

Reply via email to