I have been trying to get my testnet node to fully sync for the last week. I have a EC2 M4.xlarge instance:
- CentOS7 64bit
- testnet iri 220.127.116.11
- Oracle JDK 18.104.22.168
- Xmx 5GB
- neighbors with 5 community nodes that are fully sync'd
It takes about 4hours for the solid milestone tracker to start ticking over when I start from scratch i.e. deleting testnetdb and testnet.log folders.
Incidentally, I ran m4.large with Xmx3G and after a few hours, Solid milestone tracker thread crashed with GC overhead limit exceeded.
I'm looking for advice and guidance:
- Is this more or less expected?
- Where to look if I have a misconfiguration or sub-optimal setup?
Here is my iri.ini:
[IRI] PORT = 14600 TCP_RECEIVER_PORT = 14700 UDP_RECEIVER_PORT = 14700 NEIGHBORS = IXI_DIR = ixi HEADLESS = true DEBUG = false DB_PATH = /opt/iota/testnetdb TESTNET = true
My systemd unit file:
[Unit] Description=IOTA IRI full node Requires=network.target After=syslog.target network.target [Service] WorkingDirectory=/opt/iota ExecStart=/usr/local/java/bin/java -Xmx5g -Djava.net.preferIPv4Stack=true -jar /opt/iota/iri-22.214.171.124.jar -c /opt/iota/iri.ini --remote User=iri [Install] WantedBy=multi-user.target
Update I've given up on a 24/7 testnet node. Instead, I'm having success running a mainnet node using the same configs (of course with prod values, using mainnet jar, testnet=false, etc.). I'll attribute the success to a more fluid supply of reliable neighbors and downloadable sync'ed databases.