The nebula data is about 40g. It takes about an hour to manually execute the compaction. When the compaction is executed for about 30 minutes, it is found that the data cannot be written in. After the compaction is over, the data can be written in again.
configuration
- nebula version: v3.2.0
- Deployment method: stand-alone
- Installation method: Docker
- Whether to use the production environment: N
- hardware information
- Disk 200G HDD
- CPU, memory information 32C 32G
- Some parameters have been modified, and 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
I would like to know what might be the reason for the blocking.
