...
Excerpt |
---|
|
Recording of Call:
...
20220802 Indy Contributors Call Recording.mp4
Chat text:
- 08:24:25 From Lynn Bendixsen : time stamp on your node is fine?
- 08:24:41 From Christian Bormann : seems to be working for the 1.12.4 one
- 08:29:26 From Wade Barnes : Suspicion codes in troubleshooting; https://github.com/hyperledger/indy-node/blob/master/docs/source/troubleshooting.md
- 08:46:26 From Philipp Schlarb : @christian could you send me the link to the repo for the load generator?
- 08:53:59 From Christian Bormann : https://github.com/hyperledger/indy-did-method/issues/66
Hyperledger is committed to creating a safe and welcoming community for all. For more information please visit the Hyperledger Code of Conduct. |
---|
...
Lynn Bendixsen(Indicio) <lynn@indicio.tech>
Christian Bormann (Robert Bosch GmbH) <christiancarl.bormann@de.bosch.com>
Related Calls and Announcements
...
- Progress on completing the Ubuntu upgrade.
- Hyperledger RCs for Node and Plenum are available
- Progress made with the Sovrin build – getting the tests to run (had been failing)
- Working now on publishing artifacts
- The "Mixed Node" issue – latest updates.Indy Quarterly Report.
- Local testing looks good – mixed network, upgrades
- Testing on IDUnion Test Net - not so good
- Adding a 20.04 node seems to start fine and complete catch-up, but does not join the consensus
- Can go back to 16.04 and everything is fine, so no damage to the network
- Problem may be specific to the network – looking for another network instance to check for this
- Seems to be the issue seen previously – on the same network
- Working at trying to reproduce the issue
- In the process – Christian Bormannhas created a indy-node load generator that writes many DIDs and Schema objects
- Request from Stephen Curran– add some reads to the mix, ideally with a way to define the ratio of reads to writes to simulate a range of issuers (write-heavy) and verifiers (read-heavy)
Upgrade Notes
- Upgrading Indy to Ubuntu 20.04 Presentation
- Summary of the work done ^^
- Update on CI/CD Update and Ubuntu Upgrade
- Indy Shared GHA Repo
- Indy-Plenum:
- Indy-Node:
- indy-test-automation:
- indy-node-container:
- Call time changed – 17:00 CET / 8:00 Pacific on Thursdays.
- Indy-SDK build progress
- Issue: Mixed OS versions of Indy Node have issues:
- Issue: - running mixed nodes 16.04 and 20.04 a consensus problem occurs "in a while" (sometimes immediately, sometimes a few days has been seen)
- 2022.06.21
- Two efforts trying to replicate the problem Christian Bormann (rust script to generate load) and Gavin Bendixsen (PR to indy_node_container), working on adding a node
- At this point, the issue has not been replicated.
- There is an indy node load generator - https://github.com/hyperledger/indy-node/tree/master/scripts/performance
- Another plan of attack: Use old artifact to try to recreate, try again with RC and see if that replicates the issue.
- Note from Lynn: He has seen and documented consensus issues in the past – maybe this has nothing to do with 20.04.
- For example: 2 nodes went down seemingly together, restarted them and issue resolved.
- 2022.06.07
- Indicio team is working on a docker environment to replicate this, they are expecting to have something running in a few days.
- docker-compose, 4 nodes (3 16.04 and 1 20.04), running for a week, but not able to replicate the issue.
- Lynn to share how to do this publicly so that others could contribute.
- Put a folder into the indy-node-container repo about how to do it.
- Plan is to use indy-vdr to generate DIDs and publish them to the ledger.
- 2022.06.21
- Issue: - running mixed nodes 16.04 and 20.04 a consensus problem occurs "in a while" (sometimes immediately, sometimes a few days has been seen)
- Related work - Sovrin token-plugin repo being reworked to match indy-node/plenum.
- Mostly done the code.
- Working on the pipeline
- Linting issues documented and being cleaned
...