Hi Hemanth,
Thanks for the reply, I shall try to get that jstack and reply back, I am
also trying to download hadoop-2.0.3-alpha and see if I can overcome this
error.
Thanks,
Kishore
On Thu, Mar 21, 2013 at 3:24 PM, Hemanth Yamijala wrote:
> There is a way to confirm if it is the same bug.
Thanks Manoj for your suggestion, I have just compared one of the files in
the patch and that is not there in my version of the 2.0.0-alpha code. So,
I don't have that fix.
Thanks,
Ksihore
On Thu, Mar 21, 2013 at 1:55 PM, Manoj Babu wrote:
> In the mean time you can quickly compare the source
There is a way to confirm if it is the same bug. Can you pick a jstack on
the process that has established a connection to 50010 and post it here..
Thanks
hemanth
On Thu, Mar 21, 2013 at 12:13 PM, Krishna Kishore Bonagiri <
write2kish...@gmail.com> wrote:
> Hi Hemanth & Sandy,
>
> Thanks for
In the mean time you can quickly compare the source of the class
with provided patch in the bug.
Cheers!
Manoj.
On Thu, Mar 21, 2013 at 12:13 PM, Krishna Kishore Bonagiri <
write2kish...@gmail.com> wrote:
> Hi Hemanth & Sandy,
>
> Thanks for your reply. Yes, that indicates it is in close wait
Hi Hemanth & Sandy,
Thanks for your reply. Yes, that indicates it is in close wait state,
exactly like below:
java 30718 dsadm 200u IPv4 1178376459 0t0
TCP *:50010 (LISTEN)
java 31512 dsadm 240u IPv6 1178391921 0t0
TCP node1:51342->node1:5
There was an issue related to hung connections (HDFS-3357). But the JIRA
indicates the fix is available in Hadoop-2.0.0-alpha. Still, would be worth
checking on Sandy's suggestion
On Wed, Mar 20, 2013 at 11:09 PM, Sandy Ryza wrote:
> Hi Kishore,
>
> 50010 is the datanode port. Does your lsof ind
Hi Kishore,
50010 is the datanode port. Does your lsof indicate that the sockets are in
CLOSE_WAIT? I had come across an issue like this where that was a symptom.
-Sandy
On Wed, Mar 20, 2013 at 4:24 AM, Krishna Kishore Bonagiri <
write2kish...@gmail.com> wrote:
> Hi,
>
> I am running a date c
