Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Get rid of cluster full mesh #3984

Open
Gerold103 opened this issue Feb 13, 2019 · 0 comments
Open

Get rid of cluster full mesh #3984

Gerold103 opened this issue Feb 13, 2019 · 0 comments
Labels
blocked Not ready to be implemented feature A new functionality replication vshard Sharding related issues
Milestone

Comments

@Gerold103
Copy link
Collaborator

Get rid of whole cluster full mesh to avoid too big number of sockets. When each instance sees each other even in different replicasets, it will create too many threads and sockets according to current implementation. Now each connection with a master/slave means +1 relay/applier thread, +1 socket. So for a cluster with 100 instances there are 9900 threads and sockets, 99 per each instance. A possible solution is to make the links “weaker”. For example, interconnect instances of different replicasets either via UDP (hi, SWIM), or via temporary TCP connections, which are closed after too long idle time. Relay/applier threads should be removed and possibly merged into WAL thread, or iproto. This is a preparation for sharding integration into the core.

Follows #3983.

@Gerold103 Gerold103 added vshard Sharding related issues blocked Not ready to be implemented labels Feb 13, 2019
@kyukhin kyukhin added this to the wishlist milestone Jul 21, 2021
@kyukhin kyukhin added the feature A new functionality label Jun 24, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
blocked Not ready to be implemented feature A new functionality replication vshard Sharding related issues
Projects
None yet
Development

No branches or pull requests

2 participants