Home | About | Sematext search-lucene.com search-hadoop.com
NEW: Monitor These Apps!
elasticsearch, apache solr, apache hbase, hadoop, redis, casssandra, amazon cloudwatch, mysql, memcached, apache kafka, apache zookeeper, apache storm, ubuntu, centOS, red hat, debian, puppet labs, java, senseiDB
 Search Hadoop and all its subprojects:

Switch to Plain View
HBase >> mail # user >> Corrupt files


+
Loic Talon 2013-04-30, 10:46
+
Jean-Marc Spaggiari 2013-04-30, 11:34
+
Loic Talon 2013-04-30, 12:31
Bonjour Loïc,

I don't thnk you can restore those blocks. If you have only one datanode
and it doesn't have the missing blocks, there is no-where for hadoop to get
those blocks back. So unfortunatly I don't think you can restore them.

Also, this is more hadoop than hbase related. You might want to move the
discussion in the hadoop mailing list.

JM

2013/4/30 Loic Talon <[EMAIL PROTECTED]>

> Hi Jean-Marc,
> Thanks.
>
> I have one datanode in my cluster.
> The node isn't down.
>
> How can I restore those blocks ?
>
>
>  Loïc TALON
>
>
> [EMAIL PROTECTED] <http://teads.tv/>
> Video Ads Solutions
>
>
>
> 2013/4/30 Jean-Marc Spaggiari <[EMAIL PROTECTED]>
>
> > Hi Loïc,
> >
> > How many datanodes do you have on your cluster? Your replication factor
> is
> > set to 3 so I think you should have at least 3 datanodes?
> >
> > Is one of those nodes down? There is some blocks missing, they are maybe
> on
> > a system which is down now? Bringing it back on might restore those
> blocks.
> >
> > JM
> >
> > 2013/4/30 Loic Talon <[EMAIL PROTECTED]>
> >
> > > Hi,
> > > I have a problem with my namenode.
> > > I work with a single node.
> > >
> > > If I run hdfs fsck /hbase then return :
> > > Status: CORRUPT
> > >  Total size:    294139954971 B
> > >  Total dirs:    2429
> > >  Total files:   4204 (Files currently being written: 75)
> > >  Total blocks (validated):      6164 (avg. block size 47719006 B)
> > >   ******************************
> > > **
> > >   CORRUPT FILES:        63
> > >   MISSING BLOCKS:       50
> > >   MISSING SIZE:         3145209302 B
> > >   CORRUPT BLOCKS:       75
> > >   ********************************
> > >  Minimally replicated blocks:   6114 (99.188835 %)
> > >  Over-replicated blocks:        0 (0.0 %)
> > >  Under-replicated blocks:       6114 (99.188835 %)
> > >  Mis-replicated blocks:         0 (0.0 %)
> > >  Default replication factor:    3
> > >  Average block replication:     0.9918884
> > >  Corrupt blocks:                75
> > >  Missing replicas:              12228 (66.12589 %)
> > >  Number of data-nodes:          1
> > >  Number of racks:               1
> > > FSCK ended at Tue Apr 30 09:59:21 UTC 2013 in 273 milliseconds
> > >
> > >
> > > The filesystem under path '/hbase' is CORRUPT
> > >
> > > How I can resolv this problem ?
> > > I have try hbase namenode -recover but nothing.
> > >
> > > Thanks
> > >
> > > Loïc TALON
> > >
> > >
> > > [EMAIL PROTECTED] <http://teads.tv/>
> > > Video Ads Solutions
> > >
> >
>
NEW: Monitor These Apps!
elasticsearch, apache solr, apache hbase, hadoop, redis, casssandra, amazon cloudwatch, mysql, memcached, apache kafka, apache zookeeper, apache storm, ubuntu, centOS, red hat, debian, puppet labs, java, senseiDB