Quantcast
Viewing all articles
Browse latest Browse all 3435

Reply To: RegionServer process Connection refused

I’ve found that the regionservers are not listening on 60030 (they ARE listening on 60020). So far this is the only difference I can see between the virtual cluster and the physical cluster.

Could be causing the problem – how might I go about fixing this?

In the logs on the regionserver, it looks like the region server starts, but then it has this message repeatedly:

2015-01-29 08:26:05,421 DEBUG [regionserver60020] regionserver.HRegionServer: Master is not running yet
2015-01-29 08:26:05,421 WARN [regionserver60020] regionserver.HRegionServer: reportForDuty failed; sleeping and then retrying.
2015-01-29 08:26:08,421 INFO [regionserver60020] regionserver.HRegionServer: reportForDuty to master=WHQSBDCONSOLE.owenscorning.com,60000,1422532781386 with port=60020, startcode=1422537961453

Just to verify the ports were working OK, I did a telnet to 60020 from the master to the region server and a telnet to 60000 from the region server to the master and they both connected.

In the log on the master I see repeated:
2015-01-29 08:31:14,585 INFO [master:WHQSBDCONSOLE:60000] util.FSUtils: Waiting for dfs to exit safe mode…

I checked the filesystem to make sure there’s plenty of space. That doesn’t appear to be a problem.

Any ideas?


Viewing all articles
Browse latest Browse all 3435

Trending Articles



<script src="https://jsc.adskeeper.com/r/s/rssing.com.1596347.js" async> </script>