[MXS-2150] maxctrl alter service commands does not impact existing connections Created: 2018-11-08  Updated: 2018-11-08  Resolved: 2018-11-08

Status: Closed
Project: MariaDB MaxScale
Component/s: N/A
Affects Version/s: 2.3.0
Fix Version/s: N/A

Type: Bug Priority: Major
Reporter: Dipti Joshi (Inactive) Assignee: markus makela
Resolution: Not a Bug Votes: 0
Labels: None


 Description   

(1) Make a connection to MaxScale configured with ReadWriteSplit and causal_reads=false
(2) Send following SQL from this connection
SET @i=1;
(3) Send following SQL repeatedly from this connection
INSERT INTO t1 @i;
SELECT * from t1;
SET @i=@i+1;
(4) Since Causal_reads is false, the "SELECT *" is not giving consistent results
(5) In a separate window, maxctrl alter service Splitter-Service causal_reads true
(6) Even though causal_reads is turned ON, the results on (3) continues to show inconsistent reads
(7) now if we disconnect and connect again, and do (2) & (3) the results are consistent

This causal_reads service parameter change did not have effect on ongoing connection.



 Comments   
Comment by markus makela [ 2018-11-08 ]

Closing as Not a Bug since it's working as intended. Runtime changes are only applied for new sessions and this is how it's been since the introduction of runtime configuration changes.

Generated at Thu Feb 08 04:12:02 UTC 2024 using Jira 8.20.16#820016-sha1:9d11dbea5f4be3d4cc21f03a88dd11d8c8687422.