[ https://issues.apache.org/jira/browse/SPARK-4878?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Sean Owen resolved SPARK-4878. ------------------------------ Resolution: Not A Problem I'm guessing 'not a problem' in that there's no Akka involved anymore > driverPropsFetcher causes spurious Akka disassociate errors > ----------------------------------------------------------- > > Key: SPARK-4878 > URL: https://issues.apache.org/jira/browse/SPARK-4878 > Project: Spark > Issue Type: Bug > Components: Spark Core > Affects Versions: 1.2.0 > Reporter: Stephen Haberman > Priority: Minor > > The dedicated Akka system to fetching driver properties seems fine, but it > leads to very misleading "AssociationHandle$Disassociated", dead letter, etc. > sort of messages that can lead the user to believe something is wrong with > the cluster. > (E.g. personally I thought it was a Spark -rc1/-rc2 bug and spent awhile > poking around until I saw in the code that driverPropsFetcher is > purposefully/immediately shutdown.) > Is there any way to cleanly shutdown that initial akka system so that the > driver doesn't log these errors? -- 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