I thought that I had, but perhaps not. I assume that I would configure this on
the master, using the dfs.namenode.backup.address parameter. Is that correct?
Thanks,
Gabe
On Feb 1, 2012, at 4:27 PM, Jakob Homan wrote:
>> Posted URL
>> master:50070putimage=1&port=50090&machine=0.0.0.0&token=-31
> Posted URL
> master:50070putimage=1&port=50090&machine=0.0.0.0&token=-31:1318804155:0:1328129935000:1328129628242
Have you defined your secondary namenode address? The 2NN is telling
the NN to pull the merged image from http://0.0.0.0.0:50090.
On Wed, Feb 1, 2012 at 1:23 PM, Gabriel Rosendorf
No firewall.
Here's hdfs-site.xml from 2NN: http://pastie.org/3298304
And from NN: http://pastie.org/3298309
On Feb 1, 2012, at 4:18 PM, Harsh J wrote:
> Have you ensured there is no firewall between the two hosts? Can you
> also pastebin your hdfs-site.xml?
>
> On Thu, Feb 2, 2012 at 2:45 AM,
Have you ensured there is no firewall between the two hosts? Can you
also pastebin your hdfs-site.xml?
On Thu, Feb 2, 2012 at 2:45 AM, Gabriel Rosendorf
wrote:
> So I'm at a loss. Â Checkpointing is failing, and both hosts (NN and 2NN) are
> reachable via HTTP.
> Any ideas would be greatly appreci
