You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This commit was created on GitHub.com and signed with GitHub’s verified signature.
The key has expired.
Fixed
Fixed a bug that arose with some code that treated transactions-waiting-for-block-inclusion as if they were already stored in MongoDB (i.e. already in a block). Pull request #2318
If a user asked for a block and it happened to be an empty block, BigchainDB returned 404 Not Found, as if the block did not exist. Now it returns a 200 OK with a block containing no transactions, i.e. an empty block. Pull request #2321
Known Issues
An issue was found with the bigchaindb upsert-validator command. A solution was proposed in BEP-19 and is being implemented in pull request #2314
If you run BigchainDB locally using make start (i.e. using Docker Compose) and then you put the node under heavy write load, Tendermint can become unresponsive and running make stop can hang.
There seems to be one or more issues with Tendermint when it is put under heavy load (i.e. even when BigchainDB isn't involved). See Tendermint issues #1394, #1642 and #1661
Notes
There's a new docs page about how to set up a network where each node uses a single virtual machine.
We checked, and BigchainDB 2.0 Beta 1 works with MongoDB 3.6 (and 3.4).