The version of Nebula is v3.2.0 and it is deployed as a standalone instance using Docker. The hardware information is as follows: 200G HDD disk, 32C 32G CPU and memory information. I have made some modifications to the parameters, but the rest are default parameters:
--flagfile=/usr/local/nebula/etc/nebula-standalone.conf
--minloglevel=1
--v=1
--rocksdb_block_cache=256
--system_memory_high_watermark_ratio=0.95
--max_sessions_per_ip_per_user=10000
--enable_authorize=false
--enable_partitioned_index_filter=true
--client_idle_timeout_secs=28800
--session_idle_timeout_secs=28800
--max_edge_returned_per_vertex=1000
--daemonize=false
--containerized=true
--wal_ttl=1800 -
-rocksdb_rate_limit=30
--timezone_name=UTC+08:00
The data in Nebula is about 40g, and it takes about an hour to manually execute compaction. When the compaction is about 30 minutes in progress, it was found that the data could not be written anymore. After the compaction is completed, the data can be written again. I would like to know what could be causing the write blockage.
