떠돌이늑대's tory

VM : Centos 8.2

Keepalived 2.15Keepalived v2.1.5

Maxscale 2.5.3

Maxscale 2.5.x 설치

사전 디펜던시 설치

dnf install libatomic

maxscale 설치

rpm -Uvh maxscale-2.5.3-2.rhel.8.x86_64.rpm

keepalived 다운로드

wget https://www.keepalived.org/software/keepalived-2.1.5.tar.gz

사전 디펜던시 설치

dnf install iptables-devel

dnf install libnl3-devel

rpm -Uvh ipset-devel-7.1-1.el8.x86_64.rpm libmnl-devel-1.0.4-6.el8.x86_64.rpm

압축해제

tar zxvf keepalived-2.1.5.tar.gz

환경구성 설치전 테스트

./configure

소스컴파일

make

설치

make install

keepalived.conf 저장 디렉터리 생성

mkdir /etc/keepalived

keepalived.conf 설정

vi /etc/keepalived/keepalived.conf
global_defs {
router_id maxa                    <-maxa 는 호스트네임으로 했으나, 변경해도 상관없음
}
vrrp_script chk_myscript {
script "/etc/keepalived/scripts/is_maxscale_running.sh"
interval 2 # check every 2 seconds
fall 2 # require 2 failures for KO
rise 2 # require 2 successes for OK
}
vrrp_instance VI_1 {
state MASTER
interface ens3
virtual_router_id 51
priority 100
advert_int 1
authentication {
auth_type PASS
auth_pass mypass
}
virtual_ipaddress {
192.168.1.160
}
track_script {
chk_myscript
}
notify /etc/keepalived/scripts/notify_script.sh
}

스크립트 저장디렉터리 생성

mkdir /etc/keepalived/scripts

is_maxscale_running.sh 스크립트 작성

vi /etc/keepalived/scripts/is_maxscale_running.sh
#!/bin/bash
fileName="/etc/keepalived/scripts/maxadmin_output.txt"
rm $fileName
timeout 2s maxctrl list servers > $fileName
to_result=$?
if [ $to_result -ge 1 ]
then
echo Timed out or error, timeout returned $to_result
exit 3
else
echo MaxAdmin success, rval is $to_result
echo Checking maxadmin output sanity
grep1=$(grep galera1_dr $fileName)
grep2=$(grep galera2_dr $fileName)
grep3=$(grep galera3_dr $fileName)

if [ "$grep1" ] && [ "$grep2" ] && [ "$grep3" ]
then
echo All is fine
exit 0
else
echo Something is wrong
exit 3
fi
fi

notify_script.sh 스크립트작성

vi /etc/keepalived/scripts/notify_script.sh
#!/bin/bash
TYPE=$1
NAME=$2
STATE=$3
OUTFILE=/etc/keepalived/scripts/maxscale_state.txt

case $STATE in
"MASTER") echo "Setting this MaxScale node to active mode" > $OUTFILE
maxctrl alter maxscale passive false
exit 0
;;
"BACKUP") echo "Setting this MaxScale node to passive mode" > $OUTFILE
maxctrl alter maxscale passive true
exit 0
;;
"FAULT") echo "MaxScale failed the status check." > $OUTFILE
maxctrl alter maxscale passive true
exit 0
;;
*) echo "Unknown state" > $OUTFILE
exit 1
;;
esac

방화벽설정

firewall-cmd --add-rich-rule='rule protocol value="vrrp" accept' --permanent

방화벽적용

firewall-cmd --reload

maxscale 시작
systemctl start maxscale

keepalived 시작

systemctl start keepalived

모니터링을 위한 툴. 설치하면 자체 웹서버가 작동하여 웹상에서 모니터링 상태를 보여준다. 

메모리사용량을 살펴보기 위해 설치해봤다. 

그 외 CPU, 디스크 등등이 나온다. 

rhel 7.9 minimal 로 설치했을 경우 

bash <(curl -Ss https://my-netdata.io/kickstart.sh)

를 하면, 필요한 패키지들을 자동으로 설치하고 netdata가 설치 완료 된다. 필요한 패키지들에 대한 yum repository는 지정되어있어야 한다. 

yum repository는 설치이미지로 했는데, 그곳에 없는 패키지들이 있다. 그것들은 별도로 다운받아서 설치를 해줬다. 

libuv-1.40.0-1.el7.x86_64
libtool-ltdl-2.4.2-22.el7_3.x86_64
gc-7.2d-7.el7.x86_64
autogen-libopts-5.18-5.el7.x86_64
guile-2.0.9-5.el7.x86_64
lz4-devel-1.8.3-1.el7.x86_64
libuv-devel-1.40.0-1.el7.x86_64
libmnl-devel-1.0.3-7.el7.x86_64
json-c-devel-0.11-4.el7_0.x86_64
autogen-5.18-5.el7.x86_64

binlog_row_metadata

• Description: Controls the format used for binlog metadata logging.
  • NO_LOG: No metadata is logged (default).
  • MINIMAL: Only metadata required by a slave is logged.
  • FULL: All metadata is logged.
• Commandline: --binlog-row-metadata=value
• Scope: Global, Session
• Dynamic: Yes
• Data Type: enum
• Default Value: NO_LOG
• Valid Values: NO_LOG, MINIMAL, FULL
• Introduced: MariaDB 10.5.0

innodb_instant_alter_column_allowed

• Description:
  • If a table is altered using ALGORITHM=INSTANT, it can force the table to use a non-canonical format: A hidden metadata record at the start of the clustered index is used to store each column's DEFAULT value. This makes it possible to add new columns that have default values without rebuilding the table. Starting with MariaDB 10.4, a BLOB in the hidden metadata record is used to store column mappings. This makes it possible to drop or reorder columns without rebuilding the table. This also makes it possible to add columns to any position or drop columns from any position in the table without rebuilding the table. If a column is dropped without rebuilding the table, old records will contain garbage in that column's former position, and new records will be written with NULL values, empty strings, or dummy values.
  • This is generally not a problem. However, there may be cases where you want to avoid putting a table into this format. For example, to ensure that future UPDATE operations after an ADD COLUMN will be performed in-place, to reduce write amplification. (Instantly added columns are essentially always variable-length.) Also avoid bugs similar to MDEV-19916, or to be able to export tables to older versions of the server.
  • This variable has been introduced as a result, with the following values:
  • never (0): Do not allow instant add/drop/reorder, to maintain format compatibility with MariaDB 10.x and MySQL 5.x. If the table (or partition) is not in the canonical format, then any ALTER TABLE (even one that does not involve instant column operations) will force a table rebuild.
  • add_last (1, default in 10.3): Store a hidden metadata record that allows columns to be appended to the table instantly (MDEV-11369). In 10.4 or later, if the table (or partition) is not in this format, then any ALTER TABLE (even one that does not involve column changes) will force a table rebuild.
  • add_drop_reorder (2, default): From MariaDB 10.4 only. Like 'add_last', but allow the metadata record to store a column map, to support instant add/drop/reorder of columns.
• Commandline: --innodb-instant-alter-column-allowed=value
• Scope: Global
• Dynamic: Yes
• Data Type: enum
• Valid Values:
  • <= MariaDB 10.3: never, add_last
  • >= MariaDB 10.4: never, add_last, add_drop_reorder
• Default Value:
  • <= MariaDB 10.3: add_last
  • >= MariaDB 10.4: add_drop_reorder
• Introduced: MariaDB 10.3.23, MariaDB 10.4.13, MariaDB 10.5.3

performance_schema_events_transactions_history_long_size

• Description: Number of rows in events_transactions_history_long table. Use 0 to disable, -1 for automated sizing.
• Commandline: --performance-schema-events-transactions-history-long-size=#
• Scope: Global
• Dynamic: No
• Data Type: numeric
• Default Value: -1
• Range: -1 to 1048576
• Introduced: MariaDB 10.5.2

performance_schema_events_transactions_history_size

• Description:Number of rows per thread in events_transactions_history. Use 0 to disable, -1 for automated sizing.
• Commandline: --performance-schema-events-transactions-history-size=#
• Scope: Global
• Dynamic: No
• Data Type: numeric
• Default Value: -1
• Range: -1 to 1024
• Introduced: MariaDB 10.5.2

performance_schema_max_index_stat

• Description: Maximum number of index statistics for instrumented tables. Use 0 to disable, -1 for automated scaling.
• Commandline: --performance-schema-max-index-stat=#
• Scope: Global
• Dynamic: No
• Data Type: numeric
• Default Value: -1
• Range: -1 to 1048576
• Introduced: MariaDB 10.5.2

performance_schema_max_memory_classes

• Description: Maximum number of memory pool instruments.
• Commandline: --performance-schema-max-memory-classes=#
• Scope: Global
• Dynamic: No
• Data Type: numeric
• Default Value: 320
• Range: 0 to 1024
• Introduced: MariaDB 10.5.2

performance_schema_max_metadata_locks

• Description: Maximum number of metadata locks. Use 0 to disable, -1 for automated scaling.
• Commandline: --performance-schema-max-metadata-locks=#
• Scope: Global
• Dynamic: No
• Data Type: numeric
• Default Value: -1
• Range: -1 to 104857600
• Introduced: MariaDB 10.5.2

performance_schema_max_prepared_statement_instances

• Description: Maximum number of instrumented prepared statements. Use 0 to disable, -1 for automated scaling.
• Commandline: --performance-schema-max-prepared-statement-instances=#
• Scope: Global
• Dynamic: No
• Data Type: numeric
• Default Value: -1
• Range: -1 to 1048576
• Introduced: MariaDB 10.5.2

performance_schema_max_program_instances

• Description: Maximum number of instrumented programs. Use 0 to disable, -1 for automated scaling.
• Commandline: --performance-schema-max-program-instances=#
• Scope: Global
• Dynamic: No
• Data Type: numeric
• Default Value: -1
• Range: -1 to 1048576
• Introduced: MariaDB 10.5.2

performance_schema_max_sql_text_length

• Description: Maximum length of displayed sql text.
• Commandline: --performance-schema-max-sql-text-length=#
• Scope: Global
• Dynamic: No
• Data Type: numeric
• Default Value: 1024
• Range: 0 to 1048576
• Introduced: MariaDB 10.5.2

performance_schema_max_statement_stack

• Description: Number of rows per thread in EVENTS_STATEMENTS_CURRENT.
• Commandline: --performance-schema-max-statement-stack=#
• Scope: Global
• Dynamic: No
• Data Type: numeric
• Default Value: 10
• Range: 1 to 256
• Introduced: MariaDB 10.5.2

performance_schema_max_table_lock_stat

• Description: Maximum number of lock statistics for instrumented tables. Use 0 to disable, -1 for automated scaling.
• Commandline: --performance-schema-max-table-lock-stat=#
• Scope: Global
• Dynamic: No
• Data Type: numeric
• Default Value: -1
• Range: -1 to 1048576
• Introduced: MariaDB 10.5.2

s3_access_key

• Description: The AWS access key to access your data. See mysqld startup options for S3.
• Commandline: --s3-access-key=val
• Scope: Global
• Dynamic: No
• Data Type: String
• Default Value: (Empty)
• Introduced: MariaDB 10.5.4

s3_block_size

• Description: The default block size for a table, if not specified in CREATE TABLE. Set to 4M as default. See mysqld startup options for S3.
• Commandline: --s3-block-size=#
• Scope: Global
• Dynamic: Yes
• Data Type: Numeric
• Default Value: 4194304
• Range: 4194304 to 16777216
• Introduced: MariaDB 10.5.4

s3_bucket

• Description: The AWS bucket where your data should be stored. All MariaDB table data is stored in this bucket. See mysqld startup options for S3.
• Commandline: --s3-bucket=val
• Scope: Global
• Dynamic: No
• Data Type: String
• Default Value: MariaDB
• Introduced: MariaDB 10.5.4

s3_debug

• Description: Generates a trace file from libmarias3 on stderr (mysqld.err) for debugging the S3 protocol.
• Commandline: --s3-debug{=0|1}
• Scope: Global
• Dynamic: No
• Data Type: Boolean
• Valid Values: 0 or 1
• Default Value: 0
• Introduced: MariaDB 10.5.4

s3_host_name

• Description: Hostname for the S3 service. "s3.amazonaws.com", Amazon S3 service, by default
• Commandline: --s3-host-name=val
• Scope: Globa;
• Dynamic: No
• Data Type: String
• Default Value: s3.amazonaws.com
• Introduced: MariaDB 10.5.4

s3_pagecache_age_threshold

• Description: This characterizes the number of hits a hot block has to be untouched until it is considered aged enough to be downgraded to a warm block. This specifies the percentage ratio of that number of hits to the total number of blocks in the page cache.
• Commandline: --s3-pagecache-age-threshold=val
• Scope: Global
• Dynamic: Yes
• Data Type: Numeric
• Default Value: 300
• Range: 100 to 18446744073709551615
• Introduced: MariaDB 10.5.4

s3_pagecache_buffer_size

• Description: The size of the buffer used for index blocks for S3 tables. Increase this to get better index handling (for all reads and multiple writes) to as much as you can afford. Size can be adjusted in blocks of 8192.
• Commandline: --s3-pagecache-buffer-size=val
• Scope: Global
• Dynamic: No
• Data Type: Numeric
• Default Value: 134217728 (128M)
• Range: 33554432 to 18446744073709551615
• Introduced: MariaDB 10.5.4

s3_pagecache_division_limit

• Description: The minimum percentage of warm blocks in key cache.
• Commandline: --s3-pagecache-division-limit=val
• Scope: Global
• Dynamic: Yes
• Data Type: Numeric
• Default Value: 100
• Range: 1 to 100
• Introduced: MariaDB 10.5.4

s3_pagecache_file_hash_size

• Description: Number of hash buckets for open files. Default 512. If you have a lot of S3 files open you should increase this for faster flush of changes. A good value is probably 1/10 of number of possible open S3 files.
• Commandline: --s3-pagecache-file-hash-size=#
• Scope: Global
• Dynamic: No
• Data Type: Numeric
• Default Value: 512
• Range: 32 to 16384
• Introduced: MariaDB 10.5.4

s3_protocol_version

• Description: Protocol used to communication with S3. One of "Auto", "Amazon" or "Original" where "Auto" is the default. If you get errors like "8 Access Denied" when you are connecting to another service provider, then try to change this option. The reason for this variable is that Amazon has changed some parts of the S3 protocol since they originally introduced it but other service providers are still using the original protocol.
• Commandline: --s3-protocol-version=val
• Scope: Global
• Dynamic: Yes
• Data Type: Enum
• Valid Values: Auto, Amazon or Original
• Default Value: Auto
• Introduced: MariaDB 10.5.4

s3_region

• Description: The AWS region where your data should be stored. See mysqld startup options for S3.
• Commandline: --s3-region=val
• Scope: Global
• Dynamic: No
• Data Type: String
• Default Value: (Empty)
• Introduced: MariaDB 10.5.4

s3_replicate_alter_as_create_select

• Description: When converting S3 table to local table, log all rows in binary log. This allows the slave to replicate CREATE TABLE .. SELECT FROM s3_table even it the slave doesn't have access to the original s3_table.
• Commandline: --s3-replicate-alter-as-create-select{=0|1}
• Scope: Global
• Dynamic: No
• Data Type: Boolean
• Default Value: 1
• Introduced: MariaDB 10.5.4

s3_secret_key

• Description: The AWS secret key to access your data. See mysqld startup options for S3.
• Commandline: --s3-secret-key=val
• Scope: Global
• Dynamic: No
• Data Type: String
• Default Value: (Empty)
• Introduced: MariaDB 10.5.4

s3_slave_ignore_updates

• Description: Should be set if master and slave share the same S3 instance. This tells the slave that it can ignore any updates to the S3 tables as they are already applied on the master.
• Commandline: --s3-slave-ignore-updates{=0|1}
• Scope: Global
• Dynamic: No
• Data Type: Boolean
• Default Value: 0
• Introduced: MariaDB 10.5.4

sql_if_exists

• Description: If set to 1, adds an implicit IF EXISTS to ALTER, RENAME and DROP of TABLES, VIEWS, FUNCTIONS and PACKAGES. This variable is mainly used in replication to tag DDLs that can be ignored on the slave if the target table doesn't exist.
• Commandline: --sql-if-exists[={0|1}]
• Scope: Global, Session
• Dynamic: Yes
• Data Type: boolean
• Default Value: OFF
• Introduced: MariaDB 10.5.2

thread_pool_dedicated_listener

• Description: If set to 1, then each group will have its own dedicated listener, and the listener thread will not pick up work items. As a result, the queueing time in the Information Schema Threadpool_Queues and the actual queue size in the Information Schema Threadpool_Groups table will be more exact, since IO requests are immediately dequeued from poll, without delay.
  • This system variable is only meaningful on Unix.
• Commandline: thread-pool-dedicated-listener={0|1}
• Scope:
• Dynamic:
• Data Type: boolean
• Default Value: 0
• Introduced: MariaDB 10.5.0

thread_pool_exact_stats

• Description: If set to 1, provides better queueing time statistics by using a high precision timestamp, at a small performance cost, for the time when the connection was added to the queue. This timestamp helps calculate the queuing time shown in the Information Schema Threadpool_Queues table.
  • This system variable is only meaningful on Unix.
• Commandline: thread-pool-exact-stats={0|1}
• Scope:
• Dynamic:
• Data Type: boolean
• Default Value: 0
• Introduced: MariaDB 10.5.0

mysql_secure_installation  error

환경

• Red Hat Enterprise Linux 7
• Red Hat Virtualization if RHEL 7 is used as the virtualization host
• Red Hat Virtualization (RHV) 4.3

문제

• On a RHEL 7 host, using libguestfs utilities such as guestfish, virt-sysprep, or virt-customize to access or modify a RHEL 8 virtual disk image fails if the disk image is using an XFS or ext4 file system.

• For example:

Raw

# /usr/bin/virt-sysprep -a RHEL8.img [' [ 0.0] Examining the guest ... virt-sysprep: warning: mount_options: mount exited with status 32: mount: wrong fs type, bad option, bad superblock on /dev/mapper/rhel-root, missing codepage or helper program, or other error', ' In some cases useful info is found in syslog - try dmesg | tail or so. (ignored)', 'virt-sysprep: warning: mount_options: mount: /boot: mount point is not a directory (ignored) [ 15.5] Performing "abrt-data" ...']

• In RHV 4.3, it is not possible to create a template of RHEL8 guest due to this behavior

해결

There are two possible workarounds:

1. If viable, you can re-create the guest file systems and disable RHEL 8 file-system features that are incompatible with RHEL 7. To do so, use the mkfs utility with one of the following options:

   • For XFS file systems, use the -m reflink=0 option.
   • For ext4 file systems, use the -O ^metadata_csum option.
   • This is documented in this article.
   • Note that on a RHEL 8 host, the affected utilities work as expected.

2. Disclaimer: this workaround is unsupported - use the upstream latest libguestfs appliance.

   1. Download the latest upstream libguestfs appliance on RHEL-7 host:

      Raw

      [RHEL7.6-host]$ pwd /export [RHEL7.6-host]$ wget \ http://download.libguestfs.org/binaries/appliance/appliance-1.38.0.tar.xz

   2. Extract the upstream appliance and enumerate its content, also, make sure that qemu has access to the files:

      Raw

      [RHEL7.6-host]$ tar -Jxf appliance-1.38.0.tar.xz [RHEL7.6-host]$ ls /export/appliance initrd kernel README.fixed root [RHEL7.6-host]$ chmod -R a+rwX /export/applicance

   3. Set the LIBGUESTFS_PATH variable to the above appliance:

      Raw

      [RHEL7.6-host]$ export LIBGUESTFS_PATH=/export/appliance

   4. Validate

      • Read-only mount the RHEL-8 disk image via guestfish, and read the /etc/redhat-release file:

        Raw

        [RHEL7.6-host]$ guestfish --ro -i \ -a rhel-guest-image-8.0-1590.x86_64.qcow2 Welcome to guestfish, the guest filesystem shell for editing virtual machine filesystems and disk images. Type: ‘help’ for help on commands ‘man’ to read the manual ‘quit’ to quit the shell Operating system: Red Hat Enterprise Linux 8.0 Beta (Ootpa) /dev/sda3 mounted on / /dev/sda1 mounted on /boot ><fs> cat /etc/redhat-release Red Hat Enterprise Linux release 8.0 Beta (Ootpa)

      • Or, remove the root password via virt-edit (or reset it via virt-sysprep — refer further below):

        Raw

        [RHEL7.6-host]$ virt-edit \ -a rhel-guest-image-8.0-1590.x86_64.qcow2 \ /etc/passwd -e 's/^root:.*?:/root::/'

      • Or, uninstall the ‘cloud-init’ RPM:

        Raw

        [RHEL7.6-host]$ virt-customize --uninstall cloud-init \ -a rhel-guest-image-8.0-1590.x86_64.qcow2

      • Or just cat a file

        Raw

        [RHEL7.6-host]$ virt-cat -a rhel-guest-image-8.0-1590.x86_64.qcow2 /var/log/cloud-init.log > cloud-init.log

근본 원인

RHEL 7 is not fully compatible with certain features of the XFS and ext4 file systems in RHEL 8, based on RH Private BZ#1667478.
RHV BZ 1671895.

baseurl는 iso파일을 마운트한 곳으로 지정해주면 된다. 

Create,

Read,

Update,

Delete

https://youtu.be/-UxNUKYh7Vw

 "wsrep_provider_options" with "gmcast.segment= "