[
https://issues.apache.org/jira/browse/SPARK-58097?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
ASF GitHub Bot updated SPARK-58097:
-----------------------------------
Labels: pull-request-available (was: )
> Spark Connect UI/status store collapses sessions that share a UUID across
> different users
> -----------------------------------------------------------------------------------------
>
> Key: SPARK-58097
> URL: https://issues.apache.org/jira/browse/SPARK-58097
> Project: Spark
> Issue Type: Bug
> Components: Connect
> Affects Versions: 4.3.0
> Reporter: Venkata krishnan Sowrirajan
> Priority: Major
> Labels: pull-request-available
>
> Spark Connect identifies a session by the composite (userId, sessionId), and
> two
> different users may legally use the same session UUID (see
> SparkConnectServiceE2ESuite,
> "ReleaseSession for different user_id with same session_id do not affect each
> other").
> The Connect UI status listener and store, however, key sessions by sessionId
> alone
> (SessionInfo's natural key, and SparkConnectServerListener's live-session
> map). Sessions
> that share a UUID but belong to different users therefore collapse into a
> single record:
> execution counts merge, and whichever user closes first removes the shared
> row while the
> other session is still live. History Server replay reproduces the same result.
> This has existed since the Connect UI was added in SPARK-44394 and is already
> observable through the existing UI. It was surfaced during review of
> SPARK-57941 (Connect REST API), which reads the same store, but is
> independent of that change.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
