meiyoula created SPARK-10586:
--------------------------------
Summary: BlockManager ca't be removed when it is re-registered,
then disassociats
Key: SPARK-10586
URL: https://issues.apache.org/jira/browse/SPARK-10586
Project: Spark
Issue Type: Bug
Components: Spark Core
Reporter: meiyoula
Scene:
When the executor has been removed, but it still exists on the SparkUI web.
Looking into the executor log, I find the BlockManager has re-registers.
{quote}
2015-07-17 11:56:52,142 | WARN | [driver-heartbeater] | Told to re-register on
heartbeat | org.apache.spark.Logging$class.logWarning(Logging.scala:71)
2015-07-17 11:56:52,143 | INFO | [driver-heartbeater] | BlockManager
re-registering with master |
org.apache.spark.Logging$class.logInfo(Logging.scala:59)
2015-07-17 11:56:52,177 | INFO | [driver-heartbeater] | Trying to register
BlockManager | org.apache.spark.Logging$class.logInfo(Logging.scala:59)
2015-07-17 11:56:52,188 | INFO | [driver-heartbeater] | Registered
BlockManager | org.apache.spark.Logging$class.logInfo(Logging.scala:59)
2015-07-17 11:56:52,189 | INFO | [driver-heartbeater] | Reporting 16 blocks to
the master. | org.apache.spark.Logging$class.logInfo(Logging.scala:59)
2015-07-17 11:56:52,191 | ERROR | [SIGTERM handler] | RECEIVED SIGNAL 15:
SIGTERM |
org.apache.spark.util.SignalLoggerHandler.handle(SignalLogger.scala:57)
2015-07-17 11:56:52,248 | INFO | [Thread-1] | Shutdown hook called |
org.apache.spark.Logging$class.logInfo(Logging.scala:59)
2015-07-17 11:56:52,290 | INFO | [Thread-1] | Shutdown hook called |
org.apache.spark.Logging$class.logInfo(Logging.scala:59)
{quote}
And after a while the driver find the re-registered blockmanager is
disassociated, but didn't remove the blockmanager.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscr...@spark.apache.org
For additional commands, e-mail: issues-h...@spark.apache.org
