Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Support the new read timeout setting from Medusa #1353

Open
adejanovski opened this issue Jun 14, 2024 · 1 comment
Open

Support the new read timeout setting from Medusa #1353

adejanovski opened this issue Jun 14, 2024 · 1 comment

Comments

@adejanovski
Copy link
Contributor

adejanovski commented Jun 14, 2024

In this PR, we're adding a new read_timeout settings which should be exposed in our CRDs.

### Definition of Done
- [ ] the `read_timeout` setting is added to the [Storage](https://github.com/k8ssandra/k8ssandra-operator/blob/main/apis/medusa/v1alpha1/medusa_types.go#L28) struct and mapped appropriately in medusa.ini

┆Issue is synchronized with this Jira Story by Unito
┆Issue Number: K8OP-17

@mlallaouret
Copy link

Hello @adejanovski

Is there some information about when it will be treated ?
It's blocking the upgrade of the k8ssandra operator for us as since the PR merged on medusa side was integrated in the operator, it makes the restoration process of the cluster fail because of big files that cannot be downloaded.
I already posted a comment on the merge PR on medusa side (thelastpickle/cassandra-medusa#763 (comment)) as I do not know what is the best solution on this issue: Rollback the read_timeout update for gcp case on medusa or implement the support of the timeout on the operator side.

Thanks in advance for you answer.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
No open projects
Status: No status
Development

No branches or pull requests

2 participants