Hi TRON community,
We are consistently encountering a reproducible issue when syncing a Full Node using the official TRON snapshot.
🐛 Problem Summary
During sync, if the block height ends with 99 or 999 (e.g., 74450399, 2399999, etc.), the node:
- Either freezes completely (block number never increases), or
- Pauses syncing for 12–24 seconds before resuming
This significantly slows down or halts the sync process.
🔁 Confirmed Through Multiple Attempts
- We have tested multiple times by restoring from the same official snapshot
- Every attempt freezes at the exact same block number, particularly at block heights ending in
99 or 999
- Restarting
systemctl restart tron does not help
- This confirms that it's not a random runtime issue, but likely something within the snapshot itself or the sync logic
🧪 Additional Observations
- Sync speed is normally ~3s/block
- Monitoring shows 6s polling via Prometheus
- At
...99 or ...999, sync often stalls for multiple cycles (12–24s+)
- If sync starts at a
...999 block (e.g. 2399999), sync doesn't start at all
- No errors appear in
tron.log, gc.log, or system logs
- Peers are connected (
activeConnectCount = 10), RocksDB meta files present and correct
🔧 Environment Details
- Java 8/11 with G1GC
- 64GB+ RAM, Ubuntu 20.04/22.04
- RocksDB
CURRENT, MANIFEST-*, LOG all present in subdirectories
- Using the latest TRON snapshot
- Containerd, Prometheus, Node Exporter used for monitoring
Config contains:
sync {
syncVerify = false
}
witness {
validate-pbft-block = false
}
Hi TRON community,
We are consistently encountering a reproducible issue when syncing a Full Node using the official TRON snapshot.
🐛 Problem Summary
During sync, if the block height ends with 99 or 999 (e.g.,
74450399,2399999, etc.), the node:This significantly slows down or halts the sync process.
🔁 Confirmed Through Multiple Attempts
99or999systemctl restart trondoes not help🧪 Additional Observations
...99or...999, sync often stalls for multiple cycles (12–24s+)...999block (e.g. 2399999), sync doesn't start at alltron.log,gc.log, or system logsactiveConnectCount = 10), RocksDB meta files present and correct🔧 Environment Details
CURRENT,MANIFEST-*,LOGall present in subdirectoriesConfig contains: