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

elasticsearch issue-- failed to start shard #5315

Closed
ibagui opened this issue Mar 3, 2014 · 1 comment
Closed

elasticsearch issue-- failed to start shard #5315

ibagui opened this issue Mar 3, 2014 · 1 comment

Comments

@ibagui
Copy link

ibagui commented Mar 3, 2014

Hi,

I'm using elastic search 1.0 and logstash 1.3.3 with redis_version:2.4.10
When ever I'm trying to start logstash indexer it's giving me below error ..."failed to start shard" I deleted all the indices from elastic search before start.

[2014-03-03 17:04:33,178][WARN ][transport.netty ] [Mantra] Message not fully read (response) for [2114] handler future(org.elasticsearch.indices.recovery.RecoveryTarget$4@14487c8), error [true], resetting
[2014-03-03 17:04:33,183][WARN ][indices.cluster ] [Mantra] [logstash-2014.03.03][3] failed to start shard
org.elasticsearch.indices.recovery.RecoveryFailedException: [logstash-2014.03.03][3]: Recovery failed from [Brutacus][L0THepPDR6Cmx7O2jqVLdg][cloudclient1.aricent.com][inet[/10.203.251.143:9300]] into [Mantra][cKMntkkDT5Ws8g8_yeoTUg][cloudclient.aricent.com][inet[/10.203.251.142:9300]]
at org.elasticsearch.indices.recovery.RecoveryTarget.doRecovery(RecoveryTarget.java:303)
at org.elasticsearch.indices.recovery.RecoveryTarget.access$300(RecoveryTarget.java:65)
at org.elasticsearch.indices.recovery.RecoveryTarget$2.run(RecoveryTarget.java:171)
at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:895)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:918)

at java.lang.Thread.run(Thread.java:662)

Please help to resolve the issue.

Thanks,
Subhadip

@javanna
Copy link
Member

javanna commented Apr 4, 2014

Hi @ibagui I think you'd get proper answers if you send this type of questions to our mailing list. Anyways, looks like you are using the transport layer instead with a version of logstash that doesn't support 1.0 yet. I would switch to http output then. Can you followup on the mailing list if the problem persists please?

@javanna javanna closed this as completed Apr 4, 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

2 participants