search

tmobile / sawtooth-next-directory

Home for NEXT Directory - Powered by Hyperledger Sawtooth. Chat with the team at https://chat.hyperledger.org/channel/sawtooth-next-directory/
Apache License 2.0
11 stars 7 forks source link

Ledger-sync does not reconnect to sawtooth #691

Open jbobo opened 5 years ago

jbobo commented 5 years ago
Bug Ledger-sync does not reconnect to sawtooth
Expected behavior All components should gracefully attempt to reconnect with networked services on connection failure
Actual behavior if Sawtooth comes down or becomes disconnected from ledger-sync the microservice stalls rather than polling sawtooth until it can open a new changefeed connection.
Repro steps Take sawtooth offline while monitoring ledger-sync logs and then reconnect sawtooth.
Build Recorded on commit 39555bd81c9a6c84a91a18c5744af21e11359498, has been present for longer
Severity _1. crash/unable to recover. Requires a full reset of ledger-sync microservice
Details/Notes Bright side is that on reset ledger-sync will push all of the missed transactions to RethinkDB, the biggest impact is that while ledger-sync is down RethinkDB is not begin updated. Because RethinkDB is used for transaction auth (through business logic), and fails silently, a window of opportunity is created for users to create duplicate, or illegal transactions (if transactions that would create blocking logic have yet to be pushed to RethinkDB)