Closed nparoski closed 1 year ago
Interesting thing i noticed just before it timed out
After stopping download
Also just now it failed while it was mesuring 15-19 Mbps
Hello @nparoski. Sorry for the inconvenience. From the error message, it looks to me the cloud instance is not in a running state. Can you double-check that, please?
@oluademola Double checked, it's in running state also it indexes some random amount of data e.g 61, 12, 32 before failing. There's total 101 that needs to be indexed.
Hi @nparoski, sorry for the delay. From what I understand, I am not sure this is related to meilisearch cloud. To narrow down the issue can you please confirm if you have any problem indexing directly to the cloud with cURL or Postman for example?
Hey @oluademola I'm thinking it's my router possibly? I was able to index everything from another laptop on different network without issues (same setup WSL 2) just failed again on my PC which uses ethernet cable. Switched to wifi (hotspot from my phone network) and it worked first time.
Hello @nparoski. It's possible that the timeout was due to a network problem. I also tried to replicate the issue, but couldn't. I believe this might not be an actual bug, but please feel free to inform us if you come across any other problems. Thanks!
I'm closing this due to a lack of news. Please reopen if needed!
Description When trying to index data on Meilisearch Cloud I always timeout after ceratin amount of data is indexed, first time I got this working is when I set timeout to 1000ms but now it's not working even after 60000ms.
When indexing outside of WSL 2 env it seems to be okay but it's not an option.Just set it up and tried outside of WSL 2, same thing doesn't work. Also I should add that this is inside of docker container.I am from Europe and even servers on Frankfurt / London fail. My upload is 20-30 MB/s and download about 200. Processor: AMD 5 5600x Ram: 16 GB
Screenshots or Logs
Environment (please complete the following information):