Github user ScrapCodes commented on the pull request:
https://github.com/apache/spark/pull/2055#issuecomment-54776785
@pwendell This patch will lead to logging of messages like
```
14/09/08 10:23:39.639 WARN AppClient$ClientActor: Received unexpected actor
system event: Associated [akka.tcp://spark@localhost:35007] <-
[akka.tcp://driverPropsFetcher@localhost:54437]
14/09/08 10:23:39.639 WARN SparkDeploySchedulerBackend: Received unexpected
actor system event: Associated [akka.tcp://spark@localhost:35007] <-
[akka.tcp://driverPropsFetcher@localhost:54437]
14/09/08 10:23:39.788 WARN SparkDeploySchedulerBackend: Received unexpected
actor system event: AssociationError [akka.tcp://spark@localhost:35007] <-
[akka.tcp://driverPropsFetcher@localhost:54437]: Error [Shut down address:
akka.tcp://driverPropsFetcher@localhost:54437]
```
These are akka system messages. And I guess logging them at "WARN" would be
a little noisy(They are not many of them as I initially thought.). So I am okay
with it if logging level is changed to at least "DEBUG" or even better TRACE. I
will leave rest to your judgement.
---
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]
