You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@lucene.apache.org by "Jan Høydahl (Jira)" <ji...@apache.org> on 2020/02/13 11:40:00 UTC

[jira] [Assigned] (SOLR-10306) Document vm.swappiness and mlockall in RefGuide

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

Jan Høydahl reassigned SOLR-10306:
----------------------------------

    Assignee: Jan Høydahl

> Document vm.swappiness and mlockall in RefGuide
> -----------------------------------------------
>
>                 Key: SOLR-10306
>                 URL: https://issues.apache.org/jira/browse/SOLR-10306
>             Project: Solr
>          Issue Type: Task
>          Components: documentation
>            Reporter: Jan Høydahl
>            Assignee: Jan Høydahl
>            Priority: Minor
>          Time Spent: 10m
>  Remaining Estimate: 0h
>
> I think we should document sane best practice OS level settings in the ref guide, e.g. in https://cwiki.apache.org/confluence/display/solr/Taking+Solr+to+Production
> Such as lower system swappiness or ability to use mlockall (like this ES page https://www.elastic.co/guide/en/elasticsearch/guide/current/heap-sizing.html)
> I also found this github repo https://github.com/LucidWorks/mlockall-agent - it is old, did anyone have good experience with the agent for locking Solr's memory?



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscribe@lucene.apache.org
For additional commands, e-mail: issues-help@lucene.apache.org