-
Notifications
You must be signed in to change notification settings - Fork 14
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
Problem with the nodes of ElasticSeach #5
Comments
Hi @alvaro-lopezgarcia. Elasticsearch regularly changes its API. The version used by this project is an older one: |
Hello @arey, thanks for answering I am very grateful. Executing step: [indexMusicAlbum] 2019-07-22 16:56:23,825 [batchTaskExecutor-1] INFO com.javaetmoi.core.batch.listener.LogStepListener [75] - Step indexMusicAlbumPartition:partition0 - Read count: 201 - Write count: 0 - Commit count: 0 Thanks a lot again for your time! |
The exception cause show that the MusicBrainz database has introduced a new gender : |
Hi Arey,
My name is Alvaro and I am a 23 years old student from Madrid who has just finished a Telecommunications Engineering degree.
I am writing to you because now during the summer I am working in a project trying to develop MusicBrainz and Discogs databases in Elastic Search to learn about ES, where I am a beginner.
To index MusicBrainz I am following your tutorial, however now I had a problem that I did not know how to solve in several days. I hope that you can help me, I will be so grateful.
I followed the tutorial working with Docker and Compose, and the first part of this (the docker part) I think that worked fine.
The problem appears in the Quick Start part. After do "mvn install", the next command: mvn exec:java return the next error:
ERROR org.springframework.batch.core.step.AbstractStep [229] - Encountered an error executing step deleteIndexIfExists in job musicAlbumJob org.elasticsearch.client.transport.NoNodeAvailableException: None of the configured nodes are available: []
at org.elasticsearch.client.transport.TransportClientNodesService.ensureNodesAreAvailable(TransportClientNodesService.java:305) ~[elasticsearch-1.7.1.jar:na]
at org.elasticsearch.client.transport.TransportClientNodesService.execute(TransportClientNodesService.java:200) ~[elasticsearch-1.7.1.jar:na]
at org.elasticsearch.client.transport.support.InternalTransportIndicesAdminClient.execute(InternalTransportIndicesAdminClient.java:86) ~[elasticsearch-1.7.1.jar:na]
2019-07-18 17:18:43,551 [com.javaetmoi.elasticsearch.musicbrainz.batch.IndexBatchMain.main()] INFO org.springframework.batch.core.launch.support.SimpleJobLauncher [136] - Job: [FlowJob: [name=musicAlbumJob]] completed with the following parameters: [{}] and the following status: [FAILED]
2019-07-18 17:18:43,551 [com.javaetmoi.elasticsearch.musicbrainz.batch.IndexBatchMain.main()] INFO org.springframework.context.support.ClassPathXmlApplicationContext [984] - Closing org.springframework.context.support.ClassPathXmlApplicationContext@66d6172a: startup date [Thu Jul 18 17:18:11 CEST 2019]; root of context hierarchy
2019-07-18 17:18:43,564 [com.javaetmoi.elasticsearch.musicbrainz.batch.IndexBatchMain.main()] INFO org.springframework.scheduling.concurrent.ThreadPoolTaskExecutor [202] - Shutting down ExecutorService
2019-07-18 17:18:43,564 [com.javaetmoi.elasticsearch.musicbrainz.batch.IndexBatchMain.main()] INFO org.springframework.data.elasticsearch.client.TransportClientFactoryBean [59] - Closing elasticSearch client
I think that it should be a problem with Elasticsearch but I dont know what. I have another version of it more recent (maybe it cause trouble but I dont think so).
Do you know how can I fix that?
Thanks a lot for your time and for this project which is very cool.
I wait for your answer soon.
Alvaro.
The text was updated successfully, but these errors were encountered: