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

Move wait_for_maxscale functionality inside MaxScale

Browse Source 
By exposing a (currently undocumented) debug endpoint that lets one
monitor interval pass, we make the reuse of the monitor waiting
functionality a lot easier. With it, when MaxScale is started by the test
framework it knows that at least one monitor interval will have passed for
all monitors and that the system is ready to accept queries.
This commit is contained in:
Markus Mäkelä
2018-11-06 13:58:44 +02:00
parent a53dbeec57
commit 00d0ec5f8e
5 changed files with 43 additions and 53 deletions
Download Patch File Download Diff File Expand all files Collapse all files

8
server/core/resource.cc
View File

@ -733,6 +733,11 @@ HttpResponse cb_unix_user(const HttpRequest& request)
return HttpResponse(MHD_HTTP_OK, admin_user_to_json(request.host(), user.c_str(), USER_TYPE_UNIX));
}
HttpResponse cb_monitor_wait(const HttpRequest& request)
{
monitor_debug_wait();
return HttpResponse(MHD_HTTP_OK);
}
HttpResponse cb_create_user(const HttpRequest& request)
{
mxb_assert(request.get_json());
@ -976,6 +981,9 @@ public:
m_get.push_back(SResource(new Resource(cb_inet_user, 3, "users", "inet", ":inetuser")));
m_get.push_back(SResource(new Resource(cb_unix_user, 3, "users", "unix", ":unixuser")));
/** Debug utility endpoints */
m_get.push_back(SResource(new Resource(cb_monitor_wait, 3, "maxscale", "debug", "monitor_wait")));
/** Create new resources */
m_post.push_back(SResource(new Resource(cb_create_server, 1, "servers")));
m_post.push_back(SResource(new Resource(cb_create_monitor, 1, "monitors")));