Why support for seed_mode was removed from the Tendermint? #1343
-
|
In very earlier version we used to have the support for Seed Mode where the new node can ping the seed node and send the peers to it.It seems to me the more efficient method. Is there any shortcoming of this way? |
Beta Was this translation helpful? Give feedback.
Replies: 1 comment 5 replies
-
|
Not sure what you mean by "seed_mode was removed". There is |
Beta Was this translation helpful? Give feedback.
-
|
Thanks |
Beta Was this translation helpful? Give feedback.
-
|
Not sure if I understood your question. |
Beta Was this translation helpful? Give feedback.
-
|
Let me describe you a scenario- |
Beta Was this translation helpful? Give feedback.
-
|
Ok, I will assume you are referring to the However, it is worth noticing that connections to a seed node are short term connections. Namely, a node dials the seed node in order to request a list of peer addresses. When the seed node receives this request, it replies back to the requesting node and closes the associated connection. As a result, once replying to a request, the seed node should be able to accept a new inbound connection to handle a new request. This means that, while the |
Beta Was this translation helpful? Give feedback.
-
|
Thanks a lot @cason |
Beta Was this translation helpful? Give feedback.
Not sure what you mean by "seed_mode was removed".
There is
seed_modeflag in the configuration flag, which enables configuring a node to operate in seed mode: https://github.com/cometbft/cometbft/blob/main/config/config.go#L562