Author Topic: Seed nodes reccomendations  (Read 1720 times)

0 Members and 1 Guest are viewing this topic.

Offline emski

  • Hero Member
  • *****
  • Posts: 1282
    • View Profile
    • http://lnkd.in/nPbhxG
I've been monitoring my seed node for some time.
I was wondering is there some recommendations on settings - specifically max_connections.
I've seen it gets full even with 400 max_connections.
I think it can handle more (though it uses about 1 megabyte per second atm).

So to sum up:
Should I try to increase the max_connections further ?
Should I try to configure anything else?
Should I run another seed node at different location ?

PS: And another question:
Are only seed nodes allowed to distribute blocks?
I deleted all my seed nodes from the config JSON and added manually only my delegate as a peer. The node began receiving connections but it didn't fetch any blocks.

All nodes distribute blocks.
Redundancy is better until crash is fixed... ie: 2 processes with 200 connections is better than 1 with 400.

The initial client has my IP and port hardcoded.
I've setup autorestart and monitoring of the seed node so crash doesn't affect it that much.
Even if I run 2 instances with 200 users wouldn't this be worse than 1 instance with 400 due to duplicate connections (a peer connected to both instances taking up 2 slots instead of 1)

PS: Should a client disconnect from seed nodes after acquiring enough connections?

Offline bytemaster

I've been monitoring my seed node for some time.
I was wondering is there some recommendations on settings - specifically max_connections.
I've seen it gets full even with 400 max_connections.
I think it can handle more (though it uses about 1 megabyte per second atm).

So to sum up:
Should I try to increase the max_connections further ?
Should I try to configure anything else?
Should I run another seed node at different location ?

PS: And another question:
Are only seed nodes allowed to distribute blocks?
I deleted all my seed nodes from the config JSON and added manually only my delegate as a peer. The node began receiving connections but it didn't fetch any blocks.

All nodes distribute blocks.
Redundancy is better until crash is fixed... ie: 2 processes with 200 connections is better than 1 with 400. 
For the latest updates checkout my blog: http://bytemaster.bitshares.org
Anything said on these forums does not constitute an intent to create a legal obligation or contract between myself and anyone else.   These are merely my opinions and I reserve the right to change them at any time.

Offline emski

  • Hero Member
  • *****
  • Posts: 1282
    • View Profile
    • http://lnkd.in/nPbhxG
I've been monitoring my seed node for some time.
I was wondering is there some recommendations on settings - specifically max_connections.
I've seen it gets full even with 400 max_connections.
I think it can handle more (though it uses about 1 megabyte per second atm).

So to sum up:
Should I try to increase the max_connections further ?
Should I try to configure anything else?
Should I run another seed node at different location ?

PS: And another question:
Are only seed nodes allowed to distribute blocks?
I deleted all my seed nodes from the config JSON and added manually only my delegate as a peer. The node began receiving connections but it didn't fetch any blocks.