[ 
https://issues.apache.org/jira/browse/CASSANDRASC-58?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17737871#comment-17737871
 ] 

ASF subversion and git services commented on CASSANDRASC-58:
------------------------------------------------------------

Commit ab1884d2eedace79857489cb9dbe455ada9e4ad1 in cassandra-sidecar's branch 
refs/heads/trunk from Francisco Guerrero
[ https://gitbox.apache.org/repos/asf?p=cassandra-sidecar.git;h=ab1884d ]

CASSANDRASC-58: Support retries in Sidecar Client on Invalid Checksum

In rare occasions an SSTable upload will receive a corrupted SSTable. Bit flips
are expected to occur occassionally while transmitting SSTables from client to
server.

This commit adds support for retries in Sidecar Client when a checksum mismatch
is encountered during SSTable upload. Allowing for clients to retry

patch by Francisco Guerrero; reviewed by Dinesh Joshi, Yifan Cai for 
CASSANDRASC-58


> Support retries in Sidecar Client when MD5 checksum is mismatched
> -----------------------------------------------------------------
>
>                 Key: CASSANDRASC-58
>                 URL: https://issues.apache.org/jira/browse/CASSANDRASC-58
>             Project: Sidecar for Apache Cassandra
>          Issue Type: Improvement
>          Components: Configuration
>            Reporter: Francisco Guerrero
>            Assignee: Francisco Guerrero
>            Priority: Normal
>              Labels: pull-request-available
>
> In rare occasions an SSTable upload will get corrupted during upload. Bit 
> flips are expected to occur occasionally while transmitting the SSTables from 
> the client to the server. The current behavior of the Sidecar Client in those 
> situations is to fail fast without any retries.
> We want to support Sidecar Client retries when checksum mismatch occurs 
> during SSTable upload.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to