# Elasticsearch on Google Compute - Network issues and shard lock fails

**URL:** <https://discuss.elastic.co/t/elasticsearch-on-google-compute-network-issues-and-shard-lock-fails/145459>\
**Category:** Elasticsearch\
**Created:** [August 21, 2018, 9:03pm UTC](https://discuss.elastic.co/t/elasticsearch-on-google-compute-network-issues-and-shard-lock-fails/145459 "2018-08-21T21:03:19Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![eranhirs](https://avatars.discourse-cdn.com/v4/letter/e/e47774/32.png) [@eranhirs](https://discuss.elastic.co/u/eranhirs)\
**Post date:** [August 21, 2018, 9:03pm UTC](https://discuss.elastic.co/t/elasticsearch-on-google-compute-network-issues-and-shard-lock-fails/145459/1 "2018-08-21T21:03:19Z")

</div>

Some tech background - I have 5 nodes in the cluster, all are configured as both master and data nodes, around 2TB of data, all of them run with docker.

I just moved my cluster from AWS EC2 to Google Compute, and looking at the logs it seems there are constant network issues.

It starts with the error:

> master left (reason = failed to ping, tried [3] times, each with maximum [30s] timeout), current nodes: nodes:

Checking the logs it doesn't seem like they are restarting (running with docker), just disconnecting and reconnecting.

After a few seconds they are back online, but when they are back online I get the error

> obtaining shard lock timed out after 5000ms

Which causes them to forget they have data if I understand correctly.

When I look at the master node, I see that server specifically disconnecting and reconnecting in the logs, so I think the problem is with that server.

1. What should I check?
2. Is there any hotfix to improve the time it takes to reconnect?

---

<div class="post-metadata">

**Author:** ![eranhirs](https://avatars.discourse-cdn.com/v4/letter/e/e47774/32.png) [@eranhirs](https://discuss.elastic.co/u/eranhirs)\
**Post date:** [August 23, 2018, 7:18am UTC](https://discuss.elastic.co/t/elasticsearch-on-google-compute-network-issues-and-shard-lock-fails/145459/2 "2018-08-23T07:18:22Z")

</div>

I have some more information

> master left (reason = failed to ping, tried [3] times, each with maximum [30s] timeout), current nodes: nodes:

This is weird that for 180 seconds it couldn't ping, because only 3 seconds after the disconnect it already reconnects.

In these 3 seconds, the master node receives the message

> "mark copy as stale"

Which I guess causes the Shard Lock error.

---

<div class="post-metadata">

**Author:** ![system](https://us1.discourse-cdn.com/elastic/original/3X/1/a/1ac57faf039f6b580b3f104ef42a2a89e41014de.png) [@system](https://discuss.elastic.co/u/system)\
**Post date:** [September 20, 2018, 7:25am UTC](https://discuss.elastic.co/t/elasticsearch-on-google-compute-network-issues-and-shard-lock-fails/145459/3 "2018-09-20T07:25:26Z")

</div>

Closed on September 20, 2018, 7:25am UTC

This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.