[
https://issues.apache.org/jira/browse/SOLR-12270?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16453735#comment-16453735
]
Jan Høydahl commented on SOLR-12270:
------------------------------------
In my opinion it would be sufficient to warn in the logs, not on the console.
ES does a neat trick and enables stricter production-grade checks only when it
binds to an external network interface. For Solr the equivalent could perhaps
be to enable such console warnings or refuse to start if {{SOLR_HOST}} variable
is set (i.e. not using default localhost).
> Improve "Your Max Processes.." WARN messages while starting Solr's examples
> ---------------------------------------------------------------------------
>
> Key: SOLR-12270
> URL: https://issues.apache.org/jira/browse/SOLR-12270
> Project: Solr
> Issue Type: Improvement
> Security Level: Public(Default Security Level. Issues are Public)
> Reporter: Varun Thacker
> Priority: Major
>
> If I start Solr 7.3 I am greeted with this very VERBOSE message
>
> {code:java}
> ~/solr-7.3.0$ ./bin/solr start -e cloud -noprompt -z localhost:2181 -m 2g
> *** [WARN] *** Your open file limit is currently 256.
> It should be set to 65000 to avoid operational disruption.
> If you no longer wish to see this warning, set SOLR_ULIMIT_CHECKS to false in
> your profile or solr.in.sh
> *** [WARN] *** Your Max Processes Limit is currently 1418.
> It should be set to 65000 to avoid operational disruption.
> If you no longer wish to see this warning, set SOLR_ULIMIT_CHECKS to false in
> your profile or solr.in.sh
> Welcome to the SolrCloud example!
> Starting up 2 Solr nodes for your example SolrCloud cluster.
> Creating Solr home directory
> /Users/varunthacker/solr-7.3.0/example/cloud/node1/solr
> Cloning /Users/varunthacker/solr-7.3.0/example/cloud/node1 into
> /Users/varunthacker/solr-7.3.0/example/cloud/node2
> Starting up Solr on port 8983 using command:
> "bin/solr" start -cloud -p 8983 -s "example/cloud/node1/solr" -z
> localhost:2181 -m 2g
> *** [WARN] *** Your open file limit is currently 10240.
> It should be set to 65000 to avoid operational disruption.
> If you no longer wish to see this warning, set SOLR_ULIMIT_CHECKS to false in
> your profile or solr.in.sh
> *** [WARN] *** Your Max Processes Limit is currently 1418.
> It should be set to 65000 to avoid operational disruption.
> If you no longer wish to see this warning, set SOLR_ULIMIT_CHECKS to false in
> your profile or solr.in.sh
> Waiting up to 180 seconds to see Solr running on port 8983 [-]
> Started Solr server on port 8983 (pid=82037). Happy searching!
>
> Starting up Solr on port 7574 using command:
> "bin/solr" start -cloud -p 7574 -s "example/cloud/node2/solr" -z
> localhost:2181 -m 2g
> *** [WARN] *** Your open file limit is currently 10240.
> It should be set to 65000 to avoid operational disruption.
> If you no longer wish to see this warning, set SOLR_ULIMIT_CHECKS to false in
> your profile or solr.in.sh
> *** [WARN] *** Your Max Processes Limit is currently 1418.
> It should be set to 65000 to avoid operational disruption.
> If you no longer wish to see this warning, set SOLR_ULIMIT_CHECKS to false in
> your profile or solr.in.sh
> Waiting up to 180 seconds to see Solr running on port 7574 [\]
> Started Solr server on port 7574 (pid=82143). Happy searching!
> INFO - 2018-04-24 16:07:10.566;
> org.apache.solr.client.solrj.impl.ZkClientClusterStateProvider; Cluster at
> localhost:2181 ready
> Created collection 'gettingstarted' with 2 shard(s), 2 replica(s) with
> config-set 'gettingstarted'
> Enabling auto soft-commits with maxTime 3 secs using the Config API
> POSTing request to Config API:
> http://localhost:8983/solr/gettingstarted/config
> {"set-property":{"updateHandler.autoSoftCommit.maxTime":"3000"}}
> Successfully set-property updateHandler.autoSoftCommit.maxTime to 3000
> SolrCloud example running, please visit: http://localhost:8983/solr
> {code}
> Do we really need so many duplicate warnings for the same message?
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
