Generate Text Index on CMDB_CI and CMDB_CI_PRINTER

[rebecca75]

I've triggered the 'Generate Text Index' on cmdb_ci and cmdb_ci_printer tables to fulfill a request to have the ability to 'for text' search on these tables. I have two questions, one I did not receive the text index complete email (outbox in our STAGE env.). Second, is there any performance impacts kicking off the 'Generate Text Index' on these two fields during business hours?

[balaji_charapal · Accepted solution]

Yes, If   you generate the text index it will degrade the performance, its always better to generate text index out of business hours.

[Alex North]

Hi Rebecca,

How long since you kicked off the indexing process? Even though you only configured text_search for cmdb_ci and cmdb_ci_printer tables, the platform will be indexing the whole CMDB (it will index all the child tables of cmdb_ci).

If you go to /sys_trigger_list.do?sysparm_query=nameSTARTSWITHtext%20index, you can see whether the text index events processor is still running.

With regards to performance, it will depend on the size of your CMDB and how busy your instance is. If we trigger a full re-index of tables, we will typically do so at the weekend. This is mainly to minimize the impact of incomplete indexes returning partial search results and confusing the end users. You could also take a look at the system property glide.ts.index.parallelism. For versions (at least) up to Istanbul, this will control the number of threads the platform will kick off to index documents. The higher this value, the faster the indexing will be completed but the more load that will be placed on the database. If you see performance issues while (re-)indexing full tables, consider reducing this value. 8 is the out of box value.

Hopefully this was helpful!

Alex

[rebecca75]

I generated the text indexes on those two tables this past Monday, May 1. However, the email never came through that the indexing was done, but the 'for text' is showing for searching. I'd really like to receive the email when it's finished so that I know, but can't figure out why it's not coming through. Also, I will run it on the weekend then to minimize impact to the customers.

[rebecca75]

One more question, I'm running the following from a background script to extend the u_printer_id field from cmdb_ci_printer table to cmdb_ci table before I run the generate text indexes. Is this sound I should do off hours as well? I'm thinking yes...but just checking.

GlideDBUtil.promoteColumn('cmdb_ci_printer', 'cmdb_ci', 'u_printer_id', true);