# Retention lease background sync failed - help understand this log

**URL:** <https://discuss.elastic.co/t/retention-lease-background-sync-failed-help-understand-this-log/358334>\
**Category:** Elasticsearch\
**Created:** [April 27, 2024, 7:44am UTC](https://discuss.elastic.co/t/retention-lease-background-sync-failed-help-understand-this-log/358334 "2024-04-27T07:44:46Z")\
**Posts on this page:** 12\
**Page:** 1

<div class="post-metadata">

**Author:** ![Vikram\_R](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/vikram_r/32/127919_2.png) [@Vikram\_R](https://discuss.elastic.co/u/Vikram_R)\
**Post date:** [April 27, 2024, 7:44am UTC](https://discuss.elastic.co/t/retention-lease-background-sync-failed-help-understand-this-log/358334/1 "2024-04-27T07:44:46Z")

</div>

Hi Guys,

New to this technology, I've tried to use elasticsearch self-managed for our application in our organization.

I'm facing this "retention lease background sync failed" issue for quite some time.  
I tried to get to understand about this log, but couldn't get an insight from this log.

 ![image](https://us1.discourse-cdn.com/elastic/original/3X/5/d/5d1416f9b8434176bc6b74c3e44c6a92f6fc08cb.png)

Help me understand what was the issue in this concept and provide an solution to understand this log better.

As this was in testing phase, I had to delete entire ES resource and re-deploy from scratch due to this issue. I know this won't solve the issue yet I did so to debug if it was from uploading huge data or to find out the real cause.

Note: I've deployed the Elasticsearch and kibana in the GKE - GCP (self-managed). The log uploaded is also from the pod log of ES in GKE.

---

<div class="post-metadata">

**Author:** ![Christian\_Dahlqvist](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/christian_dahlqvist/32/4617_2.png) [@Christian\_Dahlqvist](https://discuss.elastic.co/u/Christian_Dahlqvist)\
**Post date:** [April 27, 2024, 8:20am UTC](https://discuss.elastic.co/t/retention-lease-background-sync-failed-help-understand-this-log/358334/2 "2024-04-27T08:20:00Z")

</div>

Which version of Elasticsearch are you using?

---

<div class="post-metadata">

**Author:** ![Vikram\_R](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/vikram_r/32/127919_2.png) [@Vikram\_R](https://discuss.elastic.co/u/Vikram_R)\
**Post date:** [April 29, 2024, 5:16am UTC](https://discuss.elastic.co/t/retention-lease-background-sync-failed-help-understand-this-log/358334/3 "2024-04-29T05:16:51Z")

</div>

**Elasticsearch version** : 8.12.0  
Referred and used the documentation - [self-managed elasticsearch](https://www.elastic.co/guide/en/cloud-on-k8s/current/k8s-deploy-elasticsearch.html)

FYI: During the process the we faced health check issue in GCP GKE Ingress LB.  
So modified the installing definition:

 ![image](https://us1.discourse-cdn.com/elastic/original/3X/9/e/9e5c2317dd2e6b152bc4ddcfbe9b0170502fe7bb.png)

Allowed anonymous which resolved this issue. I understand this could be potential security but we are using for testing purposes currently. So we currently ignored this warning.

---

<div class="post-metadata">

**Author:** ![Vikram\_R](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/vikram_r/32/127919_2.png) [@Vikram\_R](https://discuss.elastic.co/u/Vikram_R)\
**Post date:** [April 29, 2024, 7:21am UTC](https://discuss.elastic.co/t/retention-lease-background-sync-failed-help-understand-this-log/358334/4 "2024-04-29T07:21:26Z")

</div>

Using anonymous user resolved only the 'health check' issue faced during the process in GCP LB.

---

<div class="post-metadata">

**Author:** ![Vikram\_R](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/vikram_r/32/127919_2.png) [@Vikram\_R](https://discuss.elastic.co/u/Vikram_R)\
**Post date:** [May 2, 2024, 5:22am UTC](https://discuss.elastic.co/t/retention-lease-background-sync-failed-help-understand-this-log/358334/5 "2024-05-02T05:22:43Z")

</div>

@Christian_Dahlqvist Do you have any idea about this log ?

---

<div class="post-metadata">

**Author:** ![Christian\_Dahlqvist](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/christian_dahlqvist/32/4617_2.png) [@Christian\_Dahlqvist](https://discuss.elastic.co/u/Christian_Dahlqvist)\
**Post date:** [May 2, 2024, 6:29am UTC](https://discuss.elastic.co/t/retention-lease-background-sync-failed-help-understand-this-log/358334/6 "2024-05-02T06:29:01Z")

</div>

The first entry says it is not able to elect a master. What is the size and configuration of the cluster?

What is the output of the [cat nodes API](https://www.elastic.co/guide/en/elasticsearch/reference/8.13/cat-nodes.html)?

---

<div class="post-metadata">

**Author:** ![Vikram\_R](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/vikram_r/32/127919_2.png) [@Vikram\_R](https://discuss.elastic.co/u/Vikram_R)\
**Post date:** [May 2, 2024, 7:37am UTC](https://discuss.elastic.co/t/retention-lease-background-sync-failed-help-understand-this-log/358334/7 "2024-05-02T07:37:51Z")

</div>

@Christian_Dahlqvist

I've just followed the exact configuration given in the documentation made no changes in the size and memory.

From the yaml configuration hosted in GKE:  
 ![image](https://us1.discourse-cdn.com/elastic/original/3X/a/a/aa3a3fa70d21028bafa18a3ea8a1c29fa1559881.png)

---

<div class="post-metadata">

**Author:** ![Christian\_Dahlqvist](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/christian_dahlqvist/32/4617_2.png) [@Christian\_Dahlqvist](https://discuss.elastic.co/u/Christian_Dahlqvist)\
**Post date:** [May 2, 2024, 7:41am UTC](https://discuss.elastic.co/t/retention-lease-background-sync-failed-help-understand-this-log/358334/8 "2024-05-02T07:41:35Z")

</div>

How many nodes does the cluster have?

Also please do not post images of text as they can be very hard to read and can not be searched.

---

<div class="post-metadata">

**Author:** ![Vikram\_R](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/vikram_r/32/127919_2.png) [@Vikram\_R](https://discuss.elastic.co/u/Vikram_R)\
**Post date:** [May 2, 2024, 8:23am UTC](https://discuss.elastic.co/t/retention-lease-background-sync-failed-help-understand-this-log/358334/9 "2024-05-02T08:23:25Z")

</div>

I guess one. That is the count got from the official documentation and used the same.

---

<div class="post-metadata">

**Author:** ![Vikram\_R](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/vikram_r/32/127919_2.png) [@Vikram\_R](https://discuss.elastic.co/u/Vikram_R)\
**Post date:** [May 6, 2024, 7:00am UTC](https://discuss.elastic.co/t/retention-lease-background-sync-failed-help-understand-this-log/358334/10 "2024-05-06T07:00:25Z")

</div>

@Christian_Dahlqvist Any updates, regarding ?

---

<div class="post-metadata">

**Author:** ![Christian\_Dahlqvist](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/christian_dahlqvist/32/4617_2.png) [@Christian\_Dahlqvist](https://discuss.elastic.co/u/Christian_Dahlqvist)\
**Post date:** [May 6, 2024, 7:32am UTC](https://discuss.elastic.co/t/retention-lease-background-sync-failed-help-understand-this-log/358334/11 "2024-05-06T07:32:10Z")

</div>

No, i do not know why this would happen with just one node, so will need to leave it for someone else.

---

<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:** [June 3, 2024, 7:32am UTC](https://discuss.elastic.co/t/retention-lease-background-sync-failed-help-understand-this-log/358334/12 "2024-06-03T07:32:13Z")

</div>

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