You are viewing a plain text version of this content. The canonical link for it is here.
Posted to user@hadoop.apache.org by unmesha sreeveni <un...@gmail.com> on 2014/11/18 05:45:33 UTC
Showing INFO ipc.Client: Retrying connect to server once hadoop is
upgraded to cdh5.2.0
Upgraded my Hadoop cluster (CDH) to cdh5.2.0
But once I run my Job with iteration, It is showing after 1 st iterative
Job.
14/11/17 09:29:44 INFO ipc.Client: Retrying connect to server:
/xx.xx.xx.xx:xxxx. Already tried 0 time(s); retry policy is
RetryUpToMaximumCountWithFixedSleep(maxRetries=3, sleepTime=1000
MILLISECONDS)
14/11/17 09:29:45 INFO ipc.Client: Retrying connect to server:
/xx.xx.xx.xx:xxxx. Already tried 1 time(s); retry policy is
RetryUpToMaximumCountWithFixedSleep(maxRetries=3, sleepTime=1000
MILLISECONDS)
14/11/17 09:29:46 INFO ipc.Client: Retrying connect to server:
/xx.xx.xx.xx:xxxx. Already tried 2 time(s); retry policy is
RetryUpToMaximumCountWithFixedSleep(maxRetries=3, sleepTime=1000
MILLISECONDS)
I have some calculations in Driver class. It is working fine for small
dataset. When I tried to run 1gb data it is showing above error.
It seems like after my first job some calculation is done in driver class
and after the calculation the next job get starts. But I think it is not
waiting for the time spend for calculation in driver class(as it is 1 gb
file it takes long time for driver calculation) and throwing the above
error.
It worked fine in previous version.
Whether I missed anything during installation?
Why is it so? Pleace Advice
--
*Thanks & Regards *
*Unmesha Sreeveni U.B*
*Hadoop, Bigdata Developer*
*Centre for Cyber Security | Amrita Vishwa Vidyapeetham*
http://www.unmeshasreeveni.blogspot.in/
Re: Showing INFO ipc.Client: Retrying connect to server once hadoop
is upgraded to cdh5.2.0
Posted by Fabio <an...@gmail.com>.
I had this problem on a small cluster running Debian, in my case the
issue was caused by a reference to 0.0.0.0 as localhost in /etc/hosts, I
removed it leaving just 127.0.0.1 as localhost ip and the problem was
solved. If it's not the same issue it could be something similar about
address resolution... try to understand if this only happens between the
same source and destination.
Regards
Fabio
On 11/24/2014 05:45 AM, unmesha sreeveni wrote:
> Why is it showing like this. Any clues.
>
> On Tue, Nov 18, 2014 at 10:15 AM, unmesha sreeveni
> <unmeshabiju@gmail.com <ma...@gmail.com>> wrote:
>
> Upgraded my Hadoop cluster (CDH) to cdh5.2.0
>
> But once I run my Job with iteration, It is showing after 1 st
> iterative Job.
>
>
> |14/11/17 09:29:44 INFO ipc.Client: Retrying connect to server: /xx.xx.xx.xx:xxxx. Already tried 0 time(s); retry policy is RetryUpToMaximumCountWithFixedSleep(maxRetries=3, sleepTime=1000 MILLISECONDS)
> 14/11/17 09:29:45 INFO ipc.Client: Retrying connect to server: /xx.xx.xx.xx:xxxx. Already tried 1 time(s); retry policy is RetryUpToMaximumCountWithFixedSleep(maxRetries=3, sleepTime=1000 MILLISECONDS)
> 14/11/17 09:29:46 INFO ipc.Client: Retrying connect to server: /xx.xx.xx.xx:xxxx. Already tried 2 time(s); retry policy is RetryUpToMaximumCountWithFixedSleep(maxRetries=3, sleepTime=1000 MILLISECONDS)|
>
>
> I have some calculations in Driver class. It is working fine for
> small dataset. When I tried to run 1gb data it is showing above error.
> It seems like after my first job some calculation is done in
> driver class and after the calculation the next job get starts.
> But I think it is not waiting for the time spend for calculation
> in driver class(as it is 1 gb file it takes long time for driver
> calculation) and throwing the above error.
>
> It worked fine in previous version.
>
>
> Whether I missed anything during installation?
> Why is it so? Pleace Advice
>
> --
> */Thanks & Regards/ *
> /*
> */
> *Unmesha Sreeveni U.B/
> /*
> *Hadoop, Bigdata Developer*
> *Centre for Cyber Security | Amrita Vishwa Vidyapeetham*
> http://www.unmeshasreeveni.blogspot.in/
>
> /
> /
>
>
>
>
> --
> */Thanks & Regards/ *
> /*
> */
> *Unmesha Sreeveni U.B/
> /*
> *Hadoop, Bigdata Developer*
> *Centre for Cyber Security | Amrita Vishwa Vidyapeetham*
> http://www.unmeshasreeveni.blogspot.in/
>
> /
> /
Re: Showing INFO ipc.Client: Retrying connect to server once hadoop
is upgraded to cdh5.2.0
Posted by Fabio <an...@gmail.com>.
I had this problem on a small cluster running Debian, in my case the
issue was caused by a reference to 0.0.0.0 as localhost in /etc/hosts, I
removed it leaving just 127.0.0.1 as localhost ip and the problem was
solved. If it's not the same issue it could be something similar about
address resolution... try to understand if this only happens between the
same source and destination.
Regards
Fabio
On 11/24/2014 05:45 AM, unmesha sreeveni wrote:
> Why is it showing like this. Any clues.
>
> On Tue, Nov 18, 2014 at 10:15 AM, unmesha sreeveni
> <unmeshabiju@gmail.com <ma...@gmail.com>> wrote:
>
> Upgraded my Hadoop cluster (CDH) to cdh5.2.0
>
> But once I run my Job with iteration, It is showing after 1 st
> iterative Job.
>
>
> |14/11/17 09:29:44 INFO ipc.Client: Retrying connect to server: /xx.xx.xx.xx:xxxx. Already tried 0 time(s); retry policy is RetryUpToMaximumCountWithFixedSleep(maxRetries=3, sleepTime=1000 MILLISECONDS)
> 14/11/17 09:29:45 INFO ipc.Client: Retrying connect to server: /xx.xx.xx.xx:xxxx. Already tried 1 time(s); retry policy is RetryUpToMaximumCountWithFixedSleep(maxRetries=3, sleepTime=1000 MILLISECONDS)
> 14/11/17 09:29:46 INFO ipc.Client: Retrying connect to server: /xx.xx.xx.xx:xxxx. Already tried 2 time(s); retry policy is RetryUpToMaximumCountWithFixedSleep(maxRetries=3, sleepTime=1000 MILLISECONDS)|
>
>
> I have some calculations in Driver class. It is working fine for
> small dataset. When I tried to run 1gb data it is showing above error.
> It seems like after my first job some calculation is done in
> driver class and after the calculation the next job get starts.
> But I think it is not waiting for the time spend for calculation
> in driver class(as it is 1 gb file it takes long time for driver
> calculation) and throwing the above error.
>
> It worked fine in previous version.
>
>
> Whether I missed anything during installation?
> Why is it so? Pleace Advice
>
> --
> */Thanks & Regards/ *
> /*
> */
> *Unmesha Sreeveni U.B/
> /*
> *Hadoop, Bigdata Developer*
> *Centre for Cyber Security | Amrita Vishwa Vidyapeetham*
> http://www.unmeshasreeveni.blogspot.in/
>
> /
> /
>
>
>
>
> --
> */Thanks & Regards/ *
> /*
> */
> *Unmesha Sreeveni U.B/
> /*
> *Hadoop, Bigdata Developer*
> *Centre for Cyber Security | Amrita Vishwa Vidyapeetham*
> http://www.unmeshasreeveni.blogspot.in/
>
> /
> /
Re: Showing INFO ipc.Client: Retrying connect to server once hadoop
is upgraded to cdh5.2.0
Posted by Fabio <an...@gmail.com>.
I had this problem on a small cluster running Debian, in my case the
issue was caused by a reference to 0.0.0.0 as localhost in /etc/hosts, I
removed it leaving just 127.0.0.1 as localhost ip and the problem was
solved. If it's not the same issue it could be something similar about
address resolution... try to understand if this only happens between the
same source and destination.
Regards
Fabio
On 11/24/2014 05:45 AM, unmesha sreeveni wrote:
> Why is it showing like this. Any clues.
>
> On Tue, Nov 18, 2014 at 10:15 AM, unmesha sreeveni
> <unmeshabiju@gmail.com <ma...@gmail.com>> wrote:
>
> Upgraded my Hadoop cluster (CDH) to cdh5.2.0
>
> But once I run my Job with iteration, It is showing after 1 st
> iterative Job.
>
>
> |14/11/17 09:29:44 INFO ipc.Client: Retrying connect to server: /xx.xx.xx.xx:xxxx. Already tried 0 time(s); retry policy is RetryUpToMaximumCountWithFixedSleep(maxRetries=3, sleepTime=1000 MILLISECONDS)
> 14/11/17 09:29:45 INFO ipc.Client: Retrying connect to server: /xx.xx.xx.xx:xxxx. Already tried 1 time(s); retry policy is RetryUpToMaximumCountWithFixedSleep(maxRetries=3, sleepTime=1000 MILLISECONDS)
> 14/11/17 09:29:46 INFO ipc.Client: Retrying connect to server: /xx.xx.xx.xx:xxxx. Already tried 2 time(s); retry policy is RetryUpToMaximumCountWithFixedSleep(maxRetries=3, sleepTime=1000 MILLISECONDS)|
>
>
> I have some calculations in Driver class. It is working fine for
> small dataset. When I tried to run 1gb data it is showing above error.
> It seems like after my first job some calculation is done in
> driver class and after the calculation the next job get starts.
> But I think it is not waiting for the time spend for calculation
> in driver class(as it is 1 gb file it takes long time for driver
> calculation) and throwing the above error.
>
> It worked fine in previous version.
>
>
> Whether I missed anything during installation?
> Why is it so? Pleace Advice
>
> --
> */Thanks & Regards/ *
> /*
> */
> *Unmesha Sreeveni U.B/
> /*
> *Hadoop, Bigdata Developer*
> *Centre for Cyber Security | Amrita Vishwa Vidyapeetham*
> http://www.unmeshasreeveni.blogspot.in/
>
> /
> /
>
>
>
>
> --
> */Thanks & Regards/ *
> /*
> */
> *Unmesha Sreeveni U.B/
> /*
> *Hadoop, Bigdata Developer*
> *Centre for Cyber Security | Amrita Vishwa Vidyapeetham*
> http://www.unmeshasreeveni.blogspot.in/
>
> /
> /
Re: Showing INFO ipc.Client: Retrying connect to server once hadoop
is upgraded to cdh5.2.0
Posted by Fabio <an...@gmail.com>.
I had this problem on a small cluster running Debian, in my case the
issue was caused by a reference to 0.0.0.0 as localhost in /etc/hosts, I
removed it leaving just 127.0.0.1 as localhost ip and the problem was
solved. If it's not the same issue it could be something similar about
address resolution... try to understand if this only happens between the
same source and destination.
Regards
Fabio
On 11/24/2014 05:45 AM, unmesha sreeveni wrote:
> Why is it showing like this. Any clues.
>
> On Tue, Nov 18, 2014 at 10:15 AM, unmesha sreeveni
> <unmeshabiju@gmail.com <ma...@gmail.com>> wrote:
>
> Upgraded my Hadoop cluster (CDH) to cdh5.2.0
>
> But once I run my Job with iteration, It is showing after 1 st
> iterative Job.
>
>
> |14/11/17 09:29:44 INFO ipc.Client: Retrying connect to server: /xx.xx.xx.xx:xxxx. Already tried 0 time(s); retry policy is RetryUpToMaximumCountWithFixedSleep(maxRetries=3, sleepTime=1000 MILLISECONDS)
> 14/11/17 09:29:45 INFO ipc.Client: Retrying connect to server: /xx.xx.xx.xx:xxxx. Already tried 1 time(s); retry policy is RetryUpToMaximumCountWithFixedSleep(maxRetries=3, sleepTime=1000 MILLISECONDS)
> 14/11/17 09:29:46 INFO ipc.Client: Retrying connect to server: /xx.xx.xx.xx:xxxx. Already tried 2 time(s); retry policy is RetryUpToMaximumCountWithFixedSleep(maxRetries=3, sleepTime=1000 MILLISECONDS)|
>
>
> I have some calculations in Driver class. It is working fine for
> small dataset. When I tried to run 1gb data it is showing above error.
> It seems like after my first job some calculation is done in
> driver class and after the calculation the next job get starts.
> But I think it is not waiting for the time spend for calculation
> in driver class(as it is 1 gb file it takes long time for driver
> calculation) and throwing the above error.
>
> It worked fine in previous version.
>
>
> Whether I missed anything during installation?
> Why is it so? Pleace Advice
>
> --
> */Thanks & Regards/ *
> /*
> */
> *Unmesha Sreeveni U.B/
> /*
> *Hadoop, Bigdata Developer*
> *Centre for Cyber Security | Amrita Vishwa Vidyapeetham*
> http://www.unmeshasreeveni.blogspot.in/
>
> /
> /
>
>
>
>
> --
> */Thanks & Regards/ *
> /*
> */
> *Unmesha Sreeveni U.B/
> /*
> *Hadoop, Bigdata Developer*
> *Centre for Cyber Security | Amrita Vishwa Vidyapeetham*
> http://www.unmeshasreeveni.blogspot.in/
>
> /
> /
Re: Showing INFO ipc.Client: Retrying connect to server once hadoop
is upgraded to cdh5.2.0
Posted by unmesha sreeveni <un...@gmail.com>.
Why is it showing like this. Any clues.
On Tue, Nov 18, 2014 at 10:15 AM, unmesha sreeveni <un...@gmail.com>
wrote:
> Upgraded my Hadoop cluster (CDH) to cdh5.2.0
>
> But once I run my Job with iteration, It is showing after 1 st iterative
> Job.
>
>
> 14/11/17 09:29:44 INFO ipc.Client: Retrying connect to server: /xx.xx.xx.xx:xxxx. Already tried 0 time(s); retry policy is RetryUpToMaximumCountWithFixedSleep(maxRetries=3, sleepTime=1000 MILLISECONDS)
> 14/11/17 09:29:45 INFO ipc.Client: Retrying connect to server: /xx.xx.xx.xx:xxxx. Already tried 1 time(s); retry policy is RetryUpToMaximumCountWithFixedSleep(maxRetries=3, sleepTime=1000 MILLISECONDS)
> 14/11/17 09:29:46 INFO ipc.Client: Retrying connect to server: /xx.xx.xx.xx:xxxx. Already tried 2 time(s); retry policy is RetryUpToMaximumCountWithFixedSleep(maxRetries=3, sleepTime=1000 MILLISECONDS)
>
>
> I have some calculations in Driver class. It is working fine for small
> dataset. When I tried to run 1gb data it is showing above error.
> It seems like after my first job some calculation is done in driver class
> and after the calculation the next job get starts. But I think it is not
> waiting for the time spend for calculation in driver class(as it is 1 gb
> file it takes long time for driver calculation) and throwing the above
> error.
>
> It worked fine in previous version.
>
>
> Whether I missed anything during installation?
> Why is it so? Pleace Advice
>
> --
> *Thanks & Regards *
>
>
> *Unmesha Sreeveni U.B*
> *Hadoop, Bigdata Developer*
> *Centre for Cyber Security | Amrita Vishwa Vidyapeetham*
> http://www.unmeshasreeveni.blogspot.in/
>
>
>
--
*Thanks & Regards *
*Unmesha Sreeveni U.B*
*Hadoop, Bigdata Developer*
*Centre for Cyber Security | Amrita Vishwa Vidyapeetham*
http://www.unmeshasreeveni.blogspot.in/
Re: Showing INFO ipc.Client: Retrying connect to server once hadoop
is upgraded to cdh5.2.0
Posted by unmesha sreeveni <un...@gmail.com>.
Why is it showing like this. Any clues.
On Tue, Nov 18, 2014 at 10:15 AM, unmesha sreeveni <un...@gmail.com>
wrote:
> Upgraded my Hadoop cluster (CDH) to cdh5.2.0
>
> But once I run my Job with iteration, It is showing after 1 st iterative
> Job.
>
>
> 14/11/17 09:29:44 INFO ipc.Client: Retrying connect to server: /xx.xx.xx.xx:xxxx. Already tried 0 time(s); retry policy is RetryUpToMaximumCountWithFixedSleep(maxRetries=3, sleepTime=1000 MILLISECONDS)
> 14/11/17 09:29:45 INFO ipc.Client: Retrying connect to server: /xx.xx.xx.xx:xxxx. Already tried 1 time(s); retry policy is RetryUpToMaximumCountWithFixedSleep(maxRetries=3, sleepTime=1000 MILLISECONDS)
> 14/11/17 09:29:46 INFO ipc.Client: Retrying connect to server: /xx.xx.xx.xx:xxxx. Already tried 2 time(s); retry policy is RetryUpToMaximumCountWithFixedSleep(maxRetries=3, sleepTime=1000 MILLISECONDS)
>
>
> I have some calculations in Driver class. It is working fine for small
> dataset. When I tried to run 1gb data it is showing above error.
> It seems like after my first job some calculation is done in driver class
> and after the calculation the next job get starts. But I think it is not
> waiting for the time spend for calculation in driver class(as it is 1 gb
> file it takes long time for driver calculation) and throwing the above
> error.
>
> It worked fine in previous version.
>
>
> Whether I missed anything during installation?
> Why is it so? Pleace Advice
>
> --
> *Thanks & Regards *
>
>
> *Unmesha Sreeveni U.B*
> *Hadoop, Bigdata Developer*
> *Centre for Cyber Security | Amrita Vishwa Vidyapeetham*
> http://www.unmeshasreeveni.blogspot.in/
>
>
>
--
*Thanks & Regards *
*Unmesha Sreeveni U.B*
*Hadoop, Bigdata Developer*
*Centre for Cyber Security | Amrita Vishwa Vidyapeetham*
http://www.unmeshasreeveni.blogspot.in/
Re: Showing INFO ipc.Client: Retrying connect to server once hadoop
is upgraded to cdh5.2.0
Posted by unmesha sreeveni <un...@gmail.com>.
Why is it showing like this. Any clues.
On Tue, Nov 18, 2014 at 10:15 AM, unmesha sreeveni <un...@gmail.com>
wrote:
> Upgraded my Hadoop cluster (CDH) to cdh5.2.0
>
> But once I run my Job with iteration, It is showing after 1 st iterative
> Job.
>
>
> 14/11/17 09:29:44 INFO ipc.Client: Retrying connect to server: /xx.xx.xx.xx:xxxx. Already tried 0 time(s); retry policy is RetryUpToMaximumCountWithFixedSleep(maxRetries=3, sleepTime=1000 MILLISECONDS)
> 14/11/17 09:29:45 INFO ipc.Client: Retrying connect to server: /xx.xx.xx.xx:xxxx. Already tried 1 time(s); retry policy is RetryUpToMaximumCountWithFixedSleep(maxRetries=3, sleepTime=1000 MILLISECONDS)
> 14/11/17 09:29:46 INFO ipc.Client: Retrying connect to server: /xx.xx.xx.xx:xxxx. Already tried 2 time(s); retry policy is RetryUpToMaximumCountWithFixedSleep(maxRetries=3, sleepTime=1000 MILLISECONDS)
>
>
> I have some calculations in Driver class. It is working fine for small
> dataset. When I tried to run 1gb data it is showing above error.
> It seems like after my first job some calculation is done in driver class
> and after the calculation the next job get starts. But I think it is not
> waiting for the time spend for calculation in driver class(as it is 1 gb
> file it takes long time for driver calculation) and throwing the above
> error.
>
> It worked fine in previous version.
>
>
> Whether I missed anything during installation?
> Why is it so? Pleace Advice
>
> --
> *Thanks & Regards *
>
>
> *Unmesha Sreeveni U.B*
> *Hadoop, Bigdata Developer*
> *Centre for Cyber Security | Amrita Vishwa Vidyapeetham*
> http://www.unmeshasreeveni.blogspot.in/
>
>
>
--
*Thanks & Regards *
*Unmesha Sreeveni U.B*
*Hadoop, Bigdata Developer*
*Centre for Cyber Security | Amrita Vishwa Vidyapeetham*
http://www.unmeshasreeveni.blogspot.in/
Re: Showing INFO ipc.Client: Retrying connect to server once hadoop
is upgraded to cdh5.2.0
Posted by unmesha sreeveni <un...@gmail.com>.
Why is it showing like this. Any clues.
On Tue, Nov 18, 2014 at 10:15 AM, unmesha sreeveni <un...@gmail.com>
wrote:
> Upgraded my Hadoop cluster (CDH) to cdh5.2.0
>
> But once I run my Job with iteration, It is showing after 1 st iterative
> Job.
>
>
> 14/11/17 09:29:44 INFO ipc.Client: Retrying connect to server: /xx.xx.xx.xx:xxxx. Already tried 0 time(s); retry policy is RetryUpToMaximumCountWithFixedSleep(maxRetries=3, sleepTime=1000 MILLISECONDS)
> 14/11/17 09:29:45 INFO ipc.Client: Retrying connect to server: /xx.xx.xx.xx:xxxx. Already tried 1 time(s); retry policy is RetryUpToMaximumCountWithFixedSleep(maxRetries=3, sleepTime=1000 MILLISECONDS)
> 14/11/17 09:29:46 INFO ipc.Client: Retrying connect to server: /xx.xx.xx.xx:xxxx. Already tried 2 time(s); retry policy is RetryUpToMaximumCountWithFixedSleep(maxRetries=3, sleepTime=1000 MILLISECONDS)
>
>
> I have some calculations in Driver class. It is working fine for small
> dataset. When I tried to run 1gb data it is showing above error.
> It seems like after my first job some calculation is done in driver class
> and after the calculation the next job get starts. But I think it is not
> waiting for the time spend for calculation in driver class(as it is 1 gb
> file it takes long time for driver calculation) and throwing the above
> error.
>
> It worked fine in previous version.
>
>
> Whether I missed anything during installation?
> Why is it so? Pleace Advice
>
> --
> *Thanks & Regards *
>
>
> *Unmesha Sreeveni U.B*
> *Hadoop, Bigdata Developer*
> *Centre for Cyber Security | Amrita Vishwa Vidyapeetham*
> http://www.unmeshasreeveni.blogspot.in/
>
>
>
--
*Thanks & Regards *
*Unmesha Sreeveni U.B*
*Hadoop, Bigdata Developer*
*Centre for Cyber Security | Amrita Vishwa Vidyapeetham*
http://www.unmeshasreeveni.blogspot.in/