Uploaded image for project: 'the GGUS shopping list '
  1. the GGUS shopping list
  2. GGUS-1299

GGUS search engine - Handle queries that return a very large number of results

    XMLWordPrintable

    Details

    • Type: Task
    • Status: Closed
    • Priority: Critical
    • Resolution: Fixed
    • Affects Version/s: None
    • Fix Version/s: September 2014
    • Component/s: None
    • Labels:
      None

      Description

      Question:
      Is there any correlation between this symptom today and the scheduled KIT network intervention of Sat 26/7 given that the queries, via SOAP at least, were working last week?

      Helmut's diagnosis and suggestion:

      "With the queries at "any time" a huge amount of data is being collected. This leads to a memory allocation error.
      For the web interface it is not good that the user receives a white page.
      Not yet clear if it makes sense to increase the memory limits but in any case we will improve the error handling."

      Full symptoms' report by Maria Alandes:
      1. Web interface: On the prod instance the following queries fail (they work
      fine in the test instance):

      • List all solved tickets for any period of time
      • List all closed tickets for any period of time
      • List all verified tickets for any period of time

      2. SOAP interface: basic tests where it fails:

      SOAP interface for both test and production instances:

      • List all open tickets for any period of time with Description including
        keyword "Rod"

      SOAP interface for both production instances (it works well for test instance):

      • List all open tickets for any period of time with Description including
        keyword "test"

      And some tests with queries I´m really interested in:

      SOAP interface for both production and test instances:

      • List all open tickets for any period of time with keyword "CVMFS"

      I check an existing ticket that is open with keyword "CVMFS" and I query
      specifically, for an open ticket to that site with that keyword, and the SOAP
      prod instance fails to give me back the ticket when it actually exists.

      In the SOAP interface I´m using this filter in python:

      params.Qualification = "'GHD_Affected Site'=\"%s\" AND \
      'GHD_Short Description'LIKE\"%s\" AND \
      'GHD_Meta
      Status'=\"Open\"" % (site_name,
      description)

      result = client.service.TicketGetList(params.Qualification)

      This used to work fine before Friday and now returns error 500.

      Why schedule a network intervention on a SATURDAY?!

      Thanks
      Maria

        Attachments

          Activity

            People

            Assignee:
            hdres Helmut Dres (Inactive)
            Reporter:
            dimou Maria Dimou
            Watchers:
            Helmut Dres (Inactive), Maria Alandes Pradillo, Maria Dimou
            Votes:
            0 Vote for this issue
            Watchers:
            3 Start watching this issue

              Dates

              Due:
              Created:
              Updated:
              Resolved: