gRPC Java 1.44.0 switches default load‑balancing policy from pick_first to round_robin
The goal is to keep a local developer setup repeatable so that a gRPC Java client always connects to the same backend instance during debugging and testing. Starting with version 1.44.0 the library changed the channel‑level default from pick_first to round_robin unless an explicit policy is supplied. This alters the connection‑establishment pattern seen agai
grpc