Skip to:

  1. Skip to Jira Navigation
  2. Skip to Side Navigation
  3. Skip to Main Content

Add ability to increase timeout for the CLONE operation

Description

When a new replica (or previous one restarted) is start the CLONE operation is started. Although if data is big enough it might be not enough time for it which lead to the replica `CrashLoopBackOff` with the logs from the bootstrap:

The problem seems is that readTimeout is set to 10 seconds for the sql.Open configuration. I tried to build a test image with the readTimeout set to 10 minutes and it works as expected, we may see that CLONE longer than 10s does not produce error anymore:

I’d like to fix it but seems hard-coding the readTimeout value is not the best option? If so what is the best way to solve it? New configuration option like clone_timeout or mysql.clone_timeout, what do you think?

Environment

None

Activity

Show:

Aaditya Dubey February 3, 2025 at 10:46 AM

Hi

Thank you for the report and feedback.
Sending the concern to our engineering team for further review and updates.

Details

Assignee

Reporter

Needs QA

Yes

Story Points

Sprint

Fix versions

Affects versions

Priority

Smart Checklist

Created January 28, 2025 at 12:21 PM
Updated March 7, 2025 at 8:48 AM
Configure