GitHub user bjoernhaeuser opened a pull request: https://github.com/apache/lucene-solr/pull/11
Limit threadpools by default to 128 Integer.MAX_VALUE could kill the VM instead of providing useful error messages. 128 is a wild guess by myself. Let's discuss a good default value for this :) Jira: https://issues.apache.org/jira/browse/SOLR-8727 You can merge this pull request into a Git repository by running: $ git pull https://github.com/rebuy-de/lucene-solr limit-threadpools Alternatively you can review and apply these changes as the patch at: https://github.com/apache/lucene-solr/pull/11.patch To close this pull request, make a commit to your master/trunk branch with (at least) the following in the commit message: This closes #11 ---- commit cff552d1dc4e7bc7892d9521355c651c2ed2ad06 Author: Björn Häuser <b.haeu...@rebuy.de> Date: 2016-02-24T10:44:09Z Limit threadpools by default to 128 Integer.MAX_VALUE could kill the VM instead of providing useful error messages. 128 is a wild guess by myself. Let's discuss a good default value for this :) ---- --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as well. If your project does not have this feature enabled and wishes so, or if the feature is enabled but not working, please contact infrastructure at infrastruct...@apache.org or file a JIRA ticket with INFRA. --- --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org For additional commands, e-mail: dev-h...@lucene.apache.org