tidb2.1 升级 3.0问题

来了老弟 · 2020 年4 月 3 日 08:06

您好，

升级不会出错，升级时调整 ansible conf/tidb.yml max-index-length 参数。

pingcap/tidb-ansible/blob/e4c205731b9ca3e4884dc7d4660c0a8b23d553b2/conf/tidb.yml#L30


      
          # Set the memory quota for a query in bytes. Default: 32GB
          # mem-quota-query: 34359738368
          
          # Make "kill query" behavior compatible with MySQL. It's not recommend to
          # turn on this option when TiDB server is behind a proxy.
          # compatible-kill-query: false
          
          # check mb4 value in utf8 is used to control whether to check the mb4 characters when the charset is utf8.
          # check-mb4-value-in-utf8: true
          
          # max-index-length is used to deal with compatibility issues from v3.0.7 and previous version upgrades. It can only be in [3072, 3072*4].
          # max-index-length: 3072
          
          # alter-primary-key is used to control alter primary key feature. Default is false, indicate the alter primary key feature is disabled.
          # If it is true, we can add the primary key by "alter table". However, if a table already exists before the switch is turned true and
          # the data type of its primary key column is an integer, the primary key cannot be dropped.
          # alter-primary-key: false
          
          # server-version is used to change the version string of TiDB in the following scenarios:
          # 1. the server version returned by builtin-function `VERSION()`.
          # 2. the server version filled in handshake packets of MySQL Connection Protocol, see https://dev.mysql.com/doc/internals/en/connection-phase-packets.html#packet-Protocol::Handshake for more details.

注意事项可以参考下：