[ https://issues.apache.org/jira/browse/SPARK-12267?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Shixiong Zhu resolved SPARK-12267. ---------------------------------- Resolution: Fixed Assignee: Shixiong Zhu Fix Version/s: 2.0.0 1.6.1 Set 1.6.1 as one of fix versions. If there is RC3, should change it to 1.6.0. > Standalone master keeps references to disassociated workers until they sent > no heartbeats > ----------------------------------------------------------------------------------------- > > Key: SPARK-12267 > URL: https://issues.apache.org/jira/browse/SPARK-12267 > Project: Spark > Issue Type: Bug > Components: Spark Core > Affects Versions: 1.6.0 > Reporter: Jacek Laskowski > Assignee: Shixiong Zhu > Fix For: 1.6.1, 2.0.0 > > > While toying with Spark Standalone I've noticed the following messages > in the logs of the master: > {code} > INFO Master: Registering worker 192.168.1.6:59919 with 2 cores, 2.0 GB RAM > INFO Master: localhost:59920 got disassociated, removing it. > ... > WARN Master: Removing worker-20151210090708-192.168.1.6-59919 because > we got no heartbeat in 60 seconds > INFO Master: Removing worker worker-20151210090708-192.168.1.6-59919 > on 192.168.1.6:59919 > {code} > Why does the message "WARN Master: Removing > worker-20151210090708-192.168.1.6-59919 because we got no heartbeat in > 60 seconds" appear when the worker should've been removed already (as > pointed out in "INFO Master: localhost:59920 got disassociated, > removing it.")? > Could it be that the ids are different - 192.168.1.6:59919 vs localhost:59920? > I started master using {{./sbin/start-master.sh -h localhost}} and the > workers {{./sbin/start-slave.sh spark://localhost:7077}}. -- 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