diff options
| author | Patrick Wendell <pwendell@gmail.com> | 2014-01-05 22:37:36 -0800 |
|---|---|---|
| committer | Patrick Wendell <pwendell@gmail.com> | 2014-01-05 22:37:36 -0800 |
| commit | a2e7e0497484554f86bd71e93705eb0422b1512b (patch) | |
| tree | a1327edd944d8cc818aa9dcf7033c7db37b1d3a3 /mllib | |
| parent | 5b0986a1d675f0f9d7d14b3d48fdadcb4f7055b7 (diff) | |
| parent | 675d7eb4f064129d275a45df4c5c43f558638422 (diff) | |
| download | spark-a2e7e0497484554f86bd71e93705eb0422b1512b.tar.gz spark-a2e7e0497484554f86bd71e93705eb0422b1512b.tar.bz2 spark-a2e7e0497484554f86bd71e93705eb0422b1512b.zip | |
Merge pull request #333 from pwendell/logging-silence
Quiet ERROR-level Akka Logs
This fixes an issue I've seen where akka logs a bunch of things at ERROR level when connecting to a standalone cluster, even in the normal case. I noticed that even when lifecycle logging was disabled, the netty code inside of akka still logged away via akka's EndpointWriter class. There are also some other log streams that I think are new in akka 2.2.1 that I've disabled.
Finally, I added some better logging to the standalone client. This makes it more clear when a connection failure occurs what is going on. Previously it never explicitly said if a connection attempt had failed.
The commit messages here have some more detail.
Diffstat (limited to 'mllib')
0 files changed, 0 insertions, 0 deletions