Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

http_server: Not receiving Websocket messages #2997

Open
erikuusitalo opened this issue Nov 12, 2024 · 1 comment
Open

http_server: Not receiving Websocket messages #2997

erikuusitalo opened this issue Nov 12, 2024 · 1 comment
Labels
needs more info An issue that may be a bug or useful feature, but requires more information outputs Any tasks or issues relating specifically to outputs

Comments

@erikuusitalo
Copy link

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.

@mihaitodor
Copy link
Collaborator

Hey @erikuusitalo 👋 Thanks for reporting this issue! I think we'd need more information on how to reproduce this, since it depends on how the websocket client which connects to the http_server you configured behaves. Are you able to share a full self-contained setup that we can run to observe the issue?

@mihaitodor mihaitodor added outputs Any tasks or issues relating specifically to outputs needs more info An issue that may be a bug or useful feature, but requires more information labels Nov 19, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
needs more info An issue that may be a bug or useful feature, but requires more information outputs Any tasks or issues relating specifically to outputs
Projects
None yet
Development

No branches or pull requests

2 participants