spark-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Sean Owen (JIRA)" <j...@apache.org>
Subject [jira] [Resolved] (SPARK-16941) SparkSQLOperationManager should use synchronized Map to store SessionHandle
Date Thu, 11 Aug 2016 10:29:20 GMT

     [ https://issues.apache.org/jira/browse/SPARK-16941?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Sean Owen resolved SPARK-16941.
-------------------------------
       Resolution: Fixed
    Fix Version/s: 2.1.0

Issue resolved by pull request 14534
[https://github.com/apache/spark/pull/14534]

> SparkSQLOperationManager should use synchronized Map to store SessionHandle
> ---------------------------------------------------------------------------
>
>                 Key: SPARK-16941
>                 URL: https://issues.apache.org/jira/browse/SPARK-16941
>             Project: Spark
>          Issue Type: Bug
>          Components: SQL
>    Affects Versions: 1.5.1, 2.0.0
>            Reporter: carlmartin
>            Priority: Minor
>             Fix For: 2.1.0
>
>
> When I had run a high concurrency sql query with thriefserver, I found this error without
any previous error:
> *Error: java.util.NoSuchElementException: key not found: SessionHandle [a2ea264f-d29d-43c4-842f-4e0f2a3cf877]
(state=,code=0)*
> So I check the code in *SparkSQLOperationManager*, and found the *Map(sessionToContexts
and sessionToActivePool)* is not thread safe in it.
> I found this error in version 1.5.1 but I think the last master branch will still have
this error.



--
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


Mime
View raw message