Help Center/ TaurusDB/ FAQs/ Database Usage/ Why Are the Results Inconsistent After the MATCH AGAINST Statement Is Executed, Respectively, on the Primary Node and Read Replicas?
Updated on 2025-03-07 GMT+08:00

Why Are the Results Inconsistent After the MATCH AGAINST Statement Is Executed, Respectively, on the Primary Node and Read Replicas?

MATCH AGAINST is used to search for MySQL full-text indexes. For rows in a table, MATCH returns relevance values, that is, a similarity measure between the search string (given as the argument to AGAINST() and the text in that row in the columns named in the MATCH() list).

The primary node and read replicas use different methods to obtain the stat_n_rows value. The primary node uses the persistent method and read replicas use the transient method. Therefore, the obtained values are slightly different from each other. The execution results of MATCH AGAINST on the primary node and read replicas are different.