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.
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.
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.
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.
Install a visual monitoring plugin like kopf and ElasticHQ, you will be
able to see which shards are unassigned.
However I think you may have replicas set, which, given you only have one
one, will always result in a yellow state as the cluster cannot assign
replicas to another node.
You should also upgrade ES to a newer version if you can
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.
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.
Install a visual monitoring plugin like kopf and ElasticHQ, you will be
able to see which shards are unassigned.
However I think you may have replicas set, which, given you only have one
one, will always result in a yellow state as the cluster cannot assign
replicas to another node.
You should also upgrade ES to a newer version if you can
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.
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.
It could also be the elasticsearch integrated output in ES, which adds the
LS instance as a client node to the cluster.
And you probably don't want to kill that.
Install a visual monitoring plugin like kopf and ElasticHQ, you will be
able to see which shards are unassigned.
However I think you may have replicas set, which, given you only have one
one, will always result in a yellow state as the cluster cannot assign
replicas to another node.
You should also upgrade ES to a newer version if you can
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.
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.
Mark are you talking about upgrading to the lastest 0.9 or to 1.x.x? Still
waiting on a good method to go to the lastest 1.x in ES with out messing up
a bunch of stuff. Still in development but dont want to loose my data.
I think you are right about the replica set, I read about a setting I need
to change in elasticsearch.yml, I will see if I can find that doc. Also
will install kopf. Thanks again for the help!
On Friday, May 30, 2014 12:18:47 AM UTC-4, Mark Walkom wrote:
It could also be the elasticsearch integrated output in ES, which adds the
LS instance as a client node to the cluster.
And you probably don't want to kill that.
Install a visual monitoring plugin like kopf and ElasticHQ, you will be
able to see which shards are unassigned.
However I think you may have replicas set, which, given you only have
one one, will always result in a yellow state as the cluster cannot assign
replicas to another node.
You should also upgrade ES to a newer version if you can
On 29 May 2014 23:45, Jason Weber <dave...@gmail.com <javascript:>>
wrote:
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.
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.
Mark are you talking about upgrading to the lastest 0.9 or to 1.x.x? Still
waiting on a good method to go to the lastest 1.x in ES with out messing up
a bunch of stuff. Still in development but dont want to loose my data.
I think you are right about the replica set, I read about a setting I need
to change in elasticsearch.yml, I will see if I can find that doc. Also
will install kopf. Thanks again for the help!
On Friday, May 30, 2014 12:18:47 AM UTC-4, Mark Walkom wrote:
It could also be the elasticsearch integrated output in ES, which adds
the LS instance as a client node to the cluster.
And you probably don't want to kill that.
Install a visual monitoring plugin like kopf and ElasticHQ, you will be
able to see which shards are unassigned.
However I think you may have replicas set, which, given you only have
one one, will always result in a yellow state as the cluster cannot assign
replicas to another node.
You should also upgrade ES to a newer version if you can
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.
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.
Mark are you talking about upgrading to the lastest 0.9 or to 1.x.x?
Still waiting on a good method to go to the lastest 1.x in ES with out
messing up a bunch of stuff. Still in development but dont want to loose my
data.
I think you are right about the replica set, I read about a setting I
need to change in elasticsearch.yml, I will see if I can find that doc.
Also will install kopf. Thanks again for the help!
On Friday, May 30, 2014 12:18:47 AM UTC-4, Mark Walkom wrote:
It could also be the elasticsearch integrated output in ES, which adds
the LS instance as a client node to the cluster.
And you probably don't want to kill that.
Install a visual monitoring plugin like kopf and ElasticHQ, you will
be able to see which shards are unassigned.
However I think you may have replicas set, which, given you only have
one one, will always result in a yellow state as the cluster cannot assign
replicas to another node.
You should also upgrade ES to a newer version if you can
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.
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.
--
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.
Apache, Apache Lucene, Apache Hadoop, Hadoop, HDFS and the yellow elephant
logo are trademarks of the
Apache Software Foundation
in the United States and/or other countries.
