Skip to content

When a connection fails, the Pulsar client should return a detailed exception instead of a generic "connection error." #1315

Description

@tinswzy

Expected behavior

When the Pulsar client connection fails, we hope to receive a more detailed and specific error message, such as:

WARN[0009] Failed to connect to broker. error="dial tcp [::1]:6650: connect: connection refused" remote_addr="pulsar://localhost:6650"

Actual behavior

pulsar go client return a a generic and unclear message when connection failed, like this:

connection error

Steps to reproduce

Connecting to an abnormal or non-started Pulsar.

System configuration

Pulsar version: master & latest release

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Fields

    No fields configured for issues without a type.

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions