|| at Oct 27, 2010 at 2:02 pm
I first started by running fsck / which reported healthy. I also know from jobtracker that nothing was running during the balancing time. I filed a ticket with Cloudera, but I still appreciate any insight you or others may have.
From: firstname.lastname@example.org On Behalf Of Patrick Angeles
Sent: Wednesday, October 27, 2010 8:54 AM
Subject: Re: Large amount of corruption after balancer
The corruption may have been caused by running out of disk space. At that
point, even after rebalancing, you will still have corruption. Under normal
circumstances, balancing by itself should not result in corruption.
On Wed, Oct 27, 2010 at 9:40 AM, Jones, Nick wrote:
I just recently started running the balancer to fix job errors where a
particular task runs out of local disk; however, I've noticed that I usually
end up with a significant amount of corruption after it completes. Has
anyone else observed this behavior?
I'm using Cloudera's CDH2 distribution (0.20.1+169.89) and the balancer