spark-reviews mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From andrewor14 <>
Subject [GitHub] spark pull request: SPARK-2099. Report progress while task is runn...
Date Mon, 14 Jul 2014 05:28:17 GMT
Github user andrewor14 commented on a diff in the pull request:
    --- Diff: core/src/main/scala/org/apache/spark/HeartbeatReceiver.scala ---
    @@ -0,0 +1,33 @@
    + * 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
    + *
    + *
    + *
    + * 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
    +import org.apache.spark.executor.TaskMetrics
    +import org.apache.spark.scheduler.TaskScheduler
    +case class Heartbeat(executorId: String, taskMetrics: Array[(Long, TaskMetrics)],
    +  blockManagerId: BlockManagerId) extends Serializable
    +class HeartbeatReceiver(scheduler: TaskScheduler) extends Actor {
    +  override def receive = {
    +    case Heartbeat(executorId, taskMetrics, blockManagerId) =>
    +      sender ! scheduler.executorHeartbeat(executorId, taskMetrics, blockManagerId)
    --- End diff --
    Looks like `HeartbeatReceiver` can only exist on the driver (because it tasked in a scheduler).
Then I don't see why we can't just call `blockManagerMaster.heartBeat(...)` (and we should
rename this from `heartBeat`) directly rather than having to go through another akka exchange.

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 or file a JIRA ticket
with INFRA.

View raw message