Greenplum集群状态检查及失败segment修复(上)

最新推荐文章于 2023-11-02 09:10:20 发布
最新推荐文章于 2023-11-02 09:10:20 发布
阅读量3.1k 收藏 4
点赞数
文章标签： 大数据 数据库 python
原文链接：https://my.oschina.net/levinehuang/blog/739626
版权
本文介绍了如何检查Greenplum集群的状态，包括使用gp_segment_configuration和gpstate工具。当发现segment失败时，通过gprecoverseg工具进行修复，并详细描述了修复过程，包括确保primary和mirror的同步以及恢复segment到初始角色。最后，文中提到了遗留问题，即对不同场景下的故障恢复还需要更深入的理解。
摘要由CSDN通过智能技术生成

2019独角兽企业重金招聘Python工程师标准>>> hot3.png

一、GP集群运行状态检查

  1. 查gp_segment_configuration，status='d'表示segment失败，status='u'表示segment正常
SELECT * FROM gp_segment_configuration WHERE status='d';
  1. gpstate查看各个primary、mirror segment状态信息 集群状态：
    9个 primary segment失败
    3个 mirror segment失败
    此时，GP集群增删改查均正常，猜测是mirror segment起了作用。
[gpadmin@gpm ~]$ gpstate
20160829:17:36:08:035340 gpstate:gpm:gpadmin-[INFO]:-Starting gpstate with args: 
20160829:17:36:08:035340 gpstate:gpm:gpadmin-[INFO]:-local Greenplum Version: 'postgres (Greenplum Database) 4.3.8.2 build 1'
20160829:17:36:08:035340 gpstate:gpm:gpadmin-[INFO]:-master Greenplum Version: 'PostgreSQL 8.2.15 (Greenplum Database 4.3.8.2 build 1) on x86_64-unknown-linux-gnu, compiled by GCC gcc (GCC) 4.4.2 compiled on May  9 2016 22:28:40'
20160829:17:36:09:035340 gpstate:gpm:gpadmin-[INFO]:-Obtaining Segment details from master...
20160829:17:36:09:035340 gpstate:gpm:gpadmin-[INFO]:-Gathering data from segments...
. 
20160829:17:36:10:035340 gpstate:gpm:gpadmin-[INFO]:-Greenplum instance status summary
20160829:17:36:10:035340 gpstate:gpm:gpadmin-[INFO]:-----------------------------------------------------
20160829:17:36:10:035340 gpstate:gpm:gpadmin-[INFO]:-   Master instance                                           = Active
20160829:17:36:10:035340 gpstate:gpm:gpadmin-[INFO]:-   Master standby                                            = gps1
20160829:17:36:10:035340 gpstate:gpm:gpadmin-[INFO]:-   Standby master state                                      = Standby host passive
20160829:17:36:10:035340 gpstate:gpm:gpadmin-[INFO]:-   Total segment instance count from metadata                = 24
20160829:17:36:10:035340 gpstate:gpm:gpadmin-[INFO]:-----------------------------------------------------
20160829:17:36:10:035340 gpstate:gpm:gpadmin-[INFO]:-   Primary Segment Status
20160829:17:36:10:035340 gpstate:gpm:gpadmin-[INFO]:-----------------------------------------------------
20160829:17:36:10:035340 gpstate:gpm:gpadmin-[INFO]:-   Total primary segments                                    = 12
20160829:17:36:10:035340 gpstate:gpm:gpadmin-[INFO]:-   Total primary segment valid (at master)                   = 3
20160829:17:36:10:035340 gpstate:gpm:gpadmin-[WARNING]:-Total primary segment failures (at master)                = 9                      <<<<<<<<
20160829:17:36:10:035340 gpstate:gpm:gpadmin-[WARNING]:-Total number of postmaster.pid files missing              = 9                      <<<<<<<<
20160829:17:36:10:035340 gpstate:gpm:gpadmin-[INFO]:-   Total number of postmaster.pid files found                = 3
20160829:17:36:10:035340 gpstate:gpm:gpadmin-[WARNING]:-Total number of postmaster.pid PIDs missing               = 9                      <<<<<<<<
20160829:17:36:10:035340 gpstate:gpm:gpadmin-[INFO]:-   Total number of postmaster.pid PIDs found                 = 3
20160829:17:36:10:035340 gpstate:gpm:gpadmin-[WARNING]:-Total number of /tmp lock files missing                   = 9                      <<<<<<<<
20160829:17:36:10:035340 gpstate:gpm:gpadmin-[INFO]:-   Total number of /tmp lock files found                     = 3
20160829:17:36:10:035340 gpstate:gpm:gpadmin-[WARNING]:-Total number postmaster processes missing                 = 9                      <<<<<<<<
20160829:17:36:10:035340 gpstate:gpm:gpadmin-[INFO]:-   Total number postmaster processes found                   = 3
20160829:17:36:10:035340 gpstate:gpm:gpadmin-[INFO]:-----------------------------------------------------
20160829:17:36:10:035340 gpstate:gpm:gpadmin-[INFO]:-   Mirror Segment Status
20160829:17:36:10:035340 gpstate:gpm:gpadmin-[INFO]:-----------------------------------------------------
20160829:17:36:10:035340 gpstate:gpm:gpadmin-[INFO]:-   Total mirror segments                                     = 12
20160829:17:36:10:035340 gpstate:gpm:gpadmin-[INFO]:-   Total mirror segment valid (at master)                    = 9
20160829:17:36:10:035340 gpstate:gpm:gpadmin-[WARNING]:-Total mirror segment failures (at master)                 = 3                      <<<<<<<<
20160829:17:36:10:035340 gpstate:gpm:gpadmin-[WARNING]:-Total number of postmaster.pid files missing              = 3                      <<<<<<<<
20160829:17:36:10:035340 gpstate:gpm:gpadmin-[INFO]:-   Total number of postmaster.pid files found                = 9
20160829:17:36:10:035340 gpstate:gpm:gpadmin-[WARNING]:-Total number of postmaster.pid PIDs missing               = 3                      <<<<<<<<
20160829:17:36:10:035340 gpstate:gpm:gpadmin-[INFO]:-   Total number of postmaster.pid PIDs found                 = 9
20160829:17:36:10:035340 gpstate:gpm:gpadmin-[WARNING]:-Total number of /tmp lock files missing                   = 3                      <<<<<<<<
20160829:17:36:10:035340 gpstate:gpm:gpadmin-[INFO]:-   Total number of /tmp lock files found                     = 9
20160829:17:36:10:035340 gpstate:gpm:gpadmin-[WARNING]:-Total number postmaster processes missing                 = 3                      <<<<<<<<
20160829:17:36:10:035340 gpstate:gpm:gpadmin-[INFO]:-   Total number postmaster processes found                   = 9
20160829:17:36:10:035340 gpstate:gpm:gpadmin-[WARNING]:-Total number mirror segments acting as primary segments   = 9                      <<<<<<<<
20160829:17:36:10:035340 gpstate:gpm:gpadmin-[INFO]:-   Total number mirror segments acting as mirror segments    = 3
20160829:17:36:10:035340 gpstate:gpm:gpadmin-[INFO]:-----------------------------------------------------
  1. gpstate -m列出mirror 实例的状态和配置信息。 失败的primary segment被mirror segment顶起来了，可以看到，有9个mirror segment Acting as Primary。
[gpadmin@gpm ~]$ gpstate -m
20160829:17:38:03:035819 gpstate:gpm:gpadmin-[INFO]:-Starting gpstate with args: -m
20160829:17:38:03:035819 gpstate:gpm:gpadmin-[INFO]:-local Greenplum Version: 'postgres (Greenplum Database) 4.3.8.2 build 1'
20160829:17:38:03:035819 gpstate:gpm:gpadmin-[INFO]:-master Greenplum Version: 'PostgreSQL 8.2.15 (Greenplum Database 4.3.8.2 build 1) on x86_64-unknown-linux-gnu, compiled by GCC gcc (GCC) 4.4.2 compiled on May  9 2016 22:28:40'
20160829:17:38:03:035819 gpstate:gpm:gpadmin-[INFO]:-Obtaining Segment details from master...
20160829:17:38:04:035819 gpstate:gpm:gpadmin-[INFO]:--------------------------------------------------------------
20160829:17:38:04:035819 gpstate:gpm:gpadmin-[INFO]:--Current GPDB mirror list and status
20160829:17:38:04:035819 gpstate:gpm:gpadmin-[INFO]:--Type = Group
20160829:17:38:04:035819 gpstate:gpm:gpadmin-[INFO]:--------------------------------------------------------------
20160829:17:38:04:035819 gpstate:gpm:gpadmin-[INFO]:-   Mirror   Datadir                             Port    Status              Data Status       
20160829:17:38:04:035819 gpstate:gpm:gpadmin-[INFO]:-   gps2     /hdfs/data5/gpdata/mirror/gpseg0    50000   Acting as Primary   Change Tracking
20160829:17:38:04:035819 gpstate:gpm:gpadmin-[INFO]:-   gps2     /hdfs/data6/gpdata/mirror/gpseg1    50001   Acting as Primary   Change Tracking
20160829:17:38:04:035819 gpstate:gpm:gpadmin-[INFO]:-   gps2     /hdfs/data7/gpdata/mirror/gpseg2    50002   Acting as Primary   Change Tracking
20160829:17:38:04:035819 gpstate:gpm:gpadmin-[INFO]:-   gps2     /hdfs/data8/gpdata/mirror/gpseg3    50003   Acting as Primary   Change Tracking
20160829:17:38:04:035819 gpstate:gpm:gpadmin-[INFO]:-   gps3     /hdfs/data5/gpdata/mirror/gpseg4    50000   Acting as Primary   Change Tracking
20160829:17:38:04:035819 gpstate:gpm:gpadmin-[INFO]:-   gps3     /hdfs/data6/gpdata/mirror/gpseg5    50001   Acting as Primary   Change Tracking
20160829:17:38:04:035819 gpstate:gpm:gpadmin-[INFO]:-   gps3     /hdfs/data7/gpdata/mirror/gpseg6    50002   Acting as Primary   Change Tracking
20160829:17:38:04:035819 gpstate:gpm:gpadmin-[INFO]:-   gps3     /hdfs/data8/gpdata/mirror/gpseg7    50003   Acting as Primary   Change Tracking
20160829:17:38:04:035819 gpstate:gpm:gpadmin-[WARNING]:-gps1     /hdfs/data5/gpdata/mirror/gpseg8    50000   Failed                                <<<<<<<<
20160829:17:38:04:035819 gpstate:gpm:gpadmin-[WARNING]:-gps1     /hdfs/data6/gpdata/mirror/gpseg9    50001   Failed                                <<<<<<<<
20160829:17:38:04:035819 gpstate:gpm:gpadmin-[INFO]:-   gps1     /hdfs/data7/gpdata/mirror/gpseg10   50002   Acting as Primary   Change Tracking
20160829:17:38:04:035819 gpstate:gpm:gpadmin-[WARNING]:-gps1     /hdfs/data8/gpdata/mirror/gpseg11   50003   Failed                                <<<<<<<<
20160829:17:38:04:035819 gpstate:gpm:gpadmin-[INFO]:--------------------------------------------------------------
20160829:17:38:04:035819 gpstate:gpm:gpadmin-[WARNING]:-9 segment(s) configured as mirror(s) are acting as primaries
20160829:17:38:04:035819 gpstate:gpm:gpadmin-[WARNING]:-3 segment(s) configured as mirror(s) have failed
20160829:17:38:04:035819 gpstate:gpm:gpadmin-[WARNING]:-9 mirror segment(s) acting as primaries are in change tracking
  1. gpstate -c 查看primary instance 和 mirror instance 的对应关系
[gpadmin@gpm ~]$ gpstate -c
20160829:17:38:53:035970 gpstate:gpm:gpadmin-[INFO]:-Starting gpstate with args: -c
20160829:17:38:53:035970 gpstate:gpm:gpadmin-[INFO]:-local Greenplum Version: 'postgres (Greenplum Database) 4.3.8.2 build 1'
20160829:17:38:53:035970 gpstate:gpm:gpadmin-[INFO]:-master Greenplum Version: 'PostgreSQL 8.2.15 (Greenplum Database 4.3.8.2 build 1) on x86_64-unknown-linux-gnu, compiled by GCC gcc (GCC) 4.4.2 compiled on May  9 2016 22:28:40'
20160829:17:38:53:035970 gpstate:gpm:gpadmin-[INFO]:-Obtaining Segment details from master...
20160829:17:38:54:035970 gpstate:gpm:gpadmin-[INFO]:--------------------------------------------------------------
20160829:17:38:54:035970 gpstate:gpm:gpadmin-[INFO]:--Current GPDB mirror list and status
20160829:17:38:54:035970 gpstate:gpm:gpadmin-[INFO]:--Type = Group
20160829:17:38:54:035970 gpstate:gpm:gpadmin-[INFO]:--------------------------------------------------------------
20160829:17:38:54:035970 gpstate:gpm:gpadmin-[INFO]:-   Status                          Data State        Primary   Datadir                              Port    Mirror   Datadir                             Port
20160829:17:38:54:035970 gpstate:gpm:gpadmin-[WARNING]:-Mirror Active, Primary Failed   Change Tracking   gps1      /hdfs/data1/gpdata/primary/gpseg0    40000   gps2     /hdfs/data5/gpdata/mirror/gpseg0    50000   <<<<<<<<
20160829:17:38:54:035970 gpstate:gpm:gpadmin-[WARNING]:-Mirror Active, Primary Failed   Change Tracking   gps1      /hdfs/data2/gpdata/primary/gpseg1    40001   gps2     /hdfs/data6/gpdata/mirror/gpseg1    50001   <<<<<<<<
20160829:17:38:54:035970 gpstate:gpm:gpadmin-[WARNING]:-Mirror Active, Primary Failed   Change Tracking   gps1      /hdfs/data3/gpdata/primary/gpseg2    40002   gps2     /hdfs/data7/gpdata/mirror/gpseg2    50002   <<<<<<<<
20160829:17:38:54:035970 gpstate:gpm:gpadmin-[WARNING]:-Mirror Active, Primary Failed   Change Tracking   gps1      /hdfs/data4/gpdata/primary/gpseg3    40003   gps2     /hdfs/data8/gpdata/mirror/gpseg3    50003   <<<<<<<<
20160829:17:38:54:035970 gpstate:gpm:gpadmin-[WARNING]:-Mirror Active, Primary Failed   Change Tracking   gps2      /hdfs/data1/gpdata/primary/gpseg4    40000   gps3     /hdfs/data5/gpdata/mirror/gpseg4    50000   <<<<<<<<
20160829:17:38:54:035970 gpstate:gpm:gpadmin-[WARNING]:-Mirror Active, Primary Failed   Change Tracking   gps2      /hdfs/data2/gpdata/primary/gpseg5    40001   gps3     /hdfs/data6/gpdata/mirror/gpseg5    50001   <<<<<<<<
20160829:17:38:54:035970 gpstate:gpm:gpadmin-[WARNING]:-Mirror Active, Primary Failed   Change Tracking   gps2      /hdfs/data3/gpdata/primary/gpseg6    40002   gps3     /hdfs/data7/gpdata/mirror/gpseg6    50002   <<<<<<<<
20160829:17:38:54:035970 gpstate:gpm:gpadmin-[WARNING]:-Mirror Active, Primary Failed   Change Tracking   gps2      /hdfs/data4/gpdata/primary/gpseg7    40003   gps3     /hdfs/data8/gpdata/mirror/gpseg7    50003   <<<<<<<<
20160829:17:38:54:035970 gpstate:gpm:gpadmin-[WARNING]:-Primary Active, Mirror Failed   Change Tracking   gps3      /hdfs/data1/gpdata/primary/gpseg8    40000   gps1     /hdfs/data5/gpdata/mirror/gpseg8    50000   <<<<<<<<
20160829:17:38:54:035970 gpstate:gpm:gpadmin-[WARNING]:-Primary Active, Mirror Failed   Change Tracking   gps3      /hdfs/data2/gpdata/primary/gpseg9    40001   gps1     /hdfs/data6/gpdata/mirror/gpseg9    50001   <<<<<<<<
20160829:17:38:54:035970 gpstate:gpm:gpadmin-[WARNING]:-Mirror Active, Primary Failed   Change Tracking   gps3      /hdfs/data3/gpdata/primary/gpseg10   40002   gps1     /hdfs/data7/gpdata/mi
最低0.47元/天 解锁文章
weixin_34014277
关注
Greenplum数据库中segment的故障检测与恢复
jmx_bigdata的博客
11-28 5485
1.Greenplum数据库中segment故障检测 1.1概述 Greenplum数据库服务器（Postgres）有一个子进程，该子进程为ftsprobe，主要作用是处理故障检测。 ftsprobe 监视Greenplum数据库阵列，它以可以配置的间隔连接并扫描所有segment和数据库进程。 如果 ftsprobe无法连接到segment，它会在Greenplum数据库系统目录中将seg...
greenplum生产集群中segment故障恢复
jmx_bigdata的博客
12-15 1695
目录   一、greenplum集群环境 二、segment故障检查 2.1gpstate -m日志信息 2.2gpstate -c 日志信息 2.3gpstate -e 日志信息 2.4gpstate -s 日志信息 2.5故障说明 三、segment故障恢复 3.1在master主机上运行下面命令，重新激活失败的segment 3.2运行gpstate 命令用于验证重新同...
greenplum 节点故障修复文档
weixin_33724570的博客
04-26 2282
greenplum集群说明 greenplum整个集群是由多台服务器组合而成，任何一台服务都有可能发生软件或硬件故障，我们一起来模拟一下任何一个节点或服务器故障后，greenplumn的容错及恢复方法 master 服务器：l-test5 standby 服务器：l-test6 segment 服务器:（primary + mirror）:l-tes...
查看GP各segment信息
mengbing1990的博客
07-10 254
SELECT * FROM gp_segment_configuration order by hostname,role asc;
Greenplum数据库故障分析——UDP Packet Lost（packet reassembles failed）
肥叔菌的博客
07-05 1629
最近在项目中遇到SQL挂死，业务无法继续进行下去的情况。在经过几次测试验证（将挂死主机节点踢出集群、将udpifc切换为tcp），该问题会消失。将挂死主机节点加入集群会直接复现。但是将udp切换为tcp后，经过一段时间再切换为udp后，不会复现，但是经过一段时间后，该问题又会复现。 经过排查后，定位在于udp无法成功组包，主要表现在某台主机packet reassembles failed增长量和速度远高于其他主机。 一. Packet reassemble 当发送的UDP报文长度大于MTU大小时，IP层会
Greenplum failed segment的恢复方法
皓月如我的专栏
02-02 5728
转载自：li0924的博客《Greenplum failed segment的恢复方法》 【前记】 Segment检测及故障切换机制 GP Master首先会检测Primary状态，如果Primary不可连通，那么将会检测Mirror状态，Primary/Mirror状态总共有4种： 1. Primary活着，Mirror活着。GP Master探测Primary成功之后直接返回，进行下一
故障分析 | Greenplum Segment 故障处理
ActionTech的博客
02-02 965
作者：杨文DBA，负责客户项目的需求与维护，会点数据库，不限于MySQL、Redis、Cassandra、GreenPlum、ClickHouse、Elastic、TDSQL等等。本文来源：原创投稿*爱可生开源社区出品，原创内容未经授权不得随意使用，转载请联系小编并注明来源。
Greenplum清除mirror
12-03
1. **检查集群状态**： 在执行任何操作前，确保Greenplum集群处于健康状态，可以通过`gpstate -s`命令查看。输出中应显示"Mirror status = Synchronized"，表明所有镜像与主段同步。 2. **关闭集群**： 使用`...
【实战经验】Greenplum集群Master與Segment节点故障检测与恢复
Greenplum中文社区
06-09 2181
了解更多G...
Greenplum Segment节点掉线恢复介绍
weixin_43451783的博客
05-18 1004
1. 背景 Greenplum版本：6.13.0 问题： Segment节点异常关机，恢复Segment节点并恢复Mirror节点状态。 如图所示：sdw1节点掉线。 2. 解决方法： 2.1 查看Mirror节点状态 查看错误Segment状态 处理过程： 1. 执行命令，会在当前目录生成一个recov文件，里面包含了要恢复的节点信息 gprecoverseg -o ./recov gprecoverseg -i recov ...
GreenPlum数据库集群故障检测与恢复
hmxz2nn的博客
10-24 4232
Segment镜像概述 当Greenplum数据库高可用性被启用时，有两种类型的Segment：主Segment和镜像Segment，每个主Segment都有一个对应的镜像Segment。主Segment从Master接收请求来对该Segment的数据库做更改并且接着把那些更改复制到对应的镜像。如果主Segment变成不可用，数据库请求会被转移到镜像Segment。 Segment镜像采用了一种物...
[原]Greenplum failed segment的恢复方法
weixin_30566063的博客
10-10 326
　　当在使用greenplum过程中有不当的操作时，可能会出现segment节点宕掉的情况（比如在greenplum运行的过程中停掉其中几台segment节点的服务器），通过下面的方法可以恢复segment。 下面是现场出现的故障情况： [gpadmin@tj-soc-c04-csfb1 ~]$ gpstate -m 20161010:16:35:54:026100 gpstate:tj...
green plum集群搭建初始化报错怎么解决
weixin_42613360的博客
02-13 111
要解决 green plum 集群搭建初始化报错，首先要查看报错日志，仔细分析错误信息，从而确定出现错误的原因，根据错误信息修正相应的配置，再重新搭建 green plum 集群，即可解决报错问题。 ...
greenplum常用运维命令
sinat_37316828的博客
06-11 2750
greenplum常用命令&运维命令 目录 文章目录greenplum常用命令&运维命令元数据查看所有表基本信息查看表索引信息查询表的所有列信息查看哪些表是AO表哪些是HEAP表查看AO表的分布键查看分区表信息修改表字段类型数据运维启动和停止Greenplum数据库节点情况greenplum总体运行状态查看segment节点状态查看segment节点故障等历史信息检查segment instance同步状态查看segment节点磁盘空闲情况检查standby同步状态检查数据库日志显示在系统表
greenplum如何恢复故障segment
DreamDB的专栏
04-10 3520
环境如下： more /etc/redhat-release Red Hat Enterprise Linux Server release 7.5 (Maipo) 系统安装采取最小化安装。 greenplum-db-5.16.0-rhel7-x86_64.zip more /etc/hosts 127.0.0.1 localhost localhost.localdomain loca...
第五节课 Greenplum 常见问题分析和处理.pdf
04-09
综上所述，解决Greenplum数据库问题的关键在于合理地利用日志文件和系统管理工具，通过系统化地方法识别问题所在，从而进行有效的诊断和修复。同时，需要了解和熟悉Greenplum的各项配置参数以及故障处理的最佳实践，...
分享！Greenplum常用命令整理
雪辉博客
09-12 1622
gpstate -b =》 显示简要状态 gpstate -c =》 显示主镜像映射 gpstart -d =》 指定数据目录（默认值：$MASTER_DATA_DIRECTORY） gpstate -e =》 显示具有镜像状态问题的片段 gpstate -f =》 显示备用主机详细信息 gpstate -i =》 显示GRIPLUM数据库版本 gpstate -m =》 显示镜像实例同步状态 gpstate -p =》 显示使用端口 gpstate -Q =》 快速检查主机状态 gpstate -s =.
Greenplum segment节点异常恢复
无锋剑
08-30 2588
Segment检测及故障切换机制 GP Master首先会检测Primary状态，如果Primary不可连通，那么将会检测Mirror状态，Primary/Mirror状态总共有4种： Primary活着，Mirror活着。GP Master探测Primary成功之后直接返回，进行下一个Segment检测； Primary活着，Mirror挂了。GP Master探测Primary成功之后，通...
Greenplum管理和监控工具-gpcc-web介绍
最新发布
wt334502157的博客
11-02 1657
1. **集群监控和状态**：`gpcc-web`提供了有关整个Greenplum数据库集群状态的实时信息。您可以查看主机、段、表空间等级别的性能数据、状态和报警信息。这有助于及时识别和解决性能问题。 2. **查询性能监控**：您可以监视正在运行的查询的性能，包括查询执行计划、资源消耗和查询运行时间。这有助于识别潜在的性能瓶颈和优化查询。 3. **备份和恢复管理**：`gpcc-web`允许您配置和监视数据库备份策略，并提供了还原数据库的功能。这有助于确保数据的备份和可恢复性。
评论
添加红包

请填写红包祝福语或标题

个

红包个数最小为10个

元

红包金额最低5元

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

抵扣说明：

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

余额充值