Introduce gRPC for both the control and data path

Description

Currently, we use thrift for synchronous communication w/ the master and netty for the worker. Netty streaming RPC is complex to debug, extend, maintain and test. In addition, adding *-to-master asynchronous RPC means redundant work maintaining multiple RPC frameworks for the same kind of communication. This work aims to determine if a single consolidated RPC framework is able to meet our requirements, including performance and maintainability.

Environment

None

Assignee

Adit Madan

Reporter

Adit Madan

Labels

None

Components

Affects versions

Priority

Major
Configure