I rebooted several times and I believe its collecting the correct data now.
I still show 520 unassigned shards, but its collecting all my logs now. Is
this something I can use the redirect command for to assign it to a new
index?
Jason
On Tuesday, May 27, 2014 11:39:49 AM UTC-4, Jason Weber wrote:
>
> Could someone walk me through getting my cluster up and running. Came in
> from long weekend and my cluster was red status, I am showing a lot of
> unassigned shards.
>
> jmweber@MIDLOG01:/var/log/logstash$ curl
> localhost:9200/_cluster/health?pretty
> {
> "cluster_name" : "midlogcluster",
> "status" : "red",
> "timed_out" : false,
> "number_of_nodes" : 2,
> "number_of_data_nodes" : 1,
> "active_primary_shards" : 512,
> "active_shards" : 512,
> "relocating_shards" : 0,
> "initializing_shards" : 0,
> "unassigned_shards" : 520
> }
>
>
> I am running ES 0.90.11
>
> LS and ES are on a single server, I only have 1 node, although it shows 2,
> I get yellow status normally, it works fine with that. But I am only
> collecting like 43 events per minute vs my usual 50K.
>
> I have seen several write ups but I seem to get a lot of no handler found
> for uri statements when I try to run them.
>
> Thanks,
> Jason
>
--
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/1307dd8d-411e-4690-a6d1-8e27ce26ecec%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
