启动 kafka

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

使用 config/sever.properties 验证kafka 执行是否成功

# see kafka.server.KafkaConfig for additional details and defaults

############################# Server Basics #############################

# The id of the broker. This must be set to a unique integer for each broker.
# 表示 broker 编号， 如果集群有多个 broker， 则每个 broker 编号需要设置的不同
broker.id=0

############################# Socket Server Settings #############################

# The address the socket server listens on. It will get the value returned from 
# java.net.InetAddress.getCanonicalHostName() if not configured.
#   FORMAT:
#     listeners = listener_name://host_name:port
#   EXAMPLE:
#     listeners = PLAINTEXT://your.host.name:9092
# 对外提供的服务入口地址
# 配置相应的ip地址
listeners=PLAINTEXT://192.168.131.130:9092

# Hostname and port the broker will advertise to producers and consumers. If not set, 
# it uses the value for "listeners" if configured.  Otherwise, it will use the value
# returned from java.net.InetAddress.getCanonicalHostName().
#advertised.listeners=PLAINTEXT://your.host.name:9092

# Maps listener names to security protocols, the default is for them to be the same. See the config documentation for more details
#listener.security.protocol.map=PLAINTEXT:PLAINTEXT,SSL:SSL,SASL_PLAINTEXT:SASL_PLAINTEXT,SASL_SSL:SASL_SSL

# The number of threads that the server uses for receiving requests from the network and sending responses to the network
num.network.threads=3

# The number of threads that the server uses for processing requests, which may include disk I/O
num.io.threads=8

# The send buffer (SO_SNDBUF) used by the socket server
socket.send.buffer.bytes=102400

# The receive buffer (SO_RCVBUF) used by the socket server
socket.receive.buffer.bytes=102400

# The maximum size of a request that the socket server will accept (protection against OOM)
socket.request.max.bytes=104857600


############################# Log Basics #############################

# A comma separated list of directories under which to store log files
# 设置存放消息日志文件的地址
log.dirs=/opt/kafka/kafka_2.12-2.2.1/logs

# The default number of log partitions per topic. More partitions allow greater
# parallelism for consumption, but this will also result in more files across
# the brokers.
num.partitions=1

# The number of threads per data directory to be used for log recovery at startup and flushing at shutdown.
# This value is recommended to be increased for installations with data dirs located in RAID array.
num.recovery.threads.per.data.dir=1

############################# Internal Topic Settings  #############################
# The replication factor for the group metadata internal topics "__consumer_offsets" and "__transaction_state"
# For anything other than development testing, a value greater than 1 is recommended for to ensure availability such as 3.
offsets.topic.replication.factor=1
transaction.state.log.replication.factor=1
transaction.state.log.min.isr=1

############################# Log Flush Policy #############################

# Messages are immediately written to the filesystem but by default we only fsync() to sync
# the OS cache lazily. The following configurations control the flush of data to disk.
# There are a few important trade-offs here:
#    1. Durability: Unflushed data may be lost if you are not using replication.
#    2. Latency: Very large flush intervals may lead to latency spikes when the flush does occur as there will be a lot of data to flush.
#    3. Throughput: The flush is generally the most expensive operation, and a small flush interval may lead to excessive seeks.
# The settings below allow one to configure the flush policy to flush data after a period of time or
# every N messages (or both). This can be done globally and overridden on a per-topic basis.

# The number of messages to accept before forcing a flush of data to disk
#log.flush.interval.messages=10000

# The maximum amount of time a message can sit in a log before we force a flush
#log.flush.interval.ms=1000

############################# Log Retention Policy #############################

# The following configurations control the disposal of log segments. The policy can
# be set to delete segments after a period of time, or after a given size has accumulated.
# A segment will be deleted whenever *either* of these criteria are met. Deletion always happens
# from the end of the log.

# The minimum age of a log file to be eligible for deletion due to age
log.retention.hours=168

# A size-based retention policy for logs. Segments are pruned from the log unless the remaining
# segments drop below log.retention.bytes. Functions independently of log.retention.hours.
#log.retention.bytes=1073741824

# The maximum size of a log segment file. When this size is reached a new log segment will be created.
log.segment.bytes=1073741824

# The interval at which log segments are checked to see if they can be deleted according
# to the retention policies
log.retention.check.interval.ms=300000

############################# Zookeeper #############################

# Zookeeper connection string (see zookeeper docs for details).
# This is a comma separated host:port pairs, each corresponding to a zk
# server. e.g. "127.0.0.1:3000,127.0.0.1:3001,127.0.0.1:3002".
# You can also append an optional chroot string to the urls to specify the
# root directory for all kafka znodes.
# kafka 所需 zookeeper集群地址，教学中zookeeper和kafka都安装本机
zookeeper.connect=localhost:2181

# Timeout in ms for connecting to zookeeper
zookeeper.connection.timeout.ms=6000


############################# Group Coordinator Settings #############################

# The following configuration specifies the time, in milliseconds, that the GroupCoordinator will delay the initial consumer rebalance.
# The rebalance will be further delayed by the value of group.initial.rebalance.delay.ms as new members join the group, up to a maximum of max.poll.interval.ms.
# The default value for this is 3 seconds.
# We override this to 0 here as it makes for a better out-of-the-box experience for development and testing.
# However, in production environments the default value of 3 seconds is more suitable as this will help to avoid unnecessary, and potentially expensive, rebalances during application startup.
group.initial.rebalance.delay.ms=0
# 启动kafka脚本
[root@localhost kafka_2.12-2.2.1]# bin/kafka-server-start.sh config/server.properties

另外启动一个shell窗口：

[root@localhost opt]# ps -ef|grep kafka  // 所用shell命令校验是否成功
root      22467  22093  4 05:38 pts/1    00:00:06 /usr/local/java/jdk1.8.0_221/bin/java -Xmx1G -Xms1G -server -XX:+UseG1GC -XX:MaxGCPauseMillis=20 -XX:InitiatingHeapOccupancyPercent=35 -XX:+ExplicitGCInvokesConcurrent -Djava.awt.headless=true -Xloggc:/opt/kafka/kafka_2.12-2.2.1/bin/../logs/kafkaServer-gc.log -verbose:gc -XX:+PrintGCDetails -XX:+PrintGCDateStamps -XX:+PrintGCTimeStamps -XX:+UseGCLogFileRotation -XX:NumberOfGCLogFiles=10 -XX:GCLogFileSize=100M -Dcom.sun.management.jmxremote -Dcom.sun.management.jmxremote.authenticate=false -Dcom.sun.management.jmxremote.ssl=false -Dkafka.logs.dir=/opt/kafka/kafka_2.12-2.2.1/bin/../logs -Dlog4j.configuration=file:bin/../config/log4j.properties -cp /usr/local/java/jdk1.8.0_221/jre/lib/ext:/usr/local/java/jdk1.8.0_221/lib/tools.jar:/opt/kafka/kafka_2.12-2.2.1/bin/../libs/activation-1.1.1.jar:/opt/kafka/kafka_2.12-2.2.1/bin/../libs/aopalliance-repackaged-2.5.0-b42.jar:/opt/kafka/kafka_2.12-2.2.1/bin/../libs/argparse4j-0.7.0.jar:/opt/kafka/kafka_2.12-2.2.1/bin/../libs/audience-annotations-0.5.0.jar:/opt/kafka/kafka_2.12-2.2.1/bin/../libs/commons-lang3-3.8.1.jar:/opt/kafka/kafka_2.12-2.2.1/bin/../libs/connect-api-2.2.1.jar:/opt/kafka/kafka_2.12-2.2.1/bin/../libs/connect-basic-auth-extension-2.2.1.jar:/opt/kafka/kafka_2.12-2.2.1/bin/../libs/connect-file-2.2.1.jar:/opt/kafka/kafka_2.12-2.2.1/bin/../libs/connect-json-2.2.1.jar:/opt/kafka/kafka_2.12-2.2.1/bin/../libs/connect-runtime-2.2.1.jar:/opt/kafka/kafka_2.12-2.2.1/bin/../libs/connect-transforms-2.2.1.jar:/opt/kafka/kafka_2.12-2.2.1/bin/../libs/guava-20.0.jar:/opt/kafka/kafka_2.12-2.2.1/bin/../libs/hk2-api-2.5.0-b42.jar:/opt/kafka/kafka_2.12-2.2.1/bin/../libs/hk2-locator-2.5.0-b42.jar:/opt/kafka/kafka_2.12-2.2.1/bin/../libs/hk2-utils-2.5.0-b42.jar:/opt/kafka/kafka_2.12-2.2.1/bin/../libs/jackson-annotations-2.9.8.jar:/opt/kafka/kafka_2.12-2.2.1/bin/../libs/jackson-core-2.9.8.jar:/opt/kafka/kafka_2.12-2.2.1/bin/../libs/jackson-databind-2.9.8.jar:/opt/kafka/kafka_2.12-2.2.1/bin/../libs/jackson-datatype-jdk8-2.9.8.jar:/opt/kafka/kafka_2.12-2.2.1/bin/../libs/jackson-jaxrs-base-2.9.8.jar:/opt/kafka/kafka_2.12-2.2.1/bin/../libs/jackson-jaxrs-json-provider-2.9.8.jar:/opt/kafka/kafka_2.12-2.2.1/bin/../libs/jackson-module-jaxb-annotations-2.9.8.jar:/opt/kafka/kafka_2.12-2.2.1/bin/../libs/javassist-3.22.0-CR2.jar:/opt/kafka/kafka_2.12-2.2.1/bin/../libs/javax.annotation-api-1.2.jar:/opt/kafka/kafka_2.12-2.2.1/bin/../libs/javax.inject-1.jar:/opt/kafka/kafka_2.12-2.2.1/bin/../libs/javax.inject-2.5.0-b42.jar:/opt/kafka/kafka_2.12-2.2.1/bin/../libs/javax.servlet-api-3.1.0.jar:/opt/kafka/kafka_2.12-2.2.1/bin/../libs/javax.ws.rs-api-2.1.1.jar:/opt/kafka/kafka_2.12-2.2.1/bin/../libs/javax.ws.rs-api-2.1.jar:/opt/kafka/kafka_2.12-2.2.1/bin/../libs/jaxb-api-2.3.0.jar:/opt/kafka/kafka_2.12-2.2.1/bin/../libs/jersey-client-2.27.jar:/opt/kafka/kafka_2.12-2.2.1/bin/../libs/jersey-common-2.27.jar:/opt/kafka/kafka_2.12-2.2.1/bin/../libs/jersey-container-servlet-2.27.jar:/opt/kafka/kafka_2.12-2.2.1/bin/../libs/jersey-container-servlet-core-2.27.jar:/opt/kafka/kafka_2.12-2.2.1/bin/../libs/jersey-hk2-2.27.jar:/optkafka/kafka_2.12-2.2.1/bin/../libs/jersey-media-jaxb-2.27.jar:/opt/kafka/kafka_2.12-2.2.1/bin/../libs/jersey-server-2.27.jar:/opt/kafka/kafka_2.12-2.2.1/bin/../libs/jetty-client-9.4.14.v20181114.jar:/opt/kafka/kafka_2.12-2.2.1/bin/../libs/jetty-continuation-9.4.14.v20181114.jar:/opt/kafka/kafka_2.12-2.2.1/bin/../libs/jetty-http-9.4.14.v20181114.jar:/opt/kafka/kafka_2.12-2.2.1/bin/../libs/jetty-io-9.4.14.v20181114.jar:/opt/kafka/kafka_2.12-2.2.1/bin/../libs/jetty-security-9.4.14.v20181114.jar:/opt/kafka/kafka_2.12-2.2.1/bin/../libs/jetty-server-9.4.14.v20181114.jar:/opt/kafka/kafka_2.12-2.2.1/bin/../libs/jetty-servlet-9.4.14.v20181114.jar:/opt/kafka/kafka_2.12-2.2.1/bin/../libs/jetty-servlets-9.4.14.v20181114.jar:/opt/kafka/kafka_2.12-2.2.1/bin/../libs/jetty-util-9.4.14.v20181114.jar:/opt/kafka/kafka_2.12-2.2.1/bin/../libs/jopt-simple-5.0.4.jar:/opt/kafka/kafka_2.12-2.2.1/bin/../libs/kafka_2.12-2.2.1.jar:/opt/kafka/kafka_2.12-2.2.1/bin/../libs/kafka_2.12-2.2.1-sources.jar:/opt/kafka/kafka_2.12-2.2.1/bin/../libs/kafka-clients-2.2.1.jar:/opt/kafka/kafka_2.12-2.2.1/bin/../libs/kafka-log4j-appender-2.2.1.jar:/opt/kafka/kafka_2.12-2.2.1/bin/../libs/kafka-streams-2.2.1.jar:/opt/kafka/kafka_2.12-2.2.1/bin/../libs/kafka-streams-examples-2.2.1.jar:/opt/kafka/kafka_2.12-2.2.1/bin/../libs/kafka-streams-scala_2.12-2.2.1.jar:/opt/kafka/kafka_2.12-2.2.1/bin/../libs/kafka-streams-test-utils-2.2.1.jar:/opt/kafka/kafka_2.12-2.2.1/bin/../libs/kafka-tools-2.2.1.jar:/opt/kafka/kafka_2.12-2.2.1/bin/../libs/log4j-1.2.17.jar:/opt/kafka/kafka_2.12-2.2.1/bin/../libs/lz4-java-1.5.0.jar:/opt/kafka/kafka_2.12-2.2.1/bin/../libs/maven-artifact-3.6.0.jar:/opt/kafka/kafka_2.12-2.2.1/bin/../libs/metrics-core-2.2.0.jar:/opt/kafka/kafka_2.12-2.2.1/bin/../libs/osgi-resource-locator-1.0.1.jar:/opt/kafka/kafka_2.12-2.2.1/bin/../libs/plexus-utils-3.1.0.jar:/opt/kafka/kafka_2.12-2.2.1/bin/../libs/reflections-0.9.11.jar:/opt/kafka/kafk_2.12-2.2.1/bin/../libs/rocksdbjni-5.15.10.jar:/opt/kafka/kafka_2.12-2.2.1/bin/../libs/scala-library-2.12.8.jar:/opt/kafka/kafka_2.12-2.2.1/bin/../libs/scala-logging_2.12-3.9.0.jar:/opt/kafka/kafka_2.12-2.2.1/bin/../libs/scala-reflect-2.12.8.jar:/opt/kafka/kafka_2.12-2.2.1/bin/../libs/slf4j-api-1.7.25.jar:/opt/kafka/kafka_2.12-2.2.1/bin/../libs/slf4j-log4j12-1.7.25.jar:/opt/kafka/kafka_2.12-2.2.1/bin/../libs/snappy-java-1.1.7.2.jar:/opt/kafka/kafka_2.12-2.2.1/bin/../libs/validation-api-1.1.0.Final.jar:/opt/kafka/kafka_2.12-2.2.1/bin/../libs/zkclient-0.11.jar:/opt/kafka/kafka_2.12-2.2.1/bin/../libs/zookeeper-3.4.13.jar:/opt/kafka/kafka_2.12-2.2.1/bin/../libs/zstd-jni-1.3.8-1.jar kafka.Kafka config/server.properties
root      23149  22825  0 05:40 pts/2    00:00:00 grep --color=auto kafka
[root@localhost opt]# jps -l
22467 kafka.Kafka    // kafka线程
23203 sun.tools.jps.Jps
12551 org.apache.zookeeper.server.quorum.QuorumPeerMain   // zookeeper线程
[root@localhost opt]#
铁树哥写Java
关注
专栏目录
如何在生产环境中以非 Root 用户启动 Kafka
weixin_44976692的博客
05-29 2万+
在生产环境中以非 root 用户启动 Kafka 是一个最佳实践，能够有效提高系统安全性。创建并配置 Kafka 用户。设置目录权限确保 Kafka 用户可以访问必要的文件和目录。修改 systemd 服务文件，使 Kafka 服务以 Kafka 用户启动。启动和验证 Kafka 服务，确保配置正确。通过这些操作，可以保证 Kafka 服务以更安全的方式运行。这种方式不仅能提高安全性，还能避免使用 root 用户带来的潜在风险。
查询Kafka生产者是否连接到Kafka服务
热门推荐
weixin_44976692的博客
06-22 5万+
java领域优质创作者🌐。
kafka支持外网访问
weixin_41077841的博客
12-10 1475
listeners 修改为0.0.0.0 监控所有网卡，advertised.listeners 设置为外网ip,具体如下。advertised.listeners=PLAINTEXT://外网映射ip:9092。2.这个时候需要修改kafka的config中的server.properties中的。1.kafka正常部署之后如果不修改，外网是无法访问的，具体如下（这里是单节点）3.修改之后既可以正常登录。
kafka
qq_45064745的博客
01-11 175
kafka kafka的三作用是 解耦,异步和并行 集群里面 有多个节点 broker 一个节点有多个主题 topic 一个主题有多个分区 Topic 消息更具topic进行归类 topic 消息根据topic进行归类 producer 发送消息者 ,生产者topic 消息根据topic进行归类 topic消息根据topic进行归类 producer 发送消息者,生产者 consumer:消息...
怎样查看kafka写数据送到topic是否成功
qq_33192454的博客
09-15 1578
属性来控制确认级别。当设置为 1 或 all 时，生产者会等待主题的 leader 和副本确认消息的写入，从而确保消息被成功写入到 Kafka。如果写入失败，生产者将会重试发送消息，直到达到确认级别。请注意，Kafka 是一种分布式消息系统，消息的写入和确认可能涉及多个节点和异步操作。：创建一个 Kafka 消费者，订阅您要监控的主题，然后检查消费者是否能够消费到已经写入的消息。您可以查看 Kafka 服务器的日志，以检查消息是否已经被写入主题。您可以通过检查这个对象是否成功完成来确认消息是否被成功写入。
kafka命令行producer写数据失败，报错 Error when sending message to topic xxx with key:null
isowang的博客
07-13 1709
报错信息 Error when sending message to topic xxx with key:null 环境 服务器端 server.properties listeners=PLAINTEXT://kafka1:9092 客户端 /etc/hosts中无对应的主机 解决办法 在客户端的/etc/hosts中增加对应的主机映射
Flink Sink Kafka 和 Flink 端到端一致性建议
qq_39521139的博客
09-17 125
通俗的理解是指在一个分布式流处理系统中，从数据源（source）到数据结果（sink），整个处理过程能够保证数据的完整性和准确性，即使在面对各种故障（如节点宕机等）的情况下也是如此。以上就是今天说的 Flink Sink Kafka 和 Flink 端到端一致性的一些平时容易被忽略的点，希望对大家可以有帮助，有不同意见的，欢迎大家加我微信，大家一起讨论。当我们使用 Flink Sink Kafka 的时候，如果没有指定进入 Kafka 的 key 的话，你觉得数据会根据什么样的策略选择分区呢？
sh代码-Shell 脚本方式启动Kafka服务
07-16
本主题聚焦于如何使用Shell脚本来启动Kafka服务，一个广泛应用于大数据处理和实时消息传递的开源系统。首先，我们需要理解Shell脚本的基本语法，然后深入探讨Kafka的启动流程。 ### Shell脚本基础 Shell脚本是Linux...
MacOS 使用docker安装和启动Kafka
qq_33363472的博客
10-13 417
一、安装镜像 由于kafka依赖于zookeeper，需要先安装zookeeper的容器 1、搜索zookeeper和kafka的镜像 docker search zookeeper docker search kafka 2、找到后安装zookeeper和kafka的镜像 docker pull wurstmeister/zookeeper docker pull wurstmeister/kafka 二、启动kafka 1、启动zookeeper dock.
Kafka生产者同步和异步的JavaAPI代码演示
zxr0130的博客
10-08 1182
导入Maven的pom依赖 <dependencies> <dependency> <groupId>org.apache.kafka</groupId> <artifactId>kafka-clients</artifactId> <version>1.0.0</version> </dependen
kafka使用到的所有jar包
03-12
此文件包含了所有kafka用到的jar包。！！！！！！！！！！！！！！！！！！！！！！！！！！！！！
Kafka日志清除
sun_hong_likeIT的博客
05-05 657
(25条消息) Kafka日志清除策略_鸭梨山大哎的博客-CSDN博客_kafka 日志删除策略 # The minimum age of a log file to be eligible for deletion due to age log.retention.minutes=10 log.cleaner.enable=true # deleted文件默认保留5秒 log.cleaner.delete.retention.ms=5000 # 清理线程会每隔5s清理一次 log.cleane.
kafka 日志滚动配置
冻梨不是梨的博客
12-07 1258
kafka 定时删除数据 kafka 删除数据其实删除其日志，kafka 的数据其实是kafka 的message 固化到硬盘形成的，她允许配置成一定的策略来删除数据，。 数据删除的方式：首先进入kafka的安装目录，找到其中的config文件夹，然后进入，在里面找到server.properties 文件， 编辑该文件 vi server.properties 操作如下： cd /us...
Kafka_2.11版本的配置文件详细参数示例
love6a6的博客
12-22 814
路径：/opt/kafka/config/log4j.properties。路径：/opt/kafka/config/java.env。
高并发高可用复杂系统中的缓存架构(十九) kafka在此项目中的应用
liuerchong的博客
07-18 461
多级缓存的架构主要用来解决的问题是：时效高低数据的维度存储 时效性不高的数据，比如一些商品的基本信息，如果发生了变更，假设在 5 分钟之后再更新到页面中， 供用户观察到，也是 ok 的，那么我们采取的是异步更新缓存的策略 时效性要求很高的数据，如库存，采取的是数据库 + 缓存双写的技术方案，也解决了双写的一致性的问题 上面这两条可能直接看觉得好像差不多的，这里忽略了一个解释，对于页面来说，需要静态的生成页面， 这个过程可能稍微耗时一些，而对于双写来说则快太多了，它不负责页面渲染等工作，只需要把缓存数据
kafka 问题处理 及参数说明
精准搬砖
03-28 812
比如在ISR（In-Sync-Replicas）副本数等于3的情况下，消息发送到Leader A之后会更新LEO的值，Follower B和Follower C也会实时拉取Leader A中的消息来更新自己，HW就表示A、B、C三者同时达到的日志位移，也就是A、B、C三者中LEO最小的那个值。但是这里有一个问题，万一Partition Leader刚刚接收到消息，Follower还没来得及同步过去，结果Leader所在的broker宕机了，此时也会导致这条消息丢失，因为人家客户端已经认为发送成功了。
kafka安装整理，附带常用命令
lhmqy的博客
08-18 130
// 配置环境变量 export KAFKA_HOME=/opt/kafka export PATH=$PATH:$KAFKA_HOME/bin // 启动Kafka 普通启动和后台启动 kafka-server-start.sh ./config/server.properties kafka-server-start.sh -daemon ./config/server.properties // 创建topic kafka-topics.sh --create --zookeeper 192.16
Kafka之——Kafka配置文件server.properties（三个版本）
冰河的专栏
01-29 1万+
转载请注明出处：http://blog.csdn.net/l1028386804/article/details/79194929 前言 其实每个版本都有些许改动，只不过改动大小而已，但是网上的教程都真的太老了，其实更新一下也费不了多少时间  0.9.0 # Licensed to the Apache Software Foundation (ASF) under one or mo
Kafka之server.properties配置文件详解
夏天小厨的博客
11-29 9583
我们在搭建kafka集群时，根据业务目标不一样，对配置文件的修改补充也会有一些不同。在查看kafka的config目录之后，发现里面有很多的配置文件，但正在需要修改的有1、producer.properties:生产端的配置文件；2、consumer.properties:消费端的配置文件；3、server.properties:服务端的配置文件。其中最为重要的应该属于服务端的配置文件。这里，小厨...
Linux启动kafka命令
最新发布
09-25
然后启动Kafka服务器本身。 1. 启动ZooKeeper： 如果你已经安装了Zookeeper，可以在终端输入以下命令（假设ZooKeeper安装目录在 `/opt/zookeeper`）： ``` cd /opt/zookeeper ./bin/zkServer.sh start ``` 2....
评论
添加红包

请填写红包祝福语或标题

个

红包个数最小为10个

元

红包金额最低5元

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

抵扣说明：

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

余额充值