You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@spark.apache.org by "Sean Owen (JIRA)" <ji...@apache.org> on 2016/08/09 09:57:20 UTC
[jira] [Updated] (SPARK-16941) SparkSQLOperationManager should use
synchronized Map to store SessionHandle
[ https://issues.apache.org/jira/browse/SPARK-16941?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Sean Owen updated SPARK-16941:
------------------------------
Summary: SparkSQLOperationManager should use synchronized Map to store SessionHandle (was: SparkSQLOperationManager shuold use synchronization map to store SessionHandle)
> 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
>
> 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