2023-02-24 16:43:28 +00:00
#!/bin/bash
OK="\tOK\t\\N\t"
FAIL="\tFAIL\t\\N\t"
2023-03-01 16:34:43 +00:00
FAILURE_CONTEXT_LINES=100
FAILURE_CONTEXT_MAX_LINE_WIDTH=300
2023-02-24 16:43:28 +00:00
function escaped()
{
# That's the simplest way I found to escape a string in bash. Yep, bash is the most convenient programming language.
# Also limit lines width just in case (too long lines are not really useful usually)
clickhouse local -S 's String' --input-format=LineAsString -q "select substr(s, 1, $FAILURE_CONTEXT_MAX_LINE_WIDTH)
from table format CustomSeparated settings format_custom_row_after_delimiter='\\\\\\\\n'"
}
2023-02-27 13:25:28 +00:00
2023-02-24 16:43:28 +00:00
function head_escaped()
{
2024-02-28 23:21:50 +00:00
head -n "$FAILURE_CONTEXT_LINES" "$1" | escaped
2023-02-24 16:43:28 +00:00
}
2023-02-27 13:25:28 +00:00
2023-02-24 16:43:28 +00:00
function unts()
{
grep -Po "[0-9][0-9]:[0-9][0-9] \K.*"
}
2023-02-27 13:25:28 +00:00
2023-02-24 16:43:28 +00:00
function trim_server_logs()
{
2024-02-29 23:21:31 +00:00
head -n "$FAILURE_CONTEXT_LINES" "/test_output/$1" | grep -Eo " \[ [0-9]+ \] \{.*" | escaped
2023-02-24 16:43:28 +00:00
}
function install_packages()
{
2024-02-28 23:21:50 +00:00
dpkg -i "$1"/clickhouse-common-static_*.deb
dpkg -i "$1"/clickhouse-common-static-dbg_*.deb
dpkg -i "$1"/clickhouse-server_*.deb
dpkg -i "$1"/clickhouse-client_*.deb
2023-02-24 16:43:28 +00:00
}
function configure()
{
# install test configs
export USE_DATABASE_ORDINARY=1
export EXPORT_S3_STORAGE_POLICIES=1
2024-08-09 14:22:33 +00:00
/repo/tests/config/install.sh
2023-02-24 16:43:28 +00:00
# avoid too slow startup
sudo cat /etc/clickhouse-server/config.d/keeper_port.xml \
| sed "s|<snapshot_distance>100000</snapshot_distance>|<snapshot_distance>10000</snapshot_distance>|" \
> /etc/clickhouse-server/config.d/keeper_port.xml.tmp
sudo mv /etc/clickhouse-server/config.d/keeper_port.xml.tmp /etc/clickhouse-server/config.d/keeper_port.xml
2023-09-22 13:47:28 +00:00
2023-11-16 07:32:11 +00:00
function randomize_config_boolean_value {
2024-02-28 23:21:50 +00:00
value=$((RANDOM % 2))
sudo cat "/etc/clickhouse-server/config.d/$2.xml" \
2023-09-22 13:47:28 +00:00
| sed "s|<$1>[01]</$1>|<$1>$value</$1>|" \
2024-02-28 23:21:50 +00:00
> "/etc/clickhouse-server/config.d/$2.xml.tmp"
sudo mv "/etc/clickhouse-server/config.d/$2.xml.tmp" "/etc/clickhouse-server/config.d/$2.xml"
2023-09-22 13:47:28 +00:00
}
2023-10-18 07:59:49 +00:00
if [[ -n "$RANDOMIZE_KEEPER_FEATURE_FLAGS" ]] && [[ "$RANDOMIZE_KEEPER_FEATURE_FLAGS" -eq 1 ]]; then
# Randomize all Keeper feature flags
2023-11-16 07:32:11 +00:00
randomize_config_boolean_value filtered_list keeper_port
randomize_config_boolean_value multi_read keeper_port
randomize_config_boolean_value check_not_exists keeper_port
randomize_config_boolean_value create_if_not_exists keeper_port
2024-09-13 08:50:28 +00:00
randomize_config_boolean_value remove_recursive keeper_port
2023-10-18 07:59:49 +00:00
fi
2023-09-22 13:47:28 +00:00
2023-02-24 16:43:28 +00:00
sudo chown clickhouse /etc/clickhouse-server/config.d/keeper_port.xml
sudo chgrp clickhouse /etc/clickhouse-server/config.d/keeper_port.xml
2023-11-16 07:32:11 +00:00
if [[ -n "$ZOOKEEPER_FAULT_INJECTION" ]] && [[ "$ZOOKEEPER_FAULT_INJECTION" -eq 1 ]]; then
randomize_config_boolean_value use_compression zookeeper_fault_injection
2024-09-25 10:58:40 +00:00
randomize_config_boolean_value use_xid_64 zookeeper_fault_injection
2023-11-16 07:32:11 +00:00
else
randomize_config_boolean_value use_compression zookeeper
2024-09-25 10:58:40 +00:00
randomize_config_boolean_value use_xid_64 zookeeper
2023-11-16 07:32:11 +00:00
fi
2023-10-19 09:59:22 +00:00
2024-05-03 17:22:37 +00:00
randomize_config_boolean_value enable_block_number_column block_number
randomize_config_boolean_value enable_block_offset_column block_number
2024-01-28 11:28:08 +00:00
2023-02-24 16:43:28 +00:00
# for clickhouse-server (via service)
echo "ASAN_OPTIONS='malloc_context_size=10 verbosity=1 allocator_release_to_os_interval_ms=10000'" >> /etc/environment
# for clickhouse-client
export ASAN_OPTIONS='malloc_context_size=10 allocator_release_to_os_interval_ms=10000'
# since we run clickhouse from root
sudo chown root: /var/lib/clickhouse
local total_mem
total_mem=$(awk '/MemTotal/ { print $(NF-1) }' /proc/meminfo) # KiB
total_mem=$(( total_mem*1024 )) # bytes
# Set maximum memory usage as half of total memory (less chance of OOM).
#
# But not via max_server_memory_usage but via max_memory_usage_for_user,
# so that we can override this setting and execute service queries, like:
# - hung check
# - show/drop database
# - ...
#
# So max_memory_usage_for_user will be a soft limit, and
# max_server_memory_usage will be hard limit, and queries that should be
# executed regardless memory limits will use max_memory_usage_for_user=0,
# instead of relying on max_untracked_memory
max_server_memory_usage_to_ram_ratio=0.5
echo "Setting max_server_memory_usage_to_ram_ratio to ${max_server_memory_usage_to_ram_ratio}"
cat > /etc/clickhouse-server/config.d/max_server_memory_usage.xml <<EOL
<clickhouse>
<max_server_memory_usage_to_ram_ratio>${max_server_memory_usage_to_ram_ratio}</max_server_memory_usage_to_ram_ratio>
</clickhouse>
EOL
local max_users_mem
max_users_mem=$((total_mem*30/100)) # 30%
2024-05-07 11:47:35 +00:00
# Similar to docker/test/fuzzer/query-fuzzer-tweaks-users.xml
2023-02-24 16:43:28 +00:00
echo "Setting max_memory_usage_for_user=$max_users_mem and max_memory_usage for queries to 10G"
2024-05-07 11:47:35 +00:00
cat > /etc/clickhouse-server/users.d/stress_test_tweaks-users.xml <<EOL
2023-02-24 16:43:28 +00:00
<clickhouse>
<profiles>
<default>
2024-05-07 11:47:35 +00:00
<max_execution_time>60</max_execution_time>
2023-02-24 16:43:28 +00:00
<max_memory_usage>10G</max_memory_usage>
<max_memory_usage_for_user>${max_users_mem}</max_memory_usage_for_user>
2024-05-07 11:47:35 +00:00
<table_function_remote_max_addresses>200</table_function_remote_max_addresses>
<constraints>
<max_execution_time>
<max>60</max>
</max_execution_time>
<max_memory_usage>
<max>10G</max>
</max_memory_usage>
<table_function_remote_max_addresses>
<max>200</max>
</table_function_remote_max_addresses>
<!-- Don't waste cycles testing the old interpreter. Spend time in the new analyzer instead -->
2024-07-12 12:49:26 +00:00
<enable_analyzer>
2024-05-07 11:47:35 +00:00
<readonly/>
2024-07-12 12:49:26 +00:00
</enable_analyzer>
2024-05-07 11:47:35 +00:00
<!-- This feature is broken, deprecated and will be removed. We don't want more reports about it -->
<allow_experimental_object_type>
<readonly/>
</allow_experimental_object_type>
2024-05-18 03:11:18 +00:00
<!-- Prevent stack overflow -->
<max_ast_depth>
<readonly/>
</max_ast_depth>
2024-05-07 11:47:35 +00:00
</constraints>
2023-02-24 16:43:28 +00:00
</default>
</profiles>
</clickhouse>
EOL
cat > /etc/clickhouse-server/config.d/core.xml <<EOL
<clickhouse>
<core_dump>
<!-- 100GiB -->
<size_limit>107374182400</size_limit>
</core_dump>
<!-- NOTE: no need to configure core_path,
since clickhouse is not started as daemon (via clickhouse start)
-->
<core_path>$PWD</core_path>
</clickhouse>
EOL
}
2024-02-29 23:21:31 +00:00
function stop_server()
2023-02-24 16:43:28 +00:00
{
2024-02-29 23:21:31 +00:00
local max_tries=90
local check_hang=true
2023-02-24 16:43:28 +00:00
local pid
# Preserve the pid, since the server can hung after the PID will be deleted.
pid="$(cat /var/run/clickhouse-server/clickhouse-server.pid)"
2024-11-27 19:27:31 +00:00
# FIXME: workaround for slow shutdown of Distributed tables (due to sequential tables shutdown)
# Refs: https://github.com/ClickHouse/ClickHouse/issues/72557
clickhouse client -q "SYSTEM STOP DISTRIBUTED SENDS" ||:
2023-02-24 16:43:28 +00:00
clickhouse stop --max-tries "$max_tries" --do-not-kill && return
2024-02-28 23:21:50 +00:00
if [ "$check_hang" == true ]
2023-02-27 13:25:28 +00:00
then
2023-02-24 16:43:28 +00:00
# We failed to stop the server with SIGTERM. Maybe it hang, let's collect stacktraces.
2023-04-01 12:26:00 +00:00
# Add a special status just in case, so it will be possible to find in the CI DB
echo -e "Warning: server did not stop yet$OK" >> /test_output/test_results.tsv
2023-02-24 16:43:28 +00:00
kill -TERM "$(pidof gdb)" ||:
sleep 5
2023-04-01 12:26:00 +00:00
# The server could finally stop while we were terminating gdb, let's recheck if it's still running
2024-02-28 23:21:50 +00:00
kill -s 0 "$pid" || return
2023-04-01 12:26:00 +00:00
echo -e "Possible deadlock on shutdown (see gdb.log)$FAIL" >> /test_output/test_results.tsv
2023-02-24 16:43:28 +00:00
echo "thread apply all backtrace (on stop)" >> /test_output/gdb.log
timeout 30m gdb -batch -ex 'thread apply all backtrace' -p "$pid" | ts '%Y-%m-%d %H:%M:%S' >> /test_output/gdb.log
clickhouse stop --force
2023-10-27 09:16:00 +00:00
else
echo -e "Warning: server did not stop yet$OK" >> /test_output/test_results.tsv
clickhouse stop --force
2023-02-24 16:43:28 +00:00
fi
}
2024-02-29 23:21:31 +00:00
function start_server()
2023-02-24 16:43:28 +00:00
{
counter=0
2024-02-29 23:21:31 +00:00
max_attempt=120
2023-02-24 16:43:28 +00:00
until clickhouse-client --query "SELECT 1"
do
2024-02-29 23:21:31 +00:00
if [ "$counter" -gt "$max_attempt" ]
2023-02-24 16:43:28 +00:00
then
echo "Cannot start clickhouse-server"
rg --text "<Error>.*Application" /var/log/clickhouse-server/clickhouse-server.log > /test_output/application_errors.txt ||:
echo -e "Cannot start clickhouse-server$FAIL$(trim_server_logs application_errors.txt)" >> /test_output/test_results.tsv
cat /var/log/clickhouse-server/stdout.log
tail -n100 /var/log/clickhouse-server/stderr.log
tail -n100000 /var/log/clickhouse-server/clickhouse-server.log | rg -F -v -e '<Warning> RaftInstance:' -e '<Information> RaftInstance' | tail -n100
break
fi
# use root to match with current uid
clickhouse start --user root >/var/log/clickhouse-server/stdout.log 2>>/var/log/clickhouse-server/stderr.log
sleep 0.5
counter=$((counter + 1))
done
2023-06-05 18:21:40 +00:00
attach_gdb_to_clickhouse
2023-02-24 16:43:28 +00:00
}
function check_server_start()
{
clickhouse-client --query "SELECT 'Server successfully started', 'OK', NULL, ''" >> /test_output/test_results.tsv \
|| (rg --text "<Error>.*Application" /var/log/clickhouse-server/clickhouse-server.log > /test_output/application_errors.txt \
&& echo -e "Server failed to start (see application_errors.txt and clickhouse-server.clean.log)$FAIL$(trim_server_logs application_errors.txt)" \
>> /test_output/test_results.tsv)
# Remove file application_errors.txt if it's empty
[ -s /test_output/application_errors.txt ] || rm /test_output/application_errors.txt
}
function check_logs_for_critical_errors()
{
# Sanitizer asserts
2024-08-04 14:09:48 +00:00
sed -n '/WARNING:.*anitizer/,/^$/p' /var/log/clickhouse-server/stderr*.log >> /test_output/tmp
2023-02-24 16:43:28 +00:00
rg -Fav -e "ASan doesn't fully support makecontext/swapcontext functions" -e "DB::Exception" /test_output/tmp > /dev/null \
&& echo -e "Sanitizer assert (in stderr.log)$FAIL$(head_escaped /test_output/tmp)" >> /test_output/test_results.tsv \
|| echo -e "No sanitizer asserts$OK" >> /test_output/test_results.tsv
rm -f /test_output/tmp
# OOM
rg -Fa " <Fatal> Application: Child process was terminated by signal 9" /var/log/clickhouse-server/clickhouse-server*.log > /dev/null \
&& echo -e "Signal 9 in clickhouse-server.log$FAIL" >> /test_output/test_results.tsv \
|| echo -e "No OOM messages in clickhouse-server.log$OK" >> /test_output/test_results.tsv
# Logical errors
rg -Fa "Code: 49. DB::Exception: " /var/log/clickhouse-server/clickhouse-server*.log > /test_output/logical_errors.txt \
&& echo -e "Logical error thrown (see clickhouse-server.log or logical_errors.txt)$FAIL$(head_escaped /test_output/logical_errors.txt)" >> /test_output/test_results.tsv \
|| echo -e "No logical errors$OK" >> /test_output/test_results.tsv
# Remove file logical_errors.txt if it's empty
[ -s /test_output/logical_errors.txt ] || rm /test_output/logical_errors.txt
2024-10-30 09:16:39 +00:00
# ignore:
# - a.myext which is used in 02724_database_s3.sh and does not exist
# - "DistributedCacheTCPHandler" and "caller id: None:DistribCache" because they happen inside distributed cache server
2024-10-30 13:53:25 +00:00
# - "ReadBufferFromDistributedCache", "AsynchronousBoundedReadBuffer", "ReadBufferFromS3", "ReadBufferFromAzureBlobStorage"
# exceptions printed internally by a buffer, exception will be rethrown and handled correctly
rg --text "Code: 499.*The specified key does not exist" /var/log/clickhouse-server/clickhouse-server*.log | grep -v -e "a.myext" -e "DistributedCacheTCPHandler" -e "ReadBufferFromDistributedCache" -e "ReadBufferFromS3" -e "ReadBufferFromAzureBlobStorage" -e "AsynchronousBoundedReadBuffer" -e "caller id: None:DistribCache" > /test_output/no_such_key_errors.txt \
2023-02-24 16:43:28 +00:00
&& echo -e "S3_ERROR No such key thrown (see clickhouse-server.log or no_such_key_errors.txt)$FAIL$(trim_server_logs no_such_key_errors.txt)" >> /test_output/test_results.tsv \
|| echo -e "No lost s3 keys$OK" >> /test_output/test_results.tsv
2024-01-04 12:45:17 +00:00
rg -Fa "it is lost forever" /var/log/clickhouse-server/clickhouse-server*.log | grep 'SharedMergeTreePartCheckThread' > /dev/null \
&& echo -e "Lost forever for SharedMergeTree$FAIL" >> /test_output/test_results.tsv \
|| echo -e "No SharedMergeTree lost forever in clickhouse-server.log$OK" >> /test_output/test_results.tsv
2023-02-24 16:43:28 +00:00
# Remove file no_such_key_errors.txt if it's empty
[ -s /test_output/no_such_key_errors.txt ] || rm /test_output/no_such_key_errors.txt
2024-08-27 22:42:14 +00:00
# Crash. This must have fewer '#'s than the command below, otherwise the command below will match
# the echo of this command (if set -x is enabled, and this script's stdout is sent
# to /test_output/run.log).
rg -Fa "#######################################" /var/log/clickhouse-server/clickhouse-server*.log > /dev/null \
2023-02-24 16:43:28 +00:00
&& echo -e "Killed by signal (in clickhouse-server.log)$FAIL" >> /test_output/test_results.tsv \
|| echo -e "Not crashed$OK" >> /test_output/test_results.tsv
# It also checks for crash without stacktrace (printed by watchdog)
rg -Fa " <Fatal> " /var/log/clickhouse-server/clickhouse-server*.log > /test_output/fatal_messages.txt \
&& echo -e "Fatal message in clickhouse-server.log (see fatal_messages.txt)$FAIL$(trim_server_logs fatal_messages.txt)" >> /test_output/test_results.tsv \
|| echo -e "No fatal messages in clickhouse-server.log$OK" >> /test_output/test_results.tsv
# Remove file fatal_messages.txt if it's empty
[ -s /test_output/fatal_messages.txt ] || rm /test_output/fatal_messages.txt
2024-09-23 09:38:06 +00:00
rg -Faz "########################################" /test_output/* | rg -v "rg -Faz " > /dev/null \
2023-02-24 16:43:28 +00:00
&& echo -e "Killed by signal (output files)$FAIL" >> /test_output/test_results.tsv
function get_gdb_log_context()
{
rg -A50 -Fa " received signal " /test_output/gdb.log | head_escaped
}
rg -Fa " received signal " /test_output/gdb.log > /dev/null \
&& echo -e "Found signal in gdb.log$FAIL$(get_gdb_log_context)" >> /test_output/test_results.tsv
dmesg -T > /test_output/dmesg.log
# OOM in dmesg -- those are real
grep -q -F -e 'Out of memory: Killed process' -e 'oom_reaper: reaped process' -e 'oom-kill:constraint=CONSTRAINT_NONE' /test_output/dmesg.log \
&& echo -e "OOM in dmesg$FAIL$(head_escaped /test_output/dmesg.log)" >> /test_output/test_results.tsv \
|| echo -e "No OOM in dmesg$OK" >> /test_output/test_results.tsv
}
function collect_query_and_trace_logs()
{
2024-04-26 17:16:27 +00:00
for table in query_log trace_log metric_log
2023-02-24 16:43:28 +00:00
do
2024-08-02 10:46:37 +00:00
# Don't ignore errors here, it leads to ignore sanitizer reports when running clickhouse-local
clickhouse-local --config-file=/etc/clickhouse-server/config.xml --only-system-tables -q "select * from system.$table format TSVWithNamesAndTypes" | zstd --threads=0 > /test_output/$table.tsv.zst
2023-02-24 16:43:28 +00:00
done
}
2023-08-18 09:17:32 +00:00
# vi: ft=bash