File***could only be replicated to 0 nodes instead of minReplication (=1)

最新推荐文章于 2022-10-01 14:47:09 发布
最新推荐文章于 2022-10-01 14:47:09 发布
阅读量1.1k 收藏
点赞数
分类专栏： Hadoop
1、集群部署完成之后，测试上传文件至hdfs时，报出 File /user/hdfs_test.txt._COPYING_ could only be replicated to 0 nodes instead of minReplication (=1)的异常信息。

[hadoop@abcd08 chx]$ hadoop fs -put hdfs_test.txt /user
14/11/30 21:43:05 WARN util.NativeCodeLoader: Unable to load native-hadoop library for your platform... using builtin-java classes where applicable
14/11/30 21:43:06 WARN hdfs.DFSClient: DataStreamer Exception
org.apache.hadoop.ipc.RemoteException(java.io.IOException): File /user/hdfs_test.txt._COPYING_ could only be replicated to 0 nodes instead of minReplication (=1).  There are 0 datanode(s) running and no node(s) are excluded in this operation.
        at org.apache.hadoop.hdfs.server.blockmanagement.BlockManager.chooseTarget(BlockManager.java:1331)
        at org.apache.hadoop.hdfs.server.namenode.FSNamesystem.getAdditionalBlock(FSNamesystem.java:2198)
        at org.apache.hadoop.hdfs.server.namenode.NameNodeRpcServer.addBlock(NameNodeRpcServer.java:480)
        at org.apache.hadoop.hdfs.protocolPB.ClientNamenodeProtocolServerSideTranslatorPB.addBlock(ClientNamenodeProtocolServerSideTranslatorPB.java:299)
        at org.apache.hadoop.hdfs.protocol.proto.ClientNamenodeProtocolProtos$ClientNamenodeProtocol$2.callBlockingMethod(ClientNamenodeProtocolProtos.java:44954)
        at org.apache.hadoop.ipc.ProtobufRpcEngine$Server$ProtoBufRpcInvoker.call(ProtobufRpcEngine.java:453)
        at org.apache.hadoop.ipc.RPC$Server.call(RPC.java:1002)
        at org.apache.hadoop.ipc.Server$Handler$1.run(Server.java:1701)
        at org.apache.hadoop.ipc.Server$Handler$1.run(Server.java:1697)
        at java.security.AccessController.doPrivileged(Native Method)
        at javax.security.auth.Subject.doAs(Subject.java:396)
        at org.apache.hadoop.security.UserGroupInformation.doAs(UserGroupInformation.java:1408)
        at org.apache.hadoop.ipc.Server$Handler.run(Server.java:1695)
        at org.apache.hadoop.ipc.Client.call(Client.java:1225)
        at org.apache.hadoop.ipc.ProtobufRpcEngine$Invoker.invoke(ProtobufRpcEngine.java:202)
        at com.sun.proxy.$Proxy9.addBlock(Unknown Source)
        at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
        at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
        at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
        at java.lang.reflect.Method.invoke(Method.java:597)
        at org.apache.hadoop.io.retry.RetryInvocationHandler.invokeMethod(RetryInvocationHandler.java:164)
        at org.apache.hadoop.io.retry.RetryInvocationHandler.invoke(RetryInvocationHandler.java:83)
        at com.sun.proxy.$Proxy9.addBlock(Unknown Source)
        at org.apache.hadoop.hdfs.protocolPB.ClientNamenodeProtocolTranslatorPB.addBlock(ClientNamenodeProtocolTranslatorPB.java:291)
        at org.apache.hadoop.hdfs.DFSOutputStream$DataStreamer.locateFollowingBlock(DFSOutputStream.java:1176)
        at org.apache.hadoop.hdfs.DFSOutputStream$DataStreamer.nextBlockOutputStream(DFSOutputStream.java:1029)
        at org.apache.hadoop.hdfs.DFSOutputStream$DataStreamer.run(DFSOutputStream.java:487)
put: File /user/hdfs_test.txt._COPYING_ could only be replicated to 0 nodes instead of minReplication (=1).  There are 0 datanode(s) running and no node(s) are excluded in this operation.
14/11/30 21:43:06 ERROR hdfs.DFSClient: Failed to close file /user/hdfs_test.txt._COPYING_
org.apache.hadoop.ipc.RemoteException(java.io.IOException): File /user/hdfs_test.txt._COPYING_ could only be replicated to 0 nodes instead of minReplication (=1).  There are 0 datanode(s) running and no node(s) are excluded in this operation.
        at org.apache.hadoop.hdfs.server.blockmanagement.BlockManager.chooseTarget(BlockManager.java:1331)
        at org.apache.hadoop.hdfs.server.namenode.FSNamesystem.getAdditionalBlock(FSNamesystem.java:2198)
        at org.apache.hadoop.hdfs.server.namenode.NameNodeRpcServer.addBlock(NameNodeRpcServer.java:480)
        at org.apache.hadoop.hdfs.protocolPB.ClientNamenodeProtocolServerSideTranslatorPB.addBlock(ClientNamenodeProtocolServerSideTranslatorPB.java:299)
        at org.apache.hadoop.hdfs.protocol.proto.ClientNamenodeProtocolProtos$ClientNamenodeProtocol$2.callBlockingMethod(ClientNamenodeProtocolProtos.java:44954)
        at org.apache.hadoop.ipc.ProtobufRpcEngine$Server$ProtoBufRpcInvoker.call(ProtobufRpcEngine.java:453)
        at org.apache.hadoop.ipc.RPC$Server.call(RPC.java:1002)
        at org.apache.hadoop.ipc.Server$Handler$1.run(Server.java:1701)
        at org.apache.hadoop.ipc.Server$Handler$1.run(Server.java:1697)
        at java.security.AccessController.doPrivileged(Native Method)
        at javax.security.auth.Subject.doAs(Subject.java:396)
        at org.apache.hadoop.security.UserGroupInformation.doAs(UserGroupInformation.java:1408)
        at org.apache.hadoop.ipc.Server$Handler.run(Server.java:1695)
        at org.apache.hadoop.ipc.Client.call(Client.java:1225)
        at org.apache.hadoop.ipc.ProtobufRpcEngine$Invoker.invoke(ProtobufRpcEngine.java:202)
        at com.sun.proxy.$Proxy9.addBlock(Unknown Source)
        at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
        at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
        at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
        at java.lang.reflect.Method.invoke(Method.java:597)
        at org.apache.hadoop.io.retry.RetryInvocationHandler.invokeMethod(RetryInvocationHandler.java:164)
        at org.apache.hadoop.io.retry.RetryInvocationHandler.invoke(RetryInvocationHandler.java:83)
        at com.sun.proxy.$Proxy9.addBlock(Unknown Source)
        at org.apache.hadoop.hdfs.protocolPB.ClientNamenodeProtocolTranslatorPB.addBlock(ClientNamenodeProtocolTranslatorPB.java:291)
        at org.apache.hadoop.hdfs.DFSOutputStream$DataStreamer.locateFollowingBlock(DFSOutputStream.java:1176)
        at org.apache.hadoop.hdfs.DFSOutputStream$DataStreamer.nextBlockOutputStream(DFSOutputStream.java:1029)
        at org.apache.hadoop.hdfs.DFSOutputStream$DataStreamer.run(DFSOutputStream.java:487)
[hadoop@abcd08 chx]$ 

2、执行hadoop dfsadmin -report看集群的状态
[ hadoop@abcd08 ~]$ hadoop dfsadmin -report
DEPRECATED: Use of this script to execute hdfs command is deprecated.
Instead use the hdfs command for it.

14/11/30 22:09:51 WARN util.NativeCodeLoader: Unable to load native-hadoop library for your platform... using builtin-java classes where applicable
Configured Capacity: 0 (0 B)
Present Capacity: 0 (0 B)
DFS Remaining: 0 (0 B)
DFS Used: 0 (0 B)
DFS Used%: NaN%
Under replicated blocks: 0
Blocks with corrupt replicas: 0
Missing blocks: 0

------------------------------------------------
Datanodes available: 0 (0 total, 0 dead)
[hadoop@abcd08 ~]$    
很明显，datanode异常。

3、重新执行sh start-dfs.sh（连接执行两次，都是如下信息）：
[hadoop@abcd08 sbin]$ sh start-dfs.sh 
14/11/30 23:30:24 WARN util.NativeCodeLoader: Unable to load native-hadoop library for your platform... using builtin-java classes where applicable
Starting namenodes on [abcd08]
abcd08: starting namenode, logging to /home/hadoop/cdh4/hadoop-2.0.0-cdh4.3.0/logs/hadoop-hadoop-namenode-abcd08.out
abcd05: starting datanode, logging to /home/hadoop/cdh4/hadoop/logs/hadoop-hadoop-datanode-abcd05.out
abcd06: starting datanode, logging to /home/hadoop/cdh4/hadoop/logs/hadoop-hadoop-datanode-abcd06.out
abcd02: starting datanode, logging to /home/hadoop/cdh4/hadoop/logs/hadoop-hadoop-datanode-abcd02.out
abcd01: starting datanode, logging to /home/hadoop/cdh4/hadoop/logs/hadoop-hadoop-datanode-abcd01.out
abcd07: starting datanode, logging to /home/hadoop/cdh4/hadoop/logs/hadoop-hadoop-datanode-abcd07.out
abcd04: starting datanode, logging to /home/hadoop/cdh4/hadoop/logs/hadoop-hadoop-datanode-abcd04.out
abcd03: starting datanode, logging to /home/hadoop/cdh4/hadoop/logs/hadoop-hadoop-datanode-abcd03.out
Starting secondary namenodes [abcd01]
abcd01: starting secondarynamenode, logging to /home/hadoop/cdh4/hadoop/logs/hadoop-hadoop-secondarynamenode-abcd01.out
14/11/30 23:30:41 WARN util.NativeCodeLoader: Unable to load native-hadoop library for your platform... using builtin-java classes where applicable
[hadoop@abcd08 sbin]$ 
此证明：各datanode启动之后，进程随即又退出了。


4、查看datanode上的日志文件：
[hadoop@abcd07 logs]$ pwd
/home/hadoop/cdh4/hadoop/logs
[hadoop@abcd07 logs]$ tail -50 hadoop-hadoop-datanode-abcd07.log
2014-11-30 22:51:36,896 FATAL org.apache.hadoop.hdfs.server.datanode.DataNode: Initialization failed for block pool Block pool BP-434621394-100.101.138.60-1417342220181 (storage id DS-139576203-100.101.138.59-50010-1416757117263) service to abcd08/100.101.138.60:8020
java.io.IOException: Incompatible clusterIDs in /data1/hadoop: namenode clusterID = CID-2d09836b-d546-4066-9deb-b28cc55de11a; datanode clusterID = CID-b664bda9-3f22-412f-86bd-372f98a73a52
        at org.apache.hadoop.hdfs.server.datanode.DataStorage.doTransition(DataStorage.java:391)
        at org.apache.hadoop.hdfs.server.datanode.DataStorage.recoverTransitionRead(DataStorage.java:191)
        at org.apache.hadoop.hdfs.server.datanode.DataStorage.recoverTransitionRead(DataStorage.java:219)
        at org.apache.hadoop.hdfs.server.datanode.DataNode.initStorage(DataNode.java:911)
        at org.apache.hadoop.hdfs.server.datanode.DataNode.initBlockPool(DataNode.java:882)
        at org.apache.hadoop.hdfs.server.datanode.BPOfferService.verifyAndSetNamespaceInfo(BPOfferService.java:308)
        at org.apache.hadoop.hdfs.server.datanode.BPServiceActor.connectToNNAndHandshake(BPServiceActor.java:218)
        at org.apache.hadoop.hdfs.server.datanode.BPServiceActor.run(BPServiceActor.java:660)
        at java.lang.Thread.run(Thread.java:662)
2014-11-30 22:51:36,898 WARN org.apache.hadoop.hdfs.server.datanode.DataNode: Ending block pool service for: Block pool BP-434621394-100.101.138.60-1417342220181 (storage id DS-139576203-100.101.138.59-50010-1416757117263) service to abcd08/100.101.138.60:8020
2014-11-30 22:51:36,999 INFO org.apache.hadoop.hdfs.server.datanode.DataNode: Removed Block pool BP-434621394-100.101.138.60-1417342220181 (storage id DS-139576203-100.101.138.59-50010-1416757117263)
2014-11-30 22:51:39,000 WARN org.apache.hadoop.hdfs.server.datanode.DataNode: Exiting Datanode
2014-11-30 22:51:39,002 INFO org.apache.hadoop.util.ExitUtil: Exiting with status 0
2014-11-30 22:51:39,007 INFO org.apache.hadoop.hdfs.server.datanode.DataNode: SHUTDOWN_MSG: 
/************************************************************
SHUTDOWN_MSG: Shutting down DataNode at abcd07/100.101.138.59
************************************************************/

报的是： java.io.IOException: Incompatible clusterIDs in /data1/hadoop: namenode clusterID = CID-2d09836b-d546-4066-9deb-b28cc55de11a; datanode clusterID = CID-b664bda9-3f22-412f-86bd-372f98a73a52。


5、查看各节点的 hdfs-site.xml配置文件，找到所配置的 namenode 和 datanode 的位置，如下：
[hadoop@abcd07 hadoop]$ more hdfs-site.xml 
<!-- Put site-specific property overrides in this file. -->
<configuration>
        <property>
                <name>dfs.replication</name>
                <value>3</value>
        </property>
        <property>
                <name>dfs.namenode.name.dir</name>
                <value>/home/hadoop/cdh4/hadoop/dfs/name</value>
        </property>
        <property>
                <name>dfs.datanode.data.dir</name>
                <value>/data1/hadoop</value>
        </property>
        <property>
                <name>dfs.namenode.secondary.http-address</name>
                <value>abcd01:50090</value>
                <description></description>
        </property>
        <property>
                <name>dfs.webhdfs.enabled</name>
                <value>true</value>
        </property>
</configuration>
[hadoop@abcd07 hadoop]$

在各datanode上打开 namenode 和 datanode 的位置（上面红色标注目录），并与namenode上的/home/hadoop/cdh4/hadoop/dfs/name/current目录下VERSION进行比较，发现它们clusterID确实是不一样。


如下：

namenode上：
[hadoop@abcd08 current]$ more VERSION 
#Sun Nov 30 18:10:20 CST 2014
namespaceID=1651811630
clusterID= CID-2d09836b-d546-4066-9deb-b28cc55de11a
cTime=0
storageType=NAME_NODE
blockpoolID=BP-434621394-100.101.138.60-1417342220181
layoutVersion=-40
[hadoop@abcd08 current]$

datanode上：
[hadoop@abcd07 current]$ more VERSION 
#Mon Nov 24 00:31:56 CST 2014
namespaceID=1422355035
clusterID=CID-597dcc33-c77e-4d18-a8b9-6e940b63d3e6
cTime=0
storageType=NAME_NODE
blockpoolID=BP-178246317-100.101.138.60-1416760316740
layoutVersion=-40
[hadoop@abcd07 current]$  

clusterID不一样的原因：在第一次格式化dfs后，启动并使用了hadoop，后来又重新执行了格式化命令（hdfs namenode -format)，这时namenode的clusterID会重新生成，而datanode的clusterID 保持不变。


6、修改各datanode上的namenode上的 namenode位置下的current目录下的VERSION文件，将clusterID修改为与 namenode上的clusterID一致，问题解决。

南木流沙
关注
  • 0
    点赞
  • 踩
  • 0
    收藏
    觉得还不错? 一键收藏
  • 0
    评论
专栏目录
A comprehensive study of Convergent and Commutative Replicated Data Types-计算机科学
04-22
appor t de r ech er ch eIS SN 0249 -639 9IS RN INR IA/R R-- 7506 --F R+ EN GThème COMINSTITUT NATIONAL DE RECHERCHE EN INFORMATIQUE ET EN AUTOMATIQUEA comprehensive study of Convergent and Commutative Replicated Data TypesMarc Shapiro, INRIA & LIP6, Paris, France Nuno Pregui&ccedil;a, CITI, Universidade Nova de Lisboa, PortugalCarlos Baquero, Universidade do Minho, PortugalMarek Zawirski, INRIA & UPMC, Paris, FranceN° 7506Janvier 2011in ria-0 0555 588, ver sion 1- 13J an2 011http://hal.inria.fr
上传文件到HDFS报错：There are 0 datanode(s) running and 0 node(s) are excluded in this operation.
Cosmic Lover
04-05 2716
上传文件到HDFS的时候报错 _COPYING_ could only be written to 0 of the 1 minReplication nodes. There are 0 datanode(s) running and 0 node(s) are excluded in this operation. 解决 原因似乎是因为datanode没有启动，查了解决方法，最终stakeo...
Hadoop上传文件报错could only be written to 0 of the 1 minReplication nodes.
子非鱼的博客
09-28 8025
这个问题一般是由于使用hadoop namenode -format 格式化多次，导致spaceID不一致造成的，解决方法如下： 1、 停止集群所有的服务。指令为：stop-all.sh 2、删除hdfs中配置的data目录下的所有文件（级core-site.xml中配置的hadoop.tmp.dir）。指令为：rm -rf /home/navy/tmp/* 3、重新格式化namenode。指令...
遇到的hadoop/spark报错问题汇总
主公在此的博客
10-23 373
1.hdfs dfs -put XXX XXX时报：org.apache.hadoop.ipc.RemoteException(java.io.IOException): File /test/a.txt._COPYING_ could only be replicated to 0 nodes instead of minReplication (=1). There are 0 datanod
put: File /input._COPYING_ could only be replicated to 0 nodes instead of minReplication (=1). Ther
m0_54861980的博客
04-29 4379
Hadoop上传文件报错： operation.java.net.NoRouteToHostException: 没有到主机的路由 报错：put: File /input.COPYING could only be replicated to 0 nodes instead of minReplication (=1). There are 2 datanode(s) running and 2 node(s) are excluded in this 问题截图： 解决方法： 1.没有主机路由问题大多是
解决File ~ could only be written to 0 of the 1 minReplication nodes.
xiaoyao_zhy的博客
10-01 6685
NameNode节点存放的是文件目录，也就是文件夹、文件名称，本地可以通过公网访问 NameNode，所以可以进行文件夹的创建，当上传文件需要写入数据到DataNode时，NameNode 和DataNode 是通过局域网进行通信，NameNode返回地址为 DataNode 的私有 IP，本地无法访问。这里也可以看出大哥也使用的是服务器‘，根据上述理解我们知道因为我们使用的服务器，官方给我们提供的是可以访问的公网，但是内部名称节点和数据节点的通信是通过私网，也就是相当于；在你的服务器上，输入以下指令。
记录处理hdfs put失败的过程
qq_39276701的博客
06-22 959
在搭建好hadoop集群后，在本地执行hdfs dfs -put 命令报错 File /test01/1.txt._COPYING_ could only be written to 0 of the 1 minReplication nodes. There are 0 datanode(s) running and 0 node(s) are excluded in this operation. 后来查看了一下本地的进程 发现主节点没有启动datanode导致失败 去hadoop软件下面修改了.
copyFromLocal: File /test/file/test.txt._COPYING_ could only be replicated to 0 nodes instead of min...
weixin_34195364的博客
06-08 823
copyFromLocal: File /test/file/test.txt._COPYING_ could only be replicated to 0 nodes instead of minReplication (=1). There are 2 datanode(s) running and 2 node(s) are excluded in this operation. 关闭...
hadoop put上传文件报错
liuweidong1的博客
11-13 1775
最近准备学习下大数据相关的知识,先从hadoop学习开始,在hadoop集群环境搭建后测试上传文件一直报错, 防火墙全部关闭了,配置也没问题,格式化也没问题,查找了半天资料才发现问题,以此记录 报错:put: File /README.txt._COPYING_ could only be written to 0 of the 1 minReplication nodes. There are 0 datanode(s) running and 0 node(s) are excluded in th
Hadoop文件复制到分布式文件系统报错：.xml.COPYING_ could only be written to 0 of the 1 minReplication nodes.
xiaobai_i_xuexi的博客
10-08 872
错误截图： 这是当时老师给的DataNode没法启动的解决办法 但是我部署的时候 jps是有datanode的 如下： 但是等我复制失败的时候，再jps就没有了 “jps查看进程时发现namenode节点时有时无，于是多次格式化namenode，然后上传文件就开始报错。细心的话可以发现再次格式化过程中会有确认消息。大佬说是这个问题一般是由于使用hadoop namenode -format 格式化多次，导致spaceID不一致造成的。”（摘自：https://blog.csdn.net/qq_43148
异常处理 could only be replicated to 0 nodes, instead of 1
04-17
NULL 博文链接：https://xq0804200134.iteye.com/blog/1814655
DB - Paxos Replicated State Machines as the Basis of a High
07-10
DB - Paxos Replicated State Machines as the Basis of a High-Performance.pdf Conventional wisdom holds that Paxos is too expensive to use for high-volume, high-throughput, data-intensive applications....
Problem solving ability of disadvantaged elementary school children under four testing formats: A replicated experiment
06-29
Problem solving ability of disadvantaged elementary school children under four testing formats: A replicated experiment PROBLEM SOLVING ABILITY OF DISADVANTAGED ELERIENTARY SCHOOL CHILDREN UNDER ...
Replicated-Softmax-Model:在论文“ Replicated softmax”中重复实验
05-18
复制的Softmax模型 在论文“复制的softmax：无向主题模型”中重复实验。 Preprocess.py：在此库中，您可以读取文件并删除停用词，标点符号和... （1）比较LDA和RSM的困惑（2）比较LDA，RSM和TF-IDF的精度和召回率。
后端开发是一个涉及广泛技术和工具的领域.docx
04-30
后端开发是一个涉及广泛技术和工具的领域，这些资源对于构建健壮、可扩展和高效的Web应用程序至关重要。以下是对后端开发资源的简要介绍： 首先，掌握一门或多门编程语言是后端开发的基础。Java、Python和Node.js是其中最受欢迎的几种。Java以其跨平台性和丰富的库而著名，Python则因其简洁的语法和广泛的应用领域而备受欢迎。Node.js则通过其基于JavaScript的单线程异步I/O模型，为Web开发提供了高性能的解决方案。 其次，数据库技术是后端开发中不可或缺的一部分。关系型数据库（如MySQL、PostgreSQL）和非关系型数据库（如MongoDB、Redis）各有其特点和应用场景。关系型数据库适合存储结构化数据，而非关系型数据库则更适合处理大量非结构化数据。 此外，Web开发框架也是后端开发的重要资源。例如，Express是一个基于Node.js的Web应用开发框架，它提供了丰富的API和中间件支持，使得开发人员能够快速地构建Web应用程序。Django则是一个用Python编写的Web应用框架，它采用了MVC的软件设计模式，使得代码结构更加清晰和易于维护。
华为数字化转型实践28个精华问答glkm.pptx
04-30
华为数字化转型实践28个精华问答glkm.pptx
新员工入职培训全流程资料包gl.zip
04-30
新员工入职培训全流程资料包（100+个文件） 1入职流程指引 万科新职员入职通知书 万科新职员入职引导手册 新进员工跟进管理表 新员工入职报到工作单(文职) 新员工入职报到流程 新员工入职流程表 新员工入职手续办理流程(工厂 新员工入职手续清单 新员工入职须知 新员工入职训流程 新员工入职引导表(导师用) 2 入职工具表格 3 培训方案计划 4培训管理流程 5培训教材课件 6 培训效果检测 7 员工管理制度 8 劳动合同协议 9 新员工培训PPT模板(28套)
三菱PLC通讯程序实例
04-30
FX5U PLC作为主、从站的通讯方式程序实例，以及包含详细说明文件...
技术需求报告-集行波测距与故障录波功能于一体的电网综合故障分析系统.docx
最新发布
04-30
技术需求报告-集行波测距与故障录波功能于一体的电网综合故障分析系统.docx
hadoop异常“could only be replicated to 0 nodes, instead of 1” 解决
05-25
这个异常通常表示 Hadoop 集群中的某个数据块无法成功复制到足够数量的节点上。这可能是由于节点故障、网络...希望这些解决方案能帮助您解决 Hadoop 异常“could only be replicated to 0 nodes, instead of 1”问题。

“相关推荐”对你有帮助么？

  • 非常没帮助
  • 没帮助
  • 一般
  • 有帮助
  • 非常有帮助
提交
评论
添加红包

请填写红包祝福语或标题

个

红包个数最小为10个

元

红包金额最低5元

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

抵扣说明：

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

余额充值