[GitHub] ignite pull request #2006: IGNITE-5288: Inconsistency of committed and the m...

[asfgit]

Github user asfgit closed the pull request at:

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


---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

[GitHub] ignite pull request #2006: IGNITE-5288: Inconsistency of committed and the m...

[dspavlov]

GitHub user dspavlov opened a pull request:

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

IGNITE-5288: Inconsistency of committed and the max memory numbers …

…should not cause stopping cluster node

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

$ git pull https://github.com/gridgain/apache-ignite ignite-5288

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

https://github.com/apache/ignite/pull/2006.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 #2006


commit 0fc8c4531a86a6f13a1387a0757d3ecbd5da1e36
Author: dpavlov 
Date:   2017-05-25T12:31:00Z

IGNITE-5288: Inconsistency of committed and the max memory numbers should 
not cause stopping cluster node




---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---