Re: get rid of _all to optimize storage and perfs (Re: Splunk vs. Elastic search performance?)

[Patrick Proniewski]

Brian,

Thank you for the reply, even if it does not answer my question. 

By the way, how am I supposed to change a mapping setting? Do I have to push 
back the entire mapping with one line modified, or can I just push something 
like: 

{
  "logstash": {
 "mappings": {
"_default_": {
   "_all": {
  "enabled": false
   }
}
 }
  }
}



On 20 juin 2014, at 23:04, Brian wrote:

> Patrick,
> 
> Here's my template, along with where the _all field is disabled. You may wish 
> to add this setting to your own template, and then also add the index setting 
> to ignore malformed data (if someone's log entry occasionally slips in "null" 
> or "no-data" instead of the usual numeric value):
> 
> {
>   "automap" : {
> "template" : "logstash-*",
> "settings" : {
>   "index.mapping.ignore_malformed" : true
> },
> "mappings" : {
>   "_default_" : {
> "numeric_detection" : true,
> "_all" : { "enabled" : false },
> "properties" : {
>   "message" : { "type" : "string" },
>   "host" : { "type" : "string" },
>   "UUID" : {  "type" : "string", "index" : "not_analyzed" },
>   "logdate" : {  "type" : "string", "index" : "no" }
> }
>   }
> }
>   }
> }
> 
> Brian

-- 
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/8D497ED9-54DF-48EA-AA91-44A621B72287%40patpro.net.
For more options, visit https://groups.google.com/d/optout.

Re: Could not lock IndexWriter isLocked [false]

[Fatih Karatana]

Hi Alex,

Thanks for your reply. ES instance running on a Linux machine and I have 
only one instance 1 shard 1 replica too.
I think it is solved now by adding this line.
index.store.fs.lock: none

After I have added that parameter this problem no more occur.


On Monday, June 16, 2014 2:42:18 PM UTC+3, Alexander Reelsen wrote:
>
> Hey,
>
> what elasticsearch version are you using? Judging from the directory I 
> dont think you are using NFS, right? Are you running multiple instances 
> locally?
> Have you shutdown elasticsearch properly so that no other instance is 
> lingering around (you can use jps or or to check)
>
>
> --Alex
>
>
> On Mon, Jun 2, 2014 at 1:16 PM, Fatih Karatana  > wrote:
>
>> I try to create an index in a couple of seconds and i got this:
>> [2014-06-02 14:10:14,414][WARN ][index.engine.internal] [shardicaprio
>> ] [myindex][0] Could not lock IndexWriter isLocked [false]
>>
>>
>> And here is full stack trace:
>>
>> org.apache.lucene.store.LockObtainFailedException: Lock obtain timed out: 
>> NativeFSLock@/var/lib/elasticsearch/data/shardicaprio/nodes/0/indices/
>> myindex/0/index/write.lock
>> at org.apache.lucene.store.Lock.obtain(Lock.java:84)
>> at org.apache.lucene.index.IndexWriter.(IndexWriter.java:
>> 702)
>> at org.elasticsearch.index.engine.internal.InternalEngine.
>> createWriter(InternalEngine.java:1388)
>> at org.elasticsearch.index.engine.internal.InternalEngine.start(
>> InternalEngine.java:256)
>> at org.elasticsearch.index.shard.service.InternalIndexShard.
>> postRecovery(InternalIndexShard.java:684)
>> at org.elasticsearch.index.gateway.local.LocalIndexShardGateway.
>> recover(LocalIndexShardGateway.java:158)
>> at org.elasticsearch.index.gateway.IndexShardGatewayService$1.run
>> (IndexShardGatewayService.java:189)
>> 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:745)
>> [2014-06-02 14:10:14,533][WARN ][indices.cluster  ] [shardicaprio
>> ] [myindex][0] failed to start shard
>> org.elasticsearch.index.gateway.IndexShardGatewayRecoveryException: [
>> myindex][0] failed recovery
>> at org.elasticsearch.index.gateway.IndexShardGatewayService$1.run
>> (IndexShardGatewayService.java:248)
>> 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:745)
>> Caused by: org.elasticsearch.index.engine.EngineCreationFailureException: 
>> [myindex][0] failed to create engine
>> at org.elasticsearch.index.engine.internal.InternalEngine.start(
>> InternalEngine.java:258)
>> at org.elasticsearch.index.shard.service.InternalIndexShard.
>> postRecovery(InternalIndexShard.java:684)
>> at org.elasticsearch.index.gateway.local.LocalIndexShardGateway.
>> recover(LocalIndexShardGateway.java:158)
>> at org.elasticsearch.index.gateway.IndexShardGatewayService$1.run
>> (IndexShardGatewayService.java:189)
>> ... 3 more
>> Caused by: org.apache.lucene.store.LockObtainFailedException: Lock 
>> obtain timed out: NativeFSLock@/var/lib/elasticsearch/data/shardicaprio/
>> nodes/0/indices/myindex/0/index/write.lock
>> at org.apache.lucene.store.Lock.obtain(Lock.java:84)
>> at org.apache.lucene.index.IndexWriter.(IndexWriter.java:
>> 702)
>> at org.elasticsearch.index.engine.internal.InternalEngine.
>> createWriter(InternalEngine.java:1388)
>> at org.elasticsearch.index.engine.internal.InternalEngine.start(
>> InternalEngine.java:256)
>> ... 6 more
>> [2014-06-02 14:10:14,536][WARN ][cluster.action.shard ] [shardicaprio
>> ] [myindex][0] sending failed shard for [myindex][0], node[
>> kHOedr2wQpa3DSZj81ep_A], [P], s[INITIALIZING], indexUUID [29Uf2hH4S2-
>> FJf1LnNrM0A], reason [Failed to start shard, message [
>> IndexShardGatewayRecoveryException[[myindex][0] failed recovery]; nested: 
>> EngineCreationFailureException[[myindex][0] failed to create engine]; 
>> nested: LockObtainFailedException[Lock obtain timed out: NativeFSLock@/
>> var/lib/elasticsearch/data/shardicaprio/nodes/0/indices/myindex/0/index/
>> write.lock]; ]]
>> [2014-06-02 14:10:14,536][WARN ][cluster.action.shard ] [shardicaprio
>> ] [myindex][0] received shard failed for [myindex][0], node[
>> kHOedr2wQpa3DSZj81ep_A], [P], s[INITIALIZING], indexUUID [29Uf2hH4S2-
>> FJf1LnNrM0A], reason [Failed to start shard, message [
>> IndexShardGatewayRecoveryException[[myindex][0] failed recovery]; nested: 
>> EngineCreationFailureException[[myindex][0] failed to create engine]; 
>> nested: LockObtainFailedException[Lock obtain timed out: NativeFSLock@/
>> var/lib/elasticsearch/data/shardicaprio/nodes/0/indices/my

Re: Failed to merge - There is not enough space on the disk

[Jorge Luis Betancourt Gonzalez]

This usually means that the merge operation failed correct? With ES we must 
apply kind of the same rule as Solr for merge? 2x or 3x (worst case scenario 
ever) index size as available space to avoid this?

Greetings

On Jun 29, 2014, at 6:37 AM, Ophir Michaeli  wrote:

> Hi, 
> 
> I get an error - 
> failed to merge java.io.IOException: There is not enough space on the disk.
> The disk was full, cleaned it now.
> What is the best way not to loose what I already indexed? Or does this error 
> mean that the index is lost and I need to delete and index again?
> 
> Thanks,
> Ophir
> 
> -- 
> 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/0b1ae217-aeb4-465f-9468-d2b617a47679%40googlegroups.com.
> For more options, visit https://groups.google.com/d/optout.


VII Escuela Internacional de Verano en la UCI del 30 de junio al 11 de julio de 
2014. Ver www.uci.cu

-- 
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/F6A4AAED-BB16-4B7A-95DA-06EDD3ADDBF7%40uci.cu.
For more options, visit https://groups.google.com/d/optout.

Re: recent spam

[Mark Walkom]

Good idea, I'll ask Leslie@ES.

Regards,
Mark Walkom

Infrastructure Engineer
Campaign Monitor
email: ma...@campaignmonitor.com
web: www.campaignmonitor.com


On 30 June 2014 06:14, Warner Onstine  wrote:

> Hi all, is there any way to set up the group to be first-post flagged so
> that we all aren't getting so much spam? Seems like whatever is doing it is
> just creating and subscribing new accounts and spamming the list
> incessantly. I know it means more work for the moderators, but if you make
> more people moderators less spam would get through. This is one of the few
> groups I'm on that I regularly get spammed like this.
>
> -warner
>
> --
> 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/CAJNTuMDjNQxQdfgAhVnMhCHabdps13w7wUhcuyT2V%3DjthpUKMg%40mail.gmail.com
> 
> .
> 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/CAEM624Z%3DwpzAV_uZV4MXJC3iZK%3DmYZ8%3DhTfaWpOpf-KyBk1S1w%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

recent spam

[Warner Onstine]

Hi all, is there any way to set up the group to be first-post flagged so
that we all aren't getting so much spam? Seems like whatever is doing it is
just creating and subscribing new accounts and spamming the list
incessantly. I know it means more work for the moderators, but if you make
more people moderators less spam would get through. This is one of the few
groups I'm on that I regularly get spammed like this.

-warner

-- 
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/CAJNTuMDjNQxQdfgAhVnMhCHabdps13w7wUhcuyT2V%3DjthpUKMg%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: Completion suggester with jdbc river

[joergpra...@gmail.com]

You have two options:

- create all indices/mappings you need before instantiating a JDBC river
instance. This is the preferred option.

- or you can include a single index settings/mappings JSON into the JDBC
river instantiation command

Jörg


On Sun, Jun 29, 2014 at 7:43 PM, leningrast 
wrote:

> Hi,
>
> I plan to use ES with jprantes JDBC-River
> , a completion
> suggester
> 
> and a Postgresql Database in my next project.
>
> I tested the combination of ES, the JDBC-River and Postgres, it worked
> well for me. My problem is that i have no clue how i could built an index
> like the example index
>  on the ES completion
> suggester website (blog):
>
> curl -X PUT localhost:9200/hotels/hotel/1 -d '
> {
>   "name" : "Mercure Hotel Munich",
>   "city" : "Munich",
>   "name_suggest" : {
> "input" :  [
>   "Mercure Hotel Munich",
>   "Mercure Munich"
> ]
>   }
> }'
>
> Complete suggesters are build on top of a search graph. Each user input
> reduces the pathes on the graph. But only exact matches will remain. If
> multiple queries should leed to one result, the ES website suggests to
> provide multiple "input" fields like above. I will have thousands of
> documents and can not craft my index manually like it seems on the site.
>
> My question is now: *How can i automatically build an ES index with a
> JDBC-River?*
>
> I hope you can give me some input. Thanks in advance!
>
>
>  --
> 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/8d30f5cd-2b28-42d2-9af0-6fc7af872520%40googlegroups.com
> 
> .
> 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/CAKdsXoHNwJ7ZrvJpY%3DArByfRTmaeDVaVMT0O-%3DZEO1S026fhXQ%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Completion suggester with jdbc river

[leningrast]

Hi,

I plan to use ES with jprantes JDBC-River 
, a completion 
suggester 

 
and a Postgresql Database in my next project.

I tested the combination of ES, the JDBC-River and Postgres, it worked well 
for me. My problem is that i have no clue how i could built an index like 
the example index  on 
the ES completion suggester website (blog):

curl -X PUT localhost:9200/hotels/hotel/1 -d '
{
  "name" : "Mercure Hotel Munich",
  "city" : "Munich",
  "name_suggest" : {
"input" :  [
  "Mercure Hotel Munich",
  "Mercure Munich"
]
  }
}'

Complete suggesters are build on top of a search graph. Each user input 
reduces the pathes on the graph. But only exact matches will remain. If 
multiple queries should leed to one result, the ES website suggests to 
provide multiple "input" fields like above. I will have thousands of 
documents and can not craft my index manually like it seems on the site.

My question is now: *How can i automatically build an ES index with a 
JDBC-River?*

I hope you can give me some input. Thanks in advance!


-- 
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/8d30f5cd-2b28-42d2-9af0-6fc7af872520%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: What does "open_source" token means?

[Ivan Brusic]

"open_source" is just an example value in the tags array.

The example has two documents, both with just a single field called tags.
The first one has one value "search" and the second one has two values
(both in the same field, therefore it is an array) "search" and
"open_source"

Document 1
{ "tags" : ["search"] }

Document 2
{ "tags" : ["search", "open_source"] }

Multiple values in the same field can be thought of as an array, but Lucene
underneath considers them to be two terms in the inverted index, both
pointing at the same document.

Cheers,

Ivan


On Sun, Jun 29, 2014 at 10:17 AM, rayman  wrote:

> Hi,
> I am reading ES documentation.
>
> Trying to understand the finding_multiple_exact_values at:
> http://www.elasticsearch.org/guide/en/elasticsearch/guide/current/_finding_multiple_exact_values.html
>
>
> I didnt understand what "open_source" stands for at:
>
> { "tags" : ["search"] }
>
> { "tags" : ["search", "open_source"] }
> 
>
>
>
>  I understand that's a token type or?? maybe I am missing something basic
> for my understanding. Anyone could fill that gap for me?
>
> Thanks,
> ray.
>
> --
> 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/69b09c6b-7e97-4e6e-a726-4519bf2f4d98%40googlegroups.com
> 
> .
> 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/CALY%3DcQBBxSGrHF_5Jdk0dPt77QdhjztPjg-LJmUzajVySUu1fQ%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

What does "open_source" token means?

[rayman]

Hi,
I am reading ES documentation. 

Trying to understand the finding_multiple_exact_values 
at: 
http://www.elasticsearch.org/guide/en/elasticsearch/guide/current/_finding_multiple_exact_values.html


I didnt understand what "open_source" stands for at:

{ "tags" : ["search"] }

{ "tags" : ["search", "open_source"] } 




 I understand that's a token type or?? maybe I am missing something basic 
for my understanding. Anyone could fill that gap for me?

Thanks,
ray.

-- 
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/69b09c6b-7e97-4e6e-a726-4519bf2f4d98%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

How to see all document types for a give index?

[Jinyuan Zhou]

Thanks,

-- 
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/2097260f-9157-4de3-aedf-5713027d88ef%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: Failed to merge - There is not enough space on the disk

[Ophir Michaeli]

It looks like it takes some time for the node to get back to normal, it 
works now. thanks

On Sunday, June 29, 2014 5:27:21 PM UTC+3, Itamar Syn-Hershko wrote:
>
> If it was corrupted you would have seen other errors, not 503. Check your 
> network settings.
>
> --
>
> Itamar Syn-Hershko
> http://code972.com | @synhershko 
> Freelance Developer & Consultant
> Author of RavenDB in Action 
>
>
> On Sun, Jun 29, 2014 at 5:25 PM, Ophir Michaeli  > wrote:
>
>> Hi,
>>
>> I restarted elasticesaerch node and the ES console screen shows no error, 
>> but I can't connect to the node (with REST I get "503 Service Unavailable
>> ").
>> Is the index corrupt? 
>>
>> Thanks!
>>
>>
>> On Sunday, June 29, 2014 2:51:56 PM UTC+3, Itamar Syn-Hershko wrote:
>>
>>> This error means indexing has stopped at one point, up to that point 
>>> everything is preserved.
>>>
>>> See http://www.elasticsearch.org/guide/en/elasticsearch/
>>> reference/current/index-modules-allocation.html#disk for how to avoid 
>>> this from now on
>>>
>>> --
>>>
>>> Itamar Syn-Hershko
>>> http://code972.com | @synhershko 
>>> Freelance Developer & Consultant
>>> Author of RavenDB in Action 
>>>
>>>
>>> On Sun, Jun 29, 2014 at 1:37 PM, Ophir Michaeli  
>>> wrote:
>>>
  Hi, 

 I get an error - 
 failed to merge java.io.IOException: There is not enough space on the 
 disk.
 The disk was full, cleaned it now.
 What is the best way not to loose what I already indexed? Or does this 
 error mean that the index is lost and I need to delete and index again?

 Thanks,
 Ophir

 -- 
 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 elasticsearc...@googlegroups.com.

 To view this discussion on the web visit https://groups.google.com/d/
 msgid/elasticsearch/0b1ae217-aeb4-465f-9468-d2b617a47679%
 40googlegroups.com 
 
 .
 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 elasticsearc...@googlegroups.com .
>> To view this discussion on the web visit 
>> https://groups.google.com/d/msgid/elasticsearch/63357c69-0c1e-45f8-8b0f-962dc805bc50%40googlegroups.com
>>  
>> 
>> .
>>
>> 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/950049b0-f2f2-4648-b09a-002db1b5ab77%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

scripted partial delete

[eunever32]

Actually it is possible!
It's a mvel thing

In mvel it's possible to
_source.doc.list.remove (elem)

The options in elasticsearch documentation do not go very deep. 

Maybe another discussion group for mvel scripting questions ?

-- 
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/5110d3c4-f5e4-40a5-9eda-b5235229b2b1%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: Failed to merge - There is not enough space on the disk

[Itamar Syn-Hershko]

If it was corrupted you would have seen other errors, not 503. Check your
network settings.

--

Itamar Syn-Hershko
http://code972.com | @synhershko 
Freelance Developer & Consultant
Author of RavenDB in Action 


On Sun, Jun 29, 2014 at 5:25 PM, Ophir Michaeli 
wrote:

> Hi,
>
> I restarted elasticesaerch node and the ES console screen shows no error,
> but I can't connect to the node (with REST I get "503 Service Unavailable
> ").
> Is the index corrupt?
>
> Thanks!
>
>
> On Sunday, June 29, 2014 2:51:56 PM UTC+3, Itamar Syn-Hershko wrote:
>
>> This error means indexing has stopped at one point, up to that point
>> everything is preserved.
>>
>> See http://www.elasticsearch.org/guide/en/elasticsearch/
>> reference/current/index-modules-allocation.html#disk for how to avoid
>> this from now on
>>
>> --
>>
>> Itamar Syn-Hershko
>> http://code972.com | @synhershko 
>> Freelance Developer & Consultant
>> Author of RavenDB in Action 
>>
>>
>> On Sun, Jun 29, 2014 at 1:37 PM, Ophir Michaeli 
>> wrote:
>>
>>> Hi,
>>>
>>> I get an error -
>>> failed to merge java.io.IOException: There is not enough space on the
>>> disk.
>>> The disk was full, cleaned it now.
>>> What is the best way not to loose what I already indexed? Or does this
>>> error mean that the index is lost and I need to delete and index again?
>>>
>>> Thanks,
>>> Ophir
>>>
>>> --
>>> 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 elasticsearc...@googlegroups.com.
>>>
>>> To view this discussion on the web visit https://groups.google.com/d/
>>> msgid/elasticsearch/0b1ae217-aeb4-465f-9468-d2b617a47679%
>>> 40googlegroups.com
>>> 
>>> .
>>> 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/63357c69-0c1e-45f8-8b0f-962dc805bc50%40googlegroups.com
> 
> .
>
> 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/CAHTr4ZtXsZPp6khHVhBmvKFNEqH8PMLmnRGGZR0A3Acg_3Z4vg%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: Failed to merge - There is not enough space on the disk

[Ophir Michaeli]

Hi,

I restarted elasticesaerch node and the ES console screen shows no error, 
but I can't connect to the node (with REST I get "503 Service Unavailable").
Is the index corrupt? 

Thanks!

On Sunday, June 29, 2014 2:51:56 PM UTC+3, Itamar Syn-Hershko wrote:
>
> This error means indexing has stopped at one point, up to that point 
> everything is preserved.
>
> See 
> http://www.elasticsearch.org/guide/en/elasticsearch/reference/current/index-modules-allocation.html#disk
>  
> for how to avoid this from now on
>
> --
>
> Itamar Syn-Hershko
> http://code972.com | @synhershko 
> Freelance Developer & Consultant
> Author of RavenDB in Action 
>
>
> On Sun, Jun 29, 2014 at 1:37 PM, Ophir Michaeli  > wrote:
>
>> Hi, 
>>
>> I get an error - 
>> failed to merge java.io.IOException: There is not enough space on the 
>> disk.
>> The disk was full, cleaned it now.
>> What is the best way not to loose what I already indexed? Or does this 
>> error mean that the index is lost and I need to delete and index again?
>>
>> Thanks,
>> Ophir
>>
>> -- 
>> 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 elasticsearc...@googlegroups.com .
>> To view this discussion on the web visit 
>> https://groups.google.com/d/msgid/elasticsearch/0b1ae217-aeb4-465f-9468-d2b617a47679%40googlegroups.com
>>  
>> 
>> .
>> 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/63357c69-0c1e-45f8-8b0f-962dc805bc50%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: Failed to merge - There is not enough space on the disk

[Itamar Syn-Hershko]

This error means indexing has stopped at one point, up to that point
everything is preserved.

See
http://www.elasticsearch.org/guide/en/elasticsearch/reference/current/index-modules-allocation.html#disk
for how to avoid this from now on

--

Itamar Syn-Hershko
http://code972.com | @synhershko 
Freelance Developer & Consultant
Author of RavenDB in Action 


On Sun, Jun 29, 2014 at 1:37 PM, Ophir Michaeli 
wrote:

> Hi,
>
> I get an error -
> failed to merge java.io.IOException: There is not enough space on the disk.
> The disk was full, cleaned it now.
> What is the best way not to loose what I already indexed? Or does this
> error mean that the index is lost and I need to delete and index again?
>
> Thanks,
> Ophir
>
> --
> 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/0b1ae217-aeb4-465f-9468-d2b617a47679%40googlegroups.com
> 
> .
> 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/CAHTr4Zt2aTcYVaioqELxf1h7SQ%3Da0qyiSv_Z15wokD12vUo%3DpA%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Failed to merge - There is not enough space on the disk

[Ophir Michaeli]

Hi, 

I get an error - 
failed to merge java.io.IOException: There is not enough space on the disk.
The disk was full, cleaned it now.
What is the best way not to loose what I already indexed? Or does this 
error mean that the index is lost and I need to delete and index again?

Thanks,
Ophir

-- 
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/0b1ae217-aeb4-465f-9468-d2b617a47679%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.