CentOS 7.2

Please make sure you have checked all logs (inclluding maria server) as documented here: https://mariadb.com/kb/en/mariadb/system-troubleshooting-mariadb-columnstore/. Especially check for evidence of the um server (or pms) runnig out of memory and the processes being restarted.

Second, is there a specific reason you are using LDI? If not can you try using cpimport directly as it also faster. We have seen some evidence that very large data loads going through LDI can sometimes lead to memory being exhausted on the UM. Alternatively try with smaller LDI files.

If you are still stuck it would help if you could provide the output from the columnstoreSupport utility.

In addition to David's advice, does your data include CHAR/VARCHAR columns with multibyte text?

Thx for your answer.
When using mcsmysql to load data from a csv file, I logged the output into a file named xxx.csv.log. so the last modifed time of the log file should be the time when the error occured. Hers is the 'ls -lrt' output:

-rw-r--r-- 1 root root 115 Feb 22 22:53 catalog_returns_2_10.csv.log

-rw-r--r-- 1 root root 115 Feb 22 23:17 store_returns_2_10.csv.log

-rw-r--r-- 1 root root 115 Feb 23 00:05 catalog_returns_3_10.csv.log

-rw-r--r-- 1 root root 115 Feb 23 01:32 store_returns_3_10.csv.log

-rw-r--r-- 1 root root 115 Feb 23 05:10 web_sales_2_10.csv.log

-rw-r--r-- 1 root root 115 Feb 23 09:18 web_sales_3_10.csv.log

-rw-r--r-- 1 root root 115 Feb 23 11:35 catalog_sales_3_10.csv.log

-rw-r--r-- 1 root root 115 Feb 23 12:56 catalog_sales_2_10.csv.log

-rw-r--r-- 1 root root 115 Feb 23 14:02 store_sales_2_10.csv.log

Follow up on your suggestion, I rechecked the log file in /var/log/mariadb/columnstore on um1.
There are some msg in err.log, but the point in time does not exactly match the log file's modification time

Attachments are log files FYI. err.log info.log warning.log

The logs appear to indicate that you are trying to do LDI on multiple clients to the same table simultaneously. ColumnStore won't allow this which is probably why you are seeing errors. There are ways of doing this with cpimport, particularly loading into multiple PMs simultaneously.

@Andrew, the data is generated by standard tpc-ds tools and should not have multibyte text. Especially the table 'web_sales' do not have char/varchar columns.

solargg do you have a response on doing LDI on mulitple clients at the same, if so that is not supported? Also with very high volumes for flat files it's better to consider using cpimport?

Please re-open if you have further information on the question.