(Republishing, or using this info in a commercial product/website, is prohibited without permission. All other uses are permitted. If in doubt, please ask.)
This wait is when a thread that is participating in a full-text master merge is waiting for other threads to complete. A master merge is when an ALTER FULLTEXT CATALOG … REORGANIZE is performed to merge smaller full-text indexes into one large index (done periodically to increase performance and reduce memory and disk space).
(Books Online description: “Full-text is waiting on master merge operation. Documented for informational purposes only. Not supported. Future compatibility is not guaranteed.”)
Questions/comments on this wait type? Click here to send Paul an email, especially if you have any information to add to this topic.
Added in SQL Server version:
Removed in SQL Server version:
Extended Events wait_type value:
The map_key value in sys.dm_xe_map_values is 589 in 2008 and 2008 R2, 639 in 2012, and 655 in 2014 RTM. After 2014 RTM, you must check the DMV to get the latest value as some map_key values have changed in later builds.
I have not seen this wait be a noticeable contention point.
However, there is a known issue that can result in this wait type and failed master merges if many indexing and reorganize operations are run concurrently – see here for more details. A good workaround is to stagger the indexing and reorganize operations.
Known occurrences in SQL Server (list number matches call stack list):
- Waiting for other threads to complete during a master merge.
Abbreviated call stacks (list number matches known occurrences list):