[MXS-873] Changing server status via maxadmin is not atomic Created: 2016-09-20  Updated: 2016-12-13  Resolved: 2016-12-13

Status: Closed
Project: MariaDB MaxScale
Component/s: maxadmin
Affects Version/s: 2.0.1
Fix Version/s: 2.1.0

Type: Bug Priority: Major
Reporter: markus makela Assignee: Esa Korhonen
Resolution: Fixed Votes: 0
Labels: None

Sprint: 2016-23

 Description   

Setting or clearing the server states via maxadmin is not atomic and the setting/clearing of the state can be lost if another thread is changing the server's status at the same time. The changes to the server state should be done under a lock.


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