[MXS-493] SIGFPE when weightby parameter is 0 and using LEAST_GLOBAL_CONNECTIONS Created: 2015-11-30  Updated: 2015-12-02  Resolved: 2015-11-30

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

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


 Description   

If configured with slave_selection_criteria=LEAST_GLOBAL_CONNECTIONS and at least one server with a calculated weight of 0, MaxScale will crash when a client connects to the service. This is caused by the division by zero when the weight of the server is used to calculate which servers to connect to.



 Comments   
Comment by markus makela [ 2015-11-30 ]

Fixed by always assigning a valid weight value to all servers.

Comment by markus makela [ 2015-12-02 ]

Fixed in commit 02da87f7378053e6386a8b28aa8cbd4e50fc0f66.

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