Geo Partition analyze DDL error

General
1

Hi,
We have 9 node cluster with 3 nodes in each of the 3 regions. We have created geo partitioned tables, and when we execute analyze for the different tables on different nodes, then we encounter below error. These errors are random.

HINT: Set ‘ysql_beta_features’ yb-tserver gflag to true to suppress the warning for all beta features.
ysqlsh:analyze.sql:1: ERROR: could not serialize access due to concurrent update (query layer retry isn’t possible because data was already sent, if this is the read committed isolation (or) the first statement in repeatable read/ serializable isolation transaction, consider increasing the tserver gflag ysql_output_buffer_size)
DETAIL: Conflict with concurrently committed data. Value write after transaction start: doc ht ({ physical: 1748033399297059 }) >= read time ({ physical: 1748033124473148 }), key: SubDocKey(DocKey(CoTableId=4a1f0000-0000-0180-0030-000001000000, , [16640]), ): kConflict
CONTEXT: Catalog Version Mismatch: A DDL occurred while processing this query. Try again.
ysqlsh:analyze.sql:2: WARNING: ‘analyze’ is a beta feature!

2

Hi @explore_yb

What version are you using?

Were there DDL running at this time? Do you get an error when no DDLs are running?

3

@explore_yb, are you running these different ANALYZE commands concurrently on different nodes? If so, this error is expected. We recommend running DDLs affecting the same database to be run in a serialized manner - here is a docs link that talks about this in more detail.

4

@dorian_yugabyte @sanketh sorry for the delay response.
If we execute analyze for different tables on different nodes, then we encounter this error. Example: analyze table1 on node1 & analyze table2 on node2 then we get this error. Both tables in same database.
We are on 2.25.1.0 version

5

@explore_yb see sanketh response for your case