Nominatim import is hanging
See original GitHub issueHi! When i star import from nominatim db i get exeption like:
[main] ERROR de.komoot.photon.elasticsearch.Server - cannot install plugin: mobz /elasticsearch-head: java.io.IOException: plugin directory c:\gis\photon\photon_ data\elasticsearch\plugins\head already exists. To update the plugin, uninstall it first using --remove mobz/elasticsearch-head command [main] ERROR de.komoot.photon.elasticsearch.Server - cannot install plugin: poly fractal/elasticsearch-inquisitor: java.io.IOException: plugin directory c:\gis\p hoton\photon_data\elasticsearch\plugins\inquisitor already exists. To update the plugin, uninstall it first using --remove polyfractal/elasticsearch-inquisitor command [main] INFO org.elasticsearch.node - [Ringmaster] version[1.4.1], pid[4056], bui ld[89d3241/2014-11-26T15:49:29Z] [main] INFO org.elasticsearch.node - [Ringmaster] initializing … [main] INFO org.elasticsearch.plugins - [Ringmaster] loaded [lang-mvel, wordendi ng], sites [head, inquisitor] [main] INFO org.elasticsearch.script - [Ringmaster] compiling script file [c:\gi s\photon\photon_data\elasticsearch\config\scripts\general-score.mvel] [main] INFO org.elasticsearch.script - [Ringmaster] compiling script file [c:\gi s\photon\photon_data\elasticsearch\config\scripts\location-biased-score.mvel] [main] INFO org.elasticsearch.node - [Ringmaster] initialized [main] INFO org.elasticsearch.node - [Ringmaster] starting … [main] INFO org.elasticsearch.transport - [Ringmaster] bound_address {inet[/127. 0.0.1:9301]}, publish_address {inet[/127.0.0.1:9301]} [main] INFO org.elasticsearch.discovery - [Ringmaster] photon/QbPSEUuYQiyuDWm0aH R0tg [elasticsearch[Ringmaster][clusterService#updateTask][T#1]] INFO org.elasticsear ch.cluster.service - [Ringmaster] new_master [Ringmaster][QbPSEUuYQiyuDWm0aHR0tg ][WS-1882][inet[/127.0.0.1:9301]], reason: zen-disco-join (elected_as_master) [main] INFO org.elasticsearch.http - [Ringmaster] bound_address {inet[/127.0.0.1 :9201]}, publish_address {inet[/127.0.0.1:9201]} [main] INFO org.elasticsearch.node - [Ringmaster] started [main] INFO de.komoot.photon.elasticsearch.Server - started elastic search node [elasticsearch[Ringmaster][clusterService#updateTask][T#1]] INFO org.elasticsear ch.gateway - [Ringmaster] recovered [1] indices into cluster_state Exception in thread “main” org.elasticsearch.indices.IndexAlreadyExistsException : [photon] already exists at org.elasticsearch.cluster.metadata.MetaDataCreateIndexService.validat eIndexName(MetaDataCreateIndexService.java:167) at org.elasticsearch.cluster.metadata.MetaDataCreateIndexService.validat e(MetaDataCreateIndexService.java:559) at org.elasticsearch.cluster.metadata.MetaDataCreateIndexService.access$ 200(MetaDataCreateIndexService.java:87) at org.elasticsearch.cluster.metadata.MetaDataCreateIndexService$2.execu te(MetaDataCreateIndexService.java:243) at org.elasticsearch.cluster.service.InternalClusterService$UpdateTask.r un(InternalClusterService.java:329) at org.elasticsearch.common.util.concurrent.PrioritizedEsThreadPoolExecu tor$TieBreakingPrioritizedRunnable.run(PrioritizedEsThreadPoolExecutor.java:153)
at java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source)
at java.lang.Thread.run(Unknown Source)
Is that normal mode and i should have to wait or what,s going wrong with it?
Issue Analytics
- State:
- Created 8 years ago
- Comments:25 (9 by maintainers)
just delete the
photon_data
directory, that’s how you start from scratchsorry, our photon installation is part of a project we currently cannot spend much time on and I don’t want to risk anything going wrong and causing downtime. never touch a running system.
just close the ticket. I promise I will report any problems that might occur in future. 😉