#5265 Option to not always commit to solr

v1.0.0
closed
General
Cory Johns
2015-08-20
2012-11-09
No

Pysolr defaults to commit=True for add() and delete(). On a high-traffic allura instance, this can be too many commits and cause maxWarmingSearchers errors. There should be a config option (default True, for development) to control this flag to pysolr.

Then, when not always committing, we need to determine how to make updates take effect quickly enough. SourceForge runs a 5 minute cron which executes the "commit" paster command, which creates a task to do a commit. That may not be enough. We may need to do [#1472] also.

Related

Tickets: #1472

Discussion

  • Dave Brondsema

    Dave Brondsema - 2012-11-16
    • size: --> 2
     
  • Tim Van Steenburgh

    • status: open --> in-progress
    • assigned_to: Tim Van Steenburgh
     
  • Tim Van Steenburgh

    • summary: Option to not always commit to solr --> Option to not always commit to solr - NEEDS INI UPDATE
    • status: in-progress --> code-review
    • qa: Cory Johns
     
  • Tim Van Steenburgh

    forge:tv/5265

    Apply these updates to your production.ini: https://trac.geek.net/trac/siteops/ticket/52559

    To test manually:

    • comment out the commitWithin line in production.ini
    • restart taskd
    • create a new ticket with subject=Foo
    • Observe that subsequent searches for 'Foo' will return no results, since no commits are happening
    • uncomment commitWithin and restart taskd
    • create new ticket with subject=Baz
    • Observe that searches for 'Baz' will return a result within 10 seconds.
     
  • Dave Brondsema

    Dave Brondsema - 2012-11-30
    • labels: --> stability
     
  • Dave Brondsema

    Dave Brondsema - 2012-11-30
    • Milestone: forge-nov-30 --> forge-dec-14
     
  • Cory Johns

    Cory Johns - 2012-12-03
    • summary: Option to not always commit to solr - NEEDS INI UPDATE --> Option to not always commit to solr
    • status: code-review --> closed
     

Log in to post a comment.