v2.0.0a1
There were many changes between 1.3 and 2.0 Alpha, too many to list here. We wrote a series of blog posts to summarize most changes, especially those that affect end users and application developers:
- BigchainDB 2.0 is Byzantine Fault Tolerant
- Some HTTP API Changes in the Next Release
- Three Transaction Model Changes in the Next Release
- Changes to the Server Command Line Interface in BigchainDB 2.0
- A forthcoming post about changes in BigchainDB Server configuration settings
External Contributors
- @r7vme contributed pull request #1984 which fixed a bug in our Kubernetes-based production deployment template.
Known Issues
We intend to resolve these issues before releasing the final BigchainDB 2.0:
- There's a known Heisenbug that (sometimes) arises and we found that making the BigchainDB webserver single-threaded prevents that bug from causing problems. We intend to resolve that bug, but in the meantime our temporary workaround is to change the default webserver configuration settings to single-threaded mode, i.e.
BIGCHAINDB_SERVER_WORKERS=1andBIGCHAINDB_SERVER_THREADS=1. - Issues sometimes happen when a large transaction is sent to a BigchainDB network.