5.2.3 TiFlash Fails to Start

Note:
This topic has been translated from a Chinese forum by GPT and might contain errors.

Original topic: 5.2.3 tiflash 拉不起来

| username: TiDBer_an

[TiDB Usage Environment] Production Environment / Testing / Poc
[TiDB Version]
[Reproduction Path] What operations were performed when the issue occurred
[Encountered Issue: Issue Phenomenon and Impact]
[Resource Configuration] Go to TiDB Dashboard - Cluster Info - Hosts and take a screenshot of this page
[Attachments: Screenshots/Logs/Monitoring]

TiDB cluster version 5.2.3, there is a table with TiFlash enabled. After changing the table structure, TiFlash has been reporting internal errors.

Change Operation

Saw this issue on GitHub, is this the problem?

TiFlash Logs

| username: linnana | Original post link

Why can’t the issue be opened?

| username: TiDBer_an | Original post link

You need to use a VPN, right? It’s also difficult for me to access without a VPN.

| username: 有猫万事足 | Original post link

It seems reliable, this should be the bug.

| username: ShawnYan | Original post link

Reading mismatch data type pack. Cast from Int64 to String is NOT supported #6703

1. Minimal reproduce step (Required)

mysql> select count(*) from pk_is_handle1;
ERROR 1105 (HY000): other error for mpp stream: From MPP<query:<query_ts:1675219212921686072, local_query_id:172206, server_id:871855, start_ts:439148665346195457>,task_id:3>: Code: 0, e.displayText() = DB::Exception: Reading mismatch data type pack. Cast from Int64 to String is NOT supported!: (while reading from DTFile: /data0/db/data/t_98/stable/dmf_833), e.what() = DB::Exception,
mysql> set tidb_isolation_read_engines='tikv';
Query OK, 0 rows affected (0.05 sec)

mysql> set tidb_isolation_read_engines='tikv';
Query OK, 0 rows affected (0.04 sec)

mysql> select count(*) from pk_is_handle1;
+----------+
| count(*) |
+----------+
| 63159390 |
+----------+
1 row in set (2.39 sec)
CREATE TABLE `pk_is_handle1` (
  `a` bigint(20) NOT NULL,
  `b` int(11) DEFAULT NULL,
  `c` varchar(100) NOT NULL,
  `d` char(100) DEFAULT NULL,
  `e` float DEFAULT NULL,
  `g` double DEFAULT NULL,
  `h` decimal(8,4) DEFAULT NULL,
  `i` date DEFAULT NULL,
  `j` datetime DEFAULT NULL,
  PRIMARY KEY (`a`) /*T![clustered_index] CLUSTERED */
) ENGINE=InnoDB DEFAULT CHARSET=utf8mb4 COLLATE=utf8mb4_bin
| username: 哈喽沃德 | Original post link

Awesome, learned a lot.

| username: 小于同学 | Original post link

Bug

| username: Kongdom | Original post link

It looks like it has been fixed in these versions.

| username: system | Original post link

This topic was automatically closed 60 days after the last reply. New replies are no longer allowed.