rhel6.3配置Haproxy + Keepalived +PXC 5.7

最新推荐文章于 2021-05-05 03:29:48 发布
最新推荐文章于 2021-05-05 03:29:48 发布
阅读量460 收藏
点赞数
分类专栏： MYSQL
版权声明：本文为博主原创文章，遵循 CC 4.0 BY-SA 版权协议，转载请附上原文出处链接和本声明。
本文链接：https://blog.csdn.net/jolly10/article/details/80771260
版权

Haproxy + Keepalived +PXC 是目前比较流行的Mysql高可用方案，数据库底层通过Percona XtraDB Cluster(PXC)集群保证数据库的可用性，数据库上层通过haproxy来做负载均衡（至少两台haproxy），最后再通过keepalived（至少两台，测试环境可与haproxy使用同一台机器）来连接haproxy服务，当其中一台haproxy出现故障后，keepalived的虚拟IP会自动漂移到另一台haproxy，client端连接的是keepalived的虚拟IP,最终实现高可用的环境。

之前做了那么多的准备，今天来实际安装一下：

1，当前环境：

Haproxy IP | keepalived IP（两台主机都部署haproxy以及keepalived)
172.17.61.134 qht134
172.17.61.135 qht135
172.17.61.140 vip

PXC IP
172.17.61.131 qht131
172.17.61.132 qht132
172.17.61.133 qht133

[root@qht131 ~]# more /etc/redhat-release
Red Hat Enterprise Linux Server release 6.3 (Santiago)

[root@qht131 ~]# mysql -V
mysql  Ver 14.14 Distrib 5.7.21-20, for Linux (x86_64) using  6.0

2，配置pxc节点监控

2.1创建状态检查用户（任一pxc节点）

[root@qht131 ~]# locate clustercheck
/usr/bin/clustercheck
[root@qht131 ~]# grep clustercheckuser /usr/bin/clustercheck
# GRANT PROCESS ON *.* TO 'clustercheckuser'@'localhost' IDENTIFIED BY 'clustercheckpassword!';

[root@qht131 ~]# mysql -uroot -p
mysql> GRANT PROCESS ON *.* TO 'clustercheckuser'@'localhost' IDENTIFIED BY 'clustercheckpassword!';
Query OK, 0 rows affected, 1 warning (0.54 sec)

mysql> flush privileges;
Query OK, 0 rows affected (0.08 sec)

2.2 PXC三节点手工执行clusterchek，确保返回200

[root@qht131 ~]# clustercheck
HTTP/1.1 200 OK
Content-Type: text/plain
Connection: close
Content-Length: 40

Percona XtraDB Cluster Node is synced.
2.3关闭防火墙及selinux 
[root@qht131 ~]# chkconfig --level 2345 iptables off

[root@qht131 ~]# cat /etc/selinux/config

# This file controls the state of SELinux on the system.
# SELINUX= can take one of these three values:
#     enforcing - SELinux security policy is enforced.
#     permissive - SELinux prints warnings instead of enforcing.
#     disabled - No SELinux policy is loaded.
SELINUX=disabled  #确保是disabled或者permissive
# SELINUXTYPE= can take one of these two values:
#     targeted - Targeted processes are protected,
#     mls - Multi Level Security protection.
SELINUXTYPE=targeted

3.安装haproxy(两个节点)

需要先检查安装haproxy的节点没有安装mysql，因为haproxy.cfg所绑定的也是3306端口，如果安装的话需要关闭或者在haproxy.cfg中指定其它的端口。

以其中一个节点为例：

[root@qht135 ~]# yum install haproxy -y
[root@qht135 ~]# rpm -aq | grep haproxy
haproxy-1.5.18-1.el6.x86_64

关闭防火墙:

[root@qht135 ~]# chkconfig --level 2345 iptables off

添加以下内容到haproxy.cfg配置文件

[root@qht135 ~]# vim /etc/haproxy/haproxy.cfg  
frontend pxc-front     ##前端监控配置名称，端口，协议，对应的后端名称
bind *:3306               
mode tcp     
default_backend pxc-back

frontend stats-front    ##web状态监控配置
bind *:8080
mode http
default_backend stats-back

backend pxc-back   ###后端配置
mode tcp
balance leastconn
option httpchk
server node131 172.17.61.131:3306 check port 9200 inter 12000 rise 3 fall 3
server node132 172.17.61.132:3306 check port 9200 inter 12000 rise 3 fall 3
server node133 172.17.61.133:3306 check port 9200 inter 12000 rise 3 fall 3

backend stats-back    ###web监控访问
mode http
balance roundrobin
stats uri /haproxy/stats
stats refresh 5s
stats auth pxcstats:secret ##8080登入的帐户和密码

启动haproxy服务：

[root@qht135 rc5.d]# service haproxy start
Starting haproxy:                                          [  OK  ]

如果启动有warining的话，需要根据指定注释掉haproxy.cfg中相关的参数 。

[root@qht135 rc5.d]# netstat -nltp|grep haproxy
tcp        0      0 0.0.0.0:3306                0.0.0.0:*                   LISTEN      5595/haproxy
tcp        0      0 0.0.0.0:8080                0.0.0.0:*                   LISTEN      5595/haproxy

4，验证haproxy

先增加一个测试的用户（其中一台pxc）

[root@node131 ~]# mysql -uroot -pxxx -hlocalhost
mysql>grant all privileges on *.* to 'robin'@'192.168.%' identified by 'xxx';

不断地循环连接数据库:

[root@qht135 ~]# for i in `seq 1 1000`; do mysql -hlocalhost -P3306 -urobin -pxxx --protocol=tcp -e "select now()"; done

打开网页输入配置文件中的帐户和密码：


5.安装keepalived(两个节点）

5.1详细过程见https://blog.csdn.net/jolly10/article/details/80704973

[root@qht134 home]# wget http://www.keepalived.org/software/keepalived-1.2.2.tar.gz  
[root@qht134 home]# tar -zxvf keepalived-1.2.2.tar.gz  
[root@qht134 home]# cd keepalived-1.2.2  
[root@qht134 keepalived-1.2.2]# yum -y install gcc openssl-devel popt-devel  
[root@qht134 keepalived-1.2.2]# ./configure --prefix=/ && make && make install  
[root@qht134 keepalived-1.2.2]# chkconfig --add keepalived  
[root@qht134 keepalived-1.2.2]# chkconfig keepalived on

修改keepalived配置文件：

查看当前的网络设备名，当前是eth2

[root@qht134 keepalived-1.2.2]# ip addr
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 16436 qdisc noqueue state UNKNOWN
    link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
    inet 127.0.0.1/8 scope host lo
    inet6 ::1/128 scope host
       valid_lft forever preferred_lft forever
2: eth2: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast state UP qlen 1000
    link/ether 00:0c:29:8b:fb:c0 brd ff:ff:ff:ff:ff:ff
    inet 172.17.61.135/24 brd 172.17.61.255 scope global eth2
    inet6 fe80::20c:29ff:fe8b:fbc0/64 scope link
       valid_lft forever preferred_lft forever
[root@qht134 keepalived]# cat  /etc/keepalived/keepalived.conf
! Configuration File for keepalived


global_defs {
    router_id LVS_DEVEL
}
#monitor haproxy process,execute every 2s
vrrp_script chk_haproxy {
    script "/etc/keepalived/chk_haproxy.sh"
    interval 2
    weight 2
}
vrrp_instance VI_1 {
    state MASTER          #qht134 set MASTER,qht135 set BACKUP
    interface eth2
    virtual_router_id 51
    priority 100             #qht134 set 100,qht135 set 50
    advert_int 1
    mcast_src_ip 172.17.61.134    #real ip
    authentication {
        auth_type PASS
        auth_pass 111111
    }
    track_script {
        chk_haproxy    #monitor status of haproxy process
    }
    virtual_ipaddress {
        172.17.61.140    #VIP
    }
}

[root@qht134 keepalived]# cat /etc/keepalived/chk_haproxy.sh
#!/bin/bash
#pkill keepalived
status=$(ps aux|grep haproxy | grep -v grep | grep -v bash | wc -l)
if [ "${status}" = "0" ]; then
    /etc/init.d/haproxy start


    status2=$(ps aux|grep haproxy | grep -v grep | grep -v bash |wc -l)


    if [ "${status2}" = "0"  ]; then
            /etc/init.d/keepalived stop
    fi
fi

[root@qht134~]# chmod u+x /etc/keepalived/chk_haproxy.sh

[root@qht134 keepalived-1.2.2]# scp /etc/keepalived/chk_haproxy.sh 172.17.61.135:/etc/keepalived/

通过chk_haproxy.sh脚本，当real_server发生故障时，就停止keepalived服务，将vip飘移到另一台haproxy.


5.2，配置另一台keepalived，安装过程和qht134一致。

只有配置文件需要三个地方修改一下：

[root@qht135 keepalived]# cat  /etc/keepalived/keepalived.conf
! Configuration File for keepalived


global_defs {
    router_id LVS_DEVEL
}
#monitor haproxy process,execute every 2s
vrrp_script chk_haproxy {
    script "/etc/keepalived/chk_haproxy.sh"
    interval 2
    weight 2
}
vrrp_instance VI_1 {
    state BACKUP          #qht134 set MASTER,qht135 set BACKUP
    interface eth2
    virtual_router_id 51
    priority 50             #qht134 set 100,qht135 set 50
    advert_int 1
    mcast_src_ip 172.17.61.135    #real ip
    authentication {
        auth_type PASS
        auth_pass 111111
    }
    track_script {
        chk_haproxy    #monitor status of haproxy process
    }
    virtual_ipaddress {
        172.17.61.140    #VIP
    }
}

两个节点都打开keepalived

[root@qht134 keepalived-1.2.2]#  /etc/init.d/keepalived restart
Stopping keepalived:                                       [  OK  ]
Starting keepalived:                                       [  OK  ]

[root@qht135 keepalived-1.2.2]#  /etc/init.d/keepalived restart
Stopping keepalived:                                       [  OK  ]
Starting keepalived:                                       [  OK  ]

5.3，测试keepalived

[root@qht134 keepalived-1.2.2]#  ip addr
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 16436 qdisc noqueue state UNKNOWN
    link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
    inet 127.0.0.1/8 scope host lo
    inet6 ::1/128 scope host
       valid_lft forever preferred_lft forever
2: eth2: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast state UP qlen 1000
    link/ether 00:0c:29:42:74:a0 brd ff:ff:ff:ff:ff:ff
    inet 172.17.61.134/24 brd 172.17.61.255 scope global eth2
    inet 172.17.61.140/32 scope global eth2
    inet6 fe80::20c:29ff:fe42:74a0/64 scope link
       valid_lft forever preferred_lft forever

当前的vip是在qht134上面，来测试一下qht134的haproxy中断后，vip会不会漂移到qht135

[root@qht134 keepalived-1.2.2]# service haproxy stop
Stopping haproxy:                                          [  OK  ]
[root@qht134 keepalived]#  ip addr show eth2
2: eth2: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast state UP qlen 1000
    link/ether 00:0c:29:42:74:a0 brd ff:ff:ff:ff:ff:ff
    inet 172.17.61.134/24 brd 172.17.61.255 scope global eth2
    inet 172.17.61.140/32 scope global eth2
    inet6 fe80::20c:29ff:fe42:74a0/64 scope link
       valid_lft forever preferred_lft forever

关闭haproxy服务后，VIP并没有漂移到qht135,这是由于chk_haproxy.sh会不断监测haproxy进程，发现haproxy中断后会重启服务。

[root@qht134 keepalived]#   service haproxy status
haproxy (pid  17203) is running...

所以关闭后又被重启了。

那我只有直接关闭keepalived服务试下能不能漂移到qht135:

[root@qht134 keepalived]#  service keepalived  stop
Stopping keepalived:                                       [  OK  ]

查看/etc/log/messages发现VIP已从本机移除：

Jun 25 18:30:37 qht134 Keepalived: Terminating on signal
Jun 25 18:30:37 qht134 Keepalived_vrrp: Terminating VRRP child process on signal
Jun 25 18:30:37 qht134 Keepalived_vrrp: VRRP_Instance(VI_1) removing protocol VIPs.
Jun 25 18:30:37 qht134 Keepalived: Stopping Keepalived v1.2.2 (06/22,2018)

查看qht134的网络状态：

[root@qht134 keepalived]#  ip addr show eth2
2: eth2: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast state UP qlen 1000
    link/ether 00:0c:29:42:74:a0 brd ff:ff:ff:ff:ff:ff
    inet 172.17.61.134/24 brd 172.17.61.255 scope global eth2
    inet6 fe80::20c:29ff:fe42:74a0/64 scope link
       valid_lft forever preferred_lft forever

查看qht135的网络状态：

[root@qht135 keepalived-1.2.2]# ip addr show eth2
2: eth2: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast state UP qlen 1000
    link/ether 00:0c:29:8b:fb:c0 brd ff:ff:ff:ff:ff:ff
    inet 172.17.61.135/24 brd 172.17.61.255 scope global eth2
    inet 172.17.61.140/32 scope global eth2
    inet6 fe80::20c:29ff:fe8b:fbc0/64 scope link
       valid_lft forever preferred_lft forever

[root@qht135 keepalived-1.2.2]# tail -n5 /var/log/messages
Jun 25 18:30:41 qht131 Keepalived_vrrp: VRRP_Instance(VI_1) Entering MASTER STATE
Jun 25 18:30:41 qht131 Keepalived_vrrp: VRRP_Instance(VI_1) setting protocol VIPs.
Jun 25 18:30:41 qht131 avahi-daemon[1326]: Registering new address record for 172.17.61.140 on eth2.IPv4.
Jun 25 18:30:41 qht131 Keepalived_vrrp: VRRP_Instance(VI_1) Sending gratuitous ARPs on eth2 for 172.17.61.140
Jun 25 18:30:46 qht131 Keepalived_vrrp: VRRP_Instance(VI_1) Sending gratuitous ARPs on eth2 for 172.17.61.140

VIP已被qht135注册，说明飘移成功！

继续测试，如果qht134的keepalived重新开启后会发生什么：

[root@qht134 keepalived]#  service keepalived start
Starting keepalived:                                       [  OK  ]
[root@qht134 keepalived]#  ip addr show eth2
2: eth2: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast state UP qlen 1000
    link/ether 00:0c:29:42:74:a0 brd ff:ff:ff:ff:ff:ff
    inet 172.17.61.134/24 brd 172.17.61.255 scope global eth2
    inet 172.17.61.140/32 scope global eth2
    inet6 fe80::20c:29ff:fe42:74a0/64 scope link
       valid_lft forever preferred_lft forever

[root@qht135 keepalived-1.2.2]#  ip addr show eth2
2: eth2: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast state UP qlen 1000
    link/ether 00:0c:29:8b:fb:c0 brd ff:ff:ff:ff:ff:ff
    inet 172.17.61.135/24 brd 172.17.61.255 scope global eth2
    inet6 fe80::20c:29ff:fe8b:fbc0/64 scope link
       valid_lft forever preferred_lft forever

[root@qht135 keepalived-1.2.2]#  tail -n5 /var/log/messages
Jun 25 18:30:46 qht131 Keepalived_vrrp: VRRP_Instance(VI_1) Sending gratuitous ARPs on eth2 for 172.17.61.140
Jun 25 18:42:46 qht131 Keepalived_vrrp: VRRP_Instance(VI_1) Received higher prio advert
Jun 25 18:42:46 qht131 Keepalived_vrrp: VRRP_Instance(VI_1) Entering BACKUP STATE
Jun 25 18:42:46 qht131 Keepalived_vrrp: VRRP_Instance(VI_1) removing protocol VIPs.
Jun 25 18:42:46 qht131 avahi-daemon[1326]: Withdrawing address record for 172.17.61.140 on eth2.

从qht135的日志来看，由于qht134的等级比较高，master的服务启动后vip就被qht134夺了过去。


6. keepalived以及haproxy都安装测试完成之后，客户端只需要连接VIP就可以连接pxc数据库，至此mysql的高可用配置完成！


参考：

https://blog.csdn.net/leshami/article/details/79105893

https://www.cnblogs.com/kgdxpr/p/3325788.html

zuozhiji
关注
专栏目录
基于haproxy +keepalived 的 percona xtradb cluster 安装配置
wjl7813的博客
02-02 2357
Percona XtraDB cluster 安装与运维维护 安装准备工作  [root@pxc3 ~]# cat /etc/hosts  127.0.0.1   localhost localhost.localdomain localhost4 localhost4.localdomain4 ::1         localhost localhost.localdoma
pxc+haproxy+keepalive
weixin_45473752的博客
12-11 432
本文基于PXC 5.7集群环境来配置Haproxy以及结合Keepalived实现MySQL的读写分离，以下为主要配置方法及其步骤。 参考文档：配置Haproxy + Keepalived +PXC 5.7 部分配置文件由于无法正常启动，按可以启动的配置进行修改 一、当前环境 Haproxy IP | keepalived IP（两台主机都部署haproxy以及keepalived) 192.168.81.19 hp1 192.168.81.20 hp2 192.168.81.100 vip PXC IP
keepalived+haproxy 安装 PXC高可用
EVISWANG的博客
09-13 864
pxc节点:10.194.41.231 10.194.41.228 10.194.41.227 ha: 10.194.41.220 主 10.194.41.221 备 vip:10.194.41.199 一.安装keepalived 1.yum install keepalived 2.修改配置 主节点4上 vi /etc/keepalived/keepalived
Red Hat Enterprise Linux Server release 6.3 实现双网卡绑定
TURING.DT
04-13 1579
Red Hat Enterprise Linux Server release 6.3 实现双网卡绑定 查看OS版本 # cat /etc/issue Red Hat Enterprise Linux Server release 6.3 查看系统目前是否支持绑定功能（不显示如下信息，表示不支持，请网上查找解决方法） # cat /boot/config-2.6.32-279.e
Keepalived + Haproxy + PXC 理论篇
weixin_30537451的博客
06-18 184
最终模型： 将Kp1 + Kp2 分别和Ha1和Ha2部署在一起，同时绑定VIP ip，对外提供访问，同时监控本机的Haproxy的可用性 通过Ha1 + Ha2 为PXC提供负载均衡，分发请求到后端某台PXC，同时检测后端的PXC数据库可用性 PXC 多主复制提供读写能力 Haproxy 反向代理 工作在7层模型上，可以分析数据包中的应用层协议，并按规则进行负载 默认使用 tcp 协...
PXC+haproxy+keepalived环境搭建
aa5181的专栏
11-14 214
环境准备： 三节点PXC，部署过程见：http://blog.itpub.net/30135314/viewspace-2219505/ 192.168.8.51 ...
HAProxy+Keepalived+MySQL.pdf
09-30
编写这个脚本并在Keepalived配置中引用，以便在HAProxy异常时触发故障转移。 4. **测试**： 完成上述步骤后，启动HAProxy和Keepalived服务，进行测试以验证高可用性。可以通过模拟主服务器故障，观察是否能成功...
linux安装nginx+keepalived，和tomcat负载均衡配置，动静分离配置，主备和双主模式
07-10
本教程将详细讲解如何在Linux系统上安装Nginx、Keepalived，并进行Tomcat的负载均衡配置，以及动静分离的设置，涵盖主备模式和双主模式。通过实践这些步骤，你可以提升服务器的稳定性和性能。 首先，我们需要安装...
运维笔记43 使用saltstack配置完整线上服务(haproxy+keepalived,nginx+php+memcache,mysql主从)
No_red的博客
04-26 2761
概述:之前我们所介绍过了很多实用的服务，有负载均衡类的，web服务类的，数据库类的等等，这些服务有的配置容易，有的配置困难，那我们现在设想一下在生成环境中，有上百台，甚至上千台服务器的情况下，难道要我们去挨个去配置每一台服务器吗，这是无法想象的，所以有了saltstack这类自动化运维工具的出现，帮助我们高效快速的部署服务。 线上服务拓扑 这次的拓扑基本上已经可以胜任一个相当活跃的服务的后端架构了
vmware10下rhel6.3完整安装步骤
01-14
这个安装过程涵盖了RHEL 6.3在VMware10中的基本配置和安装步骤，包括网络、分区、时区、root密码和软件包的选择。每个步骤都是为了确保系统能够稳定运行，并根据用户的需求进行定制。在实际操作中，可能还需要根据...
HAproxy+Keepalived 负载均衡架构搭建
08-25
redhat 5.8（64位）下HAproxy+Keepalived 负载均衡架构搭建@整理V1..rar
yum源，系统版本：Red Hat Enterprise Linux Server release 6.8 (Santiago)
05-06
Red Hat 系统使用 CentOS的yum源配置文件，CentOS-Base.repo，Red Hat Enterprise Linux Server release 6.8 (Santiago)测试可用， release 6.5, release 6.9应该也可以
RHEL-5.7+DRBD+heartbeat+Oracle10R2双机安装实例.doc
10-12
RHEL-5.7+DRBD+heartbeat+Oracle10R2双机安装实例.doc
Red Hat Enterprise Linux Server release 6.3下ganglia监控系统的搭建
weixin_33948416的博客
11-11 108
ganglia 是分布式的监控系统,有两个Daemon, 分别是:客户端Ganglia Monitoring Daemon(gmond)和服务端Ganglia Meta Daemon (gmetad),还有Ganglia PHP Web Frontend(基于web的动态访问方式)组成是一个Linux下图形化监控系统运行性能的软件,界面美观、丰富,功能强大http://gan...
Red Hat Enterprise Linux Server release 6.3下Nagios平台的搭建
weixin_33815613的博客
10-27 99
nagios官方网站：http://www.nagios.org nagios下载：http://www.nagios.org/download/core/thanks/ nagios插件下载：http://www.nagios.org/download/plugins nagios-cn:http:/...
HAProxy+Keepalived+PXC负载均衡和高可用的PXC环境
08-01 269
HAProxy介绍 反向代理服务器,支持双机热备支持虚拟主机,但其配置简单,拥有非常不错的服务器健康检查功能,当其代理的后端服务器出现故障, HAProxy会自动将该服务器摘除,故障恢复后再自动将该服务器加入｡引入了frontend,backend；frontend根据任意 HTTP请求头内容做规则匹配,然后把请求定向到相关的backend. Keepalived介绍Keepaliv...
redhat6.3安装Keepalived+LVS
ceiling的博客
06-03 1194
1、下载软件 wget http://www.keepalived.org/software/keepalived-1.2.19.tar.gz 2、安装所需的依赖包 yum -y install gcc  gcc-c++ popt-devel openssl openssl-devel libnfnetlink 3、安装lvs与keepalived rpm -ivh ipvsadm-1.
redhat6.3的linux内核版本,1-6-RHEL6.3-内核升级（Red Hat Enterprise Linux Server6.3）@树袋飘零...
weixin_35009537的博客
05-05 422
本节介绍内容：1、内核的概述2、源码编译安装文件系统中的ntfs内核模块案例分析1、内核的概述Linux操作系统是用来跟硬件和用户程序互联的支撑平台，设备的驱动程序完全可以访问硬件，而设备的驱动程序以模块化的形式设置，可以进行安装和卸载。在linux中这个操作系统被称为内核。内核的主要模块包括如下：文件系统内存管理进程管理模块管理系统启动设备驱动程序等等2、源码编译安装文件系统中的ntfs内核模块...
使用nginx+keepalived构建高可用7层负载均衡
安装完成后，需要配置Keepalived的配置文件，指定VRRP组、优先级、虚拟IP等信息。 对于Nginx，同样需要在系统中安装。配置文件中应设定负载均衡策略，如轮询、最少连接数或者IP哈希等。此外，还需要在Keepalived的...
评论
添加红包

请填写红包祝福语或标题

个

红包个数最小为10个

元

红包金额最低5元

当前余额3.43元 前往充值 >
需支付：10.00元
成就一亿技术人!
领取后你会自动成为博主和红包主的粉丝 规则
hope_wisdom
发出的红包
实付元
使用余额支付
点击重新获取
扫码支付
钱包余额 0

抵扣说明：

1.余额是钱包充值的虚拟货币，按照1:1的比例进行支付金额的抵扣。
2.余额无法直接购买下载，可以购买VIP、付费专栏及课程。

余额充值