Bug #71703 Connectors may read inconsistent data during/after a shard split
Submitted: 13 Feb 2014 12:33
Reporter: Alfranio Tavares Correia Junior Email Updates:
Status: Won't fix Impact on me:
None 
Category:MySQL Fabric Severity:S3 (Non-critical)
Version:1.4.1 OS:Any
Assigned to: CPU Architecture:Any

[13 Feb 2014 12:33] Alfranio Tavares Correia Junior 
Description:
During a shard split operation, any attempt to write to the shard is forbidden but read access is still allowed. This optimization may lead to inconsistencies though.

In order to understand the issue, let's assume a single table (i.e. table_a) with 200 integers in a single shard (i.e. shard_1).

 . client knows that shard_1 has key = 150

 . shard_1 is split: shard_1 (1 - 100), shard_2 (101 - 200)

 . client still thinks that shard_1 has key 150

So the client will/may get an empty result set if it tries to fetch key 150 from shard_1.

How to repeat:
Check the shard split code.
[6 Jul 2017 19:19] Bugs System 
Status updated to 'Won't fix' (Fabric is now covered under Oracle Lifetime Sustaining Support)