镜像站点 · 本页由第三方 GitHub 只读镜像提供,非 GitHub 官方站点,不接受任何登录或凭据输入。前往 github.com
Skip to content

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

Open

Description

@hujie6

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.

Activity

  1. Technoboy- commented on Jun 21, 2022

    @Technoboy-
    Contributor

    In this case, you'd better set the pool size more than 1.

  2. hujie6 commented on Jun 21, 2022

    @hujie6
    ContributorAuthor

    In this case, you'd better set the pool size more than 1.

    Yes, in a production environment, the pool size must be greater than 1. but one of the connections is closed,it will also cause a large number of devices disconenction or connection.

  3. mattisonchao commented on Jun 24, 2022

    @mattisonchao
    Member

    Hi, @hujie6
    That is a great idea, but we should consider how to process continuous publishing messages. (In some high-rate conditions).

  4. Technoboy- commented on Jun 28, 2022

    @Technoboy-
    Contributor

    In this case, you'd better set the pool size more than 1.

    Yes, in a production environment, the pool size must be greater than 1. but one of the connections is closed,it will also cause a large number of devices disconenction or connection.

    yes, right, but reconnection will not have much impact on the business in the MQTT scenario.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

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