Hi,
Is there a way to tell ES to open closed indices automatically on first access (search or indexing)? I can do it on the application side by looking for IndexClosedException, but this seems like a natural thing that ES should be able to do, after all ES creates new indices automatically.
-- 
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+unsubscribe@googlegroups.com . 
To view this discussion on the web visit https://groups.google.com/d/msgid/elasticsearch/EBBDD69F-4D57-4312-B068-B142CF92CBF1%40venarc.com . 
For more options, visit https://groups.google.com/d/optout .
             
            
               
               
               
            
                
            
           
          
            
              
                dadoonet  
                (David Pilato)
               
              
                  
                    January 26, 2015,  8:42pm
                   
                   
              2 
               
             
            
              Opening an index is a costly operation. 
Creating a new index is not.
My 2 cents
-- 
David Pilato | Technical Advocate | Elasticsearch.com  
@dadoonet  https://twitter.com/dadoonet  | @elasticsearchfr  https://twitter.com/elasticsearchfr  | @scrutmydocs  https://twitter.com/scrutmydocs 
Le 26 janv. 2015 à 21:41, Drew Kutcharian drew@venarc.com  a écrit :
Hi,
Is there a way to tell ES to open closed indices automatically on first access (search or indexing)? I can do it on the application side by looking for IndexClosedException, but this seems like a natural thing that ES should be able to do, after all ES creates new indices automatically.
-- 
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+unsubscribe@googlegroups.com . 
To view this discussion on the web visit https://groups.google.com/d/msgid/elasticsearch/EBBDD69F-4D57-4312-B068-B142CF92CBF1%40venarc.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+unsubscribe@googlegroups.com . 
To view this discussion on the web visit https://groups.google.com/d/msgid/elasticsearch/222794C5-0686-4BCF-8C1A-C37FCC9636D7%40pilato.fr . 
For more options, visit https://groups.google.com/d/optout .
             
            
               
               
               
            
            
           
          
            
            
              I agree. But they both go thru shard allocation, no? I’m assuming opening/closing small 1 shard indexes (max 100MB total size) shouldn’t be that bad.
On Jan 26, 2015, at 12:42 PM, David Pilato david@pilato.fr  wrote:
Opening an index is a costly operation. 
Creating a new index is not.
My 2 cents
-- 
David Pilato | Technical Advocate | Elasticsearch.com  http://elasticsearch.com/  
@dadoonet  https://twitter.com/dadoonet  | @elasticsearchfr  https://twitter.com/elasticsearchfr  | @scrutmydocs  https://twitter.com/scrutmydocs 
Le 26 janv. 2015 à 21:41, Drew Kutcharian <drew@venarc.com  mailto:drew@venarc.com > a écrit :
Hi,
Is there a way to tell ES to open closed indices automatically on first access (search or indexing)? I can do it on the application side by looking for IndexClosedException, but this seems like a natural thing that ES should be able to do, after all ES creates new indices automatically.
-- 
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+unsubscribe@googlegroups.com  mailto:elasticsearch+unsubscribe@googlegroups.com . 
To view this discussion on the web visit https://groups.google.com/d/msgid/elasticsearch/EBBDD69F-4D57-4312-B068-B142CF92CBF1%40venarc.com  https://groups.google.com/d/msgid/elasticsearch/EBBDD69F-4D57-4312-B068-B142CF92CBF1%40venarc.com . 
For more options, visit https://groups.google.com/d/optout  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+unsubscribe@googlegroups.com  mailto:elasticsearch+unsubscribe@googlegroups.com . 
To view this discussion on the web visit https://groups.google.com/d/msgid/elasticsearch/222794C5-0686-4BCF-8C1A-C37FCC9636D7%40pilato.fr  https://groups.google.com/d/msgid/elasticsearch/222794C5-0686-4BCF-8C1A-C37FCC9636D7%40pilato.fr?utm_medium=email&utm_source=footer . 
For more options, visit https://groups.google.com/d/optout  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+unsubscribe@googlegroups.com . 
To view this discussion on the web visit https://groups.google.com/d/msgid/elasticsearch/89BDF355-E6BF-4A34-B160-52F34589D146%40venarc.com . 
For more options, visit https://groups.google.com/d/optout .
             
            
               
               
               
            
            
           
          
            
              
                warkolm  
                (Mark Walkom)
               
              
                  
                    January 26, 2015, 10:38pm
                   
                   
              4 
               
             
            
              That's still massively different to creating and allocating a completely 
empty index.
On 27 January 2015 at 08:23, Drew Kutcharian drew@venarc.com  wrote:
I agree. But they both go thru shard allocation, no? I’m assuming 
opening/closing small 1 shard indexes (max 100MB total size) shouldn’t be 
that bad.
On Jan 26, 2015, at 12:42 PM, David Pilato david@pilato.fr  wrote:
Opening an index is a costly operation. 
Creating a new index is not.
My 2 cents
-- 
David Pilato  | Technical Advocate  | Elasticsearch.com  
http://elasticsearch.com/  
@dadoonet  https://twitter.com/dadoonet  | @elasticsearchfr  
https://twitter.com/elasticsearchfr  | @scrutmydocs  
https://twitter.com/scrutmydocs 
Le 26 janv. 2015 à 21:41, Drew Kutcharian drew@venarc.com  a écrit :
Hi,
Is there a way to tell ES to open closed indices automatically on first 
access (search or indexing)? I can do it on the application side by looking 
for IndexClosedException, but this seems like a natural thing that ES 
should be able to do, after all ES creates new indices automatically.
-- 
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+unsubscribe@googlegroups.com . 
To view this discussion on the web visit 
https://groups.google.com/d/msgid/elasticsearch/EBBDD69F-4D57-4312-B068-B142CF92CBF1%40venarc.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+unsubscribe@googlegroups.com . 
To view this discussion on the web visit 
https://groups.google.com/d/msgid/elasticsearch/222794C5-0686-4BCF-8C1A-C37FCC9636D7%40pilato.fr  
https://groups.google.com/d/msgid/elasticsearch/222794C5-0686-4BCF-8C1A-C37FCC9636D7%40pilato.fr?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+unsubscribe@googlegroups.com . 
To view this discussion on the web visit 
https://groups.google.com/d/msgid/elasticsearch/89BDF355-E6BF-4A34-B160-52F34589D146%40venarc.com  
https://groups.google.com/d/msgid/elasticsearch/89BDF355-E6BF-4A34-B160-52F34589D146%40venarc.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+unsubscribe@googlegroups.com . 
To view this discussion on the web visit https://groups.google.com/d/msgid/elasticsearch/CAEYi1X84a0dx0-21THcPFbd-aZpSO0Bzy1NsO6B1kOhOdnGjyQ%40mail.gmail.com . 
For more options, visit https://groups.google.com/d/optout .