[
https://issues.apache.org/jira/browse/SOLR-9560?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15523464#comment-15523464
]
Jan Høydahl commented on SOLR-9560:
-----------------------------------
Perhaps we could have a {{bin/solr start -prod}} switch which turns on a bunch
of best-practice settings, such as enforcing file-handles, requiring 64-bit
Java, disabling stream handler, logging at WARN level, refusing to run as root
user, increasing log4j.appender.file.MaxFileSize, refusing to start with
default SSL/BasicAuth passwords etc... I've seen many misconfigured
prod-systems running OOTB settings :(
> Solr should check max open files and other ulimits and refuse to start if
> they are set too low
> ----------------------------------------------------------------------------------------------
>
> Key: SOLR-9560
> URL: https://issues.apache.org/jira/browse/SOLR-9560
> Project: Solr
> Issue Type: Wish
> Security Level: Public(Default Security Level. Issues are Public)
> Reporter: Shalin Shekhar Mangar
> Fix For: 6.3, master (7.0)
>
>
> Solr should check max open files and other ulimits and refuse to start if
> they are set too low. Specifically:
> # max open files should be at least 32768
> # max memory size and virtual memory should both be unlimited
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org
For additional commands, e-mail: dev-h...@lucene.apache.org
