[MCOL-5560] primproc log : repeated message PrimProc: Character set '#0' is not a compiled Created: 2023-08-22  Updated: 2023-09-22  Resolved: 2023-09-07

Status: Closed
Project: MariaDB ColumnStore
Component/s: None
Affects Version/s: None
Fix Version/s: 23.10.0

Type: Task Priority: Major
Reporter: alexey vorovich (Inactive) Assignee: Leonid Fedorov
Resolution: Fixed Votes: 0
Labels: None

Attachments: Text File primproc.log    
Sprint: 2023-8, 2023-10

 Comments   
Comment by Daniel Lee (Inactive) [ 2023-09-07 ]

Build verified: develop branch, build 8586
engine: e0d9b8270584bcc9a92f9eff3a84e949cd2f052e
server: 8178f1d088c14ff30c274081f18cbdf7b2e37d9b
buildNo: 8586

PrimProc log no longer has the reported msg.

Reproduced the issue in build 8527

[rocky8:root@rocky8~]# journalctl -u mcs-primproc|grep PrimProc
 
Sep 07 13:25:15 rocky8.localdomain env[9713]: PrimProc main process has started
 
Sep 07 13:25:58 rocky8.localdomain env[11926]: PrimProc main process has started
 
Sep 07 13:26:15 rocky8.localdomain env[12233]: PrimProc main process has started
 
Sep 07 13:26:31 rocky8.localdomain env[12242]: PrimProc: Character set '#0' is not a compiled character set and is not specified in the '/usr/share/mysql/charsets/Index.xml' file
 
Sep 07 13:26:51 rocky8.localdomain env[12242]: PrimProc: Character set '#503306832' is not a compiled character set and is not specified in the '/usr/share/mysql/charsets/Index.xml' file

Generated at Thu Feb 08 02:58:46 UTC 2024 using Jira 8.20.16#820016-sha1:9d11dbea5f4be3d4cc21f03a88dd11d8c8687422.