orientdb
orientdb copied to clipboard
Very long running drop class ___exportImportRIDMap after import database in 3.1.5
OrientDB Version: 3.1.5
Java Version: OpenJDK 1.8.0_275
OS: AWS Ubuntu 20.04 LTS
Expected behavior
With the orientdb service stopped, using console.sh, following a successful database import (with -deleteRIDMapping=false) and a successful check database, I run "drop class ___exportImportRIDMap" and expect it to complete reasonably quickly.
Actual behavior
"drop class ___exportImportRIDMap" runs for a very long time (I have one running now and I will update this issue with the exact outcome when it completes) with the console.sh java process very busy in terms of CPU and RAM usage. The import file is from an OriedntDB 2.2.29 system with 47.5 million records. I have used the -deleteRIDMapping=false option on the import database to separate the drop class from the import.
Steps to reproduce
sudo systemctl stop orienntdb cd /opt/orientdb/bin su orientdb ./console.sh create database plocal:/opt/orientdb/database/test user password import database /opt/test.gz -preserveClusterIDs=true -deleteRIDMapping=false check database disconnect exit ./console.sh connect plocal:/opt/orientdb/database/test user password drop class ___exportImportRIDMap
The drop class has now been running for over 2 hours, this is longer than the import database ran for.
After 4 hours 15 mins it just died and killed my ssh session. Reconnected and ran check database which ended "Check of storage completed in 240209ms. without errors.".
list clusters before running the drop class; +----+------------------------+----+----------------------+-----------------+--------+----------+ |# |NAME | ID|CLASS |CONFLICT-STRATEGY| COUNT|SPACE-USED| +----+------------------------+----+----------------------+-----------------+--------+----------+ |1 |___exportimportridmap | 67|___exportImportRIDMap | |23778117| | |2 |___exportimportridmap_1 | 68|___exportImportRIDMap | |23778116| | +----+------------------------+----+----------------------+-----------------+--------+----------+
list clusters after failed drop class; +----+------------------------+----+----------------------+-----------------+--------+----------+ |# |NAME | ID|CLASS |CONFLICT-STRATEGY| COUNT|SPACE-USED| |1 |___exportimportridmap | 67|___exportImportRIDMap | |11884522| | |2 |___exportimportridmap_1 | 68|___exportImportRIDMap | |23778116| | +----+------------------------+----+----------------------+-----------------+--------+----------+
Bombed out again after over 3 more hours.
list clusters after failed drop class; +----+------------------------+----+----------------------+-----------------+--------+----------+ |# |NAME | ID|CLASS |CONFLICT-STRATEGY| COUNT|SPACE-USED| +----+------------------------+----+----------------------+-----------------+--------+----------+ |1 |___exportimportridmap | 67|___exportImportRIDMap | | 275092| | |2 |___exportimportridmap_1 | 68|___exportImportRIDMap | |23778116| | +----+------------------------+----+----------------------+-----------------+--------+----------+