-
Notifications
You must be signed in to change notification settings - Fork 6.8k
-
Notifications
You must be signed in to change notification settings - Fork 6.8k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
SYSTEM FLUSH LOGS ON CLUSTER
does not throw SYNTAX_ERROR
#44264
Labels
Comments
|
#! /bin/bash
set -x
export ENDPOINT=
export PASSWORD=
for NUMBER in {1..1000}
do
export ID="rep_${NUMBER}"
~/clickhouse client --host $ENDPOINT --user default --password $PASSWORD --secure --database smoke --query "SELECT * FROM numbers(10000) FORMAT Null" --query_id ${ID}
~/clickhouse client --host $ENDPOINT --user default --password $PASSWORD --secure --database smoke --query "SYSTEM FLUSH LOGS ON CLUSTER"
for RUN in {1..10}
do
RES=$(~/clickhouse client --host $ENDPOINT --user default --password $PASSWORD --secure --database smoke --query "select count() from clusterAllReplicas(default, system.query_log) where event_date=today() and type='QueryFinish' and query_id='${ID}'")
echo $ID " " $RES
if (( $RES > 0 ))
then
break;
else if (( $RES == 0 ))
then
echo "REPRODUCED";
exit
fi
fi
done
done
|
tavplubix
changed the title
Dec 19, 2022
SYSTEM FLUSH LOGS ON CLUSTER
works but applies to initiator node onlySYSTEM FLUSH LOGS ON CLUSTER
does not throw SYNTAX_ERROR
A cluster name is missing |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Describe the unexpected behaviour
If
ON CLUSTER
is unsupported it should return error.I would expect logs to be flushed on all replicas.
If it is running asynchronously, wee need synchronous version.
How to reproduce
SELECT 1
to node1SYSTEM FLUSH LOGS ON CLUSTER
to node2SELECT * from system.query_log
from node 1Expected behavior
Query log on node1 should be flushed.
The text was updated successfully, but these errors were encountered: