Skip to content

Doesn't re-try with connection exception #45

Open
@minhtranes

Description

@minhtranes

Description:

I've been trying to evaluate the re-try capability of extension when save message into elasticsearch using elasticsearch sink. However, it seems doesn't support. Following is my extension configuration:
@sink(type = 'elasticsearch', hostname = "localhost", port = "9200", index.name = "test-retry-2", backoff.policy.retry.no = "1000", backoff.policy.wait.time = "3", backoff.policy = "constantBackoff", backoff.policy.retry.no = "1000", backoff.policy.wait.time = "3", on.error = "WAIT", @map(type = 'json', @payload("""{ "process_event data":{ "indexName":{{indexName}}, "envId":{{envId}}, "lob":{{lob}}, "status":{{status}}, "totalEnvelopeReceived":{{totalEnvelopeReceived}}, "traceId":{{traceId}} } }"""))) --@OnError(action = "STREAM") define stream TestESStream (indexName string, envId string, lob string, status string, totalEnvelopeReceived int, traceId string);
I using v3.0.2
Suggested Labels:
elasticsearch,sink

Suggested Assignees:

Affected Product Version:
v3.0.2
OS, DB, other environment details and versions:

Steps to reproduce:

  1. Create a scheduler in 5 seconds to read data from MSSQL
  2. Each message from database is pushed to simple stream TestESStream
  3. Shutdown Elasticsearch in 2 minutes
  4. Start Elasticsearch
  5. What i see in the log file are as bellow
    ERROR {io.siddhi.core.stream.output.sink.Sink} - Error on 'TestESStream_Report'. Dropping event at Sink 'elasticsearch' at 'TestESStream' as on.error='wait' does not handle 'java.net.ConnectException' error: 'null', events dropped

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions