You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@ignite.apache.org by "Ivan Veselovsky (JIRA)" <ji...@apache.org> on 2016/12/06 12:53:59 UTC
[jira] [Commented] (IGNITE-4374) Ignite should validate JVM and OS
configuration and output warning in log
[ https://issues.apache.org/jira/browse/IGNITE-4374?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15725410#comment-15725410 ]
Ivan Veselovsky commented on IGNITE-4374:
-----------------------------------------
- GC logging (in particular, PrintGCDetails and PrintGCApplicationStoppedTime) may flood the process output a lot;
- MaxDirectMemorySize does not limit Unsafe memory allocations, as far as I know;
> Ignite should validate JVM and OS configuration and output warning in log
> -------------------------------------------------------------------------
>
> Key: IGNITE-4374
> URL: https://issues.apache.org/jira/browse/IGNITE-4374
> Project: Ignite
> Issue Type: Improvement
> Reporter: Yakov Zhdanov
>
> Currently we have GridPerformanceSuggestions that output suggestions to logs on Ignite start on how Ignite can be improved.
> I suggest to go a little bit deeper and validate more configuration options and add validation for JVM and OS settings.
> Ignite should output warning if:
> * GC logging is not enabled
> * MaxDirectMemorySize is not set (-XX:MaxDirectMemorySize)
> * Heap size is greater than 30,5G and JVM cannot use compressed oops
> * Any of the recommended OS setting described here https://apacheignite.readme.io/docs/jvm-and-system-tuning are not properly set
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)