ignite-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Pavel Tupitsyn (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (IGNITE-5717) MemoryPolicy configuration and documentation improvements
Date Fri, 22 Sep 2017 12:11:00 GMT

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

Pavel Tupitsyn commented on IGNITE-5717:
----------------------------------------

{{MaxSize}} changed from 80% to 20% as part of IGNITE-5884.
.NET tests cleaned up as part of IGNITE-6486.

> MemoryPolicy configuration and documentation improvements
> ---------------------------------------------------------
>
>                 Key: IGNITE-5717
>                 URL: https://issues.apache.org/jira/browse/IGNITE-5717
>             Project: Ignite
>          Issue Type: Bug
>    Affects Versions: 2.0
>            Reporter: Sergey Chugunov
>            Priority: Critical
>              Labels: MakeTeamcityGreenAgain
>             Fix For: 2.3
>
>
> After introducing MemoryPolicy concept and related settings to Ignite there were several
cases when users run into problems with default configuration.
> It seems that approach with allocating 80% of available physical memory causes confusion
among users sitting on 32bit systems including versions of JMV (example [1]) and also hurts
stability of TeamCity.
> We need to rethink these settings and make them easier to use.
> Also it turned out that memory allocation process differs in cases of PDS on and off;
it must be properly documented.
> [1] http://apache-ignite-users.70518.x6.nabble.com/Ignite2-0-memory-policy-limit-td12840.html



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

Mime
View raw message