Slanje Nginx json zapisa pomoću Vectora u Clickhouse i Elasticsearch

vektor, dizajniran za prikupljanje, transformaciju i slanje podataka dnevnika, metrike i događaja.

→ Github

Budući da je napisan na jeziku Rust, karakteriziraju ga visoke performanse i niska potrošnja RAM-a u usporedbi s analogama. Osim toga, velika se pažnja posvećuje funkcijama vezanim uz ispravnost, posebice mogućnosti spremanja neposlanih događaja u međuspremnik na disku i rotiranja datoteka.

Arhitektonski, Vector je usmjerivač događaja koji prima poruke od jednog ili više njih izvori, opcionalno primjenom preko ovih poruka transformacije, i slanje ih jednom ili više njih odvodi.

Vector je zamjena za filebeat i logstash, može djelovati u obje uloge (primati i slati zapise), više detalja o njima Online.

Ako je u Logstashu lanac izgrađen kao ulaz → filter → izlaz onda u Vectoru jest izvori → transformira → sudoperi

Primjeri se mogu naći u dokumentaciji.

Ova je uputa revidirana uputa iz Vjačeslav Rahinski. Izvorne upute sadrže geoip obradu. Prilikom testiranja geoip-a s interne mreže, vektor je dao pogrešku.

Aug 05 06:25:31.889 DEBUG transform{name=nginx_parse_rename_fields type=rename_fields}: vector::transforms::rename_fields: Field did not exist field=«geoip.country_name» rate_limit_secs=30

Ako netko treba obraditi geoip, pogledajte originalne upute od Vjačeslav Rahinski.

Konfigurirat ćemo kombinaciju Nginx (Pristupni zapisnici) → Vektor (Klijent | Filebeat) → Vektor (Poslužitelj | Logstash) → zasebno u Clickhouseu i posebno u Elasticsearchu. Instalirat ćemo 4 servera. Iako ga možete zaobići s 3 poslužitelja.

Shema je otprilike ovakva.

Onemogućite Selinux na svim svojim poslužiteljima

sed -i 's/^SELINUX=.*/SELINUX=disabled/g' /etc/selinux/config
reboot

Instaliramo emulator HTTP poslužitelja + pomoćne programe na sve poslužitelje

Kao emulator HTTP poslužitelja koristit ćemo se nodejs-stub-poslužitelj iz Maksim Ignatenko

Nodejs-stub-server nema rpm. Ovdje stvoriti rpm za to. rpm će se kompajlirati pomoću Fedora Copr

Dodajte repozitorij antonpatsev/nodejs-stub-server

yum -y install yum-plugin-copr epel-release
yes | yum copr enable antonpatsev/nodejs-stub-server

Instalirajte nodejs-stub-server, Apache benchmark i screen terminal multiplexer na svim poslužiteljima

yum -y install stub_http_server screen mc httpd-tools screen

Ispravio sam vrijeme odgovora stub_http_server u datoteci /var/lib/stub_http_server/stub_http_server.js tako da ima više zapisa.

var max_sleep = 10;

Pokrenimo stub_http_server.

systemctl start stub_http_server
systemctl enable stub_http_server

Clickhouse instalacija na poslužitelju 3

ClickHouse koristi skup instrukcija SSE 4.2, pa osim ako nije drugačije navedeno, podrška za njega u korištenom procesoru postaje dodatni sistemski zahtjev. Evo naredbe za provjeru podržava li trenutni procesor SSE 4.2:

grep -q sse4_2 /proc/cpuinfo && echo "SSE 4.2 supported" || echo "SSE 4.2 not supported"

Prvo morate spojiti službeni repozitorij:

sudo yum install -y yum-utils
sudo rpm --import https://repo.clickhouse.tech/CLICKHOUSE-KEY.GPG
sudo yum-config-manager --add-repo https://repo.clickhouse.tech/rpm/stable/x86_64

Za instaliranje paketa morate pokrenuti sljedeće naredbe:

sudo yum install -y clickhouse-server clickhouse-client

Dopusti clickhouse-serveru da sluša mrežnu karticu u datoteci /etc/clickhouse-server/config.xml

<listen_host>0.0.0.0</listen_host>

Promjena razine zapisivanja iz praćenja u otklanjanje pogrešaka

otkloniti neispravnost

Standardne postavke kompresije:

min_compress_block_size  65536
max_compress_block_size  1048576

Za aktiviranje Zstd kompresije, savjetovano je da se ne dira konfiguracija, već da se koristi DDL.

Nisam mogao pronaći kako koristiti zstd kompresiju putem DDL-a u Googleu. Pa sam ostavio kako jest.

Kolege koji koriste zstd kompresiju u Clickhouseu neka podijele upute.

Za pokretanje poslužitelja kao demona, pokrenite:

service clickhouse-server start

Sada prijeđimo na postavljanje Clickhousea

Idite u Clickhouse

clickhouse-client -h 172.26.10.109 -m

172.26.10.109 — IP poslužitelja na kojem je instaliran Clickhouse.

Kreirajmo vektorsku bazu podataka

CREATE DATABASE vector;

Provjerimo postoji li baza podataka.

show databases;

Napravite tablicu vector.logs.

/* Это таблица где хранятся логи как есть */

CREATE TABLE vector.logs
(
    `node_name` String,
    `timestamp` DateTime,
    `server_name` String,
    `user_id` String,
    `request_full` String,
    `request_user_agent` String,
    `request_http_host` String,
    `request_uri` String,
    `request_scheme` String,
    `request_method` String,
    `request_length` UInt64,
    `request_time` Float32,
    `request_referrer` String,
    `response_status` UInt16,
    `response_body_bytes_sent` UInt64,
    `response_content_type` String,
    `remote_addr` IPv4,
    `remote_port` UInt32,
    `remote_user` String,
    `upstream_addr` IPv4,
    `upstream_port` UInt32,
    `upstream_bytes_received` UInt64,
    `upstream_bytes_sent` UInt64,
    `upstream_cache_status` String,
    `upstream_connect_time` Float32,
    `upstream_header_time` Float32,
    `upstream_response_length` UInt64,
    `upstream_response_time` Float32,
    `upstream_status` UInt16,
    `upstream_content_type` String,
    INDEX idx_http_host request_http_host TYPE set(0) GRANULARITY 1
)
ENGINE = MergeTree()
PARTITION BY toYYYYMMDD(timestamp)
ORDER BY timestamp
TTL timestamp + toIntervalMonth(1)
SETTINGS index_granularity = 8192;

Provjeravamo jesu li tablice izrađene. Idemo pokrenuti clickhouse-client i podnijeti zahtjev.

Idemo u vektorsku bazu podataka.

use vector;

Ok.

0 rows in set. Elapsed: 0.001 sec.

Pogledajmo tablice.

show tables;

┌─name────────────────┐
│ logs                │
└─────────────────────┘

Instaliranje elasticsearch na 4. poslužitelj za slanje istih podataka Elasticsearchu za usporedbu s Clickhouseom

Dodajte javni rpm ključ

rpm --import https://artifacts.elastic.co/GPG-KEY-elasticsearch

Kreirajmo 2 spremišta:

/etc/yum.repos.d/elasticsearch.repo

[elasticsearch]
name=Elasticsearch repository for 7.x packages
baseurl=https://artifacts.elastic.co/packages/7.x/yum
gpgcheck=1
gpgkey=https://artifacts.elastic.co/GPG-KEY-elasticsearch
enabled=0
autorefresh=1
type=rpm-md

/etc/yum.repos.d/kibana.repo

[kibana-7.x]
name=Kibana repository for 7.x packages
baseurl=https://artifacts.elastic.co/packages/7.x/yum
gpgcheck=1
gpgkey=https://artifacts.elastic.co/GPG-KEY-elasticsearch
enabled=1
autorefresh=1
type=rpm-md

Instalirajte elasticsearch i kibanu

yum install -y kibana elasticsearch

Budući da će biti u 1 kopiji, trebate dodati sljedeće u datoteku /etc/elasticsearch/elasticsearch.yml:

discovery.type: single-node

Kako bi taj vektor mogao slati podatke u elasticsearch s drugog poslužitelja, promijenimo network.host.

network.host: 0.0.0.0

Za povezivanje s kibanom promijenite parametar server.host u datoteci /etc/kibana/kibana.yml

server.host: "0.0.0.0"

Staro i uključite elasticsearch u automatsko pokretanje

systemctl enable elasticsearch
systemctl start elasticsearch

i kibana

systemctl enable kibana
systemctl start kibana

Konfiguriranje Elasticsearch za način rada s jednim čvorom 1 fragment, 0 replika. Najvjerojatnije ćete imati klaster velikog broja poslužitelja i ne morate to raditi.

Za buduće indekse ažurirajte zadani predložak:

curl -X PUT http://localhost:9200/_template/default -H 'Content-Type: application/json' -d '{"index_patterns": ["*"],"order": -1,"settings": {"number_of_shards": "1","number_of_replicas": "0"}}' 

Instalacija vektor kao zamjena za Logstash na serveru 2

yum install -y https://packages.timber.io/vector/0.9.X/vector-x86_64.rpm mc httpd-tools screen

Postavimo Vector kao zamjenu za Logstash. Uređivanje datoteke /etc/vector/vector.toml

# /etc/vector/vector.toml

data_dir = "/var/lib/vector"

[sources.nginx_input_vector]
  # General
  type                          = "vector"
  address                       = "0.0.0.0:9876"
  shutdown_timeout_secs         = 30

[transforms.nginx_parse_json]
  inputs                        = [ "nginx_input_vector" ]
  type                          = "json_parser"

[transforms.nginx_parse_add_defaults]
  inputs                        = [ "nginx_parse_json" ]
  type                          = "lua"
  version                       = "2"

  hooks.process = """
  function (event, emit)

    function split_first(s, delimiter)
      result = {};
      for match in (s..delimiter):gmatch("(.-)"..delimiter) do
          table.insert(result, match);
      end
      return result[1];
    end

    function split_last(s, delimiter)
      result = {};
      for match in (s..delimiter):gmatch("(.-)"..delimiter) do
          table.insert(result, match);
      end
      return result[#result];
    end

    event.log.upstream_addr             = split_first(split_last(event.log.upstream_addr, ', '), ':')
    event.log.upstream_bytes_received   = split_last(event.log.upstream_bytes_received, ', ')
    event.log.upstream_bytes_sent       = split_last(event.log.upstream_bytes_sent, ', ')
    event.log.upstream_connect_time     = split_last(event.log.upstream_connect_time, ', ')
    event.log.upstream_header_time      = split_last(event.log.upstream_header_time, ', ')
    event.log.upstream_response_length  = split_last(event.log.upstream_response_length, ', ')
    event.log.upstream_response_time    = split_last(event.log.upstream_response_time, ', ')
    event.log.upstream_status           = split_last(event.log.upstream_status, ', ')

    if event.log.upstream_addr == "" then
        event.log.upstream_addr = "127.0.0.1"
    end

    if (event.log.upstream_bytes_received == "-" or event.log.upstream_bytes_received == "") then
        event.log.upstream_bytes_received = "0"
    end

    if (event.log.upstream_bytes_sent == "-" or event.log.upstream_bytes_sent == "") then
        event.log.upstream_bytes_sent = "0"
    end

    if event.log.upstream_cache_status == "" then
        event.log.upstream_cache_status = "DISABLED"
    end

    if (event.log.upstream_connect_time == "-" or event.log.upstream_connect_time == "") then
        event.log.upstream_connect_time = "0"
    end

    if (event.log.upstream_header_time == "-" or event.log.upstream_header_time == "") then
        event.log.upstream_header_time = "0"
    end

    if (event.log.upstream_response_length == "-" or event.log.upstream_response_length == "") then
        event.log.upstream_response_length = "0"
    end

    if (event.log.upstream_response_time == "-" or event.log.upstream_response_time == "") then
        event.log.upstream_response_time = "0"
    end

    if (event.log.upstream_status == "-" or event.log.upstream_status == "") then
        event.log.upstream_status = "0"
    end

    emit(event)

  end
  """

[transforms.nginx_parse_remove_fields]
    inputs                              = [ "nginx_parse_add_defaults" ]
    type                                = "remove_fields"
    fields                              = ["data", "file", "host", "source_type"]

[transforms.nginx_parse_coercer]

    type                                = "coercer"
    inputs                              = ["nginx_parse_remove_fields"]

    types.request_length = "int"
    types.request_time = "float"

    types.response_status = "int"
    types.response_body_bytes_sent = "int"

    types.remote_port = "int"

    types.upstream_bytes_received = "int"
    types.upstream_bytes_send = "int"
    types.upstream_connect_time = "float"
    types.upstream_header_time = "float"
    types.upstream_response_length = "int"
    types.upstream_response_time = "float"
    types.upstream_status = "int"

    types.timestamp = "timestamp"

[sinks.nginx_output_clickhouse]
    inputs   = ["nginx_parse_coercer"]
    type     = "clickhouse"

    database = "vector"
    healthcheck = true
    host = "http://172.26.10.109:8123" #  Адрес Clickhouse
    table = "logs"

    encoding.timestamp_format = "unix"

    buffer.type = "disk"
    buffer.max_size = 104900000
    buffer.when_full = "block"

    request.in_flight_limit = 20

[sinks.elasticsearch]
    type = "elasticsearch"
    inputs   = ["nginx_parse_coercer"]
    compression = "none"
    healthcheck = true
    # 172.26.10.116 - сервер где установен elasticsearch
    host = "http://172.26.10.116:9200" 
    index = "vector-%Y-%m-%d"

Možete prilagoditi odjeljak transforms.nginx_parse_add_defaults.

Kao Vjačeslav Rahinski koristi ove konfiguracije za mali CDN i može postojati nekoliko vrijednosti u upstream_*

Na primjer:

"upstream_addr": "128.66.0.10:443, 128.66.0.11:443, 128.66.0.12:443"
"upstream_bytes_received": "-, -, 123"
"upstream_status": "502, 502, 200"

Ako ovo nije vaša situacija, onda se ovaj odjeljak može pojednostaviti

Kreirajmo servisne postavke za systemd /etc/systemd/system/vector.service

# /etc/systemd/system/vector.service

[Unit]
Description=Vector
After=network-online.target
Requires=network-online.target

[Service]
User=vector
Group=vector
ExecStart=/usr/bin/vector
ExecReload=/bin/kill -HUP $MAINPID
Restart=no
StandardOutput=syslog
StandardError=syslog
SyslogIdentifier=vector

[Install]
WantedBy=multi-user.target

Nakon što izradite tablice, možete pokrenuti Vector

systemctl enable vector
systemctl start vector

Vektorski dnevnici mogu se vidjeti ovako:

journalctl -f -u vector

U zapisnicima bi trebali postojati ovakvi unosi

INFO vector::topology::builder: Healthcheck: Passed.
INFO vector::topology::builder: Healthcheck: Passed.

Na klijentu (Web poslužitelj) - 1. poslužitelj

Na poslužitelju s nginxom trebate onemogućiti ipv6, budući da tablica zapisa u clickhouseu koristi polje upstream_addr IPv4, budući da ne koristim ipv6 unutar mreže. Ako ipv6 nije isključen, javljat će se pogreške:

DB::Exception: Invalid IPv4 value.: (while read the value of key upstream_addr)

Možda čitatelji, dodajte podršku za ipv6.

Napravite datoteku /etc/sysctl.d/98-disable-ipv6.conf

net.ipv6.conf.all.disable_ipv6 = 1
net.ipv6.conf.default.disable_ipv6 = 1
net.ipv6.conf.lo.disable_ipv6 = 1

Primjena postavki

sysctl --system

Instalirajmo nginx.

Dodana datoteka nginx spremišta /etc/yum.repos.d/nginx.repo

[nginx-stable]
name=nginx stable repo
baseurl=http://nginx.org/packages/centos/$releasever/$basearch/
gpgcheck=1
enabled=1
gpgkey=https://nginx.org/keys/nginx_signing.key
module_hotfixes=true

Instalirajte nginx paket

yum install -y nginx

Prvo moramo konfigurirati format dnevnika u Nginxu u datoteci /etc/nginx/nginx.conf

user  nginx;
# you must set worker processes based on your CPU cores, nginx does not benefit from setting more than that
worker_processes auto; #some last versions calculate it automatically

# number of file descriptors used for nginx
# the limit for the maximum FDs on the server is usually set by the OS.
# if you don't set FD's then OS settings will be used which is by default 2000
worker_rlimit_nofile 100000;

error_log  /var/log/nginx/error.log warn;
pid        /var/run/nginx.pid;

# provides the configuration file context in which the directives that affect connection processing are specified.
events {
    # determines how much clients will be served per worker
    # max clients = worker_connections * worker_processes
    # max clients is also limited by the number of socket connections available on the system (~64k)
    worker_connections 4000;

    # optimized to serve many clients with each thread, essential for linux -- for testing environment
    use epoll;

    # accept as many connections as possible, may flood worker connections if set too low -- for testing environment
    multi_accept on;
}

http {
    include       /etc/nginx/mime.types;
    default_type  application/octet-stream;

    log_format  main  '$remote_addr - $remote_user [$time_local] "$request" '
                      '$status $body_bytes_sent "$http_referer" '
                      '"$http_user_agent" "$http_x_forwarded_for"';

log_format vector escape=json
    '{'
        '"node_name":"nginx-vector",'
        '"timestamp":"$time_iso8601",'
        '"server_name":"$server_name",'
        '"request_full": "$request",'
        '"request_user_agent":"$http_user_agent",'
        '"request_http_host":"$http_host",'
        '"request_uri":"$request_uri",'
        '"request_scheme": "$scheme",'
        '"request_method":"$request_method",'
        '"request_length":"$request_length",'
        '"request_time": "$request_time",'
        '"request_referrer":"$http_referer",'
        '"response_status": "$status",'
        '"response_body_bytes_sent":"$body_bytes_sent",'
        '"response_content_type":"$sent_http_content_type",'
        '"remote_addr": "$remote_addr",'
        '"remote_port": "$remote_port",'
        '"remote_user": "$remote_user",'
        '"upstream_addr": "$upstream_addr",'
        '"upstream_bytes_received": "$upstream_bytes_received",'
        '"upstream_bytes_sent": "$upstream_bytes_sent",'
        '"upstream_cache_status":"$upstream_cache_status",'
        '"upstream_connect_time":"$upstream_connect_time",'
        '"upstream_header_time":"$upstream_header_time",'
        '"upstream_response_length":"$upstream_response_length",'
        '"upstream_response_time":"$upstream_response_time",'
        '"upstream_status": "$upstream_status",'
        '"upstream_content_type":"$upstream_http_content_type"'
    '}';

    access_log  /var/log/nginx/access.log  main;
    access_log  /var/log/nginx/access.json.log vector;      # Новый лог в формате json

    sendfile        on;
    #tcp_nopush     on;

    keepalive_timeout  65;

    #gzip  on;

    include /etc/nginx/conf.d/*.conf;
}

Kako ne biste pokvarili vašu trenutnu konfiguraciju, Nginx vam omogućuje da imate nekoliko access_log direktiva

access_log  /var/log/nginx/access.log  main;            # Стандартный лог
access_log  /var/log/nginx/access.json.log vector;      # Новый лог в формате json

Ne zaboravite dodati pravilo za logrotate za nove zapise (ako datoteka dnevnika ne završava s .log)

Uklonite default.conf iz /etc/nginx/conf.d/

rm -f /etc/nginx/conf.d/default.conf

Dodajte virtualni host /etc/nginx/conf.d/vhost1.conf

server {
    listen 80;
    server_name vhost1;
    location / {
        proxy_pass http://172.26.10.106:8080;
    }
}

Dodajte virtualni host /etc/nginx/conf.d/vhost2.conf

server {
    listen 80;
    server_name vhost2;
    location / {
        proxy_pass http://172.26.10.108:8080;
    }
}

Dodajte virtualni host /etc/nginx/conf.d/vhost3.conf

server {
    listen 80;
    server_name vhost3;
    location / {
        proxy_pass http://172.26.10.109:8080;
    }
}

Dodajte virtualni host /etc/nginx/conf.d/vhost4.conf

server {
    listen 80;
    server_name vhost4;
    location / {
        proxy_pass http://172.26.10.116:8080;
    }
}

Dodajte virtualne hostove (172.26.10.106 ip poslužitelja na kojem je instaliran nginx) svim poslužiteljima u datoteku /etc/hosts:

172.26.10.106 vhost1
172.26.10.106 vhost2
172.26.10.106 vhost3
172.26.10.106 vhost4

I ako je tada sve spremno

nginx -t 
systemctl restart nginx

Sada ćemo ga sami instalirati vektor

yum install -y https://packages.timber.io/vector/0.9.X/vector-x86_64.rpm

Kreirajmo datoteku postavki za systemd /etc/systemd/system/vector.service

[Unit]
Description=Vector
After=network-online.target
Requires=network-online.target

[Service]
User=vector
Group=vector
ExecStart=/usr/bin/vector
ExecReload=/bin/kill -HUP $MAINPID
Restart=no
StandardOutput=syslog
StandardError=syslog
SyslogIdentifier=vector

[Install]
WantedBy=multi-user.target

I konfigurirajte Filebeat zamjenu u konfiguraciji /etc/vector/vector.toml. IP adresa 172.26.10.108 je IP adresa log poslužitelja (Vector-Server)

data_dir = "/var/lib/vector"

[sources.nginx_file]
  type                          = "file"
  include                       = [ "/var/log/nginx/access.json.log" ]
  start_at_beginning            = false
  fingerprinting.strategy       = "device_and_inode"

[sinks.nginx_output_vector]
  type                          = "vector"
  inputs                        = [ "nginx_file" ]

  address                       = "172.26.10.108:9876"

Ne zaboravite dodati korisnika vektora u traženu grupu kako bi mogao čitati datoteke dnevnika. Na primjer, nginx u centosu stvara zapise s pravima adm grupe.

usermod -a -G adm vector

Pokrenimo vektorsku uslugu

systemctl enable vector
systemctl start vector

Vektorski dnevnici mogu se vidjeti ovako:

journalctl -f -u vector

U zapisnicima bi trebao postojati ovakav unos

INFO vector::topology::builder: Healthcheck: Passed.

Testiranje otpornosti na stres

Provodimo testiranje koristeći Apache benchmark.

Paket httpd-tools instaliran je na svim poslužiteljima

Započinjemo testiranje korištenjem referentne vrijednosti Apache s 4 različita poslužitelja na zaslonu. Prvo pokrećemo multipleksor ekranskog terminala, a zatim počinjemo s testiranjem pomoću referentne vrijednosti Apache. Kako raditi sa ekranom možete pronaći u članak.

Od 1. poslužitelja

while true; do ab -H "User-Agent: 1server" -c 100 -n 10 -t 10 http://vhost1/; sleep 1; done

Od 2. poslužitelja

while true; do ab -H "User-Agent: 2server" -c 100 -n 10 -t 10 http://vhost2/; sleep 1; done

Od 3. poslužitelja

while true; do ab -H "User-Agent: 3server" -c 100 -n 10 -t 10 http://vhost3/; sleep 1; done

Od 4. poslužitelja

while true; do ab -H "User-Agent: 4server" -c 100 -n 10 -t 10 http://vhost4/; sleep 1; done

Provjerimo podatke u Clickhouseu

Idite u Clickhouse

clickhouse-client -h 172.26.10.109 -m

Izrada SQL upita

SELECT * FROM vector.logs;

┌─node_name────┬───────────timestamp─┬─server_name─┬─user_id─┬─request_full───┬─request_user_agent─┬─request_http_host─┬─request_uri─┬─request_scheme─┬─request_method─┬─request_length─┬─request_time─┬─request_referrer─┬─response_status─┬─response_body_bytes_sent─┬─response_content_type─┬───remote_addr─┬─remote_port─┬─remote_user─┬─upstream_addr─┬─upstream_port─┬─upstream_bytes_received─┬─upstream_bytes_sent─┬─upstream_cache_status─┬─upstream_connect_time─┬─upstream_header_time─┬─upstream_response_length─┬─upstream_response_time─┬─upstream_status─┬─upstream_content_type─┐
│ nginx-vector │ 2020-08-07 04:32:42 │ vhost1      │         │ GET / HTTP/1.0 │ 1server            │ vhost1            │ /           │ http           │ GET            │             66 │        0.028 │                  │             404 │                       27 │                       │ 172.26.10.106 │       45886 │             │ 172.26.10.106 │             0 │                     109 │                  97 │ DISABLED              │                     0 │                0.025 │                       27 │                  0.029 │             404 │                       │
└──────────────┴─────────────────────┴─────────────┴─────────┴────────────────┴────────────────────┴───────────────────┴─────────────┴────────────────┴────────────────┴────────────────┴──────────────┴──────────────────┴─────────────────┴──────────────────────────┴───────────────────────┴───────────────┴─────────────┴─────────────┴───────────────┴───────────────┴─────────────────────────┴─────────────────────┴───────────────────────┴───────────────────────┴──────────────────────┴──────────────────────────┴────────────────────────┴─────────────────┴───────────────────────

Saznajte veličinu stolova u Clickhouseu

select concat(database, '.', table)                         as table,
       formatReadableSize(sum(bytes))                       as size,
       sum(rows)                                            as rows,
       max(modification_time)                               as latest_modification,
       sum(bytes)                                           as bytes_size,
       any(engine)                                          as engine,
       formatReadableSize(sum(primary_key_bytes_in_memory)) as primary_keys_size
from system.parts
where active
group by database, table
order by bytes_size desc;

Saznajmo koliko je trupaca zauzelo Clickhouse.

Veličina tablice zapisa je 857.19 MB.

Veličina istih podataka u indeksu u Elasticsearchu je 4,5 GB.

Ako u parametrima ne navedete podatke u vektoru, Clickhouse uzima 4500/857.19 = 5.24 puta manje nego u Elasticsearchu.

U vektoru se polje kompresije koristi prema zadanim postavkama.

Telegram chat by klikanica
Telegram chat by Elasticsearch
Telegram chat od "Prikupljanje i analiza sustava poruke"

Izvor: www.habr.com