Last modified: 2014-05-19 18:11:43 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 T63920, the corresponding Phabricator task for complete and up-to-date bug report information.
Bug 61920 - MergeMappingException[Merge failed with failures {[mapper [text_bytes] has different index values]}]
MergeMappingException[Merge failed with failures {[mapper [text_bytes] has di...
Status: NEW
Product: MediaWiki extensions
Classification: Unclassified
CirrusSearch (Other open bugs)
master
All All
: Low normal (vote)
: ---
Assigned To: Nobody - You can work on this!
:
Depends on:
Blocks:
  Show dependency treegraph
 
Reported: 2014-02-25 18:23 UTC by Max Semenik
Modified: 2014-05-19 18:11 UTC (History)
3 users (show)

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


Attachments

Description Max Semenik 2014-02-25 18:23:26 UTC
Repro:
* Create index
* Install GeoData with https://gerrit.wikimedia.org/r/115413
* Set $wgGeoDataUseCirrusSearch = true;
* Try updating the index:

$ php updateSearchIndexConfig.php --closeOk
content index...
        Infering index identifier...wiki_content_first
        Index exists so validating...
                Validating number of shards...ok
                Validating number of replicas...ok
        Validating analyzers...different...corrected
        Validating mappings...
                Validating mapping for page type...different...failed!
Couldn't update mappings.  Here is elasticsearch's error message: MergeMappingException[Merge failed with failures {[mapper [text_bytes] has different index values]}]
Comment 1 Nik Everett 2014-02-25 18:50:28 UTC
Depending on the circumstances this is either expected behavior or a bug.  If you haven't pulled new Cirrus code then this is likely a bug.  Then it is likely caused by an update to the mapping for text_bytes and you can't --closeOk.  You'll need to --reindexAndRemoveOk --indexIdentifier now.

Or you are trying to use Elasticsearch 1.0 which we don't yet support.  I'm working on that now.
Comment 2 Chad H. 2014-05-19 18:11:43 UTC
I hit this last week in production. --reindexAndRemoveOk --indexIdentifier now worked around it, but a more graceful failure would be nice.

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


Navigation
Links