lucene-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Cassandra Targett (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (SOLR-10306) Document vm.swappiness and mlockall in RefGuide
Date Thu, 19 Oct 2017 21:10:00 GMT

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

Cassandra Targett commented on SOLR-10306:
------------------------------------------

As of 7.1 there is now a "Deployment and Operations" section - this type of content would
fit very well there.

> Document vm.swappiness and mlockall in RefGuide
> -----------------------------------------------
>
>                 Key: SOLR-10306
>                 URL: https://issues.apache.org/jira/browse/SOLR-10306
>             Project: Solr
>          Issue Type: Task
>      Security Level: Public(Default Security Level. Issues are Public) 
>          Components: documentation
>            Reporter: Jan H√łydahl
>            Priority: Minor
>
> 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
(v6.4.14#64029)

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


Mime
View raw message