Bulk Operation

SPARK-5293 Add Outbox to cache the sending messages to resolve the message disorder issue

SPARK-5293 RPC message ordering is not guaranteed

SPARK-5293 Add connection established callback to lower level RPC layer so we don't need to check for new connections in NettyRpcHandler.receive

SPARK-5293 Post-hoc review Netty based RPC implementation - round 2

SPARK-5293 Post-hoc review Netty based RPC implementation - round 1

SPARK-5293 Remove akka dependency from SecurityManager

SPARK-5293 Remove 'Actor' from the comments

SPARK-5293 Remove the developer api SparkEnv.actorSystem and AkkaUtils

SPARK-5293 Deprecate the developer api SparkEnv.actorSystem

SPARK-5293 Remove AkkaRpcEnv and remove Akka from the dependencies of Core

SPARK-5293 Remove "StreamingContext.actorStream"

SPARK-5293 Move "StreamingContext.actorStream" to a separate project and deprecate it in StreamingContext

SPARK-5293 Move "AkkaRpcEnv" to a separate project

SPARK-5293 Remove "actorSystem" from SparkEnv

SPARK-5293 Use the new RPC implementation by default

SPARK-5293 Rename RPC askWithReply -> askWithReply, sendWithReply -> ask

SPARK-5293 Move calling `TaskScheduler.executorHeartbeatReceived` to another thread to avoid blocking the Akka thread pool

SPARK-5293 Update ReceiverTrackerActor to use the new Rpc interface

SPARK-5293 Replace JobScheduler.eventActor and JobGenerator.eventActor with EventLoop

SPARK-5293 Replace direct use of Akka with Spark RPC interface

SPARK-5293 Deprecate configurations for "askWithReply" and use new configuration names

SPARK-5293 Remove Akka systemName from Spark

SPARK-5293 Provide an alternative RPC implementation based on the network transport module

SPARK-5293 Add EventLoop and change DAGScheduler to an EventLoop

SPARK-5293 Standardize internal RPC interface