[#MCOL-2054] Version buffer overflow could get MCS cluster into read-only mode.

The client reported that after the failure MCS cluster went into read-only mode. Here is the UM log excerpt:

Dec 26 08:37:20 PROD-PIXID-CS-DATAMART-UM1 ddlpackageproc[4029]: 20.267955 |3711|18768|0| D 23 CAL0041: Start SQL statement: CREATE TABLE `cle_ago_test` (#012  `TIC_ID` int(11) DEFAULT NULL,#012  `TII_ID` int(11) DEFAULT NULL,#012  `ORIGINE` varchar(3) DEFAULT NULL,#012  `TYPE_FACTURATION_EU` char(6) DEFAULT NULL,#012  `TYPE_FACTURATION_ETT` char(6) DEFAULT NULL,#012  `OFFRE_PRINCIPALE_ID` int(11) DEFAULT NULL,#012  `DATE_MAJ` datetime DEFAULT NULL#012) ENGINE=Columnstore DEFAULT CHARSET=utf8;|dm_temp|

Dec 26 08:37:20 PROD-PIXID-CS-DATAMART-UM1 workernode[1795]: 20.338037 |0|0|0| C 30 CAL0000: VBBM::getBlocks(): version buffer overflow. Increase VersionBufferFileSize. Overflow occured in aged blocks. Requested NumBlocks:VbOid:vbFBO:lastFBO = 1:0:1877500:1877599 lbid locked is 15510793

Dec 26 08:37:24 PROD-PIXID-CS-DATAMART-UM1 ddlpackageproc[4029]: 24.772254 |3711|18768|0| D 23 CAL0042: End SQL statement

Dec 26 08:37:24 PROD-PIXID-CS-DATAMART-UM1 ddlpackageproc[4029]: 24.772858 |0|0|0| E 23 CAL0009: (2)Create table failed due to  WE: Error updating calpontsys.systable:BRM block version buffer overflow error.

The failed operation left systemFiles/dbrm/DMLLog_$txnid_1 file behind and got the cluster into read-only mode. Moreover this file called for DMLProc rollback at the cluster start so MCS reboot didn't help.

CS should either create the file after it gets enough space in VB or remove the file in case of a failure.

[MCOL-2054] Version buffer overflow could get MCS cluster into read-only mode. Created: 2018-12-27 Updated: 2023-10-25 Resolved: 2023-10-25
Status:	Closed
Project:	MariaDB ColumnStore
Component/s:	DMLProc
Affects Version/s:	1.1.6, 1.2.2
Fix Version/s:	23.10

[MCOL-2054] Version buffer overflow could get MCS cluster into read-only mode. Created: 2018-12-27 Updated: 2023-10-25 Resolved: 2023-10-25