Currently I have 4 node A, B, C and D with connect to each other in the same Corda Network.
If I want to remove node D from the network, What is the recommended way to do it?
Because now if I stop node D the other node will show that it can't connect to node D.
I'm not sure what network you are using but if..
In network bootstrapper you can update each node's network parameter file in corda folder.
Testnet I think r3 will not update network map service for you.
UAT/Prod net you have to contact r3 for remove unused node, so they'll update network map service and your node will got the new network parameter list.
And make sure that you already change command signer and participant of state that relate to node D because it'll not be able to make transaction again if node D removed.
Hope that help
Related
We are using Corda open source and would like to set up the communication between two nodes via the internet.
We have tried a public p2pAddress in node.conf with port 80 which did not work. Similarly, using another p2pPort like 10002 is also not working.
Here is an extract of our node.conf template:
detectPublicIp=false
devMode=true
messagingServerAddress="0.0.0.0:10002"
messagingServerExternal=false
myLegalName="${MY_LEGAL_NAME}"
p2pAddress="corda.mylegalname.company.com:10002"
Does anyone know how to solve this issue? The main question is: How can two nodes communicate in the Corda Network via public host names?
Thank you.
Alex
Are the two nodes registered to a Corda network? Nodes need to fetch the addresses of the other nodes from the Network Map first, otherwise they are not able to find them.
We need to change our Corda Network infrastructure. Currently we are working with one network map, three notaries (RAFT) and four additional nodes.
We will replace our network map and one notary server (notaryCluster one) with new servers.
Our plan is to perform following steps:
1. Stop all Nodes
2. Change all node.conf files needed to point to new networkmap and new notary
3. Deploy Networkmap and Notary service in new servers from scratch (not reusing data from old notary and network map)
4. Start new network map, start new notary servers, and rest of nodes (not old network and notary)
Is this process correct to ensure existing transactions will remain in the systems and will be able to work with them?
Thanks!!
There are several things you need to consider
- Stop all Nodes
You need to consider any flows that are currently in-flight to perform a clean shutdown of the node.
Version 3.1 of Corda adds a "Draining mode" feature, through which:
Commands requiring to start new flows through RPC will be rejected.
Scheduled flows due will be ignored.
Initial P2P session messages will not be processed, meaning peers will not be able to initiate new flows involving the node.
- Deploy Network map and Notary service in new servers from scratch (not reusing data from old notary and network map)
You would want to keep data from the old notary, else the notary would lose track of states that have been consumed, and the network would lose the guarantee of preventing double spends
In my scenario, Transaction is between two nodes in two different Machines. Currently am using a controller in Machine A which acts as a notary as well. Can i use two controllers one in each machine?
As discussed here: Corda Controller Node, Corda has no concept of a "controller" node.
Up until Corda 2, each network had a single network map node, no matter how many machines were involved. Each node's configuration file would point to this network map node, using its IP address and port number.
In Corda 3, the network map node was replaced with a server distributing network map files. Details about how to deploy a network across machines in Corda 3 can be found here: https://docs.corda.net/tutorial-cordapp.html#running-nodes-across-machines.
yes, you can setup your case. NotaryChangeFlow (initiating), which should be used to change a state’s notary.
I have 2 VM's with 2 different ip address and I have install the Cassandra (version 2.0.14) in each.
I have mentioned the Node A as seed node (192.168.93.3) and try to add the Node B in the existing cluster. But i can see the below mentioned Error in while try to start the cassandra in Node B.
org.apache.cassandra.exceptions.ConfigurationException:
Unable to bind to address /192.168.93.3:7000.
Set listen_address in cassandra.yaml to an interface you can bind to.
After change the list_address to localhost, rpc : 0.0.0.0 , endpointSnitch : RackInferringSnitch. I am able to start cassandra services in node B and it was included into the node A cluster.
I'm totally new to openstack and after seeing tutorials running it on both single node and multi node(at least 3 consisting 1 controller 1 compute and 1 network node) i was wondering whats the diffrence and is there any advantages with multi nodes over single nodes ones?
Open stack system consists of lot services. If you are running all these in single node , then
there will be resource scarcity issue unless you have a machine with very high CPU,RAM etc. Another advantage of multi node configuration is failover. In 3 node config if one node is down then you can continue with 2 nodes (provided you have service replication). Better go for at least 3 node config which is recommended by openstack.
With Multinode configuration, you can achieve scale-out storage solution by adding more storage needs to your needs. Also, several compute nodes can be used to increase computation needs.