Heatserver 0.9.29 released.

Please update your servers. Mandatory update!

Heatledger 0.9.29 - The HEAT is on!

Heatledger 0.9.29

This is a mandatory update, all nodes on older versions must update.

While on [testnet](https://github.com/Heat-Ledger-Ltd/heatledger-test) 8 other releases have come and gone please refer to testnet repo for details on those.

This release fixes most if not all of the forking issues we experienced before plus it enables the new realtime websocket connectors already integrated in both the web and desktop clients.

Forging rewards stay disabled. When this release proves to be stable we will put out another release which will enable forging rewards. This is to be expected by Friday 7'th of April.

https://github.com/Heat-Ledger-Ltd/heatledger/releases/tag/v0.9.29

I just updated to this new version on my VPS but can't run it.  I am re-downloading the blockchain but the initial startup doesn't have enough room to create the DB files.  I did the same thing on another server but didn't have any problems.  I looked at the blockchain directory and saw that it is using 84 GB of space.  Why is it using that much space?  I was running a server on a VPS but I can't if that is going to be the space requirement.

Are you sure it takes up 84 GB on your machine? It should take up only 4.75 GB currently (and most of that are empty blocks + space reserved for unconfirmed so you can actually pack the blockchain to under few dozen MB in case you need to transfer it).

It's a bit nasty so much ~5GB needs to be reserved despite the very small small size of actual blocks, but I've never heard it would take up anywhere near 84 GB. Must be a race condition / loop jam if you can confirm that's the case. What files are there and what are their sizes?

I double checked and then I deleted the blockchain and restarted the server just to make sure.

These are screen shots from WinSCP of my server.  Ubuntu 16.04 64 bit  (even though username is "pi")

Screen shot halfway through the memory mapping
http://imgur.com/a/JwSZc

Screen shot after memory mapping complete (notice 85 GB for total listed at bottom)
http://imgur.com/a/sgKuB

Screen shot of SSH session to show timestamp differences when creating files.  This is an average speed HDD.  Accounts and Accounts-assets took nearly 1 minute to map.
http://imgur.com/a/lFvNP

Can you confirm you are using the very latest version from https://github.com/Heat-Ledger-Ltd/heatledger/releases/tag/v0.9.29. Even if you do think you are could you please try and install again plus delete and redownload the blockchain from scratch.

The behavior you are seeing is to be expected if the "trimming" functionality would be behaving badly. The trimming involves the removal of rollback data which advances by 1 block and always acts on the last block from 720 blocks in the past.

I have inspected our own servers and am not seeing the behavior you are experiencing we also have some Ubuntu 16.04 64 bit servers like you do.

Thank you for reporting and please let us know what the outcome is of a reinstall.

Can you confirm you are using the very latest version from https://github.com/Heat-Ledger-Ltd/heatledger/releases/tag/v0.9.29. Even if you do think you are could you please try and install again plus delete and redownload the blockchain from scratch.

The behavior you are seeing is to be expected if the "trimming" functionality would be behaving badly. The trimming involves the removal of rollback data which advances by 1 block and always acts on the last block from 720 blocks in the past.

I have inspected our own servers and am not seeing the behavior you are experiencing we also have some Ubuntu 16.04 64 bit servers like you do.

Thank you for reporting and please let us know what the outcome is of a reinstall.

I deleted everything, except my own config file.  I copied everything over and restarted server.  Same thing....  Then I looked at my config file.  I had added my own maxRollback set at some high value.  After commenting this out, it fixed the problem.

I was playing with this config setting because I needed to for FIMK.  This setting in HEAT has a much larger impact on file size than it did in FIMK.

My bad....   

That would totally explain the behavior. Thanks for explaining and trying it out.
I'll be removing that config option since it doesnt really make sense in the current HEAT architecture.

Thanks for reporting!