You are viewing a plain text version of this content. The canonical link for it is here.
Posted to mapreduce-user@hadoop.apache.org by Mahmood Naderan <nt...@yahoo.com> on 2015/05/01 08:03:16 UTC
Re: ipc.client RetryUpToMaximumCountWithFixedSleep
Hi Rajesh,That was a good point. In my config, I used
<configuration>
<property>
<name>fs.default.name</name>
<value>hdfs://localhost:54310</value>
</property>
</configuration>
So I ran
hadoop -jar indexdata.jar `pwd`result hdfs://127.0.0.1:54310/data-Index
This time, I get another error:
Exception in thread "main" java.lang.NullPointerException
at IndexHDFS.indexData(IndexHDFS.java:92)
at IndexHDFS.main(IndexHDFS.java:72)
Is that a problem with IndexData.jar? Can you help with more detail information so that I can tell the developers to find the bug?
Regards,
Mahmood
Re: ipc.client RetryUpToMaximumCountWithFixedSleep
Posted by Mahmood N <nt...@yahoo.com>.
Finally I figured out the problem! Things are:
1- What are specified in the command as ADDRESS and PORT
java -jar indexdata.jar result hdfs://ADDRESS:PORT/data-Index
must be the same things as fs.default.name<property>
<name>fs.default.name</name>
<value>hdfs://ADDRESS:PORT</value>
</property>
So, having <value>hdfs://hostname:9000</value> and running hdfs://localhost:54310 fails to work (ipc.clinet time out). Even the hadoop report command says namenode is up because it read the fs.default.name
2- After matching ADDRESS and PORT, I got this errorException in thread "main" java.lang.NullPointerException
at IndexHDFS.indexData(IndexHDFS.java:92)
at IndexHDFS.main(IndexHDFS.java:72)
The problem here is that the destination folder hdfs://hostname:9000/data-Index doesn't exist and the reason is that when I used copyfromlocal, I embedded data-index/ into multiple folders (my script did that though!). So the correct form is hdfs://hostname:9000/path/to/data-Index
Now it is fine.Thanks to Sandeep for motivating me for focusing on the address and port.
Regards,
Mahmood
Re: ipc.client RetryUpToMaximumCountWithFixedSleep
Posted by Mahmood N <nt...@yahoo.com>.
Finally I figured out the problem! Things are:
1- What are specified in the command as ADDRESS and PORT
java -jar indexdata.jar result hdfs://ADDRESS:PORT/data-Index
must be the same things as fs.default.name<property>
<name>fs.default.name</name>
<value>hdfs://ADDRESS:PORT</value>
</property>
So, having <value>hdfs://hostname:9000</value> and running hdfs://localhost:54310 fails to work (ipc.clinet time out). Even the hadoop report command says namenode is up because it read the fs.default.name
2- After matching ADDRESS and PORT, I got this errorException in thread "main" java.lang.NullPointerException
at IndexHDFS.indexData(IndexHDFS.java:92)
at IndexHDFS.main(IndexHDFS.java:72)
The problem here is that the destination folder hdfs://hostname:9000/data-Index doesn't exist and the reason is that when I used copyfromlocal, I embedded data-index/ into multiple folders (my script did that though!). So the correct form is hdfs://hostname:9000/path/to/data-Index
Now it is fine.Thanks to Sandeep for motivating me for focusing on the address and port.
Regards,
Mahmood
Re: ipc.client RetryUpToMaximumCountWithFixedSleep
Posted by Mahmood N <nt...@yahoo.com>.
Finally I figured out the problem! Things are:
1- What are specified in the command as ADDRESS and PORT
java -jar indexdata.jar result hdfs://ADDRESS:PORT/data-Index
must be the same things as fs.default.name<property>
<name>fs.default.name</name>
<value>hdfs://ADDRESS:PORT</value>
</property>
So, having <value>hdfs://hostname:9000</value> and running hdfs://localhost:54310 fails to work (ipc.clinet time out). Even the hadoop report command says namenode is up because it read the fs.default.name
2- After matching ADDRESS and PORT, I got this errorException in thread "main" java.lang.NullPointerException
at IndexHDFS.indexData(IndexHDFS.java:92)
at IndexHDFS.main(IndexHDFS.java:72)
The problem here is that the destination folder hdfs://hostname:9000/data-Index doesn't exist and the reason is that when I used copyfromlocal, I embedded data-index/ into multiple folders (my script did that though!). So the correct form is hdfs://hostname:9000/path/to/data-Index
Now it is fine.Thanks to Sandeep for motivating me for focusing on the address and port.
Regards,
Mahmood
Re: ipc.client RetryUpToMaximumCountWithFixedSleep
Posted by Mahmood N <nt...@yahoo.com>.
Finally I figured out the problem! Things are:
1- What are specified in the command as ADDRESS and PORT
java -jar indexdata.jar result hdfs://ADDRESS:PORT/data-Index
must be the same things as fs.default.name<property>
<name>fs.default.name</name>
<value>hdfs://ADDRESS:PORT</value>
</property>
So, having <value>hdfs://hostname:9000</value> and running hdfs://localhost:54310 fails to work (ipc.clinet time out). Even the hadoop report command says namenode is up because it read the fs.default.name
2- After matching ADDRESS and PORT, I got this errorException in thread "main" java.lang.NullPointerException
at IndexHDFS.indexData(IndexHDFS.java:92)
at IndexHDFS.main(IndexHDFS.java:72)
The problem here is that the destination folder hdfs://hostname:9000/data-Index doesn't exist and the reason is that when I used copyfromlocal, I embedded data-index/ into multiple folders (my script did that though!). So the correct form is hdfs://hostname:9000/path/to/data-Index
Now it is fine.Thanks to Sandeep for motivating me for focusing on the address and port.
Regards,
Mahmood
Re: ipc.client RetryUpToMaximumCountWithFixedSleep
Posted by Mahmood Naderan <nt...@yahoo.com>.
Any idea is greatly appreciated.... Identifying the problem to be either from hadoop side or the third party side is helpful.... Regards,
Mahmood
On Friday, May 1, 2015 11:09 AM, Mahmood Naderan <nt...@yahoo.com> wrote:
Hi Rajesh,That was a good point. In my config, I used
<configuration>
<property>
<name>fs.default.name</name>
<value>hdfs://localhost:54310</value>
</property>
</configuration>
So I ran
hadoop -jar indexdata.jar `pwd`result hdfs://127.0.0.1:54310/data-Index
This time, I get another error:
Exception in thread "main" java.lang.NullPointerException
at IndexHDFS.indexData(IndexHDFS.java:92)
at IndexHDFS.main(IndexHDFS.java:72)
Is that a problem with IndexData.jar? Can you help with more detail information so that I can tell the developers to find the bug?
Regards,
Mahmood
Re: ipc.client RetryUpToMaximumCountWithFixedSleep
Posted by Mahmood Naderan <nt...@yahoo.com>.
Any idea is greatly appreciated.... Identifying the problem to be either from hadoop side or the third party side is helpful.... Regards,
Mahmood
On Friday, May 1, 2015 11:09 AM, Mahmood Naderan <nt...@yahoo.com> wrote:
Hi Rajesh,That was a good point. In my config, I used
<configuration>
<property>
<name>fs.default.name</name>
<value>hdfs://localhost:54310</value>
</property>
</configuration>
So I ran
hadoop -jar indexdata.jar `pwd`result hdfs://127.0.0.1:54310/data-Index
This time, I get another error:
Exception in thread "main" java.lang.NullPointerException
at IndexHDFS.indexData(IndexHDFS.java:92)
at IndexHDFS.main(IndexHDFS.java:72)
Is that a problem with IndexData.jar? Can you help with more detail information so that I can tell the developers to find the bug?
Regards,
Mahmood
Re: ipc.client RetryUpToMaximumCountWithFixedSleep
Posted by Mahmood Naderan <nt...@yahoo.com>.
Any idea is greatly appreciated.... Identifying the problem to be either from hadoop side or the third party side is helpful.... Regards,
Mahmood
On Friday, May 1, 2015 11:09 AM, Mahmood Naderan <nt...@yahoo.com> wrote:
Hi Rajesh,That was a good point. In my config, I used
<configuration>
<property>
<name>fs.default.name</name>
<value>hdfs://localhost:54310</value>
</property>
</configuration>
So I ran
hadoop -jar indexdata.jar `pwd`result hdfs://127.0.0.1:54310/data-Index
This time, I get another error:
Exception in thread "main" java.lang.NullPointerException
at IndexHDFS.indexData(IndexHDFS.java:92)
at IndexHDFS.main(IndexHDFS.java:72)
Is that a problem with IndexData.jar? Can you help with more detail information so that I can tell the developers to find the bug?
Regards,
Mahmood
Re: ipc.client RetryUpToMaximumCountWithFixedSleep
Posted by Mahmood Naderan <nt...@yahoo.com>.
Any idea is greatly appreciated.... Identifying the problem to be either from hadoop side or the third party side is helpful.... Regards,
Mahmood
On Friday, May 1, 2015 11:09 AM, Mahmood Naderan <nt...@yahoo.com> wrote:
Hi Rajesh,That was a good point. In my config, I used
<configuration>
<property>
<name>fs.default.name</name>
<value>hdfs://localhost:54310</value>
</property>
</configuration>
So I ran
hadoop -jar indexdata.jar `pwd`result hdfs://127.0.0.1:54310/data-Index
This time, I get another error:
Exception in thread "main" java.lang.NullPointerException
at IndexHDFS.indexData(IndexHDFS.java:92)
at IndexHDFS.main(IndexHDFS.java:72)
Is that a problem with IndexData.jar? Can you help with more detail information so that I can tell the developers to find the bug?
Regards,
Mahmood