search

ambrosus / issues

1 stars 0 forks source link

NOP Parity: Increased memory used on nodes since Parity 2.7.1 / 2.7.2 causing node lockups or restart #54

Open Jerome2506 opened 4 years ago

Jerome2506 commented 4 years ago

Since parity 2.7.1/2.7.2 the memory consumption of the nodes has been very high. Sometimes it reached the 2GB limit, locks up, stops syncing and/or and causes the node to restart. Its just not as stable as parity 2.5.13 was before. After digging around it seems that the openethereum team recognises the issue. After months of trying to solve it on 2.7+ branches it they couldn't get it to work.

Apparently they decided to go back to 2.5.13 (backport) and only include bug fixes and hardforks since that version to get it stable again. Release should come out in the second week of September if everything goes to plan. See https://github.com/openethereum/openethereum/issues/11858

Not sure if the team is are aware but could I would say this would be great if that could be taken up mid september in order to get the nodes stable again.

Jerome2506 commented 4 years ago

https://medium.com/openethereum/vision-for-openethereum-ex-parity-client-eb7b11f6eef8

Jerome2506 commented 3 years ago

@Primaveralina good news openethereum has released 3.1 version officially. It would be great if this could be taken up hopefully reducing the number of node crashes and instability.

https://github.com/openethereum/openethereum/releases/tag/v3.1.0

Jerome2506 commented 3 years ago

https://github.com/openethereum/openethereum/releases/tag/v3.1.1 3.1.1 released

Jerome2506 commented 3 years ago

https://github.com/openethereum/openethereum/releases/tag/v3.2.0 3.2.0 released

chamber144 commented 2 years ago

@Jerome2506 Thanks for bringing this up.

As mentioned in my community forum post increasing the available RAM seems to 'solve' it. But this means that the minimum system requirements (2GB ram) are too low. Despite of not being a very clean solution. About 30% of random Atlas nodes monitored by me having frequent downtimes. Guess this isn't ideal too.

Any developers reading this? Any intention of updating to a newer parity version?

Or shall we increase the minimum system requirements in amb.wiki instead? (This would also include adapting the community installation guides.)