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

River does not start after ES restart (IndexAlreadyExists Exception) #5

Closed
megastef opened this issue May 12, 2014 · 4 comments
Closed

Comments

@megastef
Copy link

When I restart ElasticSearch I get this message and no logs about fetching mails.

[2014-05-12 19:47:08,398][ERROR][de.saly.elasticsearch.river.imap.IMAPRiver] Unable to start IMAPRiver due to org.elasticsearch.indices.IndexAlreadyExistsException: [stefan2] already exists
org.elasticsearch.indices.IndexAlreadyExistsException: [stefan2] already exists
    at org.elasticsearch.cluster.metadata.MetaDataCreateIndexService.validateIndexName(MetaDataCreateIndexService.java:152)
    at org.elasticsearch.cluster.metadata.MetaDataCreateIndexService.validate(MetaDataCreateIndexService.java:465)
    at org.elasticsearch.cluster.metadata.MetaDataCreateIndexService.access$100(MetaDataCreateIndexService.java:85)
    at org.elasticsearch.cluster.metadata.MetaDataCreateIndexService$2.execute(MetaDataCreateIndexService.java:215)
    at org.elasticsearch.cluster.service.InternalClusterService$UpdateTask.run(InternalClusterService.java:308)
    at org.elasticsearch.common.util.concurrent.PrioritizedEsThreadPoolExecutor$TieBreakingPrioritizedRunnable.run(PrioritizedEsThreadPoolExecutor.java:134)
    at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145)
    at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)
    at java.lang.Thread.run(Thread.java:744)
@salyh salyh closed this as completed May 13, 2014
@salyh salyh reopened this May 13, 2014
@salyh
Copy link
Owner

salyh commented May 13, 2014

Ups, will have a look ...

@vanderstaaij
Copy link

Same issue here. Any idea as to when this will be fixed and in which version?

@salyh
Copy link
Owner

salyh commented Jun 20, 2014

should be fixed with 19ba058

@vanderstaaij
Copy link

Yes, fixed! Thanks.

@salyh salyh closed this as completed Jun 21, 2014
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants