It is not an HA cluster, I gave up on that due to separate problems.
And I am doing this query from the same host as the namenode.
including the netstat -tulapn
that shows the namenode is not exposing the port
On Tuesday, October 24, 2023 at 09:40:09 AM PDT, Wei-Chiu Chuang
wrote:
If it's an HA cluster, is it possible the client doesn't have the proper HA
configuration so it doesn't know what host name to connect to?
Otherwise, the usual suspect is the firewall configuration between the
client and the NameNode.
On Tue, Oct 24, 2023 at 9:05 AM Harry Jamison
wrote:
> I
I feel like I am doing something really dumb here, but my namenode is having a
connection refused on port 8020.
There is nothing in the logs that seems to indicate an error as far as I can
tell
ps aux shows the namenode is running
root 13169 10196 9 21:18 pts/100:00:02
