failed to start shard

2015-03-08 Thread Sephen Xu
[2015-03-09 13:46:33,720][WARN ][indices.cluster  ] [es_node_4_2] 
[ossdatabse-2015-02-10][6] failed to start shard
org.elasticsearch.index.gateway.IndexShardGatewayRecoveryException: 
[ossdatabse-2015-02-10][6] failed to fetch index version after copying it 
over
at 
org.elasticsearch.index.gateway.local.LocalIndexShardGateway.recover(LocalIndexShardGateway.java:136)
at 
org.elasticsearch.index.gateway.IndexShardGatewayService$1.run(IndexShardGatewayService.java:197)
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)
Caused by: 
org.elasticsearch.index.gateway.IndexShardGatewayRecoveryException: 
[ossdatabse-2015-02-10][6] shard allocated for local recovery (post api), 
should exist, but doesn't, current files: [_checksums-1424994155456, 
segments.gen]
at 
org.elasticsearch.index.gateway.local.LocalIndexShardGateway.recover(LocalIndexShardGateway.java:115)
... 4 more
Caused by: java.io.FileNotFoundException: segments_r8
at 
org.elasticsearch.index.store.Store$StoreDirectory.openInput(Store.java:471)
at org.apache.lucene.index.SegmentInfos.read(SegmentInfos.java:324)
at org.apache.lucene.index.SegmentInfos$1.doBody(SegmentInfos.java:404)
at 
org.apache.lucene.index.SegmentInfos$FindSegmentsFile.run(SegmentInfos.java:843)
at 
org.apache.lucene.index.SegmentInfos$FindSegmentsFile.run(SegmentInfos.java:694)
at org.apache.lucene.index.SegmentInfos.read(SegmentInfos.java:400)
at org.elasticsearch.common.lucene.Lucene.readSegmentInfos(Lucene.java:117)
at 
org.elasticsearch.index.gateway.local.LocalIndexShardGateway.recover(LocalIndexShardGateway.java:106)
... 4 more
[2015-03-09 13:46:33,720][WARN ][cluster.action.shard ] [es_node_4_2] 
[ossdatabse-2015-02-11][6] sending failed shard for 
[ossdatabse-2015-02-11][6], node[cq_HPV1ZSlKArq6HgciNSg], [P], 
s[INITIALIZING], indexUUID [7yEPLOpYQciVdw_W1IF5Hg], reason [Failed to 
start shard, message 
[IndexShardGatewayRecoveryException[[ossdatabse-2015-02-11][6] failed to 
fetch index version after copying it over]; nested: 
IndexShardGatewayRecoveryException[[ossdatabse-2015-02-11][6] shard 
allocated for local recovery (post api), should exist, but doesn't, current 
files: [segments.gen, _checksums-1425594266760]]; nested: 
FileNotFoundException[segments_r7]; ]]

How to solve this problem?
thx

-- 
You received this message because you are subscribed to the Google Groups 
"elasticsearch" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to elasticsearch+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/elasticsearch/40deb4ef-d445-4ed6-a821-68a383354fff%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


Re: Failed to start shard

2014-10-27 Thread Mohamed Lrhazi
Sorry dont recall! but I find this in an email  sent on the same thread
 think:

> For me the change that seemed to have worked, I keep my fingers crossed,
is to add node.master=False to all nodes except one... black magic!

Other things we did involve: Adding more nodes and deleting indexes with
zero documents.

HTH,
Mohamed.


On Mon, Oct 27, 2014 at 8:12 AM, Anirudh Perugu  wrote:

> Hi Mohamed,
>
> Did you find a solution to this problem?
>
> On Wednesday, July 23, 2014 10:06:16 AM UTC+5:30, Mohamed Lrhazi wrote:
>>
>> I went ahead and upgraded to elasticsearch-1.2.2-1.noarch, but the same
>> errors continues after cluster start.
>>
>> I notice that the node inquestion is the master, and is supposed to be a
>> non data node. it should not be starting any shards, right?
>>
>> Thanks a lot,
>> Mohamed.
>>
>>
>> On Tue, Jul 22, 2014 at 11:55 PM, Mohamed Lrhazi 
>> wrote:
>>
>>>
>>>
>>> Hello,
>>>
>>> Our master is constantly logging this error, about twice per second
>>>
>>> I saw similar error mentioned in the release notes for a previous verion, 
>>> this cluster is running 1.0.1. Is it the same issue? What work arounds do 
>>> we have?
>>>
>>>
>>>
>>> [2014-07-22 23:50:28,533][WARN ][cluster.action.shard ] [rap-es2] 
>>> [de_2007][0] received shard failed for [de_2007][0], 
>>> node[EtDIFKT7Qi-nAuvG47tGYQ], [P], s[INITIALIZING], indexUUID 
>>> [yLrHy5k7RqO6rLnl_b4kww], reason [Failed to start shard, message 
>>> [IndexShardGatewayRecoveryException[[de_2007][0] failed to fetch index 
>>> version after copying it over]; nested: 
>>> IndexShardGatewayRecoveryException[[de_2007][0] shard allocated for local 
>>> recovery (post api), should exist, but doesn't, current files: []]; nested: 
>>> IndexNotFoundException[no segments* file found in 
>>> store(least_used[rate_limited(mmapfs(/data/elasticsearch/data/Odine2/nodes/0/indices/de_2007/0/index),
>>>  type=MERGE, rate=20.0)]): files: []]; ]]
>>>
>>>
>>>  --
>>> You received this message because you are subscribed to a topic in the
>>> Google Groups "elasticsearch" group.
>>> To unsubscribe from this topic, visit https://groups.google.com/d/
>>> topic/elasticsearch/OVc_0Kqm2yk/unsubscribe.
>>> To unsubscribe from this group and all its topics, send an email to
>>> elasticsearc...@googlegroups.com.
>>> To view this discussion on the web visit https://groups.google.com/d/
>>> msgid/elasticsearch/fd9dfaef-7179-4abf-bb60-b8a93982d76a%
>>> 40googlegroups.com
>>> <https://groups.google.com/d/msgid/elasticsearch/fd9dfaef-7179-4abf-bb60-b8a93982d76a%40googlegroups.com?utm_medium=email&utm_source=footer>
>>> .
>>> For more options, visit https://groups.google.com/d/optout.
>>>
>>
>>  --
> You received this message because you are subscribed to a topic in the
> Google Groups "elasticsearch" group.
> To unsubscribe from this topic, visit
> https://groups.google.com/d/topic/elasticsearch/OVc_0Kqm2yk/unsubscribe.
> To unsubscribe from this group and all its topics, send an email to
> elasticsearch+unsubscr...@googlegroups.com.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/elasticsearch/52f5a6c8-847c-4294-a2eb-308eb9aa3fe7%40googlegroups.com
> <https://groups.google.com/d/msgid/elasticsearch/52f5a6c8-847c-4294-a2eb-308eb9aa3fe7%40googlegroups.com?utm_medium=email&utm_source=footer>
> .
>
> For more options, visit https://groups.google.com/d/optout.
>

-- 
You received this message because you are subscribed to the Google Groups 
"elasticsearch" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to elasticsearch+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/elasticsearch/CAEU_gmdtPD8Cxg%2BJmqJhtZRgMv%3DQ8SNo7qds1GT%2BOdegkGKQ-w%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.


Re: Failed to start shard

2014-10-27 Thread Anirudh Perugu
Hi Mohamed,

Did you find a solution to this problem?

On Wednesday, July 23, 2014 10:06:16 AM UTC+5:30, Mohamed Lrhazi wrote:
>
> I went ahead and upgraded to elasticsearch-1.2.2-1.noarch, but the same 
> errors continues after cluster start.
>
> I notice that the node inquestion is the master, and is supposed to be a 
> non data node. it should not be starting any shards, right?
>
> Thanks a lot,
> Mohamed.
>
>
> On Tue, Jul 22, 2014 at 11:55 PM, Mohamed Lrhazi  > wrote:
>
>>
>>
>> Hello,
>>
>> Our master is constantly logging this error, about twice per second
>>
>> I saw similar error mentioned in the release notes for a previous verion, 
>> this cluster is running 1.0.1. Is it the same issue? What work arounds do we 
>> have?
>>
>>
>>
>> [2014-07-22 23:50:28,533][WARN ][cluster.action.shard ] [rap-es2] 
>> [de_2007][0] received shard failed for [de_2007][0], 
>> node[EtDIFKT7Qi-nAuvG47tGYQ], [P], s[INITIALIZING], indexUUID 
>> [yLrHy5k7RqO6rLnl_b4kww], reason [Failed to start shard, message 
>> [IndexShardGatewayRecoveryException[[de_2007][0] failed to fetch index 
>> version after copying it over]; nested: 
>> IndexShardGatewayRecoveryException[[de_2007][0] shard allocated for local 
>> recovery (post api), should exist, but doesn't, current files: []]; nested: 
>> IndexNotFoundException[no segments* file found in 
>> store(least_used[rate_limited(mmapfs(/data/elasticsearch/data/Odine2/nodes/0/indices/de_2007/0/index),
>>  type=MERGE, rate=20.0)]): files: []]; ]]
>>
>>
>>  -- 
>> You received this message because you are subscribed to a topic in the 
>> Google Groups "elasticsearch" group.
>> To unsubscribe from this topic, visit 
>> https://groups.google.com/d/topic/elasticsearch/OVc_0Kqm2yk/unsubscribe.
>> To unsubscribe from this group and all its topics, send an email to 
>> elasticsearc...@googlegroups.com .
>> To view this discussion on the web visit 
>> https://groups.google.com/d/msgid/elasticsearch/fd9dfaef-7179-4abf-bb60-b8a93982d76a%40googlegroups.com
>>  
>> <https://groups.google.com/d/msgid/elasticsearch/fd9dfaef-7179-4abf-bb60-b8a93982d76a%40googlegroups.com?utm_medium=email&utm_source=footer>
>> .
>> For more options, visit https://groups.google.com/d/optout.
>>
>
>

-- 
You received this message because you are subscribed to the Google Groups 
"elasticsearch" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to elasticsearch+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/elasticsearch/52f5a6c8-847c-4294-a2eb-308eb9aa3fe7%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


Re: Failed to start shard

2014-07-22 Thread Mohamed Lrhazi
I went ahead and upgraded to elasticsearch-1.2.2-1.noarch, but the same
errors continues after cluster start.

I notice that the node inquestion is the master, and is supposed to be a
non data node. it should not be starting any shards, right?

Thanks a lot,
Mohamed.


On Tue, Jul 22, 2014 at 11:55 PM, Mohamed Lrhazi 
wrote:

>
> Hello,
>
> Our master is constantly logging this error, about twice per second
>
> I saw similar error mentioned in the release notes for a previous verion, 
> this cluster is running 1.0.1. Is it the same issue? What work arounds do we 
> have?
>
>
> [2014-07-22 23:50:28,533][WARN ][cluster.action.shard ] [rap-es2] 
> [de_2007][0] received shard failed for [de_2007][0], 
> node[EtDIFKT7Qi-nAuvG47tGYQ], [P], s[INITIALIZING], indexUUID 
> [yLrHy5k7RqO6rLnl_b4kww], reason [Failed to start shard, message 
> [IndexShardGatewayRecoveryException[[de_2007][0] failed to fetch index 
> version after copying it over]; nested: 
> IndexShardGatewayRecoveryException[[de_2007][0] shard allocated for local 
> recovery (post api), should exist, but doesn't, current files: []]; nested: 
> IndexNotFoundException[no segments* file found in 
> store(least_used[rate_limited(mmapfs(/data/elasticsearch/data/Odine2/nodes/0/indices/de_2007/0/index),
>  type=MERGE, rate=20.0)]): files: []]; ]]
>
>  --
> You received this message because you are subscribed to a topic in the
> Google Groups "elasticsearch" group.
> To unsubscribe from this topic, visit
> https://groups.google.com/d/topic/elasticsearch/OVc_0Kqm2yk/unsubscribe.
> To unsubscribe from this group and all its topics, send an email to
> elasticsearch+unsubscr...@googlegroups.com.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/elasticsearch/fd9dfaef-7179-4abf-bb60-b8a93982d76a%40googlegroups.com
> <https://groups.google.com/d/msgid/elasticsearch/fd9dfaef-7179-4abf-bb60-b8a93982d76a%40googlegroups.com?utm_medium=email&utm_source=footer>
> .
> For more options, visit https://groups.google.com/d/optout.
>

-- 
You received this message because you are subscribed to the Google Groups 
"elasticsearch" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to elasticsearch+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/elasticsearch/CAEU_gmfNi6nowVSM1FMxWn6XKZkk_szcy1%3DCVZ%3Dz%2BZWoZC%3D8HA%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.


Failed to start shard

2014-07-22 Thread Mohamed Lrhazi


Hello,

Our master is constantly logging this error, about twice per second

I saw similar error mentioned in the release notes for a previous verion, this 
cluster is running 1.0.1. Is it the same issue? What work arounds do we have?


[2014-07-22 23:50:28,533][WARN ][cluster.action.shard ] [rap-es2] [de_2007][0] 
received shard failed for [de_2007][0], node[EtDIFKT7Qi-nAuvG47tGYQ], [P], 
s[INITIALIZING], indexUUID [yLrHy5k7RqO6rLnl_b4kww], reason [Failed to start 
shard, message [IndexShardGatewayRecoveryException[[de_2007][0] failed to fetch 
index version after copying it over]; nested: 
IndexShardGatewayRecoveryException[[de_2007][0] shard allocated for local 
recovery (post api), should exist, but doesn't, current files: []]; nested: 
IndexNotFoundException[no segments* file found in 
store(least_used[rate_limited(mmapfs(/data/elasticsearch/data/Odine2/nodes/0/indices/de_2007/0/index),
 type=MERGE, rate=20.0)]): files: []]; ]]

-- 
You received this message because you are subscribed to the Google Groups 
"elasticsearch" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to elasticsearch+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/elasticsearch/fd9dfaef-7179-4abf-bb60-b8a93982d76a%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


Re: elasticsearch is giving error as "failed to start shard"

2014-03-03 Thread Subhadip Bagui


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

On Saturday, March 1, 2014 2:58:35 PM UTC+5:30, Subhadip Bagui wrote:
>
> Hi ,
>
> I'm trying to move elastic search on a new system, but while trying to 
> start the service its giving below exception. Althrough the process is 
> running. There was old elasticsearch 0.90 copied which is not running now 
> as I checked. Please suggest.
>
> [2014-02-28 16:40:13,588][WARN ][transport.netty  ] [DJ] Message 
> not fully read (response) for [4] handler 
> future(org.elasticsearch.indices.recovery.RecoveryTarget$4@1b4268b), error 
> [true], resetting
> [2014-02-28 16:40:13,589][WARN ][transport.netty  ] [DJ] Message 
> not fully read (response) for [3] handler 
> future(org.elasticsearch.indices.recovery.RecoveryTarget$4@151d6cb), error 
> [true], resetting
> [2014-02-28 16:40:13,590][WARN ][indices.cluster  ] [DJ] 
> [logstash-2014.02.27][1] failed to start shard
> org.elasticsearch.indices.recovery.RecoveryFailedException: 
> [logstash-2014.02.27][1]: Recovery failed from 
> [Brutacus][L0THepPDR6Cmx7O2jqVLdg][cloudclient1.aricent.com][inet[/
> 10.203.251.143:9300]] into [DJ][LajLfvlYSAGZdsyFnorwEA][
> 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)
>
> Thanks,
> Subahdip
>

-- 
You received this message because you are subscribed to the Google Groups 
"elasticsearch" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to elasticsearch+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/elasticsearch/d66ab1d6-8cb2-4019-9cc3-2054328d8864%40googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.


Re: elasticsearch is giving error as "failed to start shard"

2014-03-03 Thread Subhadip Bagui
Hi,

When I deleted all in index using rest then elasticsearch is getting up 
fine. Any help to identify the issue. 

Thanks

On Saturday, March 1, 2014 2:58:35 PM UTC+5:30, Subhadip Bagui wrote:
>
> Hi ,
>
> I'm trying to move elastic search on a new system, but while trying to 
> start the service its giving below exception. Althrough the process is 
> running. There was old elasticsearch 0.90 copied which is not running now 
> as I checked. Please suggest.
>
> [2014-02-28 16:40:13,588][WARN ][transport.netty  ] [DJ] Message 
> not fully read (response) for [4] handler 
> future(org.elasticsearch.indices.recovery.RecoveryTarget$4@1b4268b), error 
> [true], resetting
> [2014-02-28 16:40:13,589][WARN ][transport.netty  ] [DJ] Message 
> not fully read (response) for [3] handler 
> future(org.elasticsearch.indices.recovery.RecoveryTarget$4@151d6cb), error 
> [true], resetting
> [2014-02-28 16:40:13,590][WARN ][indices.cluster  ] [DJ] 
> [logstash-2014.02.27][1] failed to start shard
> org.elasticsearch.indices.recovery.RecoveryFailedException: 
> [logstash-2014.02.27][1]: Recovery failed from 
> [Brutacus][L0THepPDR6Cmx7O2jqVLdg][cloudclient1.aricent.com][inet[/
> 10.203.251.143:9300]] into [DJ][LajLfvlYSAGZdsyFnorwEA][
> 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)
>
> Thanks,
> Subahdip
>

-- 
You received this message because you are subscribed to the Google Groups 
"elasticsearch" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to elasticsearch+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/elasticsearch/9ef1288f-c9bc-4671-8de4-71938e7429f4%40googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.


Re: elasticsearch is giving error as "failed to start shard"

2014-03-02 Thread Subhadip Bagui
Hi, 

Please suggest how to resolve the issue. 

Thanks, 
Subhadip

On Saturday, March 1, 2014 2:58:35 PM UTC+5:30, Subhadip Bagui wrote:
>
> Hi ,
>
> I'm trying to move elastic search on a new system, but while trying to 
> start the service its giving below exception. Althrough the process is 
> running. There was old elasticsearch 0.90 copied which is not running now 
> as I checked. Please suggest.
>
> [2014-02-28 16:40:13,588][WARN ][transport.netty  ] [DJ] Message 
> not fully read (response) for [4] handler 
> future(org.elasticsearch.indices.recovery.RecoveryTarget$4@1b4268b), error 
> [true], resetting
> [2014-02-28 16:40:13,589][WARN ][transport.netty  ] [DJ] Message 
> not fully read (response) for [3] handler 
> future(org.elasticsearch.indices.recovery.RecoveryTarget$4@151d6cb), error 
> [true], resetting
> [2014-02-28 16:40:13,590][WARN ][indices.cluster  ] [DJ] 
> [logstash-2014.02.27][1] failed to start shard
> org.elasticsearch.indices.recovery.RecoveryFailedException: 
> [logstash-2014.02.27][1]: Recovery failed from 
> [Brutacus][L0THepPDR6Cmx7O2jqVLdg][cloudclient1.aricent.com][inet[/
> 10.203.251.143:9300]] into [DJ][LajLfvlYSAGZdsyFnorwEA][
> 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)
>
> Thanks,
> Subahdip
>

-- 
You received this message because you are subscribed to the Google Groups 
"elasticsearch" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to elasticsearch+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/elasticsearch/7a6843bd-1aa0-4a9b-8a48-c4b5a6a65907%40googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.


Re: elasticsearch is giving error as "failed to start shard"

2014-03-02 Thread Subhadip Bagui
Hi,

Please help to fix the issue.


On Saturday, March 1, 2014 2:58:35 PM UTC+5:30, Subhadip Bagui wrote:
>
> Hi ,
>
> I'm trying to move elastic search on a new system, but while trying to 
> start the service its giving below exception. Althrough the process is 
> running. There was old elasticsearch 0.90 copied which is not running now 
> as I checked. Please suggest.
>
> [2014-02-28 16:40:13,588][WARN ][transport.netty  ] [DJ] Message 
> not fully read (response) for [4] handler 
> future(org.elasticsearch.indices.recovery.RecoveryTarget$4@1b4268b), error 
> [true], resetting
> [2014-02-28 16:40:13,589][WARN ][transport.netty  ] [DJ] Message 
> not fully read (response) for [3] handler 
> future(org.elasticsearch.indices.recovery.RecoveryTarget$4@151d6cb), error 
> [true], resetting
> [2014-02-28 16:40:13,590][WARN ][indices.cluster  ] [DJ] 
> [logstash-2014.02.27][1] failed to start shard
> org.elasticsearch.indices.recovery.RecoveryFailedException: 
> [logstash-2014.02.27][1]: Recovery failed from 
> [Brutacus][L0THepPDR6Cmx7O2jqVLdg][cloudclient1.aricent.com][inet[/
> 10.203.251.143:9300]] into [DJ][LajLfvlYSAGZdsyFnorwEA][
> 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)
>
> Thanks,
> Subahdip
>

-- 
You received this message because you are subscribed to the Google Groups 
"elasticsearch" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to elasticsearch+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/elasticsearch/e3936205-8ba2-4bd9-a76c-c5f18142e1c6%40googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.


elasticsearch is giving error as "failed to start shard"

2014-03-01 Thread Subhadip Bagui
Hi ,

I'm trying to move elastic search on a new system, but while trying to 
start the service its giving below exception. Althrough the process is 
running. There was old elasticsearch 0.90 copied which is not running now 
as I checked. Please suggest.

[2014-02-28 16:40:13,588][WARN ][transport.netty  ] [DJ] Message 
not fully read (response) for [4] handler 
future(org.elasticsearch.indices.recovery.RecoveryTarget$4@1b4268b), error 
[true], resetting
[2014-02-28 16:40:13,589][WARN ][transport.netty  ] [DJ] Message 
not fully read (response) for [3] handler 
future(org.elasticsearch.indices.recovery.RecoveryTarget$4@151d6cb), error 
[true], resetting
[2014-02-28 16:40:13,590][WARN ][indices.cluster  ] [DJ] 
[logstash-2014.02.27][1] failed to start shard
org.elasticsearch.indices.recovery.RecoveryFailedException: 
[logstash-2014.02.27][1]: Recovery failed from 
[Brutacus][L0THepPDR6Cmx7O2jqVLdg][cloudclient1.aricent.com][inet[/10.203.251.143:9300]]
 
into 
[DJ][LajLfvlYSAGZdsyFnorwEA][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)

Thanks,
Subahdip

-- 
You received this message because you are subscribed to the Google Groups 
"elasticsearch" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to elasticsearch+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/elasticsearch/1ee34fd2-27f2-45bb-82d0-f11cdf07aaf2%40googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.