text_index events backing up due to frequent updates to the install_status field on cmdb (and child) tablesIssue Production instance with a high volume of unprocessed text_index event. Viewing the events list, filtering on Parm1 shows [install_status] and grouping on the table field shows cmdb_ci_patches (or any child of cmdb really) as the overwhelming majority of the unprocessed text index events.CauseThe cmdb field install_status (an integer field) is by default allowed to be text indexed upon update. This field is one of the most frequently updated during daily discovery and being able to use the global search based on this field is of little to no value. ResolutionTo resolve this issue of redundant text indexing on an integer field install_status, simply add the "no_text_index=true" (with no double quotes) to the Attributes field in the dictionary for the cmdb_ci_patches.install_status. Please note that the table could be any child of CMDB upon which Discovery does frequent updates...in your case it may not be cmdb_ci_patches. More detail regarding the use of the no_text_index=true attribute, please see our formal product documentation specific to your current product version. The below link is for Istanbul. https://docs.servicenow.com/csh?topicname=t_RemoveAnIndexForASpecificField.html&version=latest