@UrosCvijanovic The Namenode holds the Metadata that maps the files to the blocks present in the Datanode. Without this metadata, the namenode won't be able to interpret which block belongs to which file even if we manage to report all the blocks to the Namenode. Though the chances are very slim, you can try to start a new single node cluster and then map this block data with the new cluster. Copy the old data/current directory containing the block files into the new cluster’s DataNode storage directories. ... View more

@UrosCvijanovic When you reformatted the NameNode, its metadata (e.g., fsimage and edits files) was reset, and a new VERSION file was created. If you have a backup of the original NameNode directory before the format, then you can copy it to the current Namenode data dir. The clusterID and the blockPool ID should match in the Version file of both the Namenode and Datanode.  ... View more

See if you can raise a support ticket with Cloudera. The app log needs a detailed review to know what is causing the container to get fail. ... View more

If you are still not able to run the command successfully from the Region server host, then its most likely an issue with YARN. Can you check if there are any other WARNs or ERRORs in the app log apart from log4j warnings. ... View more

can you confirm if Zookeeper service is running on this host? Apart from the log4J errors, Do you see any others in the Application log? ... View more

@Amandi Can you try to run the command from a Region server host. The connection is going to a localhost on port 2181. So if Zookeeper is not running on the host from where you are running the command, it will fail. ... View more

If the current stat in hbase:meta is OPEN, I won't suggest performing any other action to change the state in meta. I suspect there are some procedures running in the backend trying to assign the region again. Do you see any procedure as such in the "Procedure & locks" section under the Hbase Master Web UI? ... View more

If the Region server reports that the region is already OPEN, try to scan the hbase:meta table from the hbase shell and check what state that region is in. If its still in OPENING state in meta, try to change its state to OPEN. Do it for one of the region and see if that brings down the RIT count to 133. ... View more