Last modified: 2013-02-16 17:30:24 UTC

Wikimedia Bugzilla is closed!

Wikimedia migrated from Bugzilla to Phabricator. Bug reports are handled in Wikimedia Phabricator.
This static website is read-only and for historical purposes. It is not possible to log in and except for displaying bug reports and their history, links might be broken. See T45920, the corresponding Phabricator task for complete and up-to-date bug report information.
Bug 43920 - Frequent search timeouts at Commons returning no results
Frequent search timeouts at Commons returning no results
Status: RESOLVED DUPLICATE of bug 42423
Product: Wikimedia
Classification: Unclassified
lucene-search-2 (Other open bugs)
unspecified
All All
: Normal normal (vote)
: ---
Assigned To: Nobody - You can work on this!
https://commons.wikimedia.org/w/index...
:
Depends on:
Blocks:
  Show dependency treegraph
 
Reported: 2013-01-13 13:59 UTC by Maarten Dammers
Modified: 2013-02-16 17:30 UTC (History)
5 users (show)

See Also:
Web browser: ---
Mobile Platform: ---
Assignee Huggle Beta Tester: ---


Attachments

Description Maarten Dammers 2013-01-13 13:59:38 UTC
I'm categorizing a lot of images and for this I use the search engine at Commons. At some point I noticed the search sometimes took a while and than returned "There were no results matching the query.". After one or more reloads of the page, the search would return the expected results.

I see two things here:
1. A timeout problem. Is the Wikimedia search backend overloaded?
2. Incorrect handling of timeouts. If a timeout occurs, the search interface should mention that and not throw "There were no results matching the query."
Comment 1 Aude 2013-02-16 13:12:20 UTC

*** This bug has been marked as a duplicate of bug 45073 ***
Comment 2 Maarten Dammers 2013-02-16 13:20:05 UTC
This is not a duplicate. This is a bug report for the behavior before the whole search farm seems to have imploded. If some would have bothered to look into this it would have deteriorated into a complete search outage.
Comment 3 Nemo 2013-02-16 13:25:42 UTC
(In reply to comment #2)
> This is not a duplicate. This is a bug report for the behavior before the
> whole
> search farm seems to have imploded. 

Yes, it's definitely not the same bug.

> If some would have bothered to look into
> this it would have deteriorated into a complete search outage.

Are you sure? It looks like a duplicate of bug 42423.
Comment 4 Nemo 2013-02-16 13:26:08 UTC

*** This bug has been marked as a duplicate of bug 42423 ***

Note You need to log in before you can comment on or make changes to this bug.


Navigation
Links