hcq/MaxScale
hcq/MaxScale
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

MXS-2275 Trigger cluster check if node is down

Browse Source 
The likely reason for a node being down is that some cluster level
modifications have been performed. Consequently a cluster check should
be triggered in that case.
This commit is contained in:
Johan Wikman 2019-02-01 14:51:32 +02:00
parent 3eb7d89c80
commit 692dd195ec
1 changed files with 21 additions and 11 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

32
server/modules/monitor/clustrixmon/clustrixmonitor.cc
View File

@ -609,25 +609,35 @@ bool ClustrixMonitor::check_http(Call::action_t action)
case http::Async::READY:
{
// There are as many results as there are nodes,
// and the results are in node order.
const vector<http::Result>& results = m_http.results();
mxb_assert(results.size() == m_nodes.size());
auto it = m_nodes.begin();
for_each(results.begin(), results.end(),
[&it](const http::Result& result) {
bool running = false;
for (const auto& result : results)
{
bool running = (result.code == 200); // HTTP OK
if (result.code == 200)
{
running = true;
}
ClustrixNode& node = it->second;
auto& node_info = it->second;
node.set_running(running);
node_info.set_running(running);
if (!running)
{
// We have to explicitly check whether the node is to be
// considered down, as the value of `health_check_threshold`
// defines how quickly a node should be considered down.
if (!node.is_running())
{
// Ok, the node is down. Trigger a cluster check at next tick.
m_last_cluster_check = 0;
}
}
++it;
});
++it;
}
}
break;