Details
-
Bug
-
Status: Closed (View Workflow)
-
Blocker
-
Resolution: Fixed
-
22.08.1, 6.4.1
-
None
Description
Cluster 3 nodes, docker compose.
Steps to reproduce:
- stop primary node
- wait after failover do its stuff
- trying to select previously existing data at new primary node failing and gives such an error in debug.log:
tail -f /var/log/mariadb/columnstore/debug.log
Nov 11 12:35:58 mcs2 controllernode[409]: 58.561877 |0|0|0| E 29 CAL0000: DBRM: error: SessionManager::getSystemState() failed (network)
%%10%%
Nov 11 12:35:59 mcs2 messagequeue[409]: 59.588469 |0|0|0| E 31 CAL0000: messageqcpp::hostnameResolver Name or service not known %%10%%
Nov 11 12:36:01 mcs2 messagequeue[409]: 01.642554 |0|0|0| E 31 CAL0000: messageqcpp::hostnameResolver Name or service not known %%10%%
After manual restart mariadbd there are no errors and select\insert works as expected.
Attachments
Issue Links
- blocks
-
MCOL-5293 Replication not working after failover -restart pm1
-
- Closed
-
Build verified: 22.08.7
engine: e243a5332b8613ce0e370a503461990fefc24fce
server: d3049350bb5c61340f5a7518b155d3c9dacdcb33
buildNo: 6202
Executed test case in mustest, test advance.a000_failover.test
Steps performed.
echo Checking MaxScale status......
echo Checking ColumnStore status on mcs1......
echo Running sanity test on mcs1......
echo Checking ColumnStore status on mcs1......
echo Stopping node mcs1......
echo Checking MaxScale status......
echo Checking ColumnStore status on mcs2......
echo Starting node mcs1......
echo Checking MaxScale status......
echo Checking ColumnStore status on mcs1......
echo Create a 1g DBT2 database on mcs2......
echo Check row counts on mcs1 for replication......
echo Drop test database......
echo Ending of test.
Test result, output from the test, has been attached.