On Oct 25, 2010, at 6:35 PM, phil young wrote:

> I had also assumed that some other jar or configuration file had been
> changed, but reviewing the timestamps on the files did not reveal the
> problem.
> On the assumption that something did in fact change, that I was not seeing,
> I renamed my $HADOOP_HOME directory and replaced it with one from a slave.
> I then restored $HADOOP_HOME/conf from the original/renamed directory, and
> voila - we're back in business.
> 

Glad to hear this.

> Brian, thanks very much for your help.
> It took literally more time for me to write the original email (5 minutes)
> than to get a reply which indicated a way to solve the problem, and another
> 5 minutes to solve it.
> That says a lot about the user group. I don't think I would have reached a
> human being in 5 minutes for the tech support for most products.
> I'll make sure to monitor this list more closely so I can pay it forward ;)
> 

No problem.  There are lots of good people on this list, and I certainly have 
done the "oh crap, I put my neck on the line for this new Hadoop thing and now 
its broke" email.

Brian

Attachment: smime.p7s
Description: S/MIME cryptographic signature

Reply via email to