Github user zsxwing commented on a diff in the pull request:

    https://github.com/apache/spark/pull/4588#discussion_r26100032
  
    --- Diff: core/src/main/scala/org/apache/spark/rpc/RpcEnv.scala ---
    @@ -0,0 +1,370 @@
    +/*
    + * Licensed to the Apache Software Foundation (ASF) under one or more
    + * contributor license agreements.  See the NOTICE file distributed with
    + * this work for additional information regarding copyright ownership.
    + * The ASF licenses this file to You under the Apache License, Version 2.0
    + * (the "License"); you may not use this file except in compliance with
    + * the License.  You may obtain a copy of the License at
    + *
    + *    http://www.apache.org/licenses/LICENSE-2.0
    + *
    + * Unless required by applicable law or agreed to in writing, software
    + * distributed under the License is distributed on an "AS IS" BASIS,
    + * WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
    + * See the License for the specific language governing permissions and
    + * limitations under the License.
    + */
    +
    +package org.apache.spark.rpc
    +
    +import java.net.URI
    +
    +import scala.concurrent.Future
    +import scala.concurrent.duration.FiniteDuration
    +import scala.reflect.ClassTag
    +
    +import org.apache.spark.{SparkException, SecurityManager, SparkConf}
    +import org.apache.spark.util.Utils
    +
    +/**
    + * An RPC environment. [[RpcEndpoint]]s need to register itself with a 
name to [[RpcEnv]] to
    + * receives messages. Then [[RpcEnv]] will process messages sent from 
[[RpcEndpointRef]] or remote
    + * nodes, and deliver them to corresponding [[RpcEndpoint]]s.
    + *
    + * [[RpcEnv]] also provides some methods to retrieve [[RpcEndpointRef]]s 
given name or uri.
    + */
    +private[spark] trait RpcEnv {
    +
    +  /**
    +   * Return RpcEndpointRef of the registered [[RpcEndpoint]]. Will be used 
to implement
    +   * [[RpcEndpoint.self]].
    +   */
    +  private[rpc] def endpointRef(endpoint: RpcEndpoint): RpcEndpointRef
    +
    +  /**
    +   * Return the address that [[RpcEnv]] is listening to.
    +   */
    +  def address: RpcAddress
    +
    +  /**
    +   * Register a [[RpcEndpoint]] with a name and return its 
[[RpcEndpointRef]]. [[RpcEnv]] does not
    +   * guarantee thread-safety.
    +   */
    +  def setupEndpoint(name: String, endpoint: RpcEndpoint): RpcEndpointRef
    +
    +  /**
    +   * Register a [[RpcEndpoint]] with a name and return its 
[[RpcEndpointRef]]. [[RpcEnv]] should
    +   * make sure thread-safely sending messages to [[RpcEndpoint]].
    +   */
    +  def setupThreadSafeEndpoint(name: String, endpoint: RpcEndpoint): 
RpcEndpointRef
    +
    +  /**
    +   * Retrieve a [[RpcEndpointRef]] which is located in the driver via its 
name.
    +   */
    +  def setupDriverEndpointRef(name: String): RpcEndpointRef
    +
    +  /**
    +   * Retrieve the [[RpcEndpointRef]] represented by `url`.
    +   */
    +  def setupEndpointRefByUrl(url: String): RpcEndpointRef
    +
    +  /**
    +   * Retrieve the [[RpcEndpointRef]] represented by `systemName`, 
`address` and `endpointName`
    --- End diff --
    
    Actually, `systemName` is a Akka concept. A uri to create ActorRef should 
contain the system name. Here is an example of a Akka ActorRef uri: 
`akka.tcp://systemname@host:port/user/actorname` 
    
    In the current codes, Spark use different system names for different 
processes. E.g., Master uses `sparkMaster`, Worker i uses `"sparkWorker" + i`, 
Driver uses `sparkDriver`.
    
    Because `systemName` is necessary for `ActorRef`, I cannot remove it from 
RPC even if it won't be used for other RPC implementation.
    



---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at [email protected] or file a JIRA ticket
with INFRA.
---

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to