[
https://issues.apache.org/jira/browse/SOLR-9560?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16083393#comment-16083393
]
Shalin Shekhar Mangar commented on SOLR-9560:
---------------------------------------------
Thanks Rohit. I think a better way to implement something like this would be to
call a Java executable class which can do comparisons and print out warnings.
It has two advantages:
# We don't need to do the implementation twice (once for bin/solr, again for
bin/solr.cmd)
# There are certain things we can do in a standard way in Java such as finding
free disk space
# Later that class can be used by a running Solr instance to expose violations
via API -- perhaps the Metrics API is apt here.
Also I think you can get most of these interesting values via JMX but if not,
it is easy to pass the values from the script to the java class.
> 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
> Labels: newdev
> Fix For: 7.0, 6.7
>
> Attachments: SOLR-9560.patch
>
>
> 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.4.14#64029)
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org
For additional commands, e-mail: dev-h...@lucene.apache.org
