Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Got ClassNotFoundException[org.elasticsearch.repositories.hdfs.HdfsRepositoryModule] error when using repository-hdfs plugin #290

Closed
sbbird opened this issue Oct 2, 2014 · 3 comments

Comments

@sbbird
Copy link

sbbird commented Oct 2, 2014

I am not sure whether my usage is correct. I tried elasticsearch-repository-hdfs plugin by

curl -XPUT 'http://localhost:9200/_snapshot/hdfs_backup/' -d '{
    "type":"hdfs", 
    "settings": { 
           "uri":"hdfs://localhost:9000/", 
           "path":"elasticsearch/hdfs_backup"
      }
}' 

Then I got the error

{"error":"RemoteTransportException[[Whiplash][inet[/10.187.17.209:9300]][cluster/repository/put]];
nested: RepositoryException[[hdfs_backup] failed to create repository]; 
nested: NoClassSettingsException[failed to load class with value [hdfs]; 
tried [hdfs, org.elasticsearch.repositories.HdfsRepositoryModule, org.elasticsearch.repositories.hdfs.HdfsRepositoryModule, org.elasticsearch.repositories.hdfs.HdfsRepositoryModule]];
nested: ClassNotFoundException[org.elasticsearch.repositories.hdfs.HdfsRepositoryModule]; ",
"status":500}

I installed elasticsearch-repository-hdfs-2.0.1-hadoop by

$ bin/plugin -i elasticsearch/elasticsearch-repository-hdfs/2.0.1-hadoop2                                                                                                                                                                                          [16:16:12]
-> Installing elasticsearch/elasticsearch-repository-hdfs/2.0.1-hadoop2...
Trying http://download.elasticsearch.org/elasticsearch/elasticsearch-repository-hdfs/elasticsearch-repository-hdfs-2.0.1-hadoop2.zip...
Downloading ..............DONE
Installed elasticsearch/elasticsearch-repository-hdfs/2.0.1-hadoop2 into /home/sbbird/tools/elasticsearch-1.3.2/plugins/repository-hdfs

The log of Elasticsearch:

$ bin/elasticsearch 
[2014-10-02 17:45:11,508][INFO ][node                     ] [Shadrac] version[1.3.4], pid[14371], build[a70f3cc/2014-09-30T09:07:17Z]
[2014-10-02 17:45:11,508][INFO ][node                     ] [Shadrac] initializing ...
[2014-10-02 17:45:11,531][INFO ][plugins                  ] [Shadrac] loaded [hdfs-snapshot], sites []
[2014-10-02 17:45:13,291][INFO ][node                     ] [Shadrac] initialized
[2014-10-02 17:45:13,291][INFO ][node                     ] [Shadrac] starting ...
[2014-10-02 17:45:13,342][INFO ][transport                ] [Shadrac] bound_address {inet[/0:0:0:0:0:0:0:0:9300]}, publish_address {inet[/10.187.17.82:9300]}
[2014-10-02 17:45:13,353][INFO ][discovery                ] [Shadrac] elasticsearch/qFnle45GSvqTjOa5qBs4sw
[2014-10-02 17:45:16,396][INFO ][cluster.service          ] [Shadrac] detected_master [Whiplash][5BCpdEhnQuuo2Rj2VEbkUQ][dave-OptiPlex-7010][inet[/10.187.17.209:9300]], added {[Whiplash][5BCpdEhnQuuo2Rj2VEbkUQ][dave-OptiPlex-7010][inet[/10.187.17.209:9300]],}, reason: zen-disco-receive(from master [[Whiplash][5BCpdEhnQuuo2Rj2VEbkUQ][dave-OptiPlex-7010][inet[/10.187.17.209:9300]]])
[2014-10-02 17:45:16,436][INFO ][http                     ] [Shadrac] bound_address {inet[/0:0:0:0:0:0:0:0:9200]}, publish_address {inet[/10.187.17.82:9200]}
[2014-10-02 17:45:16,437][INFO ][node                     ] [Shadrac] started

It seems that hdfs-snapshot has been loaded successfully.

And my elasticsearch version is 1.3.4

Maybe my usage was incorrect. I will appreciate any help or comment.

Thank you in advance.

@bhalsey
Copy link

bhalsey commented Oct 2, 2014

Did you restart your ES node? You also need to do this for each node.

@sbbird
Copy link
Author

sbbird commented Oct 3, 2014

@bhalsey Thanks to your reply.
Solved, I didn't notice there is another node running.

@sbbird sbbird closed this as completed Oct 3, 2014
costin added a commit that referenced this issue Oct 3, 2014
costin added a commit that referenced this issue Oct 3, 2014
Relates #290

(cherry picked from commit 77b587c)
@costin
Copy link
Member

costin commented Oct 3, 2014

Glad to see this sorted out. I've added instructions on restarting the node in the README to make this more visible.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

3 participants