Databases
StackOverflow2013
Postsdbo
PORunning Sunspot in production
 

Note that there are some explanatory texts on larger screens.

plurals
  1. PORunning Sunspot in production
    primarykey
    data
    text
    <p>I am running Rails 3.1 in production on Ubuntu 10.4 LTS, and with mongoid. I also install tomcat6 and solr via <a href="https://github.com/sunspot/sunspot/wiki/Configure-Solr-on-Ubuntu%2C-the-quickest-way" rel="nofollow noreferrer">this guide</a>. Everything works great, but I am not sure if I have it configured the best. I disable <code>auto_commit_after_request</code> in my sunspot.yml ask talked about <a href="https://stackoverflow.com/questions/4937314/setup-sunspot-solr-with-rails-in-production-environment">here</a>.</p> <p>I also uncommented the auto-commit section in my solrcongif.xml. It just seems like updates to indexed records take a little longer than updates to non-indexed records. Is there any way I can check to see if auto_commit_after_request is really turned off? </p> <p>Also, when I check the analysis page in solr, models that have been updated appear to be doubled indexed (I can tell because there isn't a lot of data yet). So I have one model with a keyword, but in the index it says there are 3 instances of the word (one for the create and two updates I did on the mondel). Is that normal? It just seems like this would create a bias towards frequently updated models, but also increase the size of the index.</p> <p>Below is my <code>config/sunspot.yml</code> file. If needed I can post the solrconfig.xml too, but it is big so I will leave it out for now. Is there any guide on tuning sunspot for production? Thanks!</p> <pre><code>production: solr: hostname: localhost port: 8080 log_level: WARNING path: '/solr' auto_commit_after_request: false development: solr: hostname: localhost port: 8982 log_level: INFO test: solr: hostname: localhost port: 8981 log_level: WARNING </code></pre>
    singulars
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. PTQuestion
    1. USCommunity
    1. USChris Slade
    plurals
    1. PL
      singulars
      1. LTLinked
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. PO
      singulars
      1. PTAnswer
    1. VO
      singulars
      1. PORunning Sunspot in production
      1. This table or related slice is empty.
      1. VTUpMod
    2. VO
      singulars
      1. PORunning Sunspot in production
      1. This table or related slice is empty.
      1. VTUpMod
    3. VO
      singulars
      1. PORunning Sunspot in production
      1. USFabio
      1. VTFavorite
    1. This table or related slice is empty.
 

Querying!

 
Guidance
A row detail

Detail views are divided into sections. All the information in the data section comes from columns in the selected row. The other sections display data from other, related rows.

Related data can be related in a to-one or a to-many fashion. Captions of data related in a to-many fashion link to a list view showing a filtered view of the table.

Try moving around until you find a non-empty to-many entry and click on the label to get to one. You can move back to the root by clicking on the database name in the header.

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload