You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@spark.apache.org by "chenzichu (Jira)" <ji...@apache.org> on 2024/11/26 01:21:00 UTC
[jira] [Updated] (SPARK-50407) accessing a MySQL database through a proxy that has a set timeout, an error occurs when using df.write.jdbc
[ https://issues.apache.org/jira/browse/SPARK-50407?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
chenzichu updated SPARK-50407:
------------------------------
Attachment: 图片1.png
> accessing a MySQL database through a proxy that has a set timeout, an error occurs when using df.write.jdbc
> -----------------------------------------------------------------------------------------------------------
>
> Key: SPARK-50407
> URL: https://issues.apache.org/jira/browse/SPARK-50407
> Project: Spark
> Issue Type: Bug
> Components: Connect
> Affects Versions: 3.1.0
> Reporter: chenzichu
> Priority: Minor
> Attachments: 图片1.png
>
> Original Estimate: 48h
> Remaining Estimate: 48h
>
> When accessing a MySQL database through a proxy that has a set timeout, an error occurs when using {{{}df.write.mode(SaveMode.Append).jdbc(url, table, properties){}}}.
> error msg : !image-2024-11-25-16-22-01-206.png!
>
> The reason for this error is that the JdbcRelationProvider created a connection on the driver side, but did not close it after use; instead, it was closed after the saveTable method was called. At this point, Nginx detected that there was no data transfer on the connection and directly closed the connection, leading to an error when calling conn.close(): "no more data to read from socket".
>
>
>
>
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscribe@spark.apache.org
For additional commands, e-mail: issues-help@spark.apache.org