New Contributor
Posts: 1
Registered: ‎05-15-2017

Restarting hdfs service on Data nodes

[ Edited ]

We have a 12 node cluster. It has been running fine for a while. Recently we are getting the following error while running an MR job.


org.apache.hadoop.ipc.RemoteException( File /user/cdh_velo/.staging/job_201508271043_255093/job.splitmetainfo could only be replicated to 0 nodes instead of minReplication (=1).  There are 12 datanode(s) running and no node(s) are excluded in this operation.
	at org.apache.hadoop.hdfs.server.blockmanagement.BlockManager.chooseTarget4NewBlock(
	at org.apache.hadoop.hdfs.server.namenode.FSNamesystem.getAdditionalBlock(
	at org.apache.hadoop.hdfs.server.namenode.NameNodeRpcServer.addBlock(
	at org.apache.hadoop.hdfs.server.namenode.AuthorizationProviderProxyClientProtocol.addBlock(
	at org.apache.hadoop.hdfs.protocolPB.ClientNamenodeProtocolServerSideTranslatorPB.addBlock(
	at org.apache.hadoop.hdfs.protocol.proto.ClientNamenodeProtocolProtos$ClientNamenodeProtocol$2.callBlockingMethod(
	at org.apache.hadoop.ipc.ProtobufRpcEngine$Server$
	at org.apache.hadoop.ipc.RPC$
	at org.apache.hadoop.ipc.Server$Handler$
	at org.apache.hadoop.ipc.Server$Handler$
	at Method)
	at org.apache.hadoop.ipc.Server$

	at org.apache.hadoop.ipc.ProtobufRpcEngine$Invoker.invoke(
	at com.sun.proxy.$Proxy20.addBlock(Unknown Source)
	at org.apache.hadoop.hdfs.protocolPB.ClientNamenodeProtocolTranslatorPB.addBlock(
	at sun.reflect.GeneratedMethodAccessor14.invoke(Unknown Source)
	at sun.reflect.DelegatingMethodAccessorImpl.invoke(
	at java.lang.reflect.Method.invoke(
	at com.sun.proxy.$Proxy21.addBlock(Unknown Source)
	at org.apache.hadoop.hdfs.DFSOutputStream$DataStreamer.locateFollowingBlock(
	at org.apache.hadoop.hdfs.DFSOutputStream$DataStreamer.nextBlockOutputStream(
	at org.apache.hadoop.hdfs.DFSOutputStream$


I searched for this error online and got a suggestion to add the following configuration to /etc/hadoop/conf/hdfs-site.xml




However, after adding this configuration, I am unable to restart the hdfs service because it is not found in /etc/init.d

I dont have access to cloudera manager because the person who installed this has left and no knowledge is given to me. Also we don't have a active licence for Cloudera manager (CM).


Is there any way to restart the hdfs service without using CM?


I checked if there is any disk space issue, but looks like all data nodes have sufficient space. Here is the report


hdfs dfsadmin -report
Configured Capacity: 62111967629312 (56.49 TB)
Present Capacity: 60120702897809 (54.68 TB)
DFS Remaining: 22599624797321 (20.55 TB)
DFS Used: 37521078100488 (34.13 TB)
DFS Used%: 62.41%
Under replicated blocks: 0
Blocks with corrupt replicas: 0
Missing blocks: 0
Missing blocks (with replication factor 1): 0

Posts: 768
Registered: ‎05-16-2016

Re: Restarting hdfs service on Data nodes

Did you or did you not resloved this issue . I might take a look it into it . 

Please let me know . 


1 . check if the datanodes are up and runining using command line . 

2 . how is your hadoop temp space looks ? is it runining out of space