为了做好运维面试路上的助攻手,特整理了上百道 【运维技术栈面试题集锦】 ,让你面试不慌心不跳,高薪offer怀里抱!
这次整理的面试题,小到shell、MySQL,大到K8s等云原生技术栈,不仅适合运维新人入行面试需要,还适用于想提升进阶跳槽加薪的运维朋友。
本份面试集锦涵盖了
- 174 道运维工程师面试题
- 128道k8s面试题
- 108道shell脚本面试题
- 200道Linux面试题
- 51道docker面试题
- 35道Jenkis面试题
- 78道MongoDB面试题
- 17道ansible面试题
- 60道dubbo面试题
- 53道kafka面试
- 18道mysql面试题
- 40道nginx面试题
- 77道redis面试题
- 28道zookeeper
总计 1000+ 道面试题, 内容 又全含金量又高
- 174道运维工程师面试题
1、什么是运维?
2、在工作中,运维人员经常需要跟运营人员打交道,请问运营人员是做什么工作的?
3、现在给你三百台服务器,你怎么对他们进行管理?
4、简述raid0 raid1raid5二种工作模式的工作原理及特点
5、LVS、Nginx、HAproxy有什么区别?工作中你怎么选择?
6、Squid、Varinsh和Nginx有什么区别,工作中你怎么选择?
7、Tomcat和Resin有什么区别,工作中你怎么选择?
8、什么是中间件?什么是jdk?
9、讲述一下Tomcat8005、8009、8080三个端口的含义?
10、什么叫CDN?
11、什么叫网站灰度发布?
12、简述DNS进行域名解析的过程?
13、RabbitMQ是什么东西?
14、讲一下Keepalived的工作原理?
15、讲述一下LVS三种模式的工作过程?
16、mysql的innodb如何定位锁问题,mysql如何减少主从复制延迟?
17、如何重置mysql root密码?
网上学习资料一大堆,但如果学到的知识不成体系,遇到问题时只是浅尝辄止,不再深入研究,那么很难做到真正的技术提升。
一个人可以走的很快,但一群人才能走的更远!不论你是正从事IT行业的老鸟或是对IT行业感兴趣的新人,都欢迎加入我们的的圈子(技术交流、学习资源、职场吐槽、大厂内推、面试辅导),让我们一起学习成长!
测试
ssh -i ~/.ssh/id_rsa_pgpool 10.10.10.71 date
ssh -i ~/.ssh/id_rsa_pgpool 10.10.10.72 date
ssh -i ~/.ssh/id_rsa_pgpool 10.10.10.73 date
#### 配置pgpass
su - postgres
echo “10.10.10.71:5432:replication:repuser:Repuser@2024_RP” >> ~/.pgpass
echo “10.10.10.72:5432:replication:repuser:Repuser@2024_RP” >> ~/.pgpass
echo “10.10.10.73:5432:replication:repuser:Repuser@2024_RP” >> ~/.pgpass
echo “10.10.10.71:5432:postgres:postgres:Postgres@2024_PG” >> ~/.pgpass
echo “10.10.10.72:5432:postgres:postgres:Postgres@2024_PG” >> ~/.pgpass
echo “10.10.10.73:5432:postgres:postgres:Postgres@2024_PG” >> ~/.pgpass
chmod 600 ~/.pgpass
#### pcp免密
echo ‘localhost:9898:postgres:postgres’ > ~/.pcppass
chmod 600 ~/.pcppass
#### 安装pgpool-II
yum install -y https://www.pgpool.net/yum/rpms/4.1/redhat/rhel-7-x86_64/pgpool-II-release-4.1-3.noarch.rpm
rpm -e pgdg-redhat-repo-42.0-28.noarch
– 4.1.14
yum -y install pgpool-II-pg12
yum -y install pgpool-II-pg12-debuginfo
yum -y install pgpool-II-pg12-devel
yum -y install pgpool-II-pg12-extensions
#### 授权
chown postgres.postgres /var/run/pgpool
mkdir -p /var/log/pgpool/
chown -R postgres.postgres /var/log/pgpool/
cd /etc/pgpool-II
cp failover.sh.sample failover.sh
cp follow_master.sh.sample follow_master.sh
cp recovery_1st_stage.sample recovery_1st_stage
cp pgpool_remote_start.sample pgpool_remote_start
chown postgres.postgres /etc/pgpool-II/{failover.sh,follow_master.sh,recovery_1st_stage,pgpool_remote_start} -R
chmod u+x /etc/pgpool-II/{failover.sh,follow_master.sh,recovery_1st_stage,pgpool_remote_start} -R
chmod u+x /usr/sbin/ip
chmod u+s /usr/sbin/arping
chmod u+s /sbin/ip
chmod u+s /sbin/ifup
chmod u+s /bin/ping
chmod u+s /sbin/arping
#### 配置pcp.conf
pg_md5 Postgres@2024_PG
vi /etc/pgpool-II/pcp.conf
echo “postgres:0b4854363bbbde1021c518850f0e5f32” >> /etc/pgpool-II/pcp.conf
pg_md5 -m -p -u postgres /etc/pgpool-II/pool_passwd
Postgres@2024_PG
pg_md5 -m -p -u twadmin /etc/pgpool-II/pool_passwd
TW_admin@2024_TH
#### 配置hba.conf
vi /etc/pgpool-II/pool_hba.conf
host all all 0.0.0.0/0 md5
host all all 0/0 md5
#### 配置pgpool.conf
vi pgpool.conf
pid_file_name = ‘/var/run/pgpool/pgpool.pid’
logdir = ‘/var/run/pgpool’
listen_addresses = ‘’
port = 9999
pcp_listen_addresses = '’
pcp_port = 9898
backend_hostname0 = ‘10.10.10.71’
backend_port0 = 5432
backend_weight0 = 1
backend_data_directory0 = ‘/data/pg_data’
backend_flag0 = ‘ALLOW_TO_FAILOVER’
backend_hostname1 = ‘10.10.10.72’
backend_port1 = 5432
backend_weight1 = 1
backend_data_directory1 = ‘/data/pg_data’
backend_flag1 = ‘ALLOW_TO_FAILOVER’
backend_application_name0 = ‘server1’
backend_hostname2 = ‘10.10.10.73’
backend_port2 = 5432
backend_weight2 = 1
backend_data_directory2 = ‘/data/pg_data’
backend_flag2 = ‘ALLOW_TO_FAILOVER’
backend_application_name0 = ‘server2’
流复制相关配置
replication_mode = off
load_balance_mode = on
master_slave_mode = on
master_slave_sub_mode = ‘stream’
sr_check_period = 5
sr_check_user = ‘repuser’
sr_check_password = ‘Repuser@2024_RP’
sr_check_database = ‘postgres’
数据库故障转移(故障后处理)
health_check_period = 10
health_check_timeout = 20
health_check_user = ‘postgres’
health_check_password = ‘Postgres@2024_PG’
health_check_database = ‘postgres’
failover_command = ‘/etc/pgpool-II/failover.sh %d %h %p %D %m %H %M %P %r %R’
follow_master_command = ‘/etc/pgpool-II/follow_master.sh %d %h %p %D %m %H %M %P %r %R’
recovery_user = ‘postgres’
recovery_password = ‘Postgres@2024_PG’
recovery_1st_stage_command = ‘recovery_1st_stage’
watchdog(看门狗)配置(用于检测pgpool-ii 节点状态, 为后续pgpool故障处理提供依据)
use_watchdog = on
wd_hostname = ‘10.10.10.71’
wd_port = 9000
虚拟IP指定
delegate_IP = ‘10.10.10.101’
if_cmd_path = ‘/sbin’
if_up_cmd = ‘/usr/bin/sudo /sbin/ip addr add KaTeX parse error: Expected group after '_' at position 4: _IP_̲/24 dev ens192 label ens192:0’
if_down_cmd = ‘/usr/bin/sudo /sbin/ip addr del KaTeX parse error: Expected group after '_' at position 4: _IP_̲/24 dev ens192’
arping_cmd = ‘/usr/bin/sudo /usr/sbin/arping -U KaTeX parse error: Expected group after '_' at position 4: _IP_̲ -w 1 -I ens192’
watchdog 健康检查
wd_heartbeat_port = 9694
wd_heartbeat_keepalive = 2
wd_heartbeat_deadtime = 30
heartbeat_destination0 = ‘10.10.10.72’
heartbeat_destination_port0 = 9694
heartbeat_device0 = ‘ens192’
heartbeat_destination0 = ‘10.10.10.73’
heartbeat_destination_port0 = 9694
heartbeat_device0 = ‘ens192’
其他pgpgool节点链接信息(多台请增加配置)
other_pgpool_hostname0 = ‘10.10.10.72’
other_pgpool_port0 = 9999
other_wd_port0 = 9000
watchdog 发生故障后, 处理的相关配置(宕机, pgpool进程终止)# 当某个节点故障后
other_pgpool_hostname1 = ‘10.10.10.73’
other_pgpool_port1 = 9999
other_wd_port1 = 9000
failover_when_quorum_exists = on
failover_require_consensus = on
allow_multiple_failover_requests_from_node = on
enable_consensus_with_half_votes = on
#### 修改failover.sh
PGHOME=/usr/pgsql-12
REPL_SLOT_NAME=${FAILED_NODE_HOST//[-.]/_}
POSTGRESQL_STARTUP_USER=postgres
SSH_KEY_FILE=id_rsa_pgpool
ssh -T ${SSH_OPTIONS} P O S T G R E S Q L S T A R T U P U S E R @ {POSTGRESQL_STARTUP_USER}@ POSTGRESQLSTARTUPUSER@{NEW_MASTER_NODE_HOST} ${PGHOME}/bin/psql -p ${NEW_MASTER_NODE_PORT} -c “select pg_promote(true,30)”
#### 修改follow\_master.sh
#!/bin/bash
This script is run after failover_command to synchronize the Standby with the new Primary.
First try pg_rewind. If pg_rewind failed, use pg_basebackup.
set -o xtrace
exec > >(logger -i -p local1.info) 2>&1
Special values:
1) %d = node id
2) %h = hostname
3) %p = port number
4) %D = database cluster path
5) %m = new primary node id
6) %H = new primary node hostname
7) %M = old master node id
8) %P = old primary node id
9) %r = new primary port number
10) %R = new primary database cluster path
11) %N = old primary node hostname
12) %S = old primary node port number
13) %% = ‘%’ character
NODE_ID=“$1”
NODE_HOST=“$2”
NODE_PORT=“$3”
NODE_PGDATA=“$4”
NEW_MASTER_NODE_ID=“$5”
NEW_MASTER_NODE_HOST=“$6”
OLD_MASTER_NODE_ID=“$7”
OLD_PRIMARY_NODE_ID=“$8”
NEW_MASTER_NODE_PORT=“
9
"
N
E
W
M
A
S
T
E
R
N
O
D
E
P
G
D
A
T
A
=
"
9" NEW_MASTER_NODE_PGDATA="
9"NEWMASTERNODEPGDATA="{10}”
PGHOME=/usr/pgsql-12
ARCHIVEDIR=/data/pg_arch
REPLUSER=repuser
REPLUSER_PD=Repuser@2024_RP
PCP_USER=postgres
PG_USER=postgres
PG_PD=Postgres@2024_PG
PGPOOL_PATH=/usr/bin
PCP_PORT=9898
REPL_SLOT_NAME=KaTeX parse error: Expected group after '_' at position 18: …ODE_HOST//[-.]/_̲} POSTGRESQL_ST…{SSH_KEY_FILE}"
logger -i -p local1.info follow_master.sh: start: Standby node ${NODE_ID}
Check the connection status of Standby
${PGHOME}/bin/pg_isready -h ${NODE_HOST} -p ${NODE_PORT} > /dev/null 2>&1
if [
?
−
n
e
0
]
;
t
h
e
n
l
o
g
g
e
r
−
i
−
p
l
o
c
a
l
1.
i
n
f
o
f
o
l
l
o
w
m
a
s
t
e
r
.
s
h
:
n
o
d
e
i
d
=
? -ne 0 ]; then logger -i -p local1.info follow_master.sh: node_id=
?−ne0];thenlogger−i−plocal1.infofollowmaster.sh:nodeid={NODE_ID} is not running. skipping follow master command
exit 0
fi
Test passwordless SSH
ssh -T ${SSH_OPTIONS} P O S T G R E S Q L S T A R T U P U S E R @ {POSTGRESQL_STARTUP_USER}@ POSTGRESQLSTARTUPUSER@{NEW_MASTER_NODE_HOST} ls /tmp > /dev/null
if [
?
−
n
e
0
]
;
t
h
e
n
l
o
g
g
e
r
−
i
−
p
l
o
c
a
l
1.
i
n
f
o
f
o
l
l
o
w
m
a
s
t
e
r
.
s
h
:
p
a
s
s
w
o
r
d
l
e
s
s
S
S
H
t
o
p
o
s
t
g
r
e
s
@
? -ne 0 ]; then logger -i -p local1.info follow_master.sh: passwordless SSH to postgres@
?−ne0];thenlogger−i−plocal1.infofollowmaster.sh:passwordlessSSHtopostgres@{NEW_MASTER_NODE_HOST} failed. Please setup passwordless SSH.
exit 1
fi
Get PostgreSQL major version
PGVERSION=${PGHOME}/bin/initdb -V | awk '{print $3}' | sed 's/\..*//' | sed 's/\([0-9]*\)[a-zA-Z].*/\1/'
if [
P
G
V
E
R
S
I
O
N
−
g
e
12
]
;
t
h
e
n
R
E
C
O
V
E
R
Y
C
O
N
F
=
PGVERSION -ge 12 ]; then RECOVERYCONF=
PGVERSION−ge12];thenRECOVERYCONF={NODE_PGDATA}/myrecovery.conf
else
RECOVERYCONF=${NODE_PGDATA}/recovery.conf
fi
Synchronize Standby with the new Primary.
logger -i -p local1.info follow_master.sh: pg_rewind for node $NODE_ID
Create replication slot “${REPL_SLOT_NAME}”
${PGHOME}/bin/psql -h ${NEW_MASTER_NODE_HOST} -p N E W M A S T E R N O D E P O R T − c " S E L E C T p g c r e a t e p h y s i c a l r e p l i c a t i o n s l o t ( ′ {NEW_MASTER_NODE_PORT} \ -c "SELECT pg_create_physical_replication_slot(' NEWMASTERNODEPORT −c"SELECTpgcreatephysicalreplicationslot(′{REPL_SLOT_NAME}');" >/dev/null 2>&1
if [ KaTeX parse error: Expected group as argument to '\"' at end of input: …ication slot \"{REPL_SLOT_NAME}" failed. You may need to create replication slot manually.
fi
ssh -T ${SSH_OPTIONS} P O S T G R E S Q L S T A R T U P U S E R @ {POSTGRESQL_STARTUP_USER}@ POSTGRESQLSTARTUPUSER@{NODE_HOST} "
set -o errexit
${PGHOME}/bin/pg_ctl -w -m f -D ${NODE_PGDATA} stop
${PGHOME}/bin/pg_rewind -D ${NODE_PGDATA} --source-server=\"user=${PG_USER} password=${PG_PD} host=${NEW_MASTER_NODE_HOST} port=${NEW_MASTER_NODE_PORT}\"
rm -rf ${NODE_PGDATA}/pg_replslot/*
sed -i '/primary_conninfo/d' ${NODE_PGDATA}/postgresql.auto.conf
cat >> ${NODE_PGDATA}/postgresql.auto.conf << EOT
primary_conninfo = ‘user=
R
E
P
L
U
S
E
R
p
a
s
s
w
o
r
d
=
{REPLUSER} password=
REPLUSERpassword={REPLUSER_PD} host=
N
E
W
M
A
S
T
E
R
N
O
D
E
H
O
S
T
p
o
r
t
=
{NEW_MASTER_NODE_HOST} port=
NEWMASTERNODEHOSTport={NEW_MASTER_NODE_PORT} sslmode=prefer sslcompression=0 gssencmode=prefer krbsrvname=postgres target_session_attrs=any’
EOT
if [ ${PGVERSION} -ge 12 ]; then
touch ${NODE_PGDATA}/standby.signal
echo \"standby_mode = 'on'\" > ${NODE_PGDATA}/standby.signal
else
echo \"standby_mode = 'on'\" >> ${RECOVERYCONF}
fi
#${PGHOME}/bin/pg_ctl -l /dev/null -w -D ${NODE_PGDATA} start
sudo systemctl restart postgresql-12
"
If pg_rewind failed, try pg_basebackup
if [ $? -ne 0 ]; then
logger -i -p local1.error follow_master.sh: end: pg_rewind failed. Try pg_basebackup.
fi
If start Standby successfully, attach this node
if [ $? -eq 0 ]; then
# Run pcp_attact_node to attach Standby node to Pgpool-II.
${PGPOOL_PATH}/pcp_attach_node -w -h localhost -U $PCP_USER -p ${PCP_PORT} -n ${NODE_ID}
if [ $? -ne 0 ]; then
logger -i -p local1.error follow_master.sh: end: pcp_attach_node failed
exit 1
fi
else
# If start Standby failed, drop replication slot "${REPL_SLOT_NAME}"
${PGHOME}/bin/psql -h ${NEW_MASTER_NODE_HOST} -p ${NEW_MASTER_NODE_PORT} \
-c "SELECT pg_drop_replication_slot('${REPL_SLOT_NAME}');" >/dev/null 2>&1
if [ $? -ne 0 ]; then
logger -i -p local1.error follow_master.sh: drop replication slot \"${REPL_SLOT_NAME}\" failed. You may need to drop replication slot manually.
fi
logger -i -p local1.error follow_master.sh: end: follow master command failed
exit 1
fi
logger -i -p local1.info follow_master.sh: end: follow master command complete
exit 0
#### 修改recovery\_1st\_stage
**网上学习资料一大堆,但如果学到的知识不成体系,遇到问题时只是浅尝辄止,不再深入研究,那么很难做到真正的技术提升。**
**[需要这份系统化的资料的朋友,可以点击这里获取!](https://bbs.csdn.net/forums/4f45ff00ff254613a03fab5e56a57acb)**
**一个人可以走的很快,但一群人才能走的更远!不论你是正从事IT行业的老鸟或是对IT行业感兴趣的新人,都欢迎加入我们的的圈子(技术交流、学习资源、职场吐槽、大厂内推、面试辅导),让我们一起学习成长!**
-p local1.error follow_master.sh: end: follow master command failed
exit 1
fi
logger -i -p local1.info follow_master.sh: end: follow master command complete
exit 0
修改recovery_1st_stage
网上学习资料一大堆,但如果学到的知识不成体系,遇到问题时只是浅尝辄止,不再深入研究,那么很难做到真正的技术提升。
一个人可以走的很快,但一群人才能走的更远!不论你是正从事IT行业的老鸟或是对IT行业感兴趣的新人,都欢迎加入我们的的圈子(技术交流、学习资源、职场吐槽、大厂内推、面试辅导),让我们一起学习成长!