redpanda-data / redpanda-data/benthos

http_server: Not receiving Websocket messages

Open
#124 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

http needs investigation
Dominant language
Go
Stars
571
Forks
120
Avg merge
2d 1h
Merged PRs (30d)
18

Description

When initially connecting, everything works as expected. However, upon reconnection, message handling becomes inconsistent. Sometimes messages are delivered, but this is very random, and often the reconnection fails entirely.

In some cases, the following warning appears in the logs:

WARN Failed to send message: write tcp 172.25.0.8:4195->172.25.0.1:57554: write: broken pipe  @service=redpanda-connect label="" path=root.output

image

Running config:

logger:
  level: ALL
  format: logfmt
  add_timestamp: false
  static_fields:
    '@service': redpanda-connect
input:
  kafka:
    addresses: ["redpanda:9092"] # No default (required)
    topics: ["TEST"] # No default (required)
    target_version: 2.1.0 # No default (optional)
    consumer_group: "test"
    checkpoint_limit: 1024
    auto_replay_nacks: true
buffer:
  none: {}
pipeline:
  threads: -1
  processors: []
output:
  broker:
    pattern: fan_out
    outputs:
    - stdout: {}
    # - kafka:
    #     addresses: ["redpanda:9092"] # No default (required)
    #     topic: "OUTPUT" # No default (required)
    - http_server:
        ws_path: /get/ws
        allowed_verbs:
          - GET

Any guidance or suggestions on how to resolve this issue would be greatly appreciated.

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start by reproducing the reconnection behavior with the provided http_server configuration, focusing on websocket message handling and the broken-pipe warning. Determine why reconnections fail or stop delivering messages, then verify that repeated reconnects reliably receive messages without the warning.

Written by the indexing model from the issue text.

Assessment

Tech stack
go
Domain
api, backend, networking
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.