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

Couchbase sometimes fails rename on startup. #7049

Open
wants to merge 2 commits into
base: main
Choose a base branch
from

Conversation

mikereiche
Copy link

This will retry the rename after sleeping for 10 seconds up to 6 times.

Closes #6938.

This will retry the rename after sleeping for 10 seconds up to 6 times.

Closes testcontainers#6938.
@mikereiche mikereiche requested a review from a team as a code owner May 22, 2023 23:50
@chedim
Copy link

chedim commented Sep 28, 2023

Any updates on this?

@mgroves
Copy link

mgroves commented Dec 7, 2023

This looks very similar to the issue addressed in testcontainers-dotnet: testcontainers/testcontainers-dotnet#1062

@eddumelendez
Copy link
Member

Hi, is the Couchbase nature to take that long to perform that operation? Sorry, but I think I am missing something regarding to the context where it fails. It could be not enough resources when parallelizing tests?

Other alternative:

  • Is there a config file that can be copied to the container and perform all those operations at once?

Although, it could be the only way to fix it I kind of disagree with the solution given that the worst case scenario is 60 seconds, which will not provide a good experience to users. My understanding is that proposal has been done because it is actually possible but still could fail.

I would like to understand more about it and hear other alternatives if any.

@eddumelendez
Copy link
Member

could it be that those operations are executed when the container is starting and should be when the container is started instead?

@ldoguin
Copy link

ldoguin commented Jul 26, 2024

Hello everyone, @eddumelendez coming back to this a bit late, but yes most setup operations are asynchronous, must be done in order, so we have to wait, and have no other way right now.
The other solutions would be to provide a pre-configured. But it's less flexible and not necessary what users want to test.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

[Bug] Test Container has issue while starting
5 participants