Author Topic: Careful when upgrading delegate to 0.4.25  (Read 8915 times)

0 Members and 1 Guest are viewing this topic.

Offline vikram

« Last Edit: December 12, 2014, 06:44:09 pm by vikram »

Offline abit

  • Committee member
  • Hero Member
  • *
  • Posts: 4667
    • View Profile
    • Abit's Hive Blog
  • BitShares: abit
  • GitHub: abitmore
It seems that a fork occurred before expected (<1249400).
All delegates should upgrade. Other users should upgrade as well. Wish the binary releases asap.
@vikram.
BitShares committee member: abit
BitShares witness: in.abit

Offline svk

I've updated the release notes to include a note about the memory requirement: https://github.com/BitShares/bitshares/releases/tag/v0.4.25

This doesn't appear to be true for reindexing and syncing, I've successfully reindexed and sync my seednode which has 512mb RAM and 4gb swap.

I compiled it on my personal computer which has 8gb of RAM so no issues there.
Worker: dev.bitsharesblocks

Offline ripplexiaoshan

  • Board Moderator
  • Hero Member
  • *****
  • Posts: 2300
    • View Profile
  • BitShares: jademont
I am using 2GB VPS, and it seems fine for both compiling and running, but my delegate keeps missing blocks while the wallet is up,according to bitsharesblocks.com.
BTS committee member:jademont

Offline emski

  • Hero Member
  • *****
  • Posts: 1282
    • View Profile
    • http://lnkd.in/nPbhxG
0.4.24 instances report a lot of duplicate transactions when blockchain_use_forks is used. Is it the same with you ?

Offline svk

Our delegate is running fine, but it is consuming a lot of virtual memory (2.3GB, but doesn't seem to be increasing) during initial sync. My best guess is that the people with problems are swapping due to insufficient memory. We already suspected a leak in the previous client during syncing (last client required 1.6GB on windows for initial sync).

Are the forking issues related to the new fork resolution code? Maybe the fact that the old and the new are live at the same time?
Worker: dev.bitsharesblocks

Offline abit

  • Committee member
  • Hero Member
  • *
  • Posts: 4667
    • View Profile
    • Abit's Hive Blog
  • BitShares: abit
  • GitHub: abitmore
« Last Edit: December 12, 2014, 09:02:06 am by abit »
BitShares committee member: abit
BitShares witness: in.abit

Offline btswildpig

  • Hero Member
  • *****
  • Posts: 1424
    • View Profile
I've updated the release notes to include a note about the memory requirement: https://github.com/BitShares/bitshares/releases/tag/v0.4.25

will delete the blockchain before upgrade helps ?
这个是私人账号,表达的一切言论均不代表任何团队和任何人。This is my personal account , anything I said with this account will be my opinion alone and has nothing to do with any group.

Offline vikram

I've updated the release notes to include a note about the memory requirement: https://github.com/BitShares/bitshares/releases/tag/v0.4.25

Offline Riverhead

yep, I think 3 to 4GB is a good minimum requirement for now for delegates, until we can isolate the cause of the heavier memory requirements.
Agreed. Going to upgrade.

Offline dannotestein

  • Hero Member
  • *****
  • Posts: 760
    • View Profile
    • BlockTrades International
  • BitShares: btsnow
yep, I think 3 to 4GB is a good minimum requirement for now for delegates, until we can isolate the cause of the heavier memory requirements.
http://blocktrades.us Fast/Safe/High-Liquidity Crypto Coin Converter

Xeldal

  • Guest
My 1GB instance is continually crashing while syncing, Initially this crashed and (appeared to be) locked up.  I had to restart

My 4GB instance hasn't crashed at all.

Offline Riverhead

It's possible the box may have come back. The delegate I had running on that box started missing blocks because nothing else could be processed.

I have it syncing on another box now and once it's all up to date I'll turn that on as the block signer and update my version number.


Offline dannotestein

  • Hero Member
  • *****
  • Posts: 760
    • View Profile
    • BlockTrades International
  • BitShares: btsnow
Our delegate is running fine, but it is consuming a lot of virtual memory (2.3GB, but doesn't seem to be increasing) during initial sync. My best guess is that the people with problems are swapping due to insufficient memory. We already suspected a leak in the previous client during syncing (last client required 1.6GB on windows for initial sync).
http://blocktrades.us Fast/Safe/High-Liquidity Crypto Coin Converter

Offline Riverhead