date:20140614

aliases by bulk requests

2014-06-14 Thread Harish Ved

I am trying to index some products via bulk requests. I am using 
elastic-search version 1.2.0 and am using python client from here 
 at the latest 
version.
So, I am using helpers.bulk(es, actions) for bulk requests. On indexing 
individually by es.index(index, doc_type, body) if i use an alias name in 
place of index, the alias (which was already created) is applied to that 
product (ie I can search by localhost:9200/alias/_search).
My problem is - on bulk indexing, if I define each action as {"_index": 
alias, "_type": "type", "_id": "random", "_source": body}, then the product 
is not listed in 'localhost:9200/alias/_search' but is rather empty. I am 
sure the alias is defined and points to the proper index.

PS - After bulk indexing I can search by 'localhost:9200/index/_search' 
even if I defined _index = alias in action.
My Question - How to add documents to a previously defined alias via bulk 
indexing (actions in the actions list may point to different alias)?

-- 
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/5ca8493a-1781-494b-88b3-0b5fbed3b7f2%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: Extremely Simple Java Request

2014-06-14 Thread smonasco

I rolled my own.

On Thursday, June 12, 2014 5:23:00 PM UTC-6, smonasco wrote:
>
> I've been through the API documentation and the elasticsearch source code.
>
> I'm looking to create a service that when given a list of (URL path, JSON 
> path, metric type) will take the value found at the JSON path from the JSON 
> returned from the URL in my cluster and put it into our metrics system.
>
> I'm trying to find something really simple in the Java space that will 
> give me a JSON object of some variety or a response object I can call 
> .toXContent on when I pass it the URL.
>
> Not sure if I'm explaining this well, but something like:
>
> Request request = new SimpleRequest(url);
> Response response = client.get(request).actionGet();
> XContentBuilder responseContent = XContentFactory.jsonBuilder();
> response.toXContent(responseContent, null);
>
> If I need to build it myself that's ok.  I'd just like to know it's not 
> built and maybe have a pointer or two.
>
> --Shannon Monasco
>

-- 
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/8dcd8d74-453d-4578-9f1b-1250ceaa7594%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: Deleteing index times out

2014-06-14 Thread Nikolas Everett

I've had deleted time out for large indexes one or twice but when I checked
back the index was deleted successfully.  It'd be weirder for the index to
stick around I think.
On Jun 14, 2014 7:46 PM, "Mark Walkom"  wrote:

> How big is the index?
> Have you had a look at your ES logs to see if there is anything?
>
> Regards,
> Mark Walkom
>
> Infrastructure Engineer
> Campaign Monitor
> email: ma...@campaignmonitor.com
> web: www.campaignmonitor.com
>
>
> On 15 June 2014 02:33, Kiran Koduru  wrote:
>
>> I am trying to delete an index called *dataenvironmentalmarkets *through
>> a curl request.
>>
>> curl -XDELETE 'http://myurl.com:9200/dataenvironmentalmarkets/'
>>
>> The requests times out with an exception
>>
>> {"error":"ProcessClusterEventTimeoutException[failed to process cluster
>> event (delete-index [dataenvironmentalmarkets]) within 30s]","status":503
>> }
>>
>> I also tried extending the timeout to 15m using
>>
>> curl -XDELETE '
>> http://myurl.com:9200/dataenvironmentalmarkets/?timeout=15m'
>>
>> and
>>
>>
>> curl -XDELETE 'http://myurl.com:9200/dataenvironmentalmarkets?timeout=15m
>> '
>>
>>
>> The same error. Maybe I am skipping something. Can you help ?
>>
>> 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/316f93ed-9e8c-4473-96a0-78d03c31d804%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/CAEM624Zy_xOuEEK73Jdat2NOmXApZP-R3s6NQt9-rH6DsGfGpQ%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/CAPmjWd3z3vtNW72BcNZSnNnGQZSg2rd82fOb46OhdxN%3DMGgsKw%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: Help needed: CentOS ES-Logstash-Kibana running, but 0 docs, 0 indices

2014-06-14 Thread Mark Walkom

Try swapping the host in your LS output to the actual IP of VM.

Regards,
Mark Walkom

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


On 14 June 2014 18:34, 'Robert AMS' via elasticsearch <
elasticsearch@googlegroups.com> wrote:

> Als POC I've setup a single machine with Logstash, Elasticsearch and
> Kibana, But I am stuck: It is running, but no docs are getting in ES and
> Kibana stays only a dark page. Can someone help me how to get the logs into
> ES en searchable in Kibana?
>
> This is my machine. Just install a CentOS 6.5 (virtual) server, su to root
> and copy-paste this to the command line and all will be installed:
>
> Pastebin: Install_ES_Logstash_Kibana_for_CentOS6.5
>  ( http://pastebin.com/fpz5AQzd )
>
> Wat is missing?
>
>
>  --
> 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/ee7d3476-5551-40d2-aef5-28276e7783bd%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/CAEM624Y5W8Rq1xNaxxY3aiLMpA-mRKAnv99L1%2BSi1MhVOb%2B44w%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: Deleteing index times out

2014-06-14 Thread Mark Walkom

How big is the index?
Have you had a look at your ES logs to see if there is anything?

Regards,
Mark Walkom

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


On 15 June 2014 02:33, Kiran Koduru  wrote:

> I am trying to delete an index called *dataenvironmentalmarkets *through
> a curl request.
>
> curl -XDELETE 'http://myurl.com:9200/dataenvironmentalmarkets/'
>
> The requests times out with an exception
>
> {"error":"ProcessClusterEventTimeoutException[failed to process cluster
> event (delete-index [dataenvironmentalmarkets]) within 30s]","status":503}
>
> I also tried extending the timeout to 15m using
>
> curl -XDELETE 'http://myurl.com:9200/dataenvironmentalmarkets/?timeout=15m
> '
>
> and
>
>
> curl -XDELETE 'http://myurl.com:9200/dataenvironmentalmarkets?timeout=15m'
>
>
> The same error. Maybe I am skipping something. Can you help ?
>
> 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/316f93ed-9e8c-4473-96a0-78d03c31d804%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/CAEM624Zy_xOuEEK73Jdat2NOmXApZP-R3s6NQt9-rH6DsGfGpQ%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

[ANN] Elasticsearch syslog plugin

2014-06-14 Thread joergpra...@gmail.com

Hi,

here is a small plugin for Elasticsearch for receiving syslog messages via
UDP or TCP. It is very similar to the bulk UDP module, but can parse syslog
RFC messages.

https://github.com/jprante/elasticsearch-syslog

As always, feedback is most welcome.

Best,

Jörg

-- 
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/CAKdsXoGvj1-LCK5tvA6BAW4ec-JYTDSr5aEmdcEbXP0%2B3CEggw%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: Interesting Issue

2014-06-14 Thread David Pilato

Upload your logs on gist.github.com and paste the link here.

May be some more details here: http://www.elasticsearch.org/help/

--
David Pilato | Technical Advocate | Elasticsearch.com
@dadoonet | @elasticsearchfr

Le 14 juin 2014 à 19:06:46, John Luko (johnl...@gmail.com) a écrit:

Sorry I am a n00b when it comes to ES. How would I go about that?

On Saturday, June 14, 2014 1:02:45 PM UTC-4, David Pilato wrote:
May be you should gist your logs and copy the link here?

--
David Pilato | Technical Advocate | Elasticsearch.com
@dadoonet | @elasticsearchfr

Le 14 juin 2014 à 18:44:07, John Luko (john...@gmail.com) a écrit:

Is there a particular log I should look at? In elasticsearch.log I am seeing a
lot of parser failures for a timestamp.

On Saturday, June 14, 2014 12:26:47 PM UTC-4, David Pilato wrote:
First guess is that you are running out of memory or so.
What can you see in elasticsearch logs?

Don't you see some WARN about GC?

--
David ;-)
Twitter : @dadoonet / @elasticsearchfr / @scrutmydocs

Le 14 juin 2014 à 18:06, John Luko a écrit :

We are running Elasticsearch with three nodes. The problem we keep running
into is eventually Kibana begins to run extremely slow and soon after becomes
unresponsive. If you hit refresh the wheels just keep spinning and nothing
gets displayed. Restarting the cluster appears to correct this issue, but
within 24 hours it begins again. Below is our health:

{
"cluster_name" : "elasticsearch",
"status" : "green",
"timed_out" : false,
"number_of_nodes" : 4,
"number_of_data_nodes" : 3,
"active_primary_shards" : 341,
"active_shards" : 682,
"relocating_shards" : 2,
"initializing_shards" : 0,
"unassigned_shards" : 0
}

When we initially set everything up we had a single node and we did have a span
of three weeks where we didn't have to restart the Elasticsearch service. When
we begin to pump netflow data in we began to have issues. I thought perhaps
because we had logstash and ES running on one node that was causing the issue.
Thus we added two virtual nodes and had one of them host the logstash for just
Netflow. I thought with the clustering the issue would be resolved, but sadly
I still have to start and stop the services everyday. When I look back at the
data it flows in the entire time until flat lining for a few hours and then
picks up again once I restart the services.

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 elasticsearc...@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/elasticsearch/d088f293-9dae-475a-a15e-076b3b773680%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/9a357da0-9ac6-4aaf-853d-f76f453c27d0%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/6908936b-02e7-46f9-873d-9fe3f2d1d152%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/etPan.539c8371.12200854.a69e%40MacBook-Air-de-David.local.
For more options, visit https://groups.google.com/d/optout.

Re: does document database means denormalize

2014-06-14 Thread eunever32

Great answer!  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/ddbe277a-1996-455c-b07d-82a75cb9b56e%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: Interesting Issue

2014-06-14 Thread John Luko

Sorry I am a n00b when it comes to ES.  How would I go about that?

On Saturday, June 14, 2014 1:02:45 PM UTC-4, David Pilato wrote:
>
> May be you should gist your logs and copy the link here?
>
> -- 
> *David Pilato* | *Technical Advocate* | *Elasticsearch.com*
> @dadoonet  | @elasticsearchfr 
> 
>
>
> Le 14 juin 2014 à 18:44:07, John Luko (john...@gmail.com ) a 
> écrit:
>
> Is there a particular log I should look at?  In elasticsearch.log I am 
> seeing a lot of parser failures for a timestamp.
>
> On Saturday, June 14, 2014 12:26:47 PM UTC-4, David Pilato wrote: 
>>
>>  First guess is that you are running out of memory or so.
>> What can you see in elasticsearch logs?
>>
>> Don't you see some WARN about GC?
>>
>> --
>> David ;-)
>> Twitter : @dadoonet / @elasticsearchfr / @scrutmydocs
>>
>>  
>> Le 14 juin 2014 à 18:06, John Luko  a écrit :
>>
>>  We are running Elasticsearch with three nodes.  The problem we keep 
>> running into is eventually Kibana begins to run extremely slow and soon 
>> after becomes unresponsive.  If you hit refresh the wheels just keep 
>> spinning and nothing gets displayed.  Restarting the cluster appears to 
>> correct this issue, but within 24 hours it begins again.  Below is our 
>> health: 
>>
>>  {
>>   "cluster_name" : "elasticsearch",
>>   "status" : "green",
>>   "timed_out" : false,
>>   "number_of_nodes" : 4,
>>   "number_of_data_nodes" : 3,
>>   "active_primary_shards" : 341,
>>   "active_shards" : 682,
>>   "relocating_shards" : 2,
>>   "initializing_shards" : 0,
>>   "unassigned_shards" : 0
>> }
>>  
>> When we initially set everything up we had a single node and we did have 
>> a span of three weeks where we didn't have to restart the Elasticsearch 
>> service.  When we begin to pump netflow data in we began to have issues.  I 
>> thought perhaps because we had logstash and ES running on one node that was 
>> causing the issue.  Thus we added two virtual nodes and had one of them 
>> host the logstash for just Netflow.  I thought with the clustering the 
>> issue would be resolved, but sadly I still have to start and stop the 
>> services everyday.  When I look back at the data it flows in the entire 
>> time until flat lining for a few hours and then picks up again once I 
>> restart the services.
>>
>> 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 elasticsearc...@googlegroups.com.
>> To view this discussion on the web visit 
>> https://groups.google.com/d/msgid/elasticsearch/d088f293-9dae-475a-a15e-076b3b773680%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/9a357da0-9ac6-4aaf-853d-f76f453c27d0%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/6908936b-02e7-46f9-873d-9fe3f2d1d152%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: Interesting Issue

2014-06-14 Thread David Pilato

May be you should gist your logs and copy the link here?

--
David Pilato | Technical Advocate | Elasticsearch.com
@dadoonet | @elasticsearchfr

Le 14 juin 2014 à 18:44:07, John Luko (johnl...@gmail.com) a écrit:

Is there a particular log I should look at? In elasticsearch.log I am seeing a
lot of parser failures for a timestamp.

On Saturday, June 14, 2014 12:26:47 PM UTC-4, David Pilato wrote:
First guess is that you are running out of memory or so.
What can you see in elasticsearch logs?

Don't you see some WARN about GC?

--
David ;-)
Twitter : @dadoonet / @elasticsearchfr / @scrutmydocs

Le 14 juin 2014 à 18:06, John Luko a écrit :

--
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/etPan.539c8021.79e2a9e3.a69e%40MacBook-Air-de-David.local.
For more options, visit https://groups.google.com/d/optout.

Re: Interesting Issue

2014-06-14 Thread John Luko

Is there a particular log I should look at?  In elasticsearch.log I am 
seeing a lot of parser failures for a timestamp.

On Saturday, June 14, 2014 12:26:47 PM UTC-4, David Pilato wrote:
>
> First guess is that you are running out of memory or so.
> What can you see in elasticsearch logs?
>
> Don't you see some WARN about GC?
>
> --
> David ;-)
> Twitter : @dadoonet / @elasticsearchfr / @scrutmydocs
>
>
> Le 14 juin 2014 à 18:06, John Luko > a 
> écrit :
>
> We are running Elasticsearch with three nodes.  The problem we keep 
> running into is eventually Kibana begins to run extremely slow and soon 
> after becomes unresponsive.  If you hit refresh the wheels just keep 
> spinning and nothing gets displayed.  Restarting the cluster appears to 
> correct this issue, but within 24 hours it begins again.  Below is our 
> health:
>
> {
>   "cluster_name" : "elasticsearch",
>   "status" : "green",
>   "timed_out" : false,
>   "number_of_nodes" : 4,
>   "number_of_data_nodes" : 3,
>   "active_primary_shards" : 341,
>   "active_shards" : 682,
>   "relocating_shards" : 2,
>   "initializing_shards" : 0,
>   "unassigned_shards" : 0
> }
>
> When we initially set everything up we had a single node and we did have a 
> span of three weeks where we didn't have to restart the Elasticsearch 
> service.  When we begin to pump netflow data in we began to have issues.  I 
> thought perhaps because we had logstash and ES running on one node that was 
> causing the issue.  Thus we added two virtual nodes and had one of them 
> host the logstash for just Netflow.  I thought with the clustering the 
> issue would be resolved, but sadly I still have to start and stop the 
> services everyday.  When I look back at the data it flows in the entire 
> time until flat lining for a few hours and then picks up again once I 
> restart the services.
>
> 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 elasticsearc...@googlegroups.com .
> To view this discussion on the web visit 
> https://groups.google.com/d/msgid/elasticsearch/d088f293-9dae-475a-a15e-076b3b773680%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/9a357da0-9ac6-4aaf-853d-f76f453c27d0%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Deleteing index times out

2014-06-14 Thread Kiran Koduru

I am trying to delete an index called *dataenvironmentalmarkets *through a 
curl request. 

curl -XDELETE 'http://myurl.com:9200/dataenvironmentalmarkets/'

The requests times out with an exception 

{"error":"ProcessClusterEventTimeoutException[failed to process cluster 
event (delete-index [dataenvironmentalmarkets]) within 30s]","status":503}

I also tried extending the timeout to 15m using 

curl -XDELETE 'http://myurl.com:9200/dataenvironmentalmarkets/?timeout=15m'

and


curl -XDELETE 'http://myurl.com:9200/dataenvironmentalmarkets?timeout=15m'


The same error. Maybe I am skipping something. Can you help ?

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/316f93ed-9e8c-4473-96a0-78d03c31d804%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: Interesting Issue

2014-06-14 Thread David Pilato

First guess is that you are running out of memory or so.
What can you see in elasticsearch logs?

Don't you see some WARN about GC?

--
David ;-)
Twitter : @dadoonet / @elasticsearchfr / @scrutmydocs

Le 14 juin 2014 à 18:06, John Luko a écrit :

--
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/80DCF447-DF89-4CD1-A52C-0DF21D14FC37%40pilato.fr.
For more options, visit https://groups.google.com/d/optout.

Interesting Issue

2014-06-14 Thread John Luko

We are running Elasticsearch with three nodes. The problem we keep running
into is eventually Kibana begins to run extremely slow and soon after
becomes unresponsive. If you hit refresh the wheels just keep spinning and
nothing gets displayed. Restarting the cluster appears to correct this
issue, but within 24 hours it begins again. Below is our health:

When we initially set everything up we had a single node and we did have a
span of three weeks where we didn't have to restart the Elasticsearch
service. When we begin to pump netflow data in we began to have issues. I
thought perhaps because we had logstash and ES running on one node that was
causing the issue. Thus we added two virtual nodes and had one of them
host the logstash for just Netflow. I thought with the clustering the
issue would be resolved, but sadly I still have to start and stop the
services everyday. When I look back at the data it flows in the entire
time until flat lining for a few hours and then picks up again once I
restart the services.

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/d088f293-9dae-475a-a15e-076b3b773680%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: Upgrade to 1.2.1, now broken and status yellow

2014-06-14 Thread David Pilato

It should not be broken as you just upgraded Elasticsearch.
The same json document stored in /kibana-int/dashboard should work.

I don't see what could break it. 

May be you should look at what it looks like:

curl localhost:9200/kibana-int/_search?pretty


--
David ;-)
Twitter : @dadoonet / @elasticsearchfr / @scrutmydocs


Le 14 juin 2014 à 11:07, Justin  a écrit :

So loading the default Logstash dashboard view in Kibana works after all. Seems 
just my custom dashboard somehow got corrupted which is really unfortunate 
since I spent a long time configuring and setting it up.

> On Saturday, June 14, 2014 2:00:44 AM UTC-7, Justin wrote:
> Seemed to work.
> 
> {
> "took": 41,
> "timed_out": false,
> "_shards": {
> "total": 77,
> "successful": 77,
> "failed": 0
> },
> "hits": {
> "total": 334881,
> "max_score": 1,
> "hits": [
> 
> 
>> On Saturday, June 14, 2014 1:50:27 AM UTC-7, David Pilato wrote:
>> What gives 
>> 
>> curl localhost:9200/_search?pretty
>> 
>> 
>> 
>> --
>> David ;-)
>> Twitter : @dadoonet / @elasticsearchfr / @scrutmydocs
>> 
>> 
>> Le 14 juin 2014 à 10:31, "Commando.io"  a écrit :
>> 
>> Nothing changed, worked with ES 1.2.0 and now I can't view anything in 
>> Kibana. If I go to the default Logstash in Kibana I see all documents up 
>> until the point I upgraded to 1.2.1, but then no documents after.
>> 
>> 
>> ---
>> Justin Keller (Founder)
>> Commando.io - Manage servers easily online.
>> comm...@nodesocket.com
>> https://commando.io
>> Twitter: @commando_io
>> 
>> 
>>> On Sat, Jun 14, 2014 at 1:23 AM, David Pilato  wrote:
>>> Probably something wrong in your Kibana dashboard settings, but from an 
>>> elasticsearch point of view, everything looks fine to me.
>>> 
>>> Check your Kibana dashboard settings.
>>> 
>>> 
>>> --
>>> David ;-)
>>> Twitter : @dadoonet / @elasticsearchfr / @scrutmydocs
>>> 
>>> 
>>> Le 14 juin 2014 à 10:11, Justin  a écrit :
>>> 
>>> Kibana is showing: Error Could not find Logstash. If you are using a proxy, 
>>> ensure it is configured correctly which used to work with 1.2.0.
>>> 
>>> The dashboard is stored in ES.
>>> 
 On Saturday, June 14, 2014 1:02:28 AM UTC-7, David Pilato wrote:
 Why do you think there is something wrong?
 
 It looks like ok for a one node cluster.
 
 --
 David ;-)
 Twitter : @dadoonet / @elasticsearchfr / @scrutmydocs
 
> Le 14 juin 2014 à 09:21, Justin  a écrit :
> 
> Just tried to upgrade to 1.2.1 from 1.2.0 running on a single server. I 
> stopped it, did the upgrade and started ES again. However, now it is 
> showing status yellow and not storing any documents:
> 
> {
> "status": 200,
> "name": "Dead Girl",
> "version": {
> "number": "1.2.1",
> "build_hash": "6c95b759f9e7ef0f8e17f77d850da43ce8a4b364",
> "build_timestamp": "2014-06-03T15:02:52Z",
> "build_snapshot": false,
> "lucene_version": "4.8"
> },
> "tagline": "You Know, for Search"
> }
> 
> {
> "cluster_name": "es",
> "status": "yellow",
> "timed_out": false,
> "number_of_nodes": 1,
> "number_of_data_nodes": 1,
> "active_primary_shards": 77,
> "active_shards": 77,
> "relocating_shards": 0,
> "initializing_shards": 0,
> "unassigned_shards": 77
> }
> 
> Any ideas how to fix?
> -- 
> 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/66c8cfe9-513b-4e0e-9f0b-17cb3b31041a%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/9881174a-b4d7-4694-9dea-049540d1ecf5%40googlegroups.com.
>>> 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/1yjtq-nS43E/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/BEC63D72-9298-4972-A0B3-D05B61900B4B%40pilato.fr.
>>> 
>>> 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

Re: Upgrade to 1.2.1, now broken and status yellow

2014-06-14 Thread Justin

So loading the default Logstash dashboard view in Kibana works after all. 
Seems just my custom dashboard somehow got corrupted which is really 
unfortunate since I spent a long time configuring and setting it up.

On Saturday, June 14, 2014 2:00:44 AM UTC-7, Justin wrote:
>
> Seemed to work.
>
> {"took": 41,"timed_out": false,"_shards": {"total": 77,"successful": 77,"
> failed": 0},"hits": {"total": 334881,"max_score": 1,"hits": [
> On Saturday, June 14, 2014 1:50:27 AM UTC-7, David Pilato wrote:
>>
>> What gives 
>>
>> curl localhost:9200/_search?pretty
>>
>>
>>
>> --
>> David ;-)
>> Twitter : @dadoonet / @elasticsearchfr / @scrutmydocs
>>
>>
>> Le 14 juin 2014 à 10:31, "Commando.io"  a écrit :
>>
>> Nothing changed, worked with ES 1.2.0 and now I can't view anything in 
>> Kibana. If I go to the default Logstash in Kibana I see all documents up 
>> until the point I upgraded to 1.2.1, but then no documents after.
>>
>>
>> ---
>> Justin Keller (Founder)
>> Commando.io - Manage servers easily online.
>> comm...@nodesocket.com
>> https://commando.io
>> Twitter: @commando_io
>>
>>
>> On Sat, Jun 14, 2014 at 1:23 AM, David Pilato  wrote:
>>
>>> Probably something wrong in your Kibana dashboard settings, but from an 
>>> elasticsearch point of view, everything looks fine to me.
>>>
>>> Check your Kibana dashboard settings.
>>>
>>>
>>> --
>>> David ;-)
>>> Twitter : @dadoonet / @elasticsearchfr / @scrutmydocs
>>>
>>>
>>> Le 14 juin 2014 à 10:11, Justin  a écrit :
>>>
>>> Kibana is showing: Error Could not find Logstash. If you are using a 
>>> proxy, ensure it is configured correctly which used to work with 1.2.0.
>>>
>>> The dashboard is stored in ES.
>>>
>>> On Saturday, June 14, 2014 1:02:28 AM UTC-7, David Pilato wrote:

 Why do you think there is something wrong?

 It looks like ok for a one node cluster.

 --
 David ;-)
 Twitter : @dadoonet / @elasticsearchfr / @scrutmydocs

 Le 14 juin 2014 à 09:21, Justin  a écrit :

 Just tried to upgrade to 1.2.1 from 1.2.0 running on a single server. I 
 stopped it, did the upgrade and started ES again. However, now it is 
 showing status yellow and not storing any documents:

 {"status": 200,"name": "Dead Girl","version": {"number": "1.2.1","
 build_hash": "6c95b759f9e7ef0f8e17f77d850da43ce8a4b364","
 build_timestamp": "2014-06-03T15:02:52Z","build_snapshot": false,"
 lucene_version": "4.8"},"tagline": "You Know, for Search"}

 {"cluster_name": "es","status": "yellow","timed_out": false,"
 number_of_nodes": 1,"number_of_data_nodes": 1,"active_primary_shards": 
 77,"active_shards": 77,"relocating_shards": 0,"initializing_shards": 0,
 "unassigned_shards": 77}

 Any ideas how to fix?

 -- 
 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/66c8cfe9-513b-4e0e-9f0b-17cb3b31041a%
 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/9881174a-b4d7-4694-9dea-049540d1ecf5%40googlegroups.com
>>>  
>>> 
>>> .
>>> 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/1yjtq-nS43E/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/BEC63D72-9298-4972-A0B3-D05B61900B4B%40pilato.fr
>>>  
>>> 
>>> .
>>>
>>> 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

Re: Upgrade to 1.2.1, now broken and status yellow

2014-06-14 Thread Justin

Seemed to work.

{"took": 41,"timed_out": false,"_shards": {"total": 77,"successful": 77,"
failed": 0},"hits": {"total": 334881,"max_score": 1,"hits": [
On Saturday, June 14, 2014 1:50:27 AM UTC-7, David Pilato wrote:
>
> What gives 
>
> curl localhost:9200/_search?pretty
>
>
>
> --
> David ;-)
> Twitter : @dadoonet / @elasticsearchfr / @scrutmydocs
>
>
> Le 14 juin 2014 à 10:31, "Commando.io"  > a écrit :
>
> Nothing changed, worked with ES 1.2.0 and now I can't view anything in 
> Kibana. If I go to the default Logstash in Kibana I see all documents up 
> until the point I upgraded to 1.2.1, but then no documents after.
>
>
> ---
> Justin Keller (Founder)
> Commando.io - Manage servers easily online.
> comm...@nodesocket.com 
> https://commando.io
> Twitter: @commando_io
>
>
> On Sat, Jun 14, 2014 at 1:23 AM, David Pilato  > wrote:
>
>> Probably something wrong in your Kibana dashboard settings, but from an 
>> elasticsearch point of view, everything looks fine to me.
>>
>> Check your Kibana dashboard settings.
>>
>>
>> --
>> David ;-)
>> Twitter : @dadoonet / @elasticsearchfr / @scrutmydocs
>>
>>
>> Le 14 juin 2014 à 10:11, Justin > a 
>> écrit :
>>
>> Kibana is showing: Error Could not find Logstash. If you are using a 
>> proxy, ensure it is configured correctly which used to work with 1.2.0.
>>
>> The dashboard is stored in ES.
>>
>> On Saturday, June 14, 2014 1:02:28 AM UTC-7, David Pilato wrote:
>>>
>>> Why do you think there is something wrong?
>>>
>>> It looks like ok for a one node cluster.
>>>
>>> --
>>> David ;-)
>>> Twitter : @dadoonet / @elasticsearchfr / @scrutmydocs
>>>
>>> Le 14 juin 2014 à 09:21, Justin  a écrit :
>>>
>>> Just tried to upgrade to 1.2.1 from 1.2.0 running on a single server. I 
>>> stopped it, did the upgrade and started ES again. However, now it is 
>>> showing status yellow and not storing any documents:
>>>
>>> {"status": 200,"name": "Dead Girl","version": {"number": "1.2.1","
>>> build_hash": "6c95b759f9e7ef0f8e17f77d850da43ce8a4b364","build_timestamp
>>> ": "2014-06-03T15:02:52Z","build_snapshot": false,"lucene_version": "4.8
>>> "},"tagline": "You Know, for Search"}
>>>
>>> {"cluster_name": "es","status": "yellow","timed_out": false,"
>>> number_of_nodes": 1,"number_of_data_nodes": 1,"active_primary_shards": 
>>> 77,"active_shards": 77,"relocating_shards": 0,"initializing_shards": 0,"
>>> unassigned_shards": 77}
>>>
>>> Any ideas how to fix?
>>>
>>> -- 
>>> 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/66c8cfe9-513b-4e0e-9f0b-17cb3b31041a%
>>> 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/9881174a-b4d7-4694-9dea-049540d1ecf5%40googlegroups.com
>>  
>> 
>> .
>> 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/1yjtq-nS43E/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/BEC63D72-9298-4972-A0B3-D05B61900B4B%40pilato.fr
>>  
>> 
>> .
>>
>> 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/CAORW3eqwV%2Bj5MW-L9dOP5fzgX0hCytbV6t%3DCRCudt_Ktya3PfQ%40mail.gmail.com
>  
> 
> .
> For more options, visit https://groups.google.com/

Re: Upgrade to 1.2.1, now broken and status yellow

2014-06-14 Thread David Pilato

What gives 

curl localhost:9200/_search?pretty



--
David ;-)
Twitter : @dadoonet / @elasticsearchfr / @scrutmydocs


Le 14 juin 2014 à 10:31, "Commando.io"  a écrit :

Nothing changed, worked with ES 1.2.0 and now I can't view anything in Kibana. 
If I go to the default Logstash in Kibana I see all documents up until the 
point I upgraded to 1.2.1, but then no documents after.


---
Justin Keller (Founder)
Commando.io - Manage servers easily online.
comma...@nodesocket.com
https://commando.io
Twitter: @commando_io


> On Sat, Jun 14, 2014 at 1:23 AM, David Pilato  wrote:
> Probably something wrong in your Kibana dashboard settings, but from an 
> elasticsearch point of view, everything looks fine to me.
> 
> Check your Kibana dashboard settings.
> 
> 
> --
> David ;-)
> Twitter : @dadoonet / @elasticsearchfr / @scrutmydocs
> 
> 
> Le 14 juin 2014 à 10:11, Justin  a écrit :
> 
> Kibana is showing: Error Could not find Logstash. If you are using a proxy, 
> ensure it is configured correctly which used to work with 1.2.0.
> 
> The dashboard is stored in ES.
> 
>> On Saturday, June 14, 2014 1:02:28 AM UTC-7, David Pilato wrote:
>> Why do you think there is something wrong?
>> 
>> It looks like ok for a one node cluster.
>> 
>> --
>> David ;-)
>> Twitter : @dadoonet / @elasticsearchfr / @scrutmydocs
>> 
>>> Le 14 juin 2014 à 09:21, Justin  a écrit :
>>> 
>>> Just tried to upgrade to 1.2.1 from 1.2.0 running on a single server. I 
>>> stopped it, did the upgrade and started ES again. However, now it is 
>>> showing status yellow and not storing any documents:
>>> 
>>> {
>>> "status": 200,
>>> "name": "Dead Girl",
>>> "version": {
>>> "number": "1.2.1",
>>> "build_hash": "6c95b759f9e7ef0f8e17f77d850da43ce8a4b364",
>>> "build_timestamp": "2014-06-03T15:02:52Z",
>>> "build_snapshot": false,
>>> "lucene_version": "4.8"
>>> },
>>> "tagline": "You Know, for Search"
>>> }
>>> 
>>> {
>>> "cluster_name": "es",
>>> "status": "yellow",
>>> "timed_out": false,
>>> "number_of_nodes": 1,
>>> "number_of_data_nodes": 1,
>>> "active_primary_shards": 77,
>>> "active_shards": 77,
>>> "relocating_shards": 0,
>>> "initializing_shards": 0,
>>> "unassigned_shards": 77
>>> }
>>> 
>>> Any ideas how to fix?
>>> -- 
>>> 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/66c8cfe9-513b-4e0e-9f0b-17cb3b31041a%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/9881174a-b4d7-4694-9dea-049540d1ecf5%40googlegroups.com.
> 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/1yjtq-nS43E/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/BEC63D72-9298-4972-A0B3-D05B61900B4B%40pilato.fr.
> 
> 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/CAORW3eqwV%2Bj5MW-L9dOP5fzgX0hCytbV6t%3DCRCudt_Ktya3PfQ%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/74F28145-F1A9-44EF-9B81-2654F6D5AD79%40pilato.fr.
For more options, visit https://groups.google.com/d/optout.

Help needed: CentOS ES-Logstash-Kibana running, but 0 docs, 0 indices

2014-06-14 Thread 'Robert AMS' via elasticsearch

Als POC I've setup a single machine with Logstash, Elasticsearch and 
Kibana, But I am stuck: It is running, but no docs are getting in ES and 
Kibana stays only a dark page. Can someone help me how to get the logs into 
ES en searchable in Kibana?

This is my machine. Just install a CentOS 6.5 (virtual) server, su to root 
and copy-paste this to the command line and all will be installed:

Pastebin: Install_ES_Logstash_Kibana_for_CentOS6.5 
 ( http://pastebin.com/fpz5AQzd )

Wat is missing?


-- 
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/ee7d3476-5551-40d2-aef5-28276e7783bd%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: Upgrade to 1.2.1, now broken and status yellow

2014-06-14 Thread Commando.io

Nothing changed, worked with ES 1.2.0 and now I can't view anything in
Kibana. If I go to the default Logstash in Kibana I see all documents up
until the point I upgraded to 1.2.1, but then no documents after.


---
Justin Keller (Founder)
Commando.io - Manage servers easily online.
comma...@nodesocket.com
https://commando.io
Twitter: @commando_io


On Sat, Jun 14, 2014 at 1:23 AM, David Pilato  wrote:

> Probably something wrong in your Kibana dashboard settings, but from an
> elasticsearch point of view, everything looks fine to me.
>
> Check your Kibana dashboard settings.
>
>
> --
> David ;-)
> Twitter : @dadoonet / @elasticsearchfr / @scrutmydocs
>
>
> Le 14 juin 2014 à 10:11, Justin  a écrit :
>
> Kibana is showing: Error Could not find Logstash. If you are using a
> proxy, ensure it is configured correctly which used to work with 1.2.0.
>
> The dashboard is stored in ES.
>
> On Saturday, June 14, 2014 1:02:28 AM UTC-7, David Pilato wrote:
>>
>> Why do you think there is something wrong?
>>
>> It looks like ok for a one node cluster.
>>
>> --
>> David ;-)
>> Twitter : @dadoonet / @elasticsearchfr / @scrutmydocs
>>
>> Le 14 juin 2014 à 09:21, Justin  a écrit :
>>
>> Just tried to upgrade to 1.2.1 from 1.2.0 running on a single server. I
>> stopped it, did the upgrade and started ES again. However, now it is
>> showing status yellow and not storing any documents:
>>
>> {"status": 200,"name": "Dead Girl","version": {"number": "1.2.1","
>> build_hash": "6c95b759f9e7ef0f8e17f77d850da43ce8a4b364","build_timestamp
>> ": "2014-06-03T15:02:52Z","build_snapshot": false,"lucene_version": "4.8"
>> },"tagline": "You Know, for Search"}
>>
>> {"cluster_name": "es","status": "yellow","timed_out": false,"
>> number_of_nodes": 1,"number_of_data_nodes": 1,"active_primary_shards": 77
>> ,"active_shards": 77,"relocating_shards": 0,"initializing_shards": 0,"
>> unassigned_shards": 77}
>>
>> Any ideas how to fix?
>>
>> --
>> 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/66c8cfe9-513b-4e0e-9f0b-17cb3b31041a%
>> 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/9881174a-b4d7-4694-9dea-049540d1ecf5%40googlegroups.com
> 
> .
> 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/1yjtq-nS43E/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/BEC63D72-9298-4972-A0B3-D05B61900B4B%40pilato.fr
> 
> .
>
> 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/CAORW3eqwV%2Bj5MW-L9dOP5fzgX0hCytbV6t%3DCRCudt_Ktya3PfQ%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: Upgrade to 1.2.1, now broken and status yellow

2014-06-14 Thread David Pilato

Probably something wrong in your Kibana dashboard settings, but from an 
elasticsearch point of view, everything looks fine to me.

Check your Kibana dashboard settings.

--
David ;-)
Twitter : @dadoonet / @elasticsearchfr / @scrutmydocs


Le 14 juin 2014 à 10:11, Justin  a écrit :

Kibana is showing: Error Could not find Logstash. If you are using a proxy, 
ensure it is configured correctly which used to work with 1.2.0.

The dashboard is stored in ES.

> On Saturday, June 14, 2014 1:02:28 AM UTC-7, David Pilato wrote:
> Why do you think there is something wrong?
> 
> It looks like ok for a one node cluster.
> 
> --
> David ;-)
> Twitter : @dadoonet / @elasticsearchfr / @scrutmydocs
> 
>> Le 14 juin 2014 à 09:21, Justin  a écrit :
>> 
>> Just tried to upgrade to 1.2.1 from 1.2.0 running on a single server. I 
>> stopped it, did the upgrade and started ES again. However, now it is showing 
>> status yellow and not storing any documents:
>> 
>> {
>> "status": 200,
>> "name": "Dead Girl",
>> "version": {
>> "number": "1.2.1",
>> "build_hash": "6c95b759f9e7ef0f8e17f77d850da43ce8a4b364",
>> "build_timestamp": "2014-06-03T15:02:52Z",
>> "build_snapshot": false,
>> "lucene_version": "4.8"
>> },
>> "tagline": "You Know, for Search"
>> }
>> 
>> {
>> "cluster_name": "es",
>> "status": "yellow",
>> "timed_out": false,
>> "number_of_nodes": 1,
>> "number_of_data_nodes": 1,
>> "active_primary_shards": 77,
>> "active_shards": 77,
>> "relocating_shards": 0,
>> "initializing_shards": 0,
>> "unassigned_shards": 77
>> }
>> 
>> Any ideas how to fix?
>> -- 
>> 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/66c8cfe9-513b-4e0e-9f0b-17cb3b31041a%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/9881174a-b4d7-4694-9dea-049540d1ecf5%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/BEC63D72-9298-4972-A0B3-D05B61900B4B%40pilato.fr.
For more options, visit https://groups.google.com/d/optout.

Re: Upgrade to 1.2.1, now broken and status yellow

2014-06-14 Thread Justin

Kibana is showing: Error Could not find Logstash. If you are using a proxy, 
ensure it is configured correctly which used to work with 1.2.0.

The dashboard is stored in ES.

On Saturday, June 14, 2014 1:02:28 AM UTC-7, David Pilato wrote:
>
> Why do you think there is something wrong?
>
> It looks like ok for a one node cluster.
>
> --
> David ;-)
> Twitter : @dadoonet / @elasticsearchfr / @scrutmydocs
>
> Le 14 juin 2014 à 09:21, Justin > a 
> écrit :
>
> Just tried to upgrade to 1.2.1 from 1.2.0 running on a single server. I 
> stopped it, did the upgrade and started ES again. However, now it is 
> showing status yellow and not storing any documents:
>
> {"status": 200,"name": "Dead Girl","version": {"number": "1.2.1","
> build_hash": "6c95b759f9e7ef0f8e17f77d850da43ce8a4b364","build_timestamp
> ": "2014-06-03T15:02:52Z","build_snapshot": false,"lucene_version": "4.8"}
> ,"tagline": "You Know, for Search"}
>
> {"cluster_name": "es","status": "yellow","timed_out": false,"
> number_of_nodes": 1,"number_of_data_nodes": 1,"active_primary_shards": 77,
> "active_shards": 77,"relocating_shards": 0,"initializing_shards": 0,"
> unassigned_shards": 77}
>
> Any ideas how to fix?
>
> -- 
> 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/66c8cfe9-513b-4e0e-9f0b-17cb3b31041a%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/9881174a-b4d7-4694-9dea-049540d1ecf5%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: Upgrade to 1.2.1, now broken and status yellow

2014-06-14 Thread David Pilato

Why do you think there is something wrong?

It looks like ok for a one node cluster.

--
David ;-)
Twitter : @dadoonet / @elasticsearchfr / @scrutmydocs

> Le 14 juin 2014 à 09:21, Justin  a écrit :
> 
> Just tried to upgrade to 1.2.1 from 1.2.0 running on a single server. I 
> stopped it, did the upgrade and started ES again. However, now it is showing 
> status yellow and not storing any documents:
> 
> {
> "status": 200,
> "name": "Dead Girl",
> "version": {
> "number": "1.2.1",
> "build_hash": "6c95b759f9e7ef0f8e17f77d850da43ce8a4b364",
> "build_timestamp": "2014-06-03T15:02:52Z",
> "build_snapshot": false,
> "lucene_version": "4.8"
> },
> "tagline": "You Know, for Search"
> }
> 
> {
> "cluster_name": "es",
> "status": "yellow",
> "timed_out": false,
> "number_of_nodes": 1,
> "number_of_data_nodes": 1,
> "active_primary_shards": 77,
> "active_shards": 77,
> "relocating_shards": 0,
> "initializing_shards": 0,
> "unassigned_shards": 77
> }
> 
> Any ideas how to fix?
> -- 
> 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/66c8cfe9-513b-4e0e-9f0b-17cb3b31041a%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/B667A3D9-D45E-49D2-A3B7-0CDF05627939%40pilato.fr.
For more options, visit https://groups.google.com/d/optout.

Upgrade to 1.2.1, now broken and status yellow

2014-06-14 Thread Justin

Just tried to upgrade to 1.2.1 from 1.2.0 running on a single server. I 
stopped it, did the upgrade and started ES again. However, now it is 
showing status yellow and not storing any documents:

{"status": 200,"name": "Dead Girl","version": {"number": "1.2.1","build_hash
": "6c95b759f9e7ef0f8e17f77d850da43ce8a4b364","build_timestamp": "
2014-06-03T15:02:52Z","build_snapshot": false,"lucene_version": "4.8"},"
tagline": "You Know, for Search"}

{"cluster_name": "es","status": "yellow","timed_out": false,"number_of_nodes
": 1,"number_of_data_nodes": 1,"active_primary_shards": 77,"active_shards": 
77,"relocating_shards": 0,"initializing_shards": 0,"unassigned_shards": 77}

Any ideas how to fix?

-- 
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/66c8cfe9-513b-4e0e-9f0b-17cb3b31041a%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

aliases by bulk requests

Re: Extremely Simple Java Request

Re: Deleteing index times out

Re: Help needed: CentOS ES-Logstash-Kibana running, but 0 docs, 0 indices

Re: Deleteing index times out

[ANN] Elasticsearch syslog plugin

Re: Interesting Issue

Re: does document database means denormalize

Re: Interesting Issue

Re: Interesting Issue

Re: Interesting Issue

Deleteing index times out

Re: Interesting Issue

Interesting Issue

Re: Upgrade to 1.2.1, now broken and status yellow

Re: Upgrade to 1.2.1, now broken and status yellow

Re: Upgrade to 1.2.1, now broken and status yellow

Re: Upgrade to 1.2.1, now broken and status yellow

Help needed: CentOS ES-Logstash-Kibana running, but 0 docs, 0 indices

Re: Upgrade to 1.2.1, now broken and status yellow

Re: Upgrade to 1.2.1, now broken and status yellow

Re: Upgrade to 1.2.1, now broken and status yellow

Re: Upgrade to 1.2.1, now broken and status yellow

Upgrade to 1.2.1, now broken and status yellow

24 matches

Site Navigation

Mail list logo

Footer information