• Icon: Epic Epic
    • Resolution: Unresolved
    • Icon: Major Major
    • None
    • None
    • System
    • Sphinx indexing issues
    • False
    • False
    • Not Started
    • Not Started
    • Not Started
    • Not Started
    • Not Started
    • Not Started
    • To Do
    • 10% To Do, 0% In Progress, 90% Done

      Sphinx indexing issues

      Some possible issues with sphinx searching that could apply to indexing issues.

      1)
      config/thinkingsphinx.yml contains the default sphinx configuration.
      thinkingsphinx (v5.3) is the client.
      charset_table defines what characters we accept
      min_infix_len defines minimum word-length that will be indexed

      custom configuration, found in app/indices/account_index.rb, overrides the default configuration.

      2)
      asynchronous indexing

      see index_account, SphinxIndexationWorker.perform_later(self) unless master?
      After save, we enqueue the indexation to sideqik jobs

      Sideqik could thus be the source of sphinx issues. For example, it could be that sideqik was down, or there was an error in sideqik, or the job wasn't finished, etc.

      3)
      If there is another problem not covered by the previous two points, we need to check sphinx configuration documentation for the relevant version of sphinx server.

      If sideqik is the source of the issue, this is not a blocker for the customer. For QE, yes?
      Note: we should have something for QE so they can process all the jobs at once for testing purposes - some method to use in their tests so that we/they can be sure that the problem is not sideqik.

      See also other open sphinx issues

              Unassigned Unassigned
              cbartlet Catherine Bartlett
              Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

                Created:
                Updated: