Skip to content

cluster discovery: don't discard the entire result when there are bad addresses #195

Closed
@Totktonada

Description

@Totktonada

We discussed whether we need to discard the entire result of just an address when some of addresses don't pass a validation in the scope of MeshConnection in tarantool-python (PR). (Under the word 'validation' I mean whether an address is a string that matches .+:\d+ and the port is not zero, nothing about corresponding instance availability.) We decided to warn about bad addresses and apply correct ones. I hope cluster clients in different languages should have similar behaviour where possible, so propose to bahve in this way in tarantool-java too.

To be honest I don't think this is important thing, but consistency between connectors is important.

Metadata

Metadata

Assignees

No one assigned

    Labels

    featureA new functionality

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions