chrislu 17806cde2a separate context ...

If using the same context, the downstream grpc would be cancelled when the parent grpc is cancelled.

2024-03-27 10:24:57 -07:00

..

broker_connect.go

streaming mode

2024-03-15 21:05:24 -07:00

broker_grpc_admin.go

subscriber find broker leader first

2024-02-05 23:14:25 -08:00

broker_grpc_assign.go

refactor

2024-01-22 11:06:53 -08:00

broker_grpc_balance.go

proxy to broker leader

2024-02-05 18:00:50 -08:00

broker_grpc_configure.go

proxy to broker leader

2024-02-05 18:00:50 -08:00

broker_grpc_lookup.go

proxy to broker leader

2024-02-05 18:00:50 -08:00

broker_grpc_pub_balancer.go

proxy to broker leader

2024-02-05 18:00:50 -08:00

broker_grpc_pub_follow.go

publisher is able to fully send data and receive acks

2024-03-20 12:25:40 -07:00

broker_grpc_pub.go

separate context

2024-03-27 10:24:57 -07:00

broker_grpc_sub_coordinator.go

setup follower by publisher

2024-03-24 12:57:09 -07:00

broker_grpc_sub.go

refactor

2024-03-24 13:07:51 -07:00

broker_grpc_topic_partition_control.go

Merge accumulated changes related to message queue (#5098)

2023-12-11 12:05:54 -08:00

broker_server.go

retry connecting to broker leader

2024-03-09 12:56:49 -08:00

broker_topic_conf_read_write.go

refactor

2024-03-24 13:07:51 -07:00

broker_topic_partition_read_write.go

ask follower to follow

2024-03-10 14:34:28 -07:00

broker_write.go

go fmt

2024-02-29 09:38:52 -08:00