v0.7.4
This release focuses on infrastructure scalability through enhanced gRPC integration, allowing for more efficient node deployment strategies.
Added
- RemoteDB over gRPC: Implement the ability for Juno nodes to connect to a primary node's database over gRPC, serving RPC requests without the need for syncing themselves. This feature is enabled through new flag:
--remote-db
, streamlining scalability and reducing overhead. (@omerfirmak in #1353)
Changed
- Error Logging: Reduced noise in logs by preventing the recording of errors not attributable to Juno's own operations. This ensures a clearer logging experience and easier troubleshooting. (@joshklop in #1406)
Usage
To deploy a syncing node that exposes its database over gRPC:
docker run -d \
--name juno_grpc \
--network juno-net \
-p 6064:6064 \
-v /root/snapshots/juno_mainnet:/var/lib/juno \
nethermind/juno:v0.7.4 \
--db-path /var/lib/juno \
--grpc-host 0.0.0.0 \
--grpc-port 6064 \
--grpc
To deploy a node that uses the primary node’s synced database over gRPC:
docker run -d \
--name juno_from_grpc \
--network juno-net \
-p 6065:6065 \
nethermind/juno:v0.7.4 \
--http \
--http-port 6065 \
--http-host 0.0.0.0 \
--remote-db juno_grpc:6064
Full Changelog: v0.7.3...v0.7.4