[MXS-280] SELECT INTO OUTFILE query succeeds even if backed fails Created: 2015-07-20  Updated: 2016-02-09  Resolved: 2015-07-23

Status: Closed
Project: MariaDB MaxScale
Component/s: readwritesplit
Affects Version/s: None
Fix Version/s: 1.3.0

Type: Bug Priority: Major
Reporter: Timofey Turenko Assignee: markus makela
Resolution: Fixed Votes: 0
Labels: None


 Description   

query SELECT * INTO OUTFILE '/tmp/t1.csv' FROM t1; does not generate error in case if backend fails to execute this query

steps to reproduce:
1. create /tmp/t1.csv file on all backend nodes
2. execute SELECT * INTO OUTFILE '/tmp/t1.csv' FROM t1; against RWSplit router (should be checked also with ReadConn router)
3. check error log
Error : Failed to execute select * into outfile '/tmp/t1.csv' from in 192.168.122.119:3306. HY000 File '/tmp/t1.csv' already exists

Expected result: step 2 fails with error
Actual result: no error, t1.csv does not contain info from DB



 Comments   
Comment by markus makela [ 2015-07-23 ]

If the file is created on all the nodes, the query will fail.

As long as the master node successfully executes the query, the session will continue. The slaves which fail the execution of the query will be disabled for the rest of the session and a replacement slave will be chosen.

In the case that all slaves have the file but the master does not, all slaves are disabled for the duration of the session and only the master is used.

Generated at Thu Feb 08 03:58:07 UTC 2024 using Jira 8.20.16#820016-sha1:9d11dbea5f4be3d4cc21f03a88dd11d8c8687422.