Home | About | Sematext search-lucene.com search-hadoop.com
NEW: Monitor These Apps!
elasticsearch, apache solr, apache hbase, hadoop, redis, casssandra, amazon cloudwatch, mysql, memcached, apache kafka, apache zookeeper, apache storm, ubuntu, centOS, red hat, debian, puppet labs, java, senseiDB
 Search Hadoop and all its subprojects:

Switch to Threaded View
Hadoop >> mail # user >> Re: hadoop cluster not working


Copy link to this message
-
Re: hadoop cluster not working
i have not configured, can u tell me how to configure
On Sun, Mar 10, 2013 at 7:31 PM, Hemanth Yamijala <[EMAIL PROTECTED]
> wrote:

> Have you configured your JobTracker's IPC port as 54311. Sharing your
> configuration may be helpful.
>
> Thanks
> Hemanth
>
>
> On Sun, Mar 10, 2013 at 11:56 AM, mallik arjun <[EMAIL PROTECTED]>wrote:
>
>> i have seen the logs and the reason for the error is
>> 13/03/10 10:26:45 ERROR security.UserGroupInformation:
>> PriviledgedActionException as:mallik cause:java.io.IOException: Call to
>> localhost/127.0.0.1:54311 failed on local exception:
>> java.io.IOException: Connection reset by peer
>> Exception in thread "main" java.io.IOException: Call to localhost/
>> 127.0.0.1:54311 failed on local exception: java.io.IOException:
>> Connection reset by peer
>>  at org.apache.hadoop.ipc.Client.wrapException(Client.java:1107)
>>  at org.apache.hadoop.ipc.Client.call(Client.java:1075)
>> at org.apache.hadoop.ipc.RPC$Invoker.invoke(RPC.java:225)
>>  at org.apache.hadoop.mapred.$Proxy2.getProtocolVersion(Unknown Source)
>> at org.apache.hadoop.ipc.RPC.getProxy(RPC.java:396)
>>  at org.apache.hadoop.ipc.RPC.getProxy(RPC.java:379)
>> at org.apache.hadoop.mapred.JobClient.createRPCProxy(JobClient.java:480)
>>  at org.apache.hadoop.mapred.JobClient.init(JobClient.java:474)
>> at org.apache.hadoop.mapred.JobClient.<init>(JobClient.java:457)
>>  at org.apache.hadoop.mapreduce.Job$1.run(Job.java:513)
>> at java.security.AccessController.doPrivileged(Native Method)
>>  at javax.security.auth.Subject.doAs(Subject.java:415)
>> at
>> org.apache.hadoop.security.UserGroupInformation.doAs(UserGroupInformation.java:1121)
>>  at org.apache.hadoop.mapreduce.Job.connect(Job.java:511)
>> at org.apache.hadoop.mapreduce.Job.submit(Job.java:499)
>>  at org.apache.hadoop.mapreduce.Job.waitForCompletion(Job.java:530)
>> at MaxTemperature.main(MaxTemperature.java:31)
>>  at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
>> at
>> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
>>  at
>> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
>> at java.lang.reflect.Method.invoke(Method.java:601)
>>  at org.apache.hadoop.util.RunJar.main(RunJar.java:156)
>> Caused by: java.io.IOException: Connection reset by peer
>> at sun.nio.ch.FileDispatcherImpl.read0(Native Method)
>>  at sun.nio.ch.SocketDispatcher.read(SocketDispatcher.java:39)
>> at sun.nio.ch.IOUtil.readIntoNativeBuffer(IOUtil.java:218)
>>  at sun.nio.ch.IOUtil.read(IOUtil.java:191)
>> at sun.nio.ch.SocketChannelImpl.read(SocketChannelImpl.java:359)
>>  at
>> org.apache.hadoop.net.SocketInputStream$Reader.performIO(SocketInputStream.java:55)
>> at
>> org.apache.hadoop.net.SocketIOWithTimeout.doIO(SocketIOWithTimeout.java:142)
>>  at
>> org.apache.hadoop.net.SocketInputStream.read(SocketInputStream.java:155)
>> at
>> org.apache.hadoop.net.SocketInputStream.read(SocketInputStream.java:128)
>>  at java.io.FilterInputStream.read(FilterInputStream.java:133)
>> at
>> org.apache.hadoop.ipc.Client$Connection$PingInputStream.read(Client.java:342)
>>  at java.io.BufferedInputStream.fill(BufferedInputStream.java:235)
>> at java.io.BufferedInputStream.read(BufferedInputStream.java:254)
>>  at java.io.DataInputStream.readInt(DataInputStream.java:387)
>> at
>> org.apache.hadoop.ipc.Client$Connection.receiveResponse(Client.java:804)
>>  at org.apache.hadoop.ipc.Client$Connection.run(Client.java:749)
>>
>>
>> On Sun, Mar 10, 2013 at 10:33 AM, mallik arjun <[EMAIL PROTECTED]>wrote:
>>
>>> both name node and job tracker are working well
>>>
>>>
>>>
>>> On Sun, Mar 10, 2013 at 10:25 AM, Jagat Singh <[EMAIL PROTECTED]>wrote:
>>>
>>>> What is coming on
>>>>
>>>> localhost:50070
>>>> localhost:50030
>>>>
>>>> Are you able to see console pages?
>>>>
>>>>
>>>>
>>>>
>>>> On Sun, Mar 10, 2013 at 3:49 PM, mallik arjun <[EMAIL PROTECTED]>wrote:
>>>>
>>>>> i am not able to run that command and logs are empty
NEW: Monitor These Apps!
elasticsearch, apache solr, apache hbase, hadoop, redis, casssandra, amazon cloudwatch, mysql, memcached, apache kafka, apache zookeeper, apache storm, ubuntu, centOS, red hat, debian, puppet labs, java, senseiDB