Solr
  1. Solr
  2. SOLR-130

[Patch] [Docu] Starting a mySolr document, which tries to explain how to setup a custom solr instance

    Details

    • Type: Task Task
    • Status: Closed
    • Priority: Major Major
    • Resolution: Fixed
    • Affects Version/s: None
    • Fix Version/s: None
    • Component/s: documentation
    • Labels:
      None

      Description

      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.

      1. SOLR-130.diff
        9 kB
        Thorsten Scherler

        Activity

        Thorsten Scherler created issue -
        Hide
        Thorsten Scherler added a comment -

        Initial version

        Show
        Thorsten Scherler added a comment - Initial version
        Thorsten Scherler made changes -
        Field Original Value New Value
        Attachment SOLR-130.diff [ 12350040 ]
        Hide
        Antonio Eggberg added a comment -

        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!

        Show
        Antonio Eggberg added a comment - 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!
        Hoss Man made changes -
        Component/s documentation [ 12311610 ]
        Hide
        Yonik Seeley added a comment -

        Perhaps this should be a Wiki page to make it easier to change / collaborate?

        Show
        Yonik Seeley added a comment - Perhaps this should be a Wiki page to make it easier to change / collaborate?
        Hide
        Thorsten Scherler added a comment -

        done: http://wiki.apache.org/solr/mySolr

        @Antonio, thx for the feedback, I added your comment into the wiki page.

        Show
        Thorsten Scherler added a comment - done: http://wiki.apache.org/solr/mySolr @Antonio, thx for the feedback, I added your comment into the wiki page.
        Hide
        Yonik Seeley added a comment -

        Thanks Thorsten, I've been meaning to write a step-by-step guide on how to get up and running with your own data.

        Show
        Yonik Seeley added a comment - Thanks Thorsten, I've been meaning to write a step-by-step guide on how to get up and running with your own data.
        Hide
        Yonik Seeley added a comment -

        closing.

        Show
        Yonik Seeley added a comment - closing.
        Yonik Seeley made changes -
        Status Open [ 1 ] Closed [ 6 ]
        Resolution Fixed [ 1 ]

          People

          • Assignee:
            Unassigned
            Reporter:
            Thorsten Scherler
          • Votes:
            0 Vote for this issue
            Watchers:
            0 Start watching this issue

            Dates

            • Created:
              Updated:
              Resolved:

              Development