I'm experiencing what I believe may be a bug in the elasticsearch
recovery process. That is, when a node goes down (either from load or
otherwise) and I bring it back up, one or more shards go missing. From
the logs it seems that when the data node is brought back up it is
given an empty shard thereby overwriting the shard it previously had.
I'm using elasticsearch-0.13.0 with replicas == 1 on all indices.
I'm experiencing what I believe may be a bug in the elasticsearch
recovery process. That is, when a node goes down (either from load or
otherwise) and I bring it back up, one or more shards go missing. From
the logs it seems that when the data node is brought back up it is
given an empty shard thereby overwriting the shard it previously had.
I'm using elasticsearch-0.13.0 with replicas == 1 on all indices.
Happened on Friday last week and I can't seem to find the right set of
log files. When it happens again I'll send you more detailed notes +
logs. Thanks,
I'm experiencing what I believe may be a bug in the elasticsearch
recovery process. That is, when a node goes down (either from load or
otherwise) and I bring it back up, one or more shards go missing. From
the logs it seems that when the data node is brought back up it is
given an empty shard thereby overwriting the shard it previously had.
I'm using elasticsearch-0.13.0 with replicas == 1 on all indices.
Great, thanks!. The local gateway allocation has been improved in upcoming
0.14 for some cases where this might happen, but they should be very rare,
so wondered if you hit that...
Happened on Friday last week and I can't seem to find the right set of
log files. When it happens again I'll send you more detailed notes +
logs. Thanks,
I'm experiencing what I believe may be a bug in the elasticsearch
recovery process. That is, when a node goes down (either from load or
otherwise) and I bring it back up, one or more shards go missing. From
the logs it seems that when the data node is brought back up it is
given an empty shard thereby overwriting the shard it previously had.
I'm using elasticsearch-0.13.0 with replicas == 1 on all indices.
Great, thanks!. The local gateway allocation has been improved in upcoming
0.14 for some cases where this might happen, but they should be very rare,
so wondered if you hit that...
Happened on Friday last week and I can't seem to find the right set of
log files. When it happens again I'll send you more detailed notes +
logs. Thanks,
I'm experiencing what I believe may be a bug in the elasticsearch
recovery process. That is, when a node goes down (either from load or
otherwise) and I bring it back up, one or more shards go missing. From
the logs it seems that when the data node is brought back up it is
given an empty shard thereby overwriting the shard it previously had.
I'm using elasticsearch-0.13.0 with replicas == 1 on all indices.
--jacob
So, I packaged all the logs and made them available here:
Great, thanks!. The local gateway allocation has been improved in
upcoming
0.14 for some cases where this might happen, but they should be very
rare,
so wondered if you hit that...
Happened on Friday last week and I can't seem to find the right set of
log files. When it happens again I'll send you more detailed notes +
logs. Thanks,
I'm experiencing what I believe may be a bug in the elasticsearch
recovery process. That is, when a node goes down (either from load
or
otherwise) and I bring it back up, one or more shards go missing.
From
the logs it seems that when the data node is brought back up it is
given an empty shard thereby overwriting the shard it previously
had.
I'm using elasticsearch-0.13.0 with replicas == 1 on all indices.
--jacob
So, I packaged all the logs and made them available here:
Great, thanks!. The local gateway allocation has been improved in
upcoming
0.14 for some cases where this might happen, but they should be very
rare,
so wondered if you hit that...
Happened on Friday last week and I can't seem to find the right set of
log files. When it happens again I'll send you more detailed notes +
logs. Thanks,
I'm experiencing what I believe may be a bug in the elasticsearch
recovery process. That is, when a node goes down (either from load
or
otherwise) and I bring it back up, one or more shards go missing.
From
the logs it seems that when the data node is brought back up it is
given an empty shard thereby overwriting the shard it previously
had.
I'm using elasticsearch-0.13.0 with replicas == 1 on all indices.
--jacob
So, I packaged all the logs and made them available here:
After adding more machines a (repair?) started and barraged the new
machines with data. Then the cluster went yellow and shortly after
everything stopped responding.
Great, thanks!. The local gateway allocation has been improved in
upcoming
0.14 for some cases where this might happen, but they should be very
rare,
so wondered if you hit that...
Happened on Friday last week and I can't seem to find the right set of
log files. When it happens again I'll send you more detailed notes +
logs. Thanks,
I'm experiencing what I believe may be a bug in the elasticsearch
recovery process. That is, when a node goes down (either from load
or
otherwise) and I bring it back up, one or more shards go missing.
From
the logs it seems that when the data node is brought back up it is
given an empty shard thereby overwriting the shard it previously
had.
I'm using elasticsearch-0.13.0 with replicas == 1 on all indices.
--jacob
So, I packaged all the logs and made them available here:
After adding more machines a (repair?) started and barraged the new
machines with data. Then the cluster went yellow and shortly after
everything stopped responding.
Great, thanks!. The local gateway allocation has been improved in
upcoming
0.14 for some cases where this might happen, but they should be very
rare,
so wondered if you hit that...
Happened on Friday last week and I can't seem to find the right set of
log files. When it happens again I'll send you more detailed notes +
logs. Thanks,
I'm experiencing what I believe may be a bug in the elasticsearch
recovery process. That is, when a node goes down (either from load
or
otherwise) and I bring it back up, one or more shards go missing.
From
the logs it seems that when the data node is brought back up it is
given an empty shard thereby overwriting the shard it previously
had.
I'm using elasticsearch-0.13.0 with replicas == 1 on all indices.
--jacob
So, I packaged all the logs and made them available here:
After adding more machines a (repair?) started and barraged the new
machines with data. Then the cluster went yellow and shortly after
everything stopped responding.
Great, thanks!. The local gateway allocation has been improved in
upcoming
0.14 for some cases where this might happen, but they should be very
rare,
so wondered if you hit that...
Happened on Friday last week and I can't seem to find the right set of
log files. When it happens again I'll send you more detailed notes +
logs. Thanks,
I'm experiencing what I believe may be a bug in the elasticsearch
recovery process. That is, when a node goes down (either from load
or
otherwise) and I bring it back up, one or more shards go missing.
From
the logs it seems that when the data node is brought back up it is
given an empty shard thereby overwriting the shard it previously
had.
I'm using elasticsearch-0.13.0 with replicas == 1 on all indices.
--jacob
So, I packaged all the logs and made them available here:
After adding more machines a (repair?) started and barraged the new
machines with data. Then the cluster went yellow and shortly after
everything stopped responding.
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.