You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@spark.apache.org by "Shixiong Zhu (JIRA)" <ji...@apache.org> on 2019/03/25 22:33:00 UTC

[jira] [Updated] (SPARK-27275) Potential corruption in EncryptedMessage.transferTo

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

Shixiong Zhu updated SPARK-27275:
---------------------------------
    Labels: correctness  (was: )

> Potential corruption in EncryptedMessage.transferTo
> ---------------------------------------------------
>
>                 Key: SPARK-27275
>                 URL: https://issues.apache.org/jira/browse/SPARK-27275
>             Project: Spark
>          Issue Type: Bug
>          Components: Spark Core
>    Affects Versions: 2.4.0
>            Reporter: Shixiong Zhu
>            Assignee: Shixiong Zhu
>            Priority: Major
>              Labels: correctness
>
> `EncryptedMessage.transferTo` has a potential corruption issue. When the underlying buffer has more than `1024 * 32` bytes (this should be rare but it could happen in error messages that send over the wire), it may just send a partial message as `EncryptedMessage.count` becomes less than `transferred`. This will cause the client hang forever (or timeout) as it will wait until receiving expected length of bytes,  or weird errors (such as corruption or silent correctness issue) if the channel is reused by other messages.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

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