ERROR: Too many ROS containers exist for the following projections

Hi MrBudy01,

ROS files = 176042 that's way too high.
Maximum by default is 1024 and we advise to keep this number bellow 50.

Seems the inserts are running one by one.

Hi Valdar,

Sorry if this question sounds dumb but how should I keep them under 50?

On another note how can I delete some of those ROS files for this table?

In DBveaver I don't see the option to insert them one by one or bulk.

Thank you for your answer!

You have to run mergeout on your tables / projections.

In DBeaver when loading data there is two options:
- Do-commit after row insert
- Use multi-row value insert

This last option requires your database to be at least in 11.1.

Those are not a recommandation, this is by default in my DBeaver interface (and for whatever reason some lines are in french)

My DBeaver is currently 22.3.3

In addition, try to use one COPY statement to load data from files,
By loading all files from all nodes using only ONE single COPY command on one of the nodes.
And try to increase each load dose.
You can maintain load throughput by increasing each input file size, up to an optimal size (rule of thumb 10-20 GB each).
See: https://docs.vertica.com/12.0.x/en/sql-reference/statements/copy

Hi! Thank you guys for your suggestions!

@Valdar my version of Vertica is 10.1.1 so I don't think I can use multi-row value insert.
Without that my interface looks the same as yours.
Regarding the mergeout, I used select DO_TM_TASK ('mergeout', 'xyz') on every projection that the tables uses and on the table itself and still it's importing the data very slowly and getting the same error.

@mosheg thank you for the response but I can't use the copy command because I don't have access to the nodes directly, only through dbeaver.

Hi MrBudy01

Yes, you can perform multi-row value insert as in specified in DBeaver.
If you perform a multi-row value insert into a table mystuff, DBeaver will create a statement: INSERT INTO mystuff VALUES(?,?,?) (as many question marks as mystuff has columns).
Then, it will read rows into memory, and insert all these rows in one SQL call into Vertica, read the next row set, rinse, repeat.
Vertica has been able to support that since the beginning. I used in Version 4 for the first time. Each and every one of these SQL calls create a new ROS container!
So, use multi-row insert, make the row buffer as big as your DBeaver client and the memory of your laptop allows you to, and, if you can, commit at the end, not every 10,000 rows.

First thing that comes to mind is the network. How long does a ping take? Like in here?

marco ~/1/c $ ping zbook
PING marcos-ubuntu (192.168.1.114): 56 data bytes
64 bytes from 192.168.1.114: icmp_seq=0 ttl=64 time=210.856 ms
64 bytes from 192.168.1.114: icmp_seq=1 ttl=64 time=12.268 ms
64 bytes from 192.168.1.114: icmp_seq=2 ttl=64 time=88.663 ms

Each time you issue a call with the insert of a row set, at least the loopback time - that ping can measure - is spent. Then, of course, time is spent to send the data of that row set over the network. Only then will the Vertica server pick up the data, distribute it to the right nodes depending on the segmentation criteria of the table, sort and encode the data, and finally write to disk.

Sometimes, divide and conquer helps. Split the file into manageable chunks, and load each individually.

@marcothesane this is my ping to the vertica server:
Reply from xyz: bytes=32 time=3ms TTL=62
Reply from xyz: bytes=32 time=3ms TTL=62
Reply from xyz: bytes=32 time=2ms TTL=62
Reply from xyz: bytes=32 time=3ms TTL=62

You don't need access to the nodes to perform a COPY, you can perform a COPY LOCAL.
The best solution probably!

@Valdar That worked perfectly!
Thank you!

Here is an example: COPY my_table_name FROM local 'c:\my_file_path\my_data.csv' PARSER fcsvparser() ABORT ON ERROR;