You are running it with the Java command rather than hadopp jar ... Do you have a mechanism inside your Java code to find hadoop like creating your own Configuration? On Apr 30, 2015 1:54 AM, "Mahmood Naderan" <[email protected]> wrote:
> Hi, > when I run the following command, I get ipc.client timeout error. > > [mahmood@tiger Index]$ java -jar indexdata.jar `pwd`/result hdfs:// > 127.0.0.1:9000/data-Index > 15/04/30 10:21:03 INFO ipc.Client: Retrying connect to server: > localhost.localdomain/127.0.0.1:9000. Already tried 0 time(s); retry > policy is RetryUpToMaximumCountWithFixedSleep(maxRetries=10, sleepTime=1 > SECONDS) > > [mahmood@tiger Index]$ ls > data-Index genData_Index.sh indexdata.jar result run-Index.sh > [mahmood@tiger Index]$ ls data-Index/ > lda_wiki1w_1 lda_wiki1w_2 > > > > > Hadoop is up according to the report > > [mahmood@tiger Index]$ hadoop dfsadmin -report > Warning: $HADOOP_HOME is deprecated. > Configured Capacity: 2953524240384 (2.69 TB) > Present Capacity: 602299084800 (560.93 GB) > DFS Remaining: 601237344256 (559.95 GB) > DFS Used: 1061740544 (1012.55 MB) > DFS Used%: 0.18% > Under replicated blocks: 0 > Blocks with corrupt replicas: 0 > Missing blocks: 0 > ------------------------------------------------- > Datanodes available: 1 (1 total, 0 dead) > Name: 127.0.0.1:50010 > Decommission Status : Normal > Configured Capacity: 2953524240384 (2.69 TB) > DFS Used: 1061740544 (1012.55 MB) > Non DFS Used: 2351225155584 (2.14 TB) > DFS Remaining: 601237344256(559.95 GB) > DFS Used%: 0.04% > DFS Remaining%: 20.36% > Last contact: Thu Apr 30 10:22:03 IRDT 2015 > > > Do you have any idea to fix that? > Regards, > Mahmood >
