Bug #73212 dump restore fails on shard_split with error 1840 when there is insert activity
Submitted: 6 Jul 2014 1:27 Modified: 8 Aug 2014 6:25
Reporter: Fernando Ipar (OCA) Email Updates:
Status: Won't fix Impact on me:
Category:MySQL Fabric Severity:S3 (Non-critical)
Version:1.4.3-1 OS:Any
Assigned to: CPU Architecture:Any

[6 Jul 2014 1:27] Fernando Ipar
Given the same setup described on report 73211, if there are ongoing inserts affecting the shard that will be split, the backup restore fails with this error: 

[vagrant@store ~]$ mysqlfabric sharding split_shard 1 salaries-3 --split_value=8000
Procedure :
{ uuid        = b67f49b8-4d4d-43e1-8c78-cfb7f56423ca,
  finished    = True,
  success     = False,
  return      = BackupError: ('Error while restoring the backup using the mysql client\n, %s', "ERROR 1840 (HY000) at line 24 in file: 'MySQL_node1_13306.sql': @@GLOBAL.GTID_PURGED can only be set when @@GLOBAL.GTID_EXECUTED is empty.\n"),

How to repeat:
In order to avoid hitting the error described in 73211, first set up the server user without a password. 

Then start a script that writes to the shard that will be split, and while the script is inserting, attempt the shard split.
[8 Aug 2014 6:25] Mats Kindahl
Thank you for the bug report. Verified as described.
[6 Jul 2017 19:19] Bugs System
Status updated to 'Won't fix' (Fabric is now covered under Oracle Lifetime Sustaining Support)