Moleculer Retry and Fallback Policies Without Duplicate Side Effects
A practical guide to Moleculer action-level retries and fallbacks: make transient failures recoverable without duplicating writes or hiding outages.
Loading…
ReadMeFeed / Community knowledge
#retry-policy
Real questions. Useful conversations. Find the people who know your stack.
Handle Flaky APIs in Ballerina with Declarative HTTP Client Retry
Use Ballerina 2.0’s declarative @retry annotation to add robust retry logic to your HTTP client. Combine with a circuit‑breaker, test against a mock server, and consider latency and idempotency trade‑offs.
ballerinaConfiguring Hyper-V Replica Retry Policy to Prevent Duplicate Write Operations
The goal is to configure Hyper‑V Replica so that a retry of a failed replication pass does not cause the same write to be applied twice on the replica VM. When a replication pass encounters a transient network error, Hyper‑V may retry the transfer of the changed blocks. If the retry resends blocks that were already partially committed, the replica could see
Duplicate rows after Kubeflow Pipelines component retry
Goal: configure a Kubeflow Pipelines component retry policy without duplicating writes to external storage such as SQL, S3, or GCS. Assumes Kubeflow Pipelines SDK v2 with the default Argo-based orchestrator. The KFP orchestrator restarts the container on retry but does not roll back side effects already committed by the previous attempt. Idempotency must the
kubeflowWhat webhook retry backoff schedule does Jira Cloud apply before permanent failure?
Context Jira Cloud delivers webhooks with an exponential-backoff retry policy documented only at a high level: retries continue for up to 14 days. The exact backoff intervals, jitter implementation, and the criteria that classify a delivery as permanently failed are not published. Goal Determine whether an integration can rely on deterministic retry timing f
jiraWebhook Delivery Retry Policy: Undefined Default Retry Count
Webhook Delivery Retry Policy When Harbor sends a webhook on an image push, the logs record a "Webhook failed, retrying" message. However, the documentation does not specify how many times Harbor will retry a failed delivery or what exponential back-off strategy it applies. This uncertainty can conceal a downstream failure where a webhook that never succeeds
harborPub/Sub subscription retry policy and duplicate write prevention
Pub/Sub subscription retry policy controls minimum and maximum backoff for redelivery after nack or ack deadline expiry. The configuration affects delivery timing, not delivery semantics. The documented delivery guarantee is at-least-once. The API surfaces messageId per delivery, but there is no built-in deduplication window or correlation identifier provide
googleFusion 5.x Index Pipeline Retries Require Explicit Idempotency Keys for Deduplication
Background Fusion 5.x index pipelines support configurable retry policies on stages such as the Solr Indexer, with exponential backoff and maximum attempt settings. When a stage fails transiently, Fusion retries the operation per its policy. Without idempotency controls, a retry can re-send the same document, causing duplicate indexed copies in Solr. Current
Connection pool limits causing intermittent span export failures in Jaeger
When Jaeger’s client is subjected to high‑concurrency workloads, the HTTP/UDP connection pool can reach its configured maximum (typically 50 concurrent connections). Once exhausted, the exporter emits intermittent connection pool exhausted warnings, leading to silent span drops when the internal buffer (default size 1000) overflows. Key constraints to consid
jaegertracing