Overloaded server with 200 Maria masternodes

[HelmutsHelmuts is verified member.]

this is how a Xeon E3 processor, 4 cores/8 threads and 64gb ram server looks with freshly set up 200 $Maria masternodes that have all started syncing..

once synchronised - the processors will have 15-20% load (now 100%), the ram will stay almost the same and the swap will slowly gain more and more data.

once the swap gets to its maximum > ubuntu will start switching off the processes one by one and the masternodes will start going offline.

--

in situations like these:
a) don't overload the server
b) if you do overload the server > restart it once you start seeing masternodes going offline (this will empty the swap). after that > start all the MNs the usual way = the wallets on the server and once synced, start the mns on your wallet. .. in this case, once a month.

 

[HelmutsHelmuts is verified member.]

and, yes > when you have a whole server >> you do set it up in a different way (you do not create seperate vpss for every mn).. at some point I will create a tutorial on this.

 

[HelmutsHelmuts is verified member.]

[update] the test continues

..the server is still online and kicking!! I love servers with Xeon processors!

.. 8-10 more hours and the processors will start to get easier life as the wallets will finish synchronizing.

Have a great Sunday!
Helmuts

 

[HelmutsHelmuts is verified member.]

restarting a server, as expected.. can't even log in via ssh

that's ok, used to this with overloaded masternode servers that have been just set up.

step 1 > restart
step 2 > start all the wallets 1 by 1
step 3 > start all the MNs on the desktop wallets (once the server wallets are synced)

 

[HelmutsHelmuts is verified member.]

ok, all server wallets are synchronized and the related masternodes started.

as you can see, now the cpu load is significantly lower:

---

good experiment.. before I didn't know that there is such a huge cpu load while the wallets are syncing.

The lesson or workaround if you have limited cpu resources >> launch several masternodes at the time, and once synced and started, launch the next batch (not all at once).

 

[HelmutsHelmuts is verified member.]

.. I keep reducing the numbers of mns (the swap keeps building up and this forces me to restart the server and manually start all the mns 1-by-1) > currently at 170 mns on a particular server.. will see how it goes.

The safe number should be 150, though I'm here to run tests

 

[Kutti]

.. I keep reducing the numbers of mns (the swap keeps building up and this forces me to restart the server and manually start all the mns 1-by-1) > currently at 170 mns on a particular server.. will see how it goes.

The safe number should be 150, though I'm here to run tests

Helmuts, does Maria support MultiNode Masternode deployment where we run just one Maria daemon on a server and all nodes share the same blockchain data directory?

Thanks!

 

[HelmutsHelmuts is verified member.]

Helmuts, does Maria support MultiNode Masternode deployment where we run just one Maria daemon on a server and all nodes share the same blockchain data directory?
Thanks!

Good morning Kutti,

Maria does not support MultiNode Masternode deployment in the manner you described, where multiple masternodes share the same blockchain data directory with just one daemon running on a server. Maria requires each masternode to have its own dedicated environment, including its own data directory.

Here's why:

• Masternode Requirements: Maria masternodes inherently require individual Maria daemons for independent operation and collateral locking. Sharing a single daemon would hinder this functionality.
• Blockchain Data: Maintaining data integrity is crucial for blockchain operations. Sharing a single blockchain data directory across multiple nodes could lead to inconsistencies and compromise data security.

Did this help?

Best wishes, Helmuts

 

[Kutti]

Helmuts, does Maria support MultiNode Masternode deployment where we run just one Maria daemon on a server and all nodes share the same blockchain data directory?
Thanks!

Good morning Kutti,

Maria does not support MultiNode Masternode deployment in the manner you described, where multiple masternodes share the same blockchain data directory with just one daemon running on a server. Maria requires each masternode to have its own dedicated environment, including its own data directory.

Here's why:

• Masternode Requirements: Maria masternodes inherently require individual Maria daemons for independent operation and collateral locking. Sharing a single daemon would hinder this functionality.
• Blockchain Data: Maintaining data integrity is crucial for blockchain operations. Sharing a single blockchain data directory across multiple nodes could lead to inconsistencies and compromise data security.

Did this help?

Best wishes, Helmuts

Thanks Helmuts!

Your response does help.

Have a nice day.

 

[HelmutsHelmuts is verified member.]

You too Have a nice weekend! H