You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@spark.apache.org by "Apache Spark (JIRA)" <ji...@apache.org> on 2015/01/22 09:03:34 UTC

[jira] [Commented] (SPARK-4934) Connection key is hard to read

    [ https://issues.apache.org/jira/browse/SPARK-4934?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14287089#comment-14287089 ] 

Apache Spark commented on SPARK-4934:
-------------------------------------

User 'shenh062326' has created a pull request for this issue:
https://github.com/apache/spark/pull/4157

> Connection key is hard to read
> ------------------------------
>
>                 Key: SPARK-4934
>                 URL: https://issues.apache.org/jira/browse/SPARK-4934
>             Project: Spark
>          Issue Type: Improvement
>          Components: Spark Core
>    Affects Versions: 1.1.1
>            Reporter: Hong Shen
>
> When I run a big spark job, executor have a lot of log,
> 14/12/23 15:25:31 INFO network.ConnectionManager: key already cancelled ? sun.nio.ch.SelectionKeyImpl@52b0e278
> java.nio.channels.CancelledKeyException
>         at org.apache.spark.network.ConnectionManager.run(ConnectionManager.scala:310)
>         at org.apache.spark.network.ConnectionManager$$anon$4.run(ConnectionManager.scala:139)
> It's hard to know which connection is cancelled. maby we can change to 
> logInfo("Connection already cancelled ? " + con.getRemoteAddress(), e)



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscribe@spark.apache.org
For additional commands, e-mail: issues-help@spark.apache.org