Changes between Initial Version and Version 4 of Ticket #1154


Ignore:
Timestamp:
08/24/11 09:32:05 (3 years ago)
Author:
johnglover
Comment:

Looking at the changeset, it now does a connection check at start-up of CKAN. If it fails then CKAN runs but doesn't show any packages, apart from via the Tags interface, and the search page and widget on the front-page are removed. (BTW Is this a useful thing to do? Without search, perhaps CKAN should simply not start?)

When discussing the ticket we agreed that we should allow ckan to start without search. It is possible that people simply want to list/view information without searching for it and we decided not to prevent them from doing so.

I believe the problem pudo is referring to is temporary periods when the SOLR server is slow/overloaded/down. During this time pudo and I get exception emails saying connection failed for request.

Ok, other options then:

  • if an error occurs during search, return 0 results
  • if an error occurs during search, redirect to a generic 'search is unavailable' page
  • if an error occurs during search, retry the query a certain number of times before giving up and doing one of the above.

What do you suggest?

Legend:

Unmodified
Added
Removed
Modified

  • Ticket #1154

    • Property Status changed from new to reopened
    • Property Cc sebbacon removed
    • Property Priority changed from awaiting triage to major
    • Property Owner set to johnglover
    • Property Milestone changed from to ckan-current-sprint
    • Property Keywords search added

  • Ticket #1154 – Description

    initial v4  
    11According to pudo, a ckan with activated solr extension throws a 5xx when solr is unreachable. Instead, it should behave more like a ckan without ckanext-solr when this happens. 
     2