[
https://issues.apache.org/jira/browse/SOLR-130?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12469121
]
Antonio Eggberg commented on SOLR-130:
--------------------------------------
Wow! you must be reading my mind :-) I can contribute with questions :-) As a
newbie non-java user from an enterprise prospective! I am your idea target :-)
Having said that I like to know about the following:
1. The schema.xml and solrconfig.xml are in parts very well explained. But in
some areas like as an example .. <indexDefaults> and other places there are no
explanation. It would be nice to get more info there. Specifically for example
if increase <mergeFactor> to 1000 what will happen? what are the highest value
for each properties? what is for example a "safe value".
2. It would be nice to create a deployment scenarios i.e a single server
install with XXX CPU and YYY memory just running Solr with AAA thousand docs
how should your config look like and why? and you can get about xxx Query/Sec
or something..
3. It would be nice to have a multi server deployment with some server spec and
then how should the deployment be.
4. It would also be nice to have more info regarding stopwords synonoms etc.
usage and facet etc..
I know that all of the above are case by case cos configuration by default
means case by case. But what I want to propose is a "Guidelines or Best
Practice" based on your production implementation/deployment you have done with
Cocoon. It would be nice to have some real world stories.
I think you should do like the subversion book! - A Solr open source book! :-)
> [Patch] [Docu] Starting a mySolr document, which tries to explain how to
> setup a custom solr instance
> -----------------------------------------------------------------------------------------------------
>
> Key: SOLR-130
> URL: https://issues.apache.org/jira/browse/SOLR-130
> Project: Solr
> Issue Type: Task
> Reporter: Thorsten Scherler
> Attachments: SOLR-130.diff
>
>
> While developing a custom search server based on solr I took some notes about
> the do's and don'ts. The initial patch is not a fully finished document but
> may invite other devs to enhance it.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
