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

Improve cdc_client stability

Browse Source 
It was possible that the query thread got stuck and never saw the updated
insert_val. Making the variable atomic as well as sleeping in between
queries should prevent it.
This commit is contained in:
Markus Mäkelä
2020-01-16 15:51:17 +02:00
parent 9bd692c7d3
commit b6dc67f1b9
1 changed files with 9 additions and 2 deletions
Download Patch File Download Diff File Expand all files Collapse all files

11
maxscale-system-test/cdc_client.cpp
View File

@ -20,11 +20,14 @@
#include "maxinfo_func.h"
#include "sql_t1.h"
#include <sys/epoll.h>
#include <atomic>
#include <thread>
#include <chrono>
using namespace std;
char reg_str[] = "REGISTER UUID=XXX-YYY_YYY, TYPE=JSON";
char req_str[] = "REQUEST-DATA test.t1";
int insert_val = 0;
std::atomic<int> insert_val {0};
bool exit_flag = false;
void* query_thread(void* ptr);
@ -225,10 +228,14 @@ void* query_thread(void* ptr)
if (insert_val != 0)
{
char str[256];
sprintf(str, "INSERT INTO t1 VALUES (%d, %d)", insert_val, insert_val + 100);
sprintf(str, "INSERT INTO t1 VALUES (%d, %d)", insert_val.load(), insert_val.load() + 100);
insert_val = 0;
execute_query(Test->repl->nodes[0], "%s", str);
}
else
{
std::this_thread::sleep_for(std::chrono::milliseconds(100));
}
}
Test->repl->close_connections();