Coder Social home page Coder Social logo

Comments (8)

mversic avatar mversic commented on September 26, 2024 1

there is a bug, I'm working on it

from iroha-2-docs.

mversic avatar mversic commented on September 26, 2024 1

the fix will be merged today. The changes include:

  1. It's not necessary to specify "self"(current) peer in TRUSTED_PEERS anymore
  2. when bootstraping network TRUSTED_PEERS must contain genesis peer. It can also contain other peers but it's not necessary
  3. when adding a peer to an already running network. TRUSTED_PEERS must contain at least one live/active peer. It can contain additional peers but it's not necessary

from iroha-2-docs.

mversic avatar mversic commented on September 26, 2024

seems that atm, whatever you used as the TRUSTED_PEERS when starting the network is what you should use on your new peer

from iroha-2-docs.

matisalimbene avatar matisalimbene commented on September 26, 2024

@mversic It seems to work that way. But for instance, after I register the new peer, If I query the peer count using http://localhost:8081/status/peers I get odd results:

http://localhost:8080/status/peers returns 4
http://localhost:8081/status/peers returns 4
http://localhost:8082/status/peers returns 4
http://localhost:8083/status/peers returns 3
http://localhost:8084/status/peers returns 3

They should return 5 right? the initial 4, plus the one I'm registering.

from iroha-2-docs.

mversic avatar mversic commented on September 26, 2024

they should all return 4. status/peers returns the number of connected peers excluding the reporting peer

from iroha-2-docs.

matisalimbene avatar matisalimbene commented on September 26, 2024

@mversic Thanks Marin. This is on the iroha-stable branch, correct? That's the branch I'd need to rebuild to have these fixes appled.

from iroha-2-docs.

mversic avatar mversic commented on September 26, 2024

The fix hasn't been merged yet

from iroha-2-docs.

mversic avatar mversic commented on September 26, 2024

@mversic Thanks Marin. This is on the iroha-stable branch, correct? That's the branch I'd need to rebuild to have these fixes appled.

the fix was merged. Yes you can use iroha2-stable branch or pull the latest iroha2-stable docker image

from iroha-2-docs.

Related Issues (20)

Recommend Projects

  • React photo React

    A declarative, efficient, and flexible JavaScript library for building user interfaces.

  • Vue.js photo Vue.js

    🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.

  • Typescript photo Typescript

    TypeScript is a superset of JavaScript that compiles to clean JavaScript output.

  • TensorFlow photo TensorFlow

    An Open Source Machine Learning Framework for Everyone

  • Django photo Django

    The Web framework for perfectionists with deadlines.

  • D3 photo D3

    Bring data to life with SVG, Canvas and HTML. 📊📈🎉

Recommend Topics

  • javascript

    JavaScript (JS) is a lightweight interpreted programming language with first-class functions.

  • web

    Some thing interesting about web. New door for the world.

  • server

    A server is a program made to process requests and deliver data to clients.

  • Machine learning

    Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.

  • Game

    Some thing interesting about game, make everyone happy.

Recommend Org

  • Facebook photo Facebook

    We are working to build community through open source technology. NB: members must have two-factor auth.

  • Microsoft photo Microsoft

    Open source projects and samples from Microsoft.

  • Google photo Google

    Google ❤️ Open Source for everyone.

  • D3 photo D3

    Data-Driven Documents codes.