#community-help

Resolving `circuit breaker is open` Error with Go in TS Cloud

TLDR Morgan was seeking help for a Go error message when upserting in TS cloud. Jason suggested increasing the client side timeout and left the circuit breaker timeout unchanged.

22mo

Join the chat

Nov 29, 2021 (22 months ago)

Photo of md5-9af47d330848eae988a5f9cc03e413f1

Morgan

10:52 PM

Hi we got this error with GO when upserting a document to TS cloud. circuit breaker is open. can anyone give more context on that?

Photo of md5-8813087cccc512313602b6d9f9ece19f

Jason

10:55 PM

Morgan This looks like due to too many failed or incomplete requests: https://github.com/typesense/typesense-go/tree/11841f46f60505226250e53391693f879bfd5050/typesense/api/circuit

10:56

Jason

10:56 PM

Could you try increasing the client side timeout, to make sure the batch import call has sufficient time to complete

Morgan

11:11 PM

Thanks Jason, that was very helpful. So the likely reason is the request sent to TS server was closed before it can respond, correct? that way, by increasing client side timeout, you mean ConnectionTimeout?

Jason

11:12 PM

Yup, that's correct

Morgan

11:13 PM

Great, thanks. Do you think I should also increase WithCircuitBreakerTimeout?

Jason

11:33 PM

It looks like that might control the time between retries... Ideally we want the very first request to succeed and not timeout. So I'd leave circuit breaker timeout as is.

Typesense

Lightning-fast, open source search engine for everyone | Knowledge Base powered by Struct.AI

Indexed 2764 threads (79% resolved)

Join Our Community Manage subscription

Similar Threads

Troubleshooting Indexing Duration in Typesense Import

Alan asked about lengthy indexing times for importing documents to Typesense. Jason suggested various potential causes, including network connectivity and system resources. They later identified the problem to be an error in Alan's code.

11mo

Inquiry and Troubleshooting of Typesense Cloud

Alex is addressing memory usage, import, and bandwidth issues with Typesense Cloud. Jason helped determine the issues and offered solutions, including in-place upgrades and potential use of Cloudflare for security.

22mo

Handling Kinesis Stream Event Batching with Typesense

Dui had questions about how to handle Kinesis stream events with Typesense. Kishore Nallan suggested using upsert mode for creation/update and differentiating with logical deletion. After various discussions including identifying and resolving a bug, they finalized to introduce an `emplace` action in Typesense v0.23.

20mo