Skip to content

How to use iproto.advertise.client (how to connect to an instance) #4292

Open
@Totktonada

Description

@Totktonada

Related dev. issue(s): N/A

Product: Tarantool
Since: 3.0.0
Audience/target: application and external components developers
Root document: https://www.tarantool.io/en/doc/latest/reference/configuration/configuration_reference/#configuration-reference-iproto-advertise-client
SME: @ Totktonada

Details

There is the iproto.advertise.client option, which holds an URI for external clients, which tells them how to connect to the given tarantool instance (config schema, brief description, website documentation).

However, there is no formal agreement how an external client should connect to tarantool. Some clients may use only iproto.advertise.client, some may fallback to iproto.listen. Some may fallback only if iproto.advertise.client is not set, but some may fallback if it is set, but inaccessible.

This documentation request aims to hold an agreement between a writer of server's configuration and a developer of a logic on the external client.

The agreement is the following.

  1. If iproto.advertise.client is set, it is used to connect. No attempts are performed for other URIs (including iproto.listen, iproto.advertise.{peer,sharding}).

  2. If (and only if) iproto.advertise.client is unset, iproto.listen URIs are tried.

    Note 1: It is unspecified, in which order the iproto.listen URIs are tried.

    Note 2: A client may filter out iproto.listen URIs without an attempt to connect if it is known that it is impossible to connect (for example, if the URI has a zero port) -- it is considered as an optimization and shouldn't affect the overall behavior.

Definition of done

  • TBD
  • TBD

Planning checklist

  • Pick product label: server.
  • Pick type label:
  • Estimate complexity in storypoints in the title
  • Add to Documentation board → Backlog

Metadata

Metadata

Assignees

No one assigned

    Labels

    server[area] Task relates to Tarantool's server (core) functionality

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions