if the connection from proxy to broker is down, it will cause many client connections to be closed

Open
#675 4 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
5/5
Estimated time
Over a week
Newbie friendliness
30/100
Issue type
Feature
Clarity
Needs clarification
Activity status
Stale
Tech stack
java
Domain
backend, distributed-systems

Research direction

Start by tracing how the proxy shares its broker connection and how failures propagate to device client connections. Determine whether the intended behavior is to preserve the shared connection or keep device clients open, then define failure-handling tests for the one-connection, many-device case; the issue names no files or tests.

Written by the indexing model from the issue text.

Description

Is your enhancement request related to a problem? Please describe.
If one thousand devices are connected to the proxy node, and the connection pool size from proxy to broker is one. that means one thousand devices share one connection. if the connection from proxy to broker is closed due to some exceptions, it will cause 1000 devices to go offline at the same time. This may not be what the user expects to see.

Describe the solution you'd like

  1. If an exception occurs from the proxy to the broker, we may not close the shared connection, or do not close the device client connection.
Dominant language
Java
Stars
190
Forks
56
Avg merge
27m
Merged PRs (30d)
1

Contributor guide

No contributing guide indexed for this repository

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.

More from streamnative/mop

All issues in streamnative/mop

Similar issues

More Java issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.