[Koha-bugs] [Bug 27078] Starman hanging in 3-node Koha cluster when 1 node goes offline.

[bugzilla-daemon at bugs.koha-community.org]

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=27078

--- Comment #8 from David Cook <dcook at prosentient.com.au> ---
Another suggestion would be to look into whatever logging/monitoring you have
for Elasticsearch, MariaDB Galera, and Memcached. 

If I were you, I'd be checking those logs, when I experience the Koha latency. 

Going back to my previous example, I had a Keycloak cluster that had 2 active
nodes and 2 dead nodes. Requests were only going to the 2 active nodes, but
they were struggling, because they were obsessing over checking the 2 dead
nodes. 

Admittedly, that doesn't always happen. It was a bit of a fluke that I noticed
one time, but it was interesting. 

Looking at Galera... it looks like there's a default 5 second timeout
inactivity:
https://galeracluster.com/library/documentation/galera-parameters.html#evs-suspect-timeout. 

After you power off/disconnect Node A, does the performance degradation stay
for a long time? Or does it resolve itself after X minutes?

-- 
You are receiving this mail because:
You are watching all bug changes.
You are the assignee for the bug.