[jira] [Updated] (CASSANDRA-14517) Short read protection can cause partial updates to be read

2020-03-16 Thread ZhaoYang (Jira)


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

ZhaoYang updated CASSANDRA-14517:
-
Fix Version/s: (was: 4.0)
   4.x

Changed fix version to 4.x ..Please let me know if you think differently.. 

> Short read protection can cause partial updates to be read
> --
>
> Key: CASSANDRA-14517
> URL: https://issues.apache.org/jira/browse/CASSANDRA-14517
> Project: Cassandra
>  Issue Type: Bug
>  Components: Legacy/Coordination
>Reporter: Blake Eggleston
>Priority: Normal
> Fix For: 4.x
>
>
> If a read is performed in two parts due to short read protection, and the 
> data being read is written to between reads, the coordinator will return a 
> partial update. Specifically, this will occur if a single partition batch 
> updates clustering values on both sides of the SRP break, or if a range 
> tombstone is written that deletes data on both sides of the break. At the 
> coordinator level, this breaks the expectation that updates to a partition 
> are atomic, and that you can’t see partial updates.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

-
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org



[jira] [Updated] (CASSANDRA-14517) Short read protection can cause partial updates to be read

2018-11-18 Thread C. Scott Andreas (JIRA)


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

C. Scott Andreas updated CASSANDRA-14517:
-
Component/s: Coordination

> Short read protection can cause partial updates to be read
> --
>
> Key: CASSANDRA-14517
> URL: https://issues.apache.org/jira/browse/CASSANDRA-14517
> Project: Cassandra
>  Issue Type: Bug
>  Components: Coordination
>Reporter: Blake Eggleston
>Priority: Major
> Fix For: 4.0
>
>
> If a read is performed in two parts due to short read protection, and the 
> data being read is written to between reads, the coordinator will return a 
> partial update. Specifically, this will occur if a single partition batch 
> updates clustering values on both sides of the SRP break, or if a range 
> tombstone is written that deletes data on both sides of the break. At the 
> coordinator level, this breaks the expectation that updates to a partition 
> are atomic, and that you can’t see partial updates.



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

-
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org



[jira] [Updated] (CASSANDRA-14517) Short read protection can cause partial updates to be read

2018-06-12 Thread Blake Eggleston (JIRA)


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

Blake Eggleston updated CASSANDRA-14517:

Description: If a read is performed in two parts due to short read 
protection, and the data being read is written to between reads, the 
coordinator will return a partial update. Specifically, this will occur if a 
single partition batch updates clustering values on both sides of the SRP 
break, or if a range tombstone is written that deletes data on both sides of 
the break. At the coordinator level, this breaks the expectation that updates 
to a partition are atomic, and that you can’t see partial updates.  (was: If a 
read is performed in two parts due to short read protection, and the data being 
read is written to between reads, the coordinator will return a partial update. 
Specifically, this will occur if a single partition batch updates clustering 
values on both sides of the SRP break, or if a range tombstone is written that 
deletes data on both sides of the break. At the coordinator level, this breaks 
the expectation that updates to a partition are atomic, and that you can’t see 
partial updates.
 
In some cases, read repair can make this partial update permanent. If a write 
hits a single node, but fails to reach the other replicas, part of it is 
returned via SRP and read repaired to the rest of the replicas, then the single 
node with then full write fails before repair or read repair, the partial write 
will become permanent.)

> Short read protection can cause partial updates to be read
> --
>
> Key: CASSANDRA-14517
> URL: https://issues.apache.org/jira/browse/CASSANDRA-14517
> Project: Cassandra
>  Issue Type: Bug
>Reporter: Blake Eggleston
>Priority: Major
> Fix For: 4.0
>
>
> If a read is performed in two parts due to short read protection, and the 
> data being read is written to between reads, the coordinator will return a 
> partial update. Specifically, this will occur if a single partition batch 
> updates clustering values on both sides of the SRP break, or if a range 
> tombstone is written that deletes data on both sides of the break. At the 
> coordinator level, this breaks the expectation that updates to a partition 
> are atomic, and that you can’t see partial updates.



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

-
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org



[jira] [Updated] (CASSANDRA-14517) Short read protection can cause partial updates to be read

2018-06-12 Thread Blake Eggleston (JIRA)


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

Blake Eggleston updated CASSANDRA-14517:

Fix Version/s: 4.0

> Short read protection can cause partial updates to be read
> --
>
> Key: CASSANDRA-14517
> URL: https://issues.apache.org/jira/browse/CASSANDRA-14517
> Project: Cassandra
>  Issue Type: Bug
>Reporter: Blake Eggleston
>Priority: Major
> Fix For: 4.0
>
>
> If a read is performed in two parts due to short read protection, and the 
> data being read is written to between reads, the coordinator will return a 
> partial update. Specifically, this will occur if a single partition batch 
> updates clustering values on both sides of the SRP break, or if a range 
> tombstone is written that deletes data on both sides of the break. At the 
> coordinator level, this breaks the expectation that updates to a partition 
> are atomic, and that you can’t see partial updates.
>  
> In some cases, read repair can make this partial update permanent. If a write 
> hits a single node, but fails to reach the other replicas, part of it is 
> returned via SRP and read repaired to the rest of the replicas, then the 
> single node with then full write fails before repair or read repair, the 
> partial write will become permanent.



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

-
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org