Weaviate RAFT Heartbeat Timeout and Leader Elections

How to fix it

Try these in order — the most common fix is first.

1. 1. Tune RAFT

   Copy steps
   1. Raise RAFT_TIMEOUTS_MULTIPLIER (default 5 in 1.31+; try 10 or 15)
   2. Consider limiting GOMAXPROCS if you have many collections
   Did this fix it? Yes No

2. 2. Fix the underlying pressure

   Copy steps
   1. Check memory, CPU and network connectivity
   2. The 99999999 port is intentional for nodes outside memberlist, not a separate bug
   Did this fix it? Yes No

Symptoms

Logs show 'heartbeat timeout reached, starting election'; the cluster flaps leaders; sometimes 'dial tcp: address 99999999: invalid port'.

Why it happens

• Nodes miss heartbeat windows under heavy load or latency
• Memberlist instability from too many collections or network problems

This guide also covers

• weaviate heartbeat timeout reached
• weaviate raft leader election
• weaviate invalid port 99999999

The same problem in other apps

All not loading, error messages & connection guides →

• Qdrant "Wrong input: Vector dimension error: expected dim, got" (Qdrant)
• Pinecone 429 Too Many Requests Error (Pinecone)
• Milvus "collection not loaded" Error (Milvus)

Other Weaviate errors

• Weaviate Out of Memory (OOM Killed)
• Weaviate Error: Vector Lengths Don't Match
• Weaviate gRPC Deadline Exceeded Error
• Weaviate Batch Import Errors and Failed Objects
• Weaviate 'Memory Pressure: Cannot Init Shard' Error
• Weaviate Stuck on 'Schema Catching Up' at Startup
• How to Cancel Weaviate Cloud and Avoid Charges