When importing data from an EXCEL file with threads: 5 (default) then data becomes twisted

Details

Description

By default, its number of threads when inserting data from an EXCEL file into the DB is 5 currently.
It has a bug in that part so that it takes even longer than thread=1, which means it doesn't work correctly. Even worse, data in the table are twisted from each of thread because of frequent deadlock.

Fixed to be:
fixing multi-threading INSERT operation to be correctly working.
Otherwise not support multi-threads when importing data.

Quickly,
Make the default value to be 1 (single thread). 5 threads surely makes deadlock.

Activity

Ascending order - Click to sort in descending order
Hide
Permalink
庞启仁 added a comment -

This is JDBC bugs.
When have a primary key in table, use multi-thread to insert data and commit at the same time, JDBC is deadlock.

Show
庞启仁 added a comment - This is JDBC bugs. When have a primary key in table, use multi-thread to insert data and commit at the same time, JDBC is deadlock.
Hide
Permalink
Laura Oh added a comment - - edited

When importing in the CM/CQB from he excel or csv file, the DB usually has the existing table schema having PK in 99% of cases. Which means a deadlock highly occurs when multi-inserting to a single table. Therefore the cubrid tool should work on a single thread INSERT to a each table(dividing a thread for each table) or each thread should have a different commit period(not to complete all of ongoing operations at the same time) otherwise the default value should be "1" for a single threaded INSERT.

Show
Laura Oh added a comment - - edited When importing in the CM/CQB from he excel or csv file, the DB usually has the existing table schema having PK in 99% of cases. Which means a deadlock highly occurs when multi-inserting to a single table. Therefore the cubrid tool should work on a single thread INSERT to a each table(dividing a thread for each table) or each thread should have a different commit period(not to complete all of ongoing operations at the same time) otherwise the default value should be "1" for a single threaded INSERT.
Hide
Permalink
庞启仁 added a comment -

I think this is JDBC or CUBRID server problem. Why cause the deadlock when have a PK?
For improving the insert performance, the JDBC or CUBRID server should solve this problem.

Show
庞启仁 added a comment - I think this is JDBC or CUBRID server problem. Why cause the deadlock when have a PK? For improving the insert performance, the JDBC or CUBRID server should solve this problem.
Hide
Permalink
Laura Oh added a comment -

the current 8.4.0 has improved a deadlock problem when multi-inserting to a table however the previous 8.3.X or 8.2.X versions have serious deadlock problems. Even if the server is 8.4.0, a deadlock highly occurs on the table having PK+other indexes. Therefore CM/CQB tools should be fixed considering the current engine's limitations accordingly.

Show
Laura Oh added a comment - the current 8.4.0 has improved a deadlock problem when multi-inserting to a table however the previous 8.3.X or 8.2.X versions have serious deadlock problems. Even if the server is 8.4.0, a deadlock highly occurs on the table having PK+other indexes. Therefore CM/CQB tools should be fixed considering the current engine's limitations accordingly.
Hide
Permalink
庞启仁 added a comment -

Fix it in version CUBRID Manager 8.4.1.0006 and CUBRID Query Browser 1.2.2.0006

Solution:
When have PK or index in table, defaultly use one thread

Show
庞启仁 added a comment - Fix it in version CUBRID Manager 8.4.1.0006 and CUBRID Query Browser 1.2.2.0006 Solution: When have PK or index in table, defaultly use one thread
Hide
Permalink
高艳铭 added a comment -

Fixed in version CM8.4.1.0009

Show
高艳铭 added a comment - Fixed in version CM8.4.1.0009

People

  • Assignee:
    高艳铭
    Reporter:
    Laura Oh
Vote (0)
Watch (0)

Dates

  • Created:
    Updated:
    Resolved: