Open dylancaponi opened 1 year ago
Hey, thanks for the issue! We throw an unreachable host error because after a timeout error, we will try an other host (Algolia's API offers multiple), then if there's no host left we end up in an AlgoliaUnreachableHostException
I can however confirm that it can be misleading when doing large enough operations
I'm now seeing this error regardless how big I set the readTimeout. I've triple checked App ID and API Key.
Oh, you also get this message if the index does not exist. I would expect index does not Exist
rather than an unreachable hosts error...
Description
Client throws
algoliasearch.exceptions.AlgoliaUnreachableHostException
: Unreachable hosts duringreplace_all_objects
operation. The issue was not that hosts were unreachable but that the operation was timing out. I fixed the problem by settingreadTimeout
to 100:A timeout should produce a timeout error. Unreachable is misleading.
Steps To Reproduce
See description. Use
replace_all_objects
on a sufficiently big index. Mine was 6393 rows and 10+ columns some with significant text blocks.