ES Cluster Restart Issue

Elastic Stack Elasticsearch
1

Hi Shay,

While restart my ES Cluster any one index get following error for
every time and the ES Cluster health was 'red' , specified Index
shards not initialized, so I could not able to access the index.

"[2011-03-25 22:59:59,925][WARN ][index.gateway.fs ]
[Boneyard] [database12][5]
failed to read commit point [commit-0]
java.lang.ArrayIndexOutOfBoundsException
[2011-03-25 22:59:59,925][WARN ][index.gateway.fs ] [Boneyard]
[database12][5]
failed to read commit point [commit-1]
java.io.IOException: No commit point data
at
org.elasticsearch.index.gateway.CommitPoints.fromXContent(CommitPoint
s.java:127)
at
org.elasticsearch.index.gateway.blobstore.BlobStoreIndexShardGateway.
recover(BlobStoreIndexShardGateway.java:372)
at org.elasticsearch.index.gateway.IndexShardGatewayService
$1.run(IndexS
hardGatewayService.java:144)
at java.util.concurrent.ThreadPoolExecutor
$Worker.runTask(ThreadPoolExec
utor.java:886)
at java.util.concurrent.ThreadPoolExecutor
$Worker.run(ThreadPoolExecutor
.java:908)
at java.lang.Thread.run(Thread.java:619)
[2011-03-25 22:59:59,925][WARN ][indices.cluster ] [Boneyard]
[database12][5]
failed to start shard
org.elasticsearch.index.gateway.IndexShardGatewayRecoveryException:
[database12][5] Co
mmit points exists but none could be loaded
at
org.elasticsearch.index.gateway.blobstore.BlobStoreIndexShardGateway.
recover(BlobStoreIndexShardGateway.java:380)
at org.elasticsearch.index.gateway.IndexShardGatewayService
$1.run(IndexS
hardGatewayService.java:144)
at java.util.concurrent.ThreadPoolExecutor
$Worker.runTask(ThreadPoolExec
utor.java:886)
at java.util.concurrent.ThreadPoolExecutor
$Worker.run(ThreadPoolExecutor
.java:908)
at java.lang.Thread.run(Thread.java:619)"

Every restart I have loss any one index in the ES cluster, so please
advice me to avoid this type of errors

Below I mentioned MY ES Cluster & Index details

ES Cluster - 3 Data Node and 1 No data Node

index:
number_of_shards : 6
number_of_replicas : 1

YML Setting

network :
host : 10.67.85.4

gateway:
type: fs
fs:
location: \dataserver\ElasticSearchGateway
indices:
memory:
index_buffer_size : 20%
index:
gateway:
snapshot_on_close: false
cluster:
name: threenode

http:
enabled: false

index:
number_of_shards : 6
number_of_replicas : 1

bootstrap:

mlockall : true"

Kindly do the needful

Thanks,

Katrinaa

2

Hiya

While restart my ES Cluster any one index get following error for
every time and the ES Cluster health was 'red' , specified Index
shards not initialized, so I could not able to access the index.

A few questions:

  • how are you running and restarting ES?
  • what version of ES are you using (because the restart API has
    been disabled in recent versions)
  • was your cluster 'green' before you restarted?
  • why are you using a shared gateway instead of the default
    local gateway?

ta

clint

3

Hi Clint,

Thanks for the Questions.

  1. ES Running in DOS Mode and restart using Ctrl+C
  2. Version No - 15.2
  3. Yes - Cluster health was 'Green'
  4. Gateway pointed to NAS, so I am using Network path

Thanks,

Katrinaa.

On Mar 26, 3:18 pm, Clinton Gormley clin...@iannounce.co.uk wrote:

Hiya

While restart my ES Cluster any one index get following error for
every time and the ES Cluster health was 'red' , specified Index
shards not initialized, so I could not able to access the index.

A few questions:

  • how are you running and restarting ES?
  • what version of ES are you using (because the restart API has
    been disabled in recent versions)
  • was your cluster 'green' before you restarted?
  • why are you using a shared gateway instead of the default
    local gateway?

ta

clint

4

You should see in the logging failures to load commit points. Can you gist those? (don't paste it into mails).
On Saturday, March 26, 2011 at 12:37 PM, Katrina K wrote:

Hi Clint,

Thanks for the Questions.

  1. ES Running in DOS Mode and restart using Ctrl+C
  2. Version No - 15.2
  3. Yes - Cluster health was 'Green'
  4. Gateway pointed to NAS, so I am using Network path

Thanks,

Katrinaa.

On Mar 26, 3:18 pm, Clinton Gormley clin...@iannounce.co.uk wrote:

Hiya

While restart my ES Cluster any one index get following error for
every time and the ES Cluster health was 'red' , specified Index
shards not initialized, so I could not able to access the index.

A few questions:

  • how are you running and restarting ES?
  • what version of ES are you using (because the restart API has
    been disabled in recent versions)
  • was your cluster 'green' before you restarted?
  • why are you using a shared gateway instead of the default
    local gateway?

ta

clint